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

    The gateway address does not lie within the chosen interface's subnet.

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    5 Posts 4 Posters 10.8k 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.
    • D
      Darkk
      last edited by

      I haven't touched DHCP in ages

      Current build: 2.0-RC3 (i386)
      built on Fri Jul 8 19:24:31 EDT 2011

      When editing the LAN's DHCP I get this error:

      The following input errors were detected:

      The gateway address does not lie within the chosen interface's subnet.

      I normally leave the gateway entry blank as I figured it will pull the default gateway info on it's own.   Has this changed?  For now I put in the gateway IP and working fine.

      This happened when I was trying to add a static IP mapping which brought me to that error on the page.

      Thanks,
      Darkk

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

        That was fixed earlier today, new input validation that overlooked that.

        1 Reply Last reply Reply Quote 0
        • M
          Metu69salemi
          last edited by

          Aha,

          I had the same which we discussed in here:http://forum.pfsense.org/index.php/topic,38733.0.html
          I'll update and check that behavior again. Sorry for hijacking this topic.

          1 Reply Last reply Reply Quote 0
          • F
            fthomasr
            last edited by

            Yeah I got this today just before shipping my first 2.0 nano alix router out. Freaked me out because I was under the gun to ship it out and when I got it I quadrupled checked my subnet over and over. Thanks for this thread! I just set the gateway IP so I could get it out the door. I guess I can update it to the latest snapshot once it goes live. I'm assuming today's snapshot has it resolved?

            1 Reply Last reply Reply Quote 0
            • D
              Darkk
              last edited by

              Yes today's snapshot fixed this issue.  Thanks everybody!!

              Darkk

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