Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    One dpinger gateway status offline

    Scheduled Pinned Locked Moved
    2.3-RC Snapshot Feedback and Issues - ARCHIVED
    5
    16
    17.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      shopro
      last edited by

      It is all like the following:

      06:03:37.002800 IP MY-IP > 8.8.8.8: ICMP echo request, id 20936, seq 23535, length 8

      With the following exception happening once during the 10sec period:

      06:03:43.916388 IP MY-IP.43911 > 8.8.8.8.53: UDP, length 43
06:03:43.941188 IP 8.8.8.8.53 > MY-IP.43911: UDP, length 88
      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        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?

        1 Reply Last reply Reply Quote 0
        • S
          shopro
          last edited by

          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.

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            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.

            1 Reply Last reply Reply Quote 0
            • S
              shopro
              last edited by

              Just sent the .cap file as email, thank you.

              1 Reply Last reply Reply Quote 0
              • C
                cmb
                last edited by

                Working with shopro and dennypage we tracked this down to this.
                https://redmine.pfsense.org/issues/5830

                1 Reply Last reply Reply Quote 0
                • J
                  jwt Netgate
                  last edited by

                  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.

                  1 Reply Last reply Reply Quote 0
                  • C
                    cmb
                    last edited by

                    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.

                    1 Reply Last reply Reply Quote 0
                    • S
                      shopro
                      last edited by

                      Working like a charm. Thank you!  :)

                      1 Reply Last reply Reply Quote 0
                      • C
                        cmb
                        last edited by

                        Good to hear. Thanks Denny!

                        1 Reply Last reply Reply Quote 0
                        • dennypageD
                          dennypage
                          last edited by

                          You're welcome.

                          1 Reply Last reply Reply Quote 0
                          • First post
                            Last post