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

    Need Help, set up Wizard did not complete!

    Scheduled Pinned Locked Moved General pfSense Questions
    10 Posts 4 Posters 750 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.
    • R
      Rogerthat
      last edited by

      Hello,

      I am setting up my Netgate 2100 for the first time and when I reloaded the configuration at the end of the Set up Wizard, nothing ever happened and the screen did not return to the Dashboard as it was supposed to. I also cannot access WebGUI, browser says unable to connect.

      Please help, thank you!

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        Did you change the LAN subnet during the wizard? If so you would need to force the client to pull a new dhcp lease from pfSense. Usually easiest to just replug the cable to do that.

        Steve

        R 1 Reply Last reply Reply Quote 0
        • R
          Rogerthat @stephenw10
          last edited by

          @stephenw10 Thanks for replying ..

          I ran the set up wizard again to complettion however, this time WAN and LAN ended up on the same subnet, and I do know that shouldn't be.

          How would I fix that?

          GertjanG 1 Reply Last reply Reply Quote 0
          • GertjanG
            Gertjan @Rogerthat
            last edited by Gertjan

            @Rogerthat said in Need Help, set up Wizard did not complete!:

            How would I fix that?

            Tell us why !
            So I look in my glass boll and see this "you kept the LAN settings to default = 192.168.1.1/24 and you kept WAN settings on DHCP" and now you discover that your upstream ISP router also uses 192.168.1.1/24 on its own LAN, so pfSense obtains a 192.168.1.x on its WAN and that ... is "router admin final exam question number one : 👎 for you ( it happened all of us ones - every router you buy mostly uses 192.168.1.1/24 as the default LAN network, pfSense is no exception ).

            Am I right ?
            If so, you have an important decision to make :
            Change the pfSense to RFC1918 (whatever) 192.168.2.1/24 and don't forget to change also DHCP LAN server settings accordingly.
            Or
            Connect to your ISP upstream router, change it's LAN network to (some nice RFC1918) : 192.168.10.1/24

            Something else ?

            No "help me" PM's please. Use the forum, the community will thank you.
            Edit : and where are the logs ??

            R 1 Reply Last reply Reply Quote 0
            • R
              Rogerthat @Gertjan
              last edited by

              @Gertjan thanks for your reply .. But here is the problem

              I already knew that my ISP default IP was the same as pfsense default IP, and I followed the instructions of the Netgate 2100 manual for changing the pfsense default IP during the set up wizard. However, when I do that (change to 192.168.2.1/24 during set up), the WebGUI becomes immediately inaccessable at the changed IP address.

              So then I factory reset the 2100, re-run the set up Wizard without changing the default IP, and the set up completes. But now there is a conflict between WAN and LAN. Then when I try to change the LAN IP from the interface post set up, the WebGUI once again becomes unreachable, so I can't then change the DHCP server settings!

              None of the instructions provided in the 2100 manual work as instructed during the set up wizard! Working from the console is not an option because I am on Mac and don't know how to use terminal to install necessary drivers and such to make console operable. :(

              Bob.DigB GertjanG 2 Replies Last reply Reply Quote 0
              • Bob.DigB
                Bob.Dig LAYER 8 @Rogerthat
                last edited by

                @Rogerthat said in Need Help, set up Wizard did not complete!:

                Then when I try to change the LAN IP from the interface post set up, the WebGUI once again becomes unreachable, so I can't then change the DHCP server settings!

                Then don't use DHCP.

                1 Reply Last reply Reply Quote 0
                • stephenw10S
                  stephenw10 Netgate Administrator
                  last edited by

                  You can change the LAN subnet and save but not apply. Then update the dhcp server settings. Then apply the interface change.

                  Or rerun the wizard that does that for you.

                  R 1 Reply Last reply Reply Quote 1
                  • GertjanG
                    Gertjan @Rogerthat
                    last edited by

                    In complement to the solution mentioned above :

                    @Rogerthat said in Need Help, set up Wizard did not complete!:

                    Working from the console is not an option because I am on Mac and don't know how to use terminal to install necessary drivers and such to make console operable. :(

                    The console access is not some gadget for nerds.
                    You need to have this one operational. Connecting to the USB Console Port, select MacOS, goto Downloads, select the MAcOSx driver ZP package, download it, install it.

                    Why , Because the day you have an 'network interface problem' you can't hook up a screen and a keyboard, there will be only the serial USB port to work with.
                    You'll see, it is feasible.

                    No "help me" PM's please. Use the forum, the community will thank you.
                    Edit : and where are the logs ??

                    R 1 Reply Last reply Reply Quote 1
                    • R
                      Rogerthat @stephenw10
                      last edited by

                      @stephenw10 Yes, I should have thought of that first. I ended up changing the IP on my ISP and re running the set up, and I am up and running now. Thanks for replying.

                      1 Reply Last reply Reply Quote 1
                      • R
                        Rogerthat @Gertjan
                        last edited by

                        @Gertjan You are 100% correct, and I am on it!

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