Hello @jimp - I am all set now. I reinstalled everything. working now. thxx

Actually, I figured it out! But, thanks for your help! I was configuring my new pfSense box offline, and there is a known bug in 2.4.5 where there can be 30-90 second delays when offline. This has since been patched and corrected in 2.4.5-p1 Again, thanks to everyone for their help. I REALLY appreciate it! -Rob

It's been fixed in the repo, current snapshots should be OK

Or do the portforward trick along with the DHCP handing out pihole as DNS https://docs.netgate.com/pfsense/en/latest/dns/redirecting-all-dns-requests-to-pfsense.html Just substitute 127.0.0.1 with the pihole ip Something like this [image: 1592337241428-selection_2020061621-52-59.png]

https://redmine.pfsense.org/issues/10667

@watts3000 - I set this up recently and now trying to remember the steps. I believe I had IP Passthrough still enabled but but set to manual. Then entered static IP and gateway on pfSense side and was able to connect.

Hello there. I had the same problem, accessing my router behind PfSense. Internal lan is 192.168.0.x Pfsense on 192.168.0.254 Router is 192.168.1.254 There was no way to access it. Then i checked my network card IPs. I had 2 assigned. 192.168.0.22 and 192.168.1.22 Removed 192.168.1.22 amd then BANG! router interface is reachable. Is really THAT simple as other people wrote. NO need to mess up anything. Hope this helps someone. Have a nice day, Mario

Should be similar to https://forum.netgate.com/topic/144492/best-practice-moving-xg-7100-config-to-sg-5100 -Rico

John, I tryed it. I did create an USB having a conf directory and containing two files (to be sure) config.xml config-pfSense.lan-20200615125949.xml Whats ever it was not recognised / not used Perhaps because the usb had been used as gpt device before. What-ever. It did not work So I did it the complicated way (using a very long UTP-cable) Louis

@noplan alles klar. Dann fuchs ich mich mal durch die ganzen Einstellungen durch :) Bis jetzt gefällt es mir super! Danke für deine Unterstützung.

bla bla bla are you really trying to bully me? eh sadly I don't have time for this shit, I'd rather help than stay here to argue

i think i figure it out. i mean i just understand what was the other user "Derelict" trying to explain. thanks "Derelict"

@bmeeks said in kernel: em1: Watchdog timeout -- resetting: Hmm... I would not say everything is working. Those errors point to something being really not right. If it just started up out of the blue, my first suspicion would be hardware. Could even be something as simple as the card needs reseating into the slot to make sure it has a good connection with the bus. There were issues with hardware watchdog timeouts with the generic FreeBSD drivers for Realtek NICs, and in that case compiling and using the Realtek-supplied native drivers corrected the problem. However, Intel NICs have historically been very well behaved in FreeBSD using the kernel drivers. Just asking, but are you 100% positive beyond a shadow of a doubt that you have genuine Intel NIC hardware? There are some cheap Chinese knockoffs of popular Intel NICs out there for sale. If you got a "steal of a deal" on the NIC, I would be suspicious. Hi B. Yeah. 100% sure. Bought them off Intel themselves :) I went to the Interface page and chose autoselect instaed of default and the errors were gone immediately. Weird.

Thanks for the clarification on a few things. It's helped me get my mind round everything better and giving me a clearer idea of what direction I need to go to get everything as I want.

OK. I found it. Under System/Advanced/Admin Access. [I am unable to delete my post. Sorry for the noise.]

Send the logs to a syslog server. Once they're off the FW you're only limited by disk space on the syslog server.

https://www.netgate.com/resources/videos/bandwidth-monitoring-on-pfsense.html -Rico