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

    Pfsense Initial Setup Lan Issue

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    14 Posts 4 Posters 19.8k 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.
    • A
      analyzethat
      last edited by

      I cannot show you the pfsense interfaces because I cannot access the webgui, because I cant communicate with LAN. So as you said, I plugged my PC into the LAN in pfsense, and manually assign (because DHCP is not working apparently) and IP in the same subnet as my lan, using the same mask, and the LAN IP as the gateway. I still cannot ping the LAN ip, or access the webgui. ARP table shows nothing for pfsense. I did a little troubleshooting from the pfsense box itself, which yielded something interesting.

      First, I pinged my mode, which worked fine.
      Then I pinged Google (8.8.8.8), that worked no problem.
      Then I pinged my LAN IP which worked fine.
      Then I tried pinging the PC that is connected to LAN, and the system kernel panicked.
      So I tried again… same result. Anytime I try to ping through the LAN interface, a kernel panick... I hope someone has an idea :(

      1 Reply Last reply Reply Quote 0
      • A
        analyzethat
        last edited by

        another update… apparently the interface was not going up by default so I had to "ifconfig re1 up"
        and after that, there was no inet address so I had to "ifconfig re1 172.16.0.1 up"

        still does not work though.

        1 Reply Last reply Reply Quote 0
        • A
          analyzethat
          last edited by

          Im starting to think I have an unsupported NIC (DLink DGE-530T) and this can't be resolved, which is awesome.

          1 Reply Last reply Reply Quote 0
          • A
            analyzethat
            last edited by

            I can now ping my PC on LAN subnet without kernel panic…

            1 Reply Last reply Reply Quote 0
            • A
              analyzethat
              last edited by

              I can now ping anything on the LAN subnet from the pfsense box, but not the pfsense box from the LAN subnet.

              My arp table is as follows:

              
              C:\Users\Aaron>arp -a
              
              Interface: 169.254.18.215 --- 0x13
                Internet Address      Physical Address      Type
                224.0.0.22            01-00-5e-00-00-16     static
                224.0.0.252           01-00-5e-00-00-fc     static
              
              Interface: 169.254.217.52 --- 0x14
                Internet Address      Physical Address      Type
                224.0.0.22            01-00-5e-00-00-16     static
                224.0.0.252           01-00-5e-00-00-fc     static
              
              Interface: 172.16.0.37 --- 0x2f
                Internet Address      Physical Address      Type
                172.16.0.1            90-94-e4-5f-55-85     dynamic
                172.16.255.255        ff-ff-ff-ff-ff-ff     static
                224.0.0.22            01-00-5e-00-00-16     static
                224.0.0.252           01-00-5e-00-00-fc     static
                255.255.255.255       ff-ff-ff-ff-ff-ff     static
              
              C:\Users\Aaron>
              
              1 Reply Last reply Reply Quote 0
              • A
                analyzethat
                last edited by

                172.16.0.1 is the pfsense LAN IP, and that is the correct Mac address for it, but I still can't access the web-interface

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

                  @analyzethat:

                  Im starting to think I have an unsupported NIC (DLink DGE-530T) and this can't be resolved, which is awesome.

                  What is the FreeBSD device name for your LAN device? (displayed by shell command```

                  /etc/rc.banner

                  
                  What version of pfSense are you using?
                  
                  Your arp table shows entries in the 172.16.0.37/x subnet but your pfSense LAN IP address is 192.168.1.1.  How does the system whose arp table you displayed get to the pfSense LAN interface?
                  1 Reply Last reply Reply Quote 0
                  • A
                    analyzethat
                    last edited by

                    Sorry, my pfsense LAN IP is not 192.168.1.1 anymore, i had modified it to 172.16.0.1 for later avoidance of VPN issues. I thought I had mentioned that but must have forgotten.  I am running the beta version as this was the only version to even detect my NIC. The LAN device is labeled "usbus0"

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

                      @analyzethat:

                      Sorry, my pfsense LAN IP is not 192.168.1.1 anymore, i had modified it to 172.16.0.1 for later avoidance of VPN issues.

                      Did you reboot after changing the LAN IP address. It has been my experience that a reboot seemed to me necessary after changing subnet of interface.

                      @analyzethat:

                      I am running the beta version as this was the only version to even detect my NIC. The LAN device is labeled "usbus0"

                      So you are using a GigE device for your WAN interface and a USB NIC for your LAN? Strange choice! It is  while since I used a USB NIC, but I have a recollection the device name of USB NIC was something like ue0, udav0 etc not a name of an I/O bus. Please post the output of pfSense command```

                      ifconfig

                      1 Reply Last reply Reply Quote 1
                      • A
                        analyzethat
                        last edited by

                        Resolved…
                        added hw.usb.no_pf=1 to loader.conf file. The issue was with my interface being given two names by pfsense, and neither being configurable.

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