The gateway address does not lie within one of the chosen interfac

  • Hi I receive the above message when I go to :

    System> Routing > Gateways > Edit

    And try to save my config.

    The interface in question is:

    Clearly is in the chosen subnet.

    If I add the gateway from Interfaces > interface name it will save but if I visit  System> Routing > Gateways > Edit and save the gateway the error reoccurs.

    Can anyone suggest a fix?

  • LAYER 8 Global Moderator

    So what interface is this on?

    I have created a vlan with that interface - and it lets me create the gateway.

    What version of pfsense are you running?
    Do you have any other interfaces that might overlap?

    I see an error when I try and add it from the interface page - but if go to routing an add it works just fine.  I am running 2.4 beta built on Mon Apr 03 09:02:25 CDT 2017

  • Hi Johnpoz

    2.3.3-RELEASE-p1 (amd64)

    The interface is em1

    I'm pretty sure the other interfaces do not overlap.

    WAN_VIRGIN 1000baseT <full-duplex>82..X.X.X
    LAN 1000baseT <full-duplex>
    WAN_COUNCIL autoselect



  • LAYER 8 Global Moderator

    what is the mask on the lan?

    Did you try it from the routing tab vs just adding it from the interface.. It works there.  If failing from the add on the interface we can file a bug report in redmine.

  • Its a /24

    The frustrating thing is that I'm using pfsense to replace 2 old dlink's running tomato, where this config JFW.

  • LAYER 8 Global Moderator

    And it JFW when you do it from the actual place your suppose to do it from as well.. ;)

    Add it from the actual place your suppose to add gateway from vs the shortcut in the interface that only calls up a small portion of the form for adding a gateway.  It is possible there is something wrong with that shortcut form.

    As you can see I was able to add exact same gateway..  BTW /22 is Fing huge transit.. Is this really a public IP your getting from your ISP and your replacing it with a rfc1918 address to obfuscate it?  Or does your isp use rfc1918 space for its customers.. I find it hard to believe that a /22 would be used in a private network setting as a transit network..

    Once we have you up and running we can check redmine for any current reports of this with the shortcut form of adding a gateway or report it after validation and or others chiming in that they too are seeing the problem.. I have seen it from the shortcut form give an error but I am running beta.. I can fire up a 2.3.3p1 instance and validate it there, etc.

  • "And it JFW when you do it from the actual place your suppose to do it from as well.. "
    I beg to differ but it doesn't!

    Its a WAN connection from our local municipal council who do use an RFC1918 to deliver an IP to us :-(

    ![Screenshot from 2017-04-04 14:25:29.png](/public/imported_attachments/1/Screenshot from 2017-04-04 14:25:29.png)
    ![Screenshot from 2017-04-04 14:25:29.png_thumb](/public/imported_attachments/1/Screenshot from 2017-04-04 14:25:29.png_thumb)

  • LAYER 8 Global Moderator

    And as you saw in my post it does.  I have setup multiple gateways like this multiple times and never any issues.

    So you are only showing this

    WAN_COUNCIL      autoselect

    That doesn't say what the MASK is.. You sure its not set to /32 which the drop down defaults too when adding an interface IP.  Double check the mask on your interface.  And then try to add your gateway.

  • its set to /22.

    ![Screenshot from 2017-04-06 07:39:45.png](/public/imported_attachments/1/Screenshot from 2017-04-06 07:39:45.png)
    ![Screenshot from 2017-04-06 07:39:45.png_thumb](/public/imported_attachments/1/Screenshot from 2017-04-06 07:39:45.png_thumb)

  • Darn it I found the problem!

    I had entered a VIP on the interface with a netmask of /24! Doh!

    I've removed that and am now somewhere nearer getting it all working.

    Thanks for the help.


Log in to reply