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

    LAN Connectivity Issues on amd64-20140423-1356 Build?

    2.2 Snapshot Feedback and Problems - RETIRED
    3
    6
    1.4k
    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
      asayler
      last edited by

      I just upgraded my test system (Lanner FW-7551, https://forum.pfsense.org/index.php?topic=74995) from one of the x64 2.2 alpha snapshots from last week (I believe one from 4/14/14) to today's snapshot (20140423-1356). After doing so and rebooting, the LAN interface seems to have stopped properly handling connections from my machine. On the older snapshot, everything (that I tested) was working fine.

      I have the LAN interface setup to provide DHCP for 193.168.3.1/24. But when I connect to the LAN interface from my desktop (direct connection, no switch, etc) and make a DHCP request, the request never properly completes. When I set a static address on my desktop (e.g. 192.168.3.3), I can neither ping nor access the web interface at 192.168.3.1. There does seem to be some connectivity: when I dump the DHCP logs from pfSense (via a serial terminal) I see the connection attempts:

      [2.2-ALPHA][root@eagle.nest]/root(12): tail /var/log/dhcpd.log
      Apr 23 22:21:36 eagle dhcpd: DHCPACK on 192.168.3.200 to 58:6d:8f:b4:38:2c (raptor) via igb2
      Apr 23 22:21:38 eagle dhcpd: DHCPREQUEST for 192.168.3.200 from 58:6d:8f:b4:38:2c (raptor) via igb2
      Apr 23 22:21:38 eagle dhcpd: DHCPACK on 192.168.3.200 to 58:6d:8f:b4:38:2c (raptor) via igb2
      Apr 23 22:21:42 eagle dhcpd: DHCPREQUEST for 192.168.3.200 from 58:6d:8f:b4:38:2c (raptor) via igb2
      Apr 23 22:21:42 eagle dhcpd: DHCPACK on 192.168.3.200 to 58:6d:8f:b4:38:2c (raptor) via igb2
      Apr 23 22:21:51 eagle dhcpd: DHCPDISCOVER from 58:6d:8f:b4:38:2c (raptor) via igb2
      Apr 23 22:21:51 eagle dhcpd: DHCPOFFER on 192.168.3.200 to 58:6d:8f:b4:38:2c (raptor) via igb2
      Apr 23 22:21:55 eagle dhcpd: DHCPDISCOVER from 58:6d:8f:b4:38:2c (raptor) via igb2
      Apr 23 22:21:55 eagle dhcpd: DHCPOFFER on 192.168.3.200 to 58:6d:8f:b4:38:2c (raptor) via igb2

      The activity light on the LAN interface is blinking quickly, even when no (apparent) traffic is being generated by my machine. ifconfig shows the links up and physically connected on both ends.

      Maybe incoming traffic (to pfsense) is working fine, but all the outgoing traffic is being dropped?

      The WAN interface still seems to be working fine: I can ping the internet from it, etc. But the LAN interface certainly has issues: no ping, no http, no dhcp, etc.

      I've only tried the upgrade from the older snapshot at this point. I haven't tried a fresh amd64-20140423-1356 install.

      Any one else having issues with the amd64-20140423-1356 snapshots and LAN connectivity?

      Anything else I can provide to be more helpful? I can pull out wireshark, etc if need be. Or provide additional logs (although a quick glance didn't see anything obvious in the normal logs).

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

        I upgraded from the last snap to today's just now and LAN works ok. However, your issue sounds quite a bit like the one I had a few days ago (https://forum.pfsense.org/index.php?topic=74793.msg412613#msg412613) which I attributed to a broken network card. Perhaps it wasn't broken after all?

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

          @Fegu:

          I upgraded from the last snap to today's just now and LAN works ok. However, your issue sounds quite a bit like the one I had a few days ago (https://forum.pfsense.org/index.php?topic=74793.msg412613#msg412613) which I attributed to a broken network card. Perhaps it wasn't broken after all?

          I tested the issue on multiple interfaces (both setup as LAN and OPT) and had teh issue on any interface that wasn't assigned to WAN. All of these interfaces were fine a day ago. I doubt it's a hardware issue.

          If anyone wants me to gather more data, give a shout. Otherwise I'll blow the system away this weekend and try a fresh reinstall from one of the latest snapshots.

          Maybe jumping forward a weeks worth of snaps and using an upgrade install threw something off…

          1 Reply Last reply Reply Quote 0
          • O
            ozlecz
            last edited by

            any further testing done..fresh install etc..was planning to buy same box

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

              I haven't had a chance to test again in the last few weeks, but I'm hoping to try out both the latest 2.1 and teh latest 2.2 builds next week. I'm assuming a fresh install would work fine. I'll update you once I've had a chance to give it a go again.

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

                Sorry it's taken awhile for me to get back to this…

                I'm using the latest 2.2 snapshots (from a fresh install) and they seem to be working fine. No idea what happened before,  but must have been an upgrade-related fluke in a much older build.

                A 2.1 fresh install still works fine off USB but hangs when trying to boot to hard disk. So I'll stick with 2.2 on this hardware for now.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post