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

    Can't connect to the Pfsense Web GUI when Wan is plugged in

    Scheduled Pinned Locked Moved webGUI
    2 Posts 2 Posters 677 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.
    • W
      wizencrowd
      last edited by

      Hello

      For a school project I need to configure a server with pfsense. We want to use it as a captive portal. My problem is that I can't get in the WebGUI when I have my Wan connection plugged in. When I freshly booted my server I need to unplug the wan cable, then I can login in pfsense. After that I can plug the wan cable back in an everything works. Do you guys now How i can fix this? When I booted the server I don't have internet, but when I login in pfsense I get internet.

      Some info that might be usefull:

      • Lan IP : 192.168.1.100

      • Wan IP : 192.168.1.103 (DHCP)

      Hope you guys can help!
      Thank you!

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

        @wizencrowd:

        For a school project I need to configure a server with pfsense. We want to use it as a captive portal. My problem is that I can't get in the WebGUI when I have my Wan connection plugged in.

        What ??
        (but you explain why afterwards …)

        When I freshly booted my server I need to unplug the wan cable, then I can login in pfsense. After that I can plug the wan cable back in an everything works. Do you guys now How i can fix this? When I booted the server I don't have internet, but when I login in pfsense I get internet.

        @wizencrowd:

        Some info that might be usefull:

        • Lan IP : 192.168.1.100

        • Wan IP : 192.168.1.103 (DHCP)

        Thanks for the info.
        You totally broke one of the most important rules when it comes routing.
        KEEP LAN on 192.168.1.1/24
        Make WAN something 192.168.2.1/24 or 10.0.0.1/16 but NOT in the 192.168.1.1.1/24 segment.
        IF your WAN needs to be in 192.168.1.0/24 then make your LAN (example) 192.168.2.1/24

        Remember : your are operating a router/firewall, not a switch.

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

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