@messerchmidt here is a better link via my google drive: https://drive.google.com/file/d/1LjmwhmAyct2ScxPhZg0gQQMhpPi_JEBu/view?usp=sharing

You can add them as a feature request in Redmine. Or add comments to an existing request there uf there is something close enough to yours. Steve

Indeed, you should not do that! Mostly because enabling the complete FreeBSD pkg repo that can very easily pull in packages that break functionality by replacing the customised versions we have in pfSense. Installing individual pkgs directly using the full path like that can work as long as the dependencies list is met. If it needs a huge list of other things there's every chance it will break something. Small basic utilities. Plex is not that! Steve

When it get's an IP but you're unable to ping anything beyond the WAN subnet what error you see when you try? That sounds like it has a bad default route or no default route. Check the routing table. If you have more than one gateway defined on the firewall make sure the WAN DHCP gateway is set as default in System > Routing > Gateways. Steve

Those values are pulled from netstat and I'm not aware of any way to reset them unfortunately. https://www.freebsd.org/cgi/man.cgi?query=netstat Steve

miniupnpd cannot use a private IP as the WAN and will fail to add forwards. If something is restarting it you will see that logged. See: https://redmine.pfsense.org/issues/10398 Steve

I would open a bug report for that: https://redmine.pfsense.org/ Include the same details you have here. Seems reasonable not to expect that behaviour. Steve

I was able to solve the gateway being listed as pending by adding an IPv6 gateway monitoring address (I used Google). But no progress on the other issue. Does anyone have any insight?

@derelict thank you i will try that

@Chrischevy , what pfsense packages did you install?

@stewart said in Gateway error on both WANs at same time: I guess that as long as it's working then you're all set. I don't know why changing those IPs made a difference and I wouldn't expect things to be moved back from WAN2 to WAN1. Maybe you have a reconnect period on the VPNs that's being hit and they reconnect over the new WAN1 connection? I don't know. Maybe an open connection keep the vpn on WAN2 and revert to WAN1 when there's no activity. Anyway, I'll look into this because I want to be sure that vpn connections come back to WAN1. Otherwise I have two solutions: implement the automatic failover of 4G router (but I have no control on it) implement some scripting to force the come back to WAN1 Thanks a lot

@viragomann I think this is what is happening. https://docs.netgate.com/pfsense/en/latest/troubleshooting/logs-arp-moved.html

@bingo600 Yes.

That makes sense. However, if I recall correctly this is happening not only for P2P. I'd understand that almost all ISP's have some kind of a traffic shaping for P2P traffic but this happens with usenet too which is very very rarely used here in the Philippines. They don't even know what it is. I haven't tried using a VPN but that would be a good test. But in my initial traffic monitor graph, does that point to throttling even though those dips are only for a few seconds that I don't even see the drop in speed in the actual download clients themselves?

Could be not sync'd yet, could be a rate limiting thing... If you capture the KOD packet - it should include a hint to why..

@bitspiel @lnguyen @Stewart Thank you all for the help, it has provided a path for me to travel along. The link is quite helpful and the presenter seems to use a pfSense box with a switch, so I was doing this wrong. I will try to use rules on the other lan OPT ports and see what comes of it. I'll update on my progress in the next few days.