Just today the printer dropped out again, but I cannot find a reason for it.

I assigned the printer to 192.168.1.120 in pfsense. When I type the ip address I get a printer settings page in the browser so I know I am communicating with the printer. However, when I try to print I get a network error in the print queue.

I'm still using the Netgear R6700v3, but as a wireless access point only. I'll try turning it off and using only the Unifi Lite AP instead.

EDIT:
I since pulled my R6700v3 even as an access point, connected the printer to the Unifi Lite, then removed and reinstalled the printer drivers. Printing is back. I'm pretty sure all my printer issues originated from the R6700v3.

Link above flagged by Malwarebytes for malware.
STAY AWAY. REPORTED.

@gertjan https://forum.netgate.com/topic/160418/site-to-site-vpn-configuration-between-pfsense-and-cisco-asa-5505

I can able to ping asa to pfsense but I can't able to ping pfsense to asa help pls

I solved the problem. After installing the patch, I added Pre Shared Key on the IPsec side and the problem was resolved.

https://forum.netgate.com/topic/154841/l2tp-issue-since-last-update

You can't downgrade in place. But you should be able to upgrade to the 21.02 release from there since it will newer.

Otherwise if you need to be back on 2.4.5p1 now open a ticket with and we'll get straight back to with the recovery image: https://go.netgate.com/

Steve

Thanks, I should have known that! I forgot I was in a browser window.

@chrisathome
Sorted it out. I learned about the CIDR table and the subnet I needed. Set fields. Restarted router. Done!

The external config locator will check attached fat32 devices for a config.xml file and automatically pull it in at boot:
https://docs.netgate.com/pfsense/en/latest/backup/restore-during-install.html#restore-using-the-external-configuration-locator-ecl

But that is only after installing. There is no way to install pfSense entirely headless.

What are you installing onto?

Steve

@lispeedyg 🤷

So you plan to have two connections between the modem and the existing router and you want to put the SG-2100 in one of them?

I thing we might need a diagram here.

Steve

If you have replaced the drive and reinstalled the NDI should have remained the same.

If you open a ticket with us we can get try to find device keys used by that NDI.
https://go.netgate.com/

Steve

Thanks all!

i have an update on my pfsense issue.
after i reinstalled windows on my pc (My Old installation died for some reason... 😢) Pfsense got the correct time, and the graphs are now working!
thank you @johnpoz and for everyone for trying to help me with this issue!

@stephenw10 Ok thanks for the info, I'll know that for future.

just an update I guess.
Have installed PFsense to a PCI riser -64gb Kingston M.2 SSD
Removed the horrible raid card and 160gb SAS disks. it was a heck of a job updating its firmware, but its fairly quiet with BMC and bios update and got rid of ther ebay smell from it.
Seem's to be around 40w being on so its already less then the firebox just being on. this R210 came with a X3430, but ill look at getting a L chip to lower the number abit.
Im pleased I managed to get 24 port WS-2950-24 from work.

Dafoxx

@mcury said in Cannot boot kernel with SMP enabled:

@tomlawesome Oh, SMP, somehow I read SMT in your topic, ehhe, don't know how that happened..
SMT would be Simultaneous multithreading

Easy mistake to make! No harm done, and I learned something in the process!

@kiokoman Thank you it worked.

Service was not started so I started it and then stop it after that I could remove it and then reinstall it

Hi Team discard the above request as I figured out that netgate was stuck in sequence and I went through console port and made factory reset to start from begining.

@bmeeks Great! Thanks for your help...

No not really, in such a setup it would have no internet access even. Most soho router have no way to set a gateway on the lan.

So even if you forwarded traffic to it from the internet, it wouldn't be able to answer back, unless you also had setup a source nat on pfsense.

While sure as any device on your network, pc, iot device, etc. It's on your network and things on your network would be able to talk to it.. But not sure what sort of vulnerability you would be worried about in such a setup.

Correctly secure your wifi, wpa2 with good complex length psk and you should be good to go.