Those are just local broadcast/multicast things, normal for it to do on the network segment. Not indicative of a problem. It's how it finds other devices on the network and vice versa.

@heper I just would like to squeeze every bit of performance. I'm running suricata, pfblocker and AdGuard Home inside my pfSense. I think I was able to bring back the bursting experience by making sure all offloadings are disabled and leaving to default, parameters that impact security. The advise found in the link above I think is so strict. Speed is very stable now and it's bursting to ny subscribed speed

@bmeeks Thanks, you're right. Will check out which rule is blocking VPN.

Hmm, I think I just googled it. Like: https://asnlookup.com/organization/facebook/

Anyone still hitting this who can test there is a patch now available here: https://redmine.pfsense.org/issues/13671#note-4 We need feedback there to confirm it. Steve

There's a patch on the ticket now available if anyone can test it. If we get some positive feedback there we can commit it for 23.01. https://redmine.pfsense.org/issues/13671#note-4 Steve

If you add a dyndns entry to it you will be notified when that changes. For a failover group that will show when it fails over.

I just found an old email about this thread and had forgotten about it because once you read an email, it's no longer highlighted. I felt I should come back to close it. The problem was unrelated to pfsense completely. What it was is that I had a test SIP system on another network using the same ITSP. When it would register with the ITSP, it would break registrations from the second SIP server, the one I was actually using now. Once I shut down the original, everything started working again. Sorry it took so long to come back and explain this and thank you for helping me.

@gabacho4 Thank you for explaining, I too wondered about those settings.

It's still open, you should just be able to add a comment to it. I added one.

@michmoor @stephenw10 This has been resolved. Thanks for the guidance.

Are you running pfBlocker? Snort/Suricata? Anything show as blocked? Steve

@magikmark it shouldn't as those have to all originate from OUTSIDE your network, not inside.

@stephenw10 said in Supported CPU C-States: Mmm, @mvikman's CPU must be very lightly used. Anything I've ever tried that on looks more like your output there, mostly in C1. LOL yeah, it's just my home router and it's got a i5-6500, just haven't had time to dabble with pfblocker and such things yet @mrsunfire No, that was the only line I added. Though I have PowerD set to Adaptive instead of HiAdaptive because HiAdaptive doesn't seem let CPU to throttle speed lower MHz...

@rcoleman-netgate said in LAN port hangs when using Web UI: @nathanzumwalt MESH is evil. Agreed... even the new network topology didn't keep the eero devices from interfering with pfSense eventually (just took a little longer for the same symptoms to appear). I replaced the eero mesh with some Netgear wifi access points and the network has been stable ever since.

@nimrod said in Is it possible for one to "slip through"?: @stephenw10 Wouldnt this option prevented this issue ? [image: 1668875890441-5f219169-7aca-464b-a7b3-ac7b58515f4e-image-resized.png] Just to add my 2 cents worth, I just ran into a situation where the states were not being cleared because an IP appeared to remain after the force command. I ended up manually clearing the states to fix the issue. I would say, if all else fails, manually clear the states as was suggested earlier, I think.

@johnpoz thank you both for the reply

It's dangerous (or at least confusing) to talk about VLAN 0 or 1 as an actual VLAN because you almost never want that. Switches use 1 as the 'native' VLAN meaning they use that for untagged traffic internally in the switch. You should never see traffic tagged VLAN1 outside the switch.l Seeing it usually means something is configured incorrectly and unexpected results may occur! https://docs.netgate.com/pfsense/en/latest/vlan/security.html#using-the-default-vlan-1 In ESXi VLAN 4095 means pass all VLANs. So allow tagged traffic on any VLAN to pass the switch much like most unmanaged switches would. If you do have some tagging happening somewhere the addition switch on that one client that works could be stripping it. Especially if it's VLAN1. That seems unlikely though. Hard to imagine that could have been set by a power outage. Or that it would have worked before that. Steve

Yeah, I would definitely use access point mode. And LACP lagg there should not do anything much until you exceed the single links speed at 941Mbps. Assuming Gigabit. Even with wifi6 it's hard to reach that over wifi. Also it only helps with multiple connections sharing that. A single connection is still limited to one link. Steve