@elduder You might want this: https://github.com/homebridge/homebridge May find valuable info here too: https://forum.netgate.com/topic/154163/can-i-use-ips-to-trigger-a-custom-action

You can not put the wan and lan on the same network.. Sure looks like your going to connect the wan and lan to the same network.

UFS keeps extra space that is not available to regular users so when the filesystem is completely filled for user and non-user data, it shows 108%. : tunefs -p / tunefs: POSIX.1e ACLs: (-a) disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: soft update journaling: (-j) enabled tunefs: gjournal: (-J) disabled tunefs: trim: (-t) disabled tunefs: maximum blocks per file in a cylinder group: (-e) 4096 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: space to hold for metadata blocks: (-k) 6408 tunefs: optimization preference: (-o) time tunefs: volume label: (-L) Note the value for -m

Using something like IPMI? With that I can attach an ISO image on my PC and boot the data center server off of it. Takes a while to boot of course as it has to upload but it can be done. pfSense isn't involved in that scenario.

Update: Looks like the NIC is buggered. Threw PFsense onto another PC and a different second NIC and getting full 1Gb transfers as expected. Put the quad-card into the PC and it refused to boot with it in. RMA time!!

@Gertjan Very educating... thank you!

ck42, it looks like it is single-queued

Update/reboot when there's a remote vuln that can affect my box. All ports blocked by default, so pretty much has to be a FreeBSD kernel issue. Had 400+ days at some point the past year. Been hanging out on 2.4.4-p3 for a bit now.

@Gertjan This is interesting. The reason I have alias called pfSense because it lists LAN addresses like 192.168.90.1 etc as well as DDNS addresses. I did not see "This Firewall" blocking external DDNS IPs. Did you? PS: Thinking about it I'd say it should block ANY IPs, maybe a good feature request ? Thx

pfsense routes anything not in its own LAN subnet(s) out the WAN. It does not matter if the address is in private space or not. If your address is the default 192.168.1.0/24 and you try to reach 192.168.5.50 it will forward that request out the WAN to/through the modem. As johnpoz said "They are being intercepted by the device, because of the IP of the dest." +1 My switch right here has an address of 172.31.125.2 and I expect it to answer when I go to that address. But it otherwise does its job of distributing traffic on my LAN. Modems do likewise.

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.