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

    Can't Connect On Reboot

    General pfSense Questions
    2
    6
    1.1k
    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
      clevoir
      last edited by

      I have just setup pfSense on an Intel Atom dual core motherboard, with 2 NIC interfaces

      I have WAN set up as DHCP and LAN as fixed IP.

      With both inferfaces connected, after pfSense has sucessfull booted I can't get a connection to the GUI or the internet.

      The only round this is to disconnect the WAN connection, then on reboot I can see the GUI using the fixed IP address.

      I then connect the WAN connection (to an ASDL router), and once a DHCP ip address has been allocted I can then access the GUI and the internet

      Why can't I simply be able to reboot with both WAN and LAN interfaces connected?

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

        What ip addresses and subnets are you using? You might have a subnet conflict if the WAN isn't using a public IP.

        Steve

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

          Thanks for your reply, I am using the same subnet on WAN and LAN

          LAN is fixed 192.168.1.200

          WAN is DHCP, but I have set the DHCP allocation on the  ADSL router to between 192.168.1.250 and 192.168.1.255

          The gateway on the ADSL router is 192.168.1.1

          I guess that I really should have the WAN and LAN on seperate subnets, but the ADSL router is already carrying out NAT between the ISP and it's LAN ports

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

            Yep. In its default configuration, routing/NATing, pfSense must have a different subnet on each interface. Overlapping subnets on different interfaces breaks routing as you've found.
            Just set the pfSense LAN to something difference like 192.168.100.1/24 for example.
            In the long term it's preferable to have your dsl modem bridge your public IP to the pfSense WAN so you're not double NATing.

            Steve

            Edit: Typo

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

              Thanks, I am new to this and still getting my head around it :)

              As I have currently have the same subnets for LAN and WAN, could this also be the cause of my problems at the bottom of this post?

              https://forum.pfsense.org/index.php?topic=29944.135

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

                Possibly if there's still some conflict. I don't see anything immediately so I'd guess at some openvpn problem.

                Steve

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