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

    can not access pfsense via lan

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 2 Posters 2.2k 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.
    • G
      genfoch01
      last edited by

      i just installed pfsense 2.4.5 CE
      I added the lan /wan interfaces then added a lan ip on the lan interface.

      however, i am not able to access the web ui via http or https

      from the pfsense console i can see the lan interface does have the ip i gave it. i can also see it has a link light.
      i can also ping machines on the lan from the pfsense console but can not ping the pfsense machine from those machines.

      my first thought was i had somehow switched the wan/lan interfaces so i disabled the firewall with pfctl -d but still am not able to access the web ui.

      any thoughts would be helpful.
      Thanks for your time.

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

        @genfoch01 said in can not access pfsense via lan:

        somehow switched the wan/lan interfaces so i disabled the firewall with pfctl -d

        Switching the two RJ45 from WAN <=> LAN would have been much faster ;)

        What will always work :
        The device you are using uses default network settings - the one it had when you bought it ? If it's set up using DHCP, it will ask on it's 'LAN' for an IP/gateway/mask/DNS.
        Did you use the default DHCP server setup on pfSense ? Did you setup up a pool with IP's ?
        So, check you device : did it receive these 4 (four !!) items ?
        Like 192.168.1.100 as the IP /24 for the mask, and 192.168.1.1 as the gateway AND the DNS.
        (these default values are sooooooo perfect)

        What has been tested, and known to fail right away :
        Setting up a LAN IP on pfSense with a mask of /32 which means : this LAN has ONE IP, and pfSense is using it. The DHCP server can't work any more. The mask should be something like /24.
        Next-best (worst) is : using a device with some static IP setting that inhibits network functionality.
        Broken network cables and switches are also popular.

        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
        • G
          genfoch01
          last edited by

          Hey, thanks for the response let me give more info
          some may be superfluous but you never know.

          the lan i set up was 192.168.1.2 / 24 with no gw i left the WAN set up blank ( by default it uses dhcp ) but it was not connected as i wanted to configure pfsense before i connected it to the wan

          with the lan ip applied and without the pfsense dhcp enabled (so it would not clash with my current dhcp server which this new build is going to replace) i wanted to connect to the web ui and configure everything then swap the WAN connection over and everything would work just fine.
          but I can't get access to the web ui even though i can see the correct interface has the correct ip and a link and is "up" (ifconfig from the shell ). i can see the link light on my switch and i can ping stuff on my network from the pfsense machine but can't ping the pfsense machine from any machine on my network. I also tried ssh ( enabled ssh on pfsense ) but could not make an ssh connection either . if i could not ping out, i'd think the nic was dead but i can so i'm not sure what the heck is going on.

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

            @genfoch01 said in can not access pfsense via lan:

            but it was not connected as i wanted to configure pfsense before i connected it to the wan

            Hummm. Not really needed - except if you hooked up devices on its LAN that you do not trust at all.
            And worse : I can happens that you access the GUI with big delays (2 minutes) if the WAN is down.

            Why skipping 192.168.2.1 ?

            You did set up the DHCP server on LAN, right ?

            remove switch from LAN, hook up your PC directly.
            Set the device using manual IP settings like :
            IP = 192.168.1. mask 255.255.225.0 or /243
            Now you can - should be able - to ping 192.168.1.2 - and connect to the GUI on 192.168.1.2

            or, if you're sure the pfSense DHCP server on LAN is set up correctly, connect your PC to pfsense and it will obtain an IP in the 192.168.1.x-y range - the range is the pool of the DHCP server.

            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.