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.

Try looking at the ruleset in /tmp/rules.debug when it's failed. Then do a filter reload so it's working and check again. Compare the files, what changes? (if anything) Steve

@bingo600 okay, THAT is a useful tidbit, thank you, and thank you guys for the replies, I look forward to testing this out again then later today after I fix my mess of a problem I somehow introduced myself last night! once again, thank you guys for making this possible, all of you developers and everyone with the pfsense team, THANK YOU. love this software.

@bmeeks I had to undo it. Just got a call that for about the last hour or so calls have been going straight to voicemail intermittently. Looks like it broke the VOIP at the location.

@jknott said in NTP and automatic switch to DST ?: @ninthwave It changed for me, on both pfsense and computer behind it. Don't forget, NTP provides UTC and it's up to the client to provide the offset from it. On Linux, data is downloaded to provide the DST dates and I expect the same happens on FreeBSD. Strange because all my devices get their NTP time from my pfSense. And, while my Windows for instance, adjusted to DST, pfSense itself did not.