Navigation

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

    Proxmox/OVH - no route added to GW after upgrade to 2.5.0

    Routing and Multi WAN
    3
    4
    207
    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.
    • K
      knownasq last edited by

      Problem

      After updating a Proxmox VM on OVH to 2.5.0 I was left with no internet access.

      Upon further inspection I noticed there was no route to the gateway(on an different subnet) being added.

      I have added a working solution below if it helps anyone else out that is finding themselves in a similar situation.

      Failed Solutions

      I tried deleting the WAN gateway from the GUI and then re-adding it making sure the Use non-local gateway option is selected. Upon doing this no route is added to the gateway that resides on the different/external subnet.

      Working Solution

      Login via SSH and then add the route manually:

      route add -net XXX.XXX.XXX.254/32 -iface vtnet0
      route add default XXX.XXX.XXX.254
      

      Replace XXX.XXX.XXX with the IP of your OVH box substituting the host part of the address with 254.

      Once WAN connection is back up, install the ShellCmd package and add the commands listed above to automate this on system boot.

      Question

      Is there a to make this work through the GUI on 2.5.0 without using the ShellCmd package as this seems a bit of a hack job?

      This same setup worked on 2.4.5.

      I have tried looking for any new advanced options in the GUI that might be causing the issue but can't find any.

      1 Reply Last reply Reply Quote 1
      • V
        vlehemonet last edited by

        Thank you!

        I got the same problem with the same architecture and it was driving me crazy !

        The workaround works for me too.

        The default route set in the GUI is never installed in the routing table.

        1 Reply Last reply Reply Quote 0
        • jimp
          jimp Rebel Alliance Developer Netgate last edited by

          https://redmine.pfsense.org/issues/11433

          You can install the System Patches package and then create an entry for a97987a5d1df8219f40433270fce0e3ef49345dc to apply the fix.

          1 Reply Last reply Reply Quote 2
          • K
            knownasq last edited by knownasq

            Thank you

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

            Products

            • Platform Overview
            • TNSR
            • pfSense Plus
            • Appliances

            Services

            • Training
            • Professional Services

            Support

            • Subscription Plans
            • Contact Support
            • Product Lifecycle
            • Documentation

            News

            • Media Coverage
            • Press
            • Events

            Resources

            • Blog
            • FAQ
            • Find a Partner
            • Resource Library
            • Security Information

            Company

            • About Us
            • Careers
            • Partners
            • Contact Us
            • Legal
            Our Mission

            We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

            Subscribe to our Newsletter

            Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

            © 2021 Rubicon Communications, LLC | Privacy Policy