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

    First Setup Wizard default IP

    Scheduled Pinned Locked Moved
    2.4 Development Snapshots
    2
    5
    945
    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.
    • N
      nelioromao
      last edited by

      Wend change the default ip 192.168.1.1 to samething else on the first run of the web wizard the IP is not change.

      2.4.0-BETA (amd64)
      built on Sat Apr 15 02:21:01 CDT 2017
      FreeBSD 11.0-RELEASE-p8

      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        It works for me in a VM.
        What special or interesting environment do you have?
        Exactly what are you entering in the wizard?

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • N
          nelioromao
          last edited by

          I am using a VirtualBox. With 1 Hostonly network and one bridge network cart (2 virtual networks)

          Wend the setup finish i open the browser 192.168.1.1

          Then i start the wizard for complete the setup, Wend show the default ip
          i change to 192.168.200.254 and then wend finish i try to login/ping and nothing happens.

          Than i look ate the console on the VM and the default ip was the same, have been not change.

          1 Reply Last reply Reply Quote 0
          • P
            phil.davis
            last edited by

            Did you wait a minute and press enter on the console to refresh the menu?
            You also need to change your client IP in LAN into the new LAN subnet (or release/renew the client DHCP so it gets a new IP address in the new subnet), so that it will learn the new gateway IP and be able to find/connect to the webGUI at the new LAN IP address.

            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

            1 Reply Last reply Reply Quote 0
            • N
              nelioromao
              last edited by

              | Did you wait a minute and press enter on the console to refresh the menu? |

              No i didn't wait a minute. maybe that was the problem.

              | You also need to change your client IP in LAN into the new LAN subnet (or release/renew the client DHCP so it gets a new IP address in the new subnet), so that it will learn the new gateway IP and be able to find/connect to the webGUI at the new LAN IP address.
              |

              Yes a have done that.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post