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

    No access Web Interface when set ip on lan

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    7 Posts 3 Posters 9.9k 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.
    • C
      cleriston
      last edited by

      I am running PFSense 2.0 on VirtualBox in Ubuntu.
      The interface Wan with IP via DHCP.
      When I set the ip on the Lan interface can no longer access PFSense via the web interface.
      Where am I wrong?

      1 Reply Last reply Reply Quote 0
      • W
        wallabybob
        last edited by

        @cleriston:

        When I set the ip on the Lan interface can no longer access PFSense via the web interface.

        How did you access the pfSense web interface BEFORE you set the LAN IP address? Through which interface and using what IP address?

        How did you attempt to access the pfSense web interface AFTER you set the LAN IP address? Through which interface and using what IP address?

        It is often (maybe even always) necessary to restart the webconfigurator (menu item 11 in the console menu) after changing the LAN IP address.

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

          How did you access the pfSense web interface BEFORE you set the LAN IP address? Through which interface and using what IP address?

          Yes! I can access Web Interface Throug which wan interface with Wan Ip 192.168.56.101 (Given by VirtualBox via DHCP)

          How did you attempt to access the pfSense web interface AFTER you set the LAN IP address? Through which interface and using what IP address

          Through of both address. Wan 192.168.56.101 and Lan 192.168.5.1

          It is often (maybe even always) necessary to restart the webconfigurator (menu item 11 in the console menu) after changing the LAN IP address.

          I tried using the option 11 but continued with the same problem.

          I do not have this network 192.168.5.255.
          I just wanted to test the options pfsense II and with this I need to set a Lan.

          For now thanks for help

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

            I believe that once you enable the LAN interface management traffic is blocked on the WAN interface.

            If you don't have a computer on the LAN network that you can manage pfSense from, you will need to create a firewall rule on the WAN interface before you enable your LAN that will accept TCP traffic on ports 443 (or 80 or 22 depending on how you manage your firewall).

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

              PJ2 thanks for your help, but by default the rule already exists with description "Anti-Lockout Rule"

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

                Yes - that rule moves to the LAN interface when the LAN is enabled.  You will need to create a manual rule on the WAN interface if you want it to apply after you enable the LAN.

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

                  PJ2 Thank you!

                  It Worked!

                  I create the rule accepting everything in the wan interface
                  After I enabled Lan Interface I remove "Anti-Lockout Rule" in the Lan Interface!

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