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

    Impossible to add a default gateway outside attached subnets !

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    4 Posts 3 Posters 2.4k 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.
    • P
      p.rousset
      last edited by

      Okay, you will say this is not usual, but…  :P

      I have to run pfSense in a virtual machine on my server. This server is hosted by OVH which provide me some IP failover that work in XenServer/Vmware. The WAN configuration should be that one (as explained here : http://help.ovh.co.uk/BridgeClient / http://guides.ovh.com/BridgeClient) :

      IP: 86.95.150.79/32
      Default gateway: 45.15.95.254
      Satic route: 45.15.95.254/32 to 86.95.150.79

      The problem is that in pfSense you cannot add a default gateway outside the attached subnets, even if there is static route to reach it. I think this is wrong since it's possible in some configuration.

      I'm thinking to open an issue, what do you think ?  ???

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

        Not a valid network config, but there are instructions in a feature request ticket in redmine.pfsense.org on how to make that work, not sure the ticket # offhand, look there and you'll find it.

        1 Reply Last reply Reply Quote 0
        • P
          p.rousset
          last edited by

          @cmb:

          Not a valid network config, but there are instructions in a feature request ticket in redmine.pfsense.org on how to make that work, not sure the ticket # offhand, look there and you'll find it.

          Thank for your advise, the ticket is here: http://redmine.pfsense.org/issues/972

          Unfortunately, when I type :```
          route add -net gatewayip/32 -iface em0 -cloning

          
          Pfsense return me :```
          route: bad keyword: cloning
          

          So I tried without the parameter -cloning but I'm not an expert in routing/freebsd, so I don't know if it will really work as expected? Do there is any other way to add the clone flag on pfSense 2?

          1 Reply Last reply Reply Quote 0
          • G
            Gloom
            last edited by

            the -cloning option is no longer supported under FreeBSd 8.x
            It should work without the -cloning option

            Never underestimate the power of human stupidity

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