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

    WAN configuration change stops access to WEB GUI

    Scheduled Pinned Locked Moved General pfSense Questions
    10 Posts 2 Posters 267 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.
    • U
      unsichtbarre
      last edited by

      Howdy,
      If I disable the WAN interface and/or set IP configuration to "none" and then apply, I immediately loose access to the web GUI.

      Is this known/normal? pfSense 2.7.2 fully updated.

      THX,
      -John

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

        How are you connected to it? What does the console show?

        Steve

        U 1 Reply Last reply Reply Quote 0
        • U
          unsichtbarre @stephenw10
          last edited by

          @stephenw10 console continues to show both WAN and LAN IP, connecting to LAN but if I disable WAN or change IP configuration to "none" it stops all connectivity to LAN.

          THX,
          -JB

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

            So you can't even ping the LAN interface address?

            Can you ping out from pfSense to the LAN client?

            If you revert that change o you're able to connect what do the logs show?

            U 1 Reply Last reply Reply Quote 0
            • U
              unsichtbarre @stephenw10
              last edited by

              @stephenw10 no ping. I have not tried reverting, however, re-assigning the WAN IP gets the LAN back online.

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

                So no ping in either direction? What error is shown when you try to ping out?

                The only way I can imagine this happening is if the LAN is somehow conflicting with the WAN but it's hard to see how that could happen unless it's a sub interface of some sort.

                U 1 Reply Last reply Reply Quote 0
                • U
                  unsichtbarre @stephenw10
                  last edited by

                  @stephenw10 WAN is a dedicated interface, LAN has a VLAN

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

                    But LAN is not a VLAN on WAN?

                    Try to ping out from LAN when WAN is down, what error is shown?

                    U 1 Reply Last reply Reply Quote 0
                    • U
                      unsichtbarre @stephenw10
                      last edited by

                      @stephenw10 Not a VLAN on WAN. Did not try to ping out from LAN while offline. Ping in shows "destination host unreachable"

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

                        That implies the client cannot ARP for the IP. That could be because the LAN stops responding entirely but no way to be sure without more tests.

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