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

“Invalid WAN IP Address” error during Setup Wizard configuration using ISP-provided details

Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
static ipinvalid ipsetup
6 Posts 4 Posters 2.7k 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
    paanvaannd
    last edited by Jun 15, 2019, 2:11 PM

    • Hardware: SG-3100
    • OS: pfSense 2.4.4-RELEASE-p3

    I am following the directions provided on the “Getting Started” page for the SG-3100 manual. They worked well when using DHCP on a residential account, but I am having issues setting it up with a static IP now that I have migrated to such services with my ISP.

    • Primary / secondary DNS domains: what my ISP has provided me
    • WAN interface: Static
    • IP Address: xxx.0.yyy.72
    • Upstream Gateway: xxx.0.yyy.73
    • Subnet Mask: 255.255.255.248

    (Full IP addresses redacted... not sure about security practices on whether it’s advisable to give out the full address or not online.)

    Here is what is confusing me. My ISP tells me that the network mask is 255.255.255.248, which should translate to a CIDR range of “/29,” right? Upon selection of 29 as the Subnet Mask option and entry of the IP Address and Upstream Gateway as provided by my ISP, I get the following error:

    The following input errors were detected:

    • Invalid WAN IP Address. Please press back in the browser window and correct.

    I tried 32 as the Subnet Mask once by mistake and it let me continue... but there was no Internet connection after that. The Gateways status page showed the WANGW interface as offline with 100% loss.

    I have verified with my ISP that all of the information that I have from them is correct. I have power cycled the router and modem and reconnected them after a few minutes as generally recommended. I have verified with the ISP that the gateway is pinging properly on their end.

    Why is pfSense telling me that the data I have entered along with the proper (I assume) CIDR range constitutes an improper address? What can I do to resolve this issue? What other information or diagnostic steps would be helpful in fixing this issue?

    1 Reply Last reply Reply Quote 0
    • K
      kiokoman LAYER 8
      last edited by Jun 15, 2019, 9:29 PM

      @paanvaannd said in “Invalid WAN IP Address” error during Setup Wizard configuration using ISP-provided details:

      xxx.0.yyy.73

      i have this on one of my pfsense, maybe it work for you
      Interface - WAN
      wanstat.jpg

      ̿' ̿'\̵͇̿̿\з=(◕_◕)=ε/̵͇̿̿/'̿'̿ ̿
      Please do not use chat/PM to ask for help
      we must focus on silencing this @guest character. we must make up lies and alter the copyrights !
      Don't forget to Upvote with the 👍 button for any post you find to be helpful.

      1 Reply Last reply Reply Quote 0
      • J
        johnpoz LAYER 8 Global Moderator
        last edited by Jun 15, 2019, 11:21 PM

        .72/29 is the wire not the first host... Not good practice to use that IP..

        The first host on .72/29 would be .73 which would normally be ISP device where your IP would be .74

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.7.2, 24.11

        1 Reply Last reply Reply Quote 1
        • R
          Rico LAYER 8 Rebel Alliance
          last edited by Jun 16, 2019, 7:33 AM

          Exactly like johnpoz said.
          I have .48/28 where .49 is the ISP device and .50 to .62 is for my hosts.

          -Rico

          1 Reply Last reply Reply Quote 1
          • P
            paanvaannd
            last edited by paanvaannd Jun 17, 2019, 12:47 AM Jun 16, 2019, 6:52 PM

            Thank you all for the responses!

            What you mentioned makes perfect sense.

            I will try this out later today and update this comment with the results, but I expect using the next IP number up in the range as I should have done will indeed be the solution.

            e: Indeed, that was the solution!

            1 Reply Last reply Reply Quote 0
            • R
              Rico LAYER 8 Rebel Alliance
              last edited by Jun 19, 2019, 10:11 PM

              Glad you have it working now. ☺

              -Rico

              1 Reply Last reply Reply Quote 0
              6 out of 6
              • First post
                6/6
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                This community forum collects and processes your personal information.
                consent.not_received