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

    Gateway monitor pending after upgrade to 2.6.0

    Routing and Multi WAN
    2
    5
    820
    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.
    • C
      cmaffio
      last edited by

      Hi, I've upgrade two pfsense from 2.4.4 to 2.6.0.
      In this two firewall are present 4 WAN.
      After the upgrade all the WAN, randomly, have the status monitor in pending status.
      If I go to the Gateways logs i can read:

      Jun 9 09:32:26 dpinger 34899 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 194.119.192.34 bind_addr 195.103.230.190 identifier "HDSLGW "
      Jun 9 09:32:26 dpinger 35087 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 77.242.131.225 bind_addr 77.242.131.238 identifier "WICGW "
      Jun 9 09:32:26 dpinger 35765 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr 8.8.8.8 bind_addr 62.173.172.252 identifier "GWFIBRA "

      and in the General logs I can see:
      Jun 9 14:29:34 php-fpm 6039 /widgets/widgets/gateways.widget.php: dpinger: timeout while retrieving status for gateway WICGW
      Jun 9 14:29:41 php-fpm 365 /widgets/widgets/gateways.widget.php: dpinger: timeout while retrieving status for gateway WICGW
      Jun 9 14:29:48 php-fpm 364 /widgets/widgets/gateways.widget.php: dpinger: timeout while retrieving status for gateway WICGW
      Jun 9 14:29:55 php-fpm 91077 /widgets/widgets/gateways.widget.php: dpinger: timeout while retrieving status for gateway WICGW
      Jun 9 14:30:02 php-fpm 75394 /widgets/widgets/gateways.widget.php: dpinger: timeout while retrieving status for gateway WICGW
      Jun 9 14:30:09 php-fpm 39332 /widgets/widgets/gateways.widget.php: dpinger: timeout while retrieving status for gateway WICGW
      Jun 9 14:30:16 php-fpm 75394 /widgets/widgets/gateways.widget.php: dpinger: timeout while retrieving status for gateway GWADSL

      How can i resolve this problem?

      Best regards

      1 Reply Last reply Reply Quote 0
      • jimpJ jimp moved this topic from Problems Installing or Upgrading pfSense Software on
      • C
        cmaffio
        last edited by

        Hi, I've tried to restart the 2.6.0 and the 2.5.2 too but the problem is always here.
        The PFSense is a VM hosted by a ESXi 6.5.0

        I've tried to restart the ESXi too.

        Someone can help me?

        Best regards

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

          Another very strange behavior
          All ping I do to every IP, the reply time is always at 0

          ping 8.8.8.8
          PING 8.8.8.8 (8.8.8.8): 56 data bytes
          64 bytes from 8.8.8.8: icmp_seq=0 ttl=117 time=0.000 ms
          64 bytes from 8.8.8.8: icmp_seq=1 ttl=117 time=0.000 ms
          64 bytes from 8.8.8.8: icmp_seq=2 ttl=117 time=0.000 ms

          ping 8.8.4.4
          PING 8.8.4.4 (8.8.4.4): 56 data bytes
          64 bytes from 8.8.4.4: icmp_seq=0 ttl=117 time=0.000 ms
          64 bytes from 8.8.4.4: icmp_seq=1 ttl=117 time=0.000 ms
          64 bytes from 8.8.4.4: icmp_seq=2 ttl=117 time=0.000 ms

          ping www.google.com
          PING www.google.com (142.250.184.68): 56 data bytes
          64 bytes from 142.250.184.68: icmp_seq=0 ttl=117 time=0.000 ms
          64 bytes from 142.250.184.68: icmp_seq=1 ttl=117 time=0.000 ms
          64 bytes from 142.250.184.68: icmp_seq=2 ttl=117 time=0.000 ms

          Is the ping code wrong?

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

            Hi, I try to summarize the problem after the analyzes I carried out:

            Two HP servers with ESXi 6.5, connected with 4 WAN and 1 LAN and connected directly by a dedicated connection for SYNC.

            On each ESXi a PFSense is virtualized, at the beginning it was a 2.4.4p3

            I upgraded the two PFSense installations to 2.6.0 from 2.4.5 (the system skipped the transition from 2.5.x)

            During the updates I did not find any problems, even after the PFSense were working correctly, I did not immediately notice the "Pending" of the WAN monitoring. After a few hours I notice that this pending is very frequent and going to see in the logs I detect the reports that I reported in the first post:

            Jun 9 14:30:02 php-fpm 75394 /widgets/widgets/gateways.widget.php: dpinger: timeout while retrieving status for gateway WICGW
            Jun 9 14:30:09 php-fpm 39332 /widgets/widgets/gateways.widget.php: dpinger: timeout while retrieving status for gateway WICGW
            Jun 9 14:30:16 php-fpm 75394 /widgets/widgets/gateways.widget.php: dpinger: timeout while retrieving status for gateway GWADSL

            After various other checks I find that even the ping had problems, in fact, regardless of the destination IP, the ping time was always at 0

            ping 8.8.8.8
            PING 8.8.8.8 (8.8.8.8): 56 data bytes
            64 bytes from 8.8.8.8: icmp_seq = 0 ttl = 117 time = 0.000 ms
            64 bytes from 8.8.8.8: icmp_seq = 1 ttl = 117 time = 0.000 ms
            64 bytes from 8.8.8.8: icmp_seq = 2 ttl = 117 time = 0.000 ms

            ping 8.8.4.4
            PING 8.8.4.4 (8.8.4.4): 56 data bytes
            64 bytes from 8.8.4.4: icmp_seq = 0 ttl = 117 time = 0.000 ms
            64 bytes from 8.8.4.4: icmp_seq = 1 ttl = 117 time = 0.000 ms
            64 bytes from 8.8.4.4: icmp_seq = 2 ttl = 117 time = 0.000 ms

            ping www.google.com
            PING www.google.com (142.250.184.68): 56 data bytes
            64 bytes from 142.250.184.68: icmp_seq = 0 ttl = 117 time = 0.000 ms
            64 bytes from 142.250.184.68: icmp_seq = 1 ttl = 117 time = 0.000 ms
            64 bytes from 142.250.184.68: icmp_seq = 2 ttl = 117 time = 0.000 ms

            I have checked both on PFSense and on VMWare to see the various parameters but I have not solved anything. I changed the monitor IPs but again I couldn't find anything.

            I then started to reinstall everything without success, I tried to do a new installation of 2.6.0, 2.5.2 and 2.5.1 and configure only one interface and do the tests but again the problem was always present.

            I then recovered a 2.3.4 and as before I configured only a network interface and everything worked correctly, I then arrived at 2.4.5 passing from 2.4.4 and in each step check the monitoring and ping and everything was working correctly . When I then switched to 2.5.1 and later the problem arose again.

            I then went back, thanks to the snapshots, to 2.4.5 and restored the configuration and everything continued to work correctly

            Has anyone ever had a similar problem?

            D 1 Reply Last reply Reply Quote 0
            • D
              ddbnj @cmaffio
              last edited by

              @cmaffio

              If I unplug the fiber to my modem, I can only get a "pending" status on dpinger. My site to site VPN's appropriately report down status.

              Not sure if that's the same problem as you but something is different in gateway monitoring.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.