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

    Monitoring IP since 2.3.3

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 2 Posters 519 Views
    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.
    • J Offline
      jdemeza
      last edited by

      Since upgrading to version 2.3.3-RELEASE I have been having issues monitoring my VPN gateways. The gateway itself doesn't respond to ICMP so I was using the public address of the VPN server. For example I am using NordVPN and the public IP for au17.nordvpn.com is 103.231.89.30. This used to work without issue but since the upgrade, I can't ping that IP when the source_address is the interface attached to the VPN. As a result the VPN gateways all present as down.

      Thanks for any suggestions.

      1 Reply Last reply Reply Quote 0
      • J Offline
        jdemeza
        last edited by

        I should also mention that I can successfully ping that IP from any other gateway interface eg WAN.

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

          Have you tried setting Data Payload to 1 in System / Routing / Gateways / Edit?

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