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

    PfSense 2.2 ovh failoverip (gateway outside subnet)

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 3 Posters 4.9k 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.
    • W
      wmrichard
      last edited by

      Dear pfSense,

      I have a dedicated server at ovh running vmware. Now I'm trying to get internet, with a gateway outside the subnet. pfSense doesn't likte this setting because it is a weird configuration which doesn't correspondents to any RFC's.

      I have tried the following "tweak":
      route add -net gateway.254/32 -iface vmx0
      route add default gateway.254

      This works for the most part, I get internet on the firewall, but not in the LAN. It looks like pfsense doesn't think that the wan is the gateway. Is there some way to get around this? A command or something?
      I tried running with a /16 network (this works!), this makes the gateway and the wan ip in the same network, but then I get blocked by ovh, because I must use a /32 network to limit their broadcast.

      Thank you so much in advance,

      wmrichard

      1 Reply Last reply Reply Quote 0
      • W
        Wizard-ICT
        last edited by

        In the web interface, go to WAN under interfaces and set the Default Gateway in there.

        You still need to use the route add… commands (run them using shellcmd at start up). Setting the gateway in the interface doesn't actually work in terms of providing a gateway, but it makes pfSense think it has a gateway. Without it it doesn't realise it can use that interface to access the internet.

        I've been running 2.0.3 for over a year and 2.2 for a few days (testing) on OVH and Hyper-V with these settings and it works fine, even with the gateway on another subnet.

        1 Reply Last reply Reply Quote 0
        • W
          wmrichard
          last edited by

          @Wizard-ICT:

          In the web interface, go to WAN under interfaces and set the Default Gateway in there.

          You still need to use the route add… commands (run them using shellcmd at start up). Setting the gateway in the interface doesn't actually work in terms of providing a gateway, but it makes pfSense think it has a gateway. Without it it doesn't realise it can use that interface to access the internet.

          I've been running 2.0.3 for over a year and 2.2 for a few days (testing) on OVH and Hyper-V with these settings and it works fine, even with the gateway on another subnet.

          Thank you so much it works.

          1 Reply Last reply Reply Quote 0
          • K
            kendalf1
            last edited by

            This is how I setup OVH with pfsense 2.2

            OVH networking setup

            1. Add a failover IP in OVH console (y.y.y.y)
            2. Create a virtual mac in OVH console for failover IP

            VMWare setup
            3. Edit the vm guest nic settings.  On the network adapter in vmware, change it to manual and give it the virtual mac assigned from step 2

            PFsense setup
            4. The failover ip from step 1 is the nic ip (y.y.y.y).  The gateway is the primary OVH server IP with 254 for last Octet (x.x.x.254).  Subnet mask is 32. Pfsense will complain in command line setup of networking.  Just set this up in GUI.
            5. The following lines can be added from the shell (option 8 from command prompt in Pfsense) - the first time you setup pfsense.  They are needed to make the default gateway work because it is not on the same subnet.
            6. route add -host x.x.x254 -iface vmx0 (or whatever interface you have)
            route add default x.x.x.254
            7. To add them to pfsense so it works after reboot, Install the shellcmd package for pfsense.  Add them in the same order as above.  The type is shellcmd

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