@manjotsc said in Intermittent Network Drops pfSense:

arprequest_internal: cannot find matching address

That sounds like some device is trying to reach an IP that is no longer available? Could there be some "states" that are lurking or something thinking the main gateway is still up even if it isn't? Only, I guess since you said you did reboot, the state table should be cleared...
Perhaps there there is something in the gateway monitoring that is not set up correctly or there is an IP conflict?

@Farh
Disabling reply-to on the accessed node - yeah, this could be a reason.
When enabled, replies are directed to the gateway, which is stated in the interface settings.

Disabling reply-to could lead into issues with multi-WAN setup, however.
To avoid this, you can add pass rules to the top of the WAN rule set only for the source of the WAN subnet and disable reply-to in the advanced options.

@Normandy214 Over here I'm using Tachus Fiber. I have their gig service.

CFC

@viragomann Perfect, that worked! Thanks!

bridge-fixed.png

@viragomann Hello again, everything is working fine. But sometimes have a delay in opening sites, like 1,2 sec delays. Looks like resolving delay. Could you please give a tip, what to check? Here are my settings:
Screenshot_12-11-2024_131743_192.168.20.1.jpeg
Screenshot_12-11-2024_131718_192.168.20.1.jpeg
Screenshot_12-11-2024_13209_192.168.20.1.jpeg
Screenshot_12-11-2024_132517_192.168.20.1.jpeg
Screenshot_12-11-2024_13254_192.168.20.1.jpeg
Screenshot_12-11-2024_132453_192.168.20.1.jpeg
Screenshot_12-11-2024_132425_192.168.20.1.jpeg
Screenshot_12-11-2024_132438_192.168.20.1.jpeg
Screenshot_12-11-2024_133042_192.168.20.1.jpeg
Screenshot_12-11-2024_132922_192.168.20.1.jpeg

Unbound " network interfaces " also checked all local interfaces as well and " outbound network interfaces " only localhost

After further investigation, the ISP was at fault and wasn't able to find a resolution with them.

Moved ISPs and the issues went away.

@Charlie48
You can connect two NICs to the ISP box though, I think, but you can only state the gateway on one of them. This would not have any drawbacks, however.

I expect, that the DHCP sets also the default gateway. Then just assign the static IP to the other NIC without stating a gateway.

@gld yeah normally pfsense by default will hand out the interface the dhcp server is running on as the gateway, and you can leave it blank - you should kind of see the IP of the interface in the settings just greyed out.. But it seems, that if you switch to kea, and then back this fails..

other.jpg

Yeah I would say its some sort of bug with moving to kea and then back? But I had moved to kea when it first came out just to see and it was working. But that was back with 23.09, maybe something in 24.03 is flaky... If still doing it when 24.11 drops I will check and see and if not already there put in a bug report.

But your the 2nd person I have seen with same sort of issue, no gateway and had switch to kea and then back.

I am totally lost after several tests.

If i replace my PfSense by a PC with the same setup
IP 192.168.10.99
Gateway 192.168.10.254
DNS 8.8.8.8

I have internet doing well

Although the 2 Wans as per first post are OK, the WANGW seems to be not usable.

The ckecks I made:

WANGW is tier2 of a Group Where WAN2ADSL_DHCP is Tier 1 (failover objective).
If I swap Tier1 and Tier2, although WANGW states online, no more access to Internet.
I suspect that the Online state of WANGW is wrong so the group does not swap to tier2.

If I unplug igb0 which is the WAN plug (associated with WANGW) the state remains Online.

I am lost.

Help appreciated, many thanks.

@viragomann Thanks 🙂 I'll have a look

@skoota said in Apple TV - VPN vs. Local Traffic Routing:

I am running a Netgate 4200 with pfSense 24.03.

ExpressVPN

Gives .... Google : pfsense expressvpn.

I' uses / played a bit with these instructions a while back, they are pretty accurate.

When you are asked to create a Firewall > Aliases, and where the instructions tell you to add a network like 192.168.1.1/24, add just your Apple TV IP, or some IPs that have to use the VPN.
More info in the pfSense manual : policy routing.

To answer my own question: The problem is due to TCP packet reordering, which the default TCP stack of freeBSD 15 does not handle very well.

The solution would be to activate the RACK TCP stack available in freeBSD. However, pfSense+ has this feature of stock freeBSD disabled.
https://freebsdfoundation.org/our-work/journal/browser-based-edition/networking-10th-anniversary/rack-and-alternate-tcp-stacks-for-freebsd/

I created an issue on the PfSense redmine and ask anyone experiencing similar issues to support it: https://redmine.pfsense.org/issues/15813

@McMurphy Both an HAProxy (including a -devel version) and Squid package exist via Package Manager. I could not speak to which would be better for your use case as I have no use for either one.