What's happening with PFSense? This is confusing!
What's happening with PFSense? This is confusing!
I've made the adjustments. The problem remains occasionally, so I'll check again tomorrow evening. Appreciate your reply!
I reviewed the changes and confirmed everything is up to date. Please let me know if you have any further concerns. Regarding the DNS issue with RealTek network interfaces on pfSense, it seems to be a driver-related UDP checksum offload problem. I’ve switched to Intel interfaces and haven’t encountered this in about six years.
Following some tests, it appears to function properly. I plan to turn off all the clients' VPNs I set up for this temporary solution and observe the results after 24 hours. I’m looking forward to positive outcomes.
It's a positive decision to go with Intel for your NIC. You've got two gigabit models, which should help. I'll review your settings to ensure everything is correct. I'm confident this will restore your network performance to its former state.
The ARP hint proved very helpful for another challenge, since I struggled to locate my UniFi access points which weren't appearing in DHCP leases or the Ubiquiti discovery tool. I found them in the ARP tables and successfully entered the right IP addresses into the controller. Now I can manage my access points again!
Are you certain there aren't ARP problems? Typically ARP issues stem from the connected switching rather than pfSense itself, especially when dealing with the attached switches. This can happen due to wrong VLAN tagging or improperly set trunk ports—assuming a single LAN interface. What internal switches and VLAN settings are you using? I've noticed unmanaged switches sometimes piggybacking managed ones, which can cause problems if the attached port is a trunk with an untagged native VLAN (like vlan1).