One dpinger gateway status offline
-
Huh, so apparently 8.8.8.8 replies to DNS from that WAN, but not ping. Or maybe something upstream of you is blocking it. If you go to Diag>Ping and choose source WAN and try to ping 8.8.8.8 do you get a reply? Do you get a reply pinging 8.8.8.8 from hosts on the LAN going out via that same WAN?
-
Ping works from Diag>Ping as expected and it also works perfectly from any of the hosts on the LAN.
Also tried changing the 8.8.8.8 to 8.8.4.4 which works on the VPN interface but I get the same problem.
-
Ok, put it back to 8.8.8.8, and repeat that same packet capture on WAN. Leave it running for about 10 seconds to catch the monitor pings, then go to Diag>Ping and ping from source WAN. Then stop the capture, download the pcap file and either attach it here, or can email it to me (cmb at pfsense dot org) with a link to this thread.
-
Just sent the .cap file as email, thank you.
-
Working with shopro and dennypage we tracked this down to this.
https://redmine.pfsense.org/issues/5830 -
Denny has updated dpinger (to version 1.5).
I expect that Renato will update the code in pfSense soon. You should have a version of pfSense software v2.3 (still BETA) that has the fix within a few days.
-
This option's been added to the gateway advanced settings. System>Routing, edit your gateway, specify something > 0 in the "Data Payload" field. Confirmed that works, and should definitely fix your issue shopro given the troubleshooting we've been through to narrow down and verify the issue.
-
Working like a charm. Thank you! :)
-
Good to hear. Thanks Denny!
-
You're welcome.
