Hmm, I not aware of any blacklisting there. Could be co-incidental I guess.

@stephenw10 Done! Thanks for reviewing; let me know if you need anything else from me. SG

Well you test there seems to show it's possible with the right NICs. There have been a few other similar posts. Most systems will not though. I haven't tried it personally, I can only dream of 1G where I am!

If you have a paid Plus subscription then open a ticket with TAC to discuss. Usually it can be migrated if you had to replace failed hardware for example.

@stephenw10 I did shut it down twice while troubleshooting, to make it restart. This was while the network was down, and I was trying to figure out why, before I connected a monitor directly to it. I'll go through the logs again, and see if I can find any clues to why it went down in the first place ( and what caused the config file to be left empty ).

@allsome Yup I was about to respond that unchecking it should do what you need, at least as far as I can tell. I am still using it with this firewall and Proton's SMTP service and it's working fine.

@Gertjan thank you very much i have removed the VLAN ID from the network card settings directly and i try the config on the unifi control and now work on allow device.

The option is moved to the DHCP server setup page when Kea is running in 24.11. You can now choose to register leases from each interface separately if required.

@Gertjan as a last resort i will enable that ;). If i would be owner of hotel i also would not enable that ;)

@snunez Configure pfSense to send logs to a remote log server (Status / System Logs / Settings / Remote Logging Options) and use syslog-ng on the remote system to provide the integration. That said, have you considered a log system like Graylog instead of a messaging system?

@Gertjan said in pfSense behind pfSense - Not getting WAN IP from PFS1: edit : and if this doesn't work, then you have to place a smart switch between PS1 and PS2. Split out the VLAN ID from PS1 out on this switch, and connect the assigned port to the pfSense 2 WAN. I have several managed switchs and PFS2 was connected to one of the ports on one of the switches, which was configured with that VLAN-id. When I said I could ping the PFS1 IP address but nothing beyond, I assumed that it will be understood that internal networking was setup okay. BTW, in the 7th post, I posted the reason for not working in the first place and then it started working as expected after the reboot, then it becomes very obvious that VLAN, tagging, managed switch etc. weren't the issue at all. The question was why PFS1 couldn't provide an IP to PFS2 in the first place, via DHCP.

@Gertjan i know htop exist but it lacks some features. I understand security reasons and i appreciate them, but having btop would be nice :)

@bdeprez said in pfsense dns lookup (netgate.com) every 30 seconds: Is there a reason for this? As said above : a TTL for a domain zone (whatever zone), I still don't know why that would be needed (exception : mega zones like Microsoft.com google.com facebook.com etc - and, afaik, netgate.com isn't that big as a company - or, for example, load scheduling over en entire server park) But as we all learn on this forum, people do things with DNS that can't be explained by reasoning. It gets even better : while posting here on the forum, I used - that is, my browser is, polling forum.netgate.com constantly. Exactly what you found. Guess what, "forum.netgate.com" also has a 60 sec TTL : so [image: 1737546395272-1b3794a9-ed4e-43eb-bd57-d3d30edbb93f-image.png] All request are received, and answered out of the (local !) unbound cache. Not sure why it asks for a IPv4. I used IPv6, and IPv4 exists as a fallback But ... I have this option checked : [image: 1737546564225-7bc6aab6-136b-402d-bb90-1a77ea3c1998-image.png] which does what it says that it does (or, probably better : what I make of it ^^ ) If an already resolved domain name, now in the resolver cache, starts to reach a zero TTL unbound will re-resolve automatically so it can answer a requesting client always right away, without going out and do the entire resolve process 'while I'm waiting (the give to take 100 ( ? ? msec this will take). So, I, the admin, was asking for it. As always, to see stupid things you need to be two : the one who creates them, and the other, who sees them. So, ones a "forum.netgate.com" resolved host name exists in my local unbound resolver cache, it will stay there, and get refreshed every TTL-10% = 54 seconds. Let's contact "netgate.com", and ask if they can lower that 60 to 1 seconds, because "why not ?!". Their domain name servers will get smacked with requests ... Btw : No, pfSEnse isn't polling netgate.com for "telemetry" reasons. pfSenses wants to resolves "netgate.com" a couple of time per day ( ? ) while checking for possible updates and some more reasons.

@stephenw10 said in Netgate 8200 connection questions: Nice! Yes I think we have seen reports of those WD 520 series working but not available new any longer AFAIK. yeah, that's the only issue; I wish I could buy new I think, I'll buy another pair, to keep as the spare. Did you move the support screw or use adapters for those? Just moved the support screws. [image: 1737444626679-d6e918e8-a1b7-40cb-9eda-c79290216ddc-image.png] Was pleased to see that mainboard has the native support of diffrent-length M.2 and Netgate was kind enough to supply the extra screws.

Is the layer3 switch routing between those VLANs? If is that could create asymmetric traffic in pfSense. But run pcaps in pfSense so you can whats actually going through both the interfaces. The earlier pcap show the server sends the Key Exchange Init packet but the client never receives it. So does that arrive at pfSense at all?

@Wylbur said in How do I figure out what part of SNORT is causing a data xfer to fail?: Meanwhile, I had not realized that this alert area was available. Apparently with the upgrade to 2.7.2? Uhh ... no. The ALERTS tab has been present in the package since the package was created. Snort has never existed on pfSense without an ALERTS tab being present. That goes back more than 12 years. There is also a Dashboard Widget that can be enabled for Snort. It shows the most recent 5 or so alerts (the exact count is configurable in the widget).

I'm returning to this thread with an update. New hardware is in place. The backup - restore - reassign interfaces process was completely flawless and painless. The new Broadcom-based ports are behaving where the previous hardware's Realtek ports were not. The problem was solved with $200 in hardware. For those reading after 2025-01-20, the price from China may be higher.

Thanks for the report. The issue may be tracked here: https://redmine.pfsense.org/issues/16005

@patient0 didn't notice that. Thanks!