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

    LAN Goes Dead During Boot

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    9 Posts 3 Posters 3.7k 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.
    • N
      NOYB
      last edited by

      …    --- LAN Interface starts responding.
      Confituring firewall…...done.
      Starting PFLOG... done.
      Setting up gateway monitors...done.
      Synchronizing user settings...done.
      Starting webConfigurator...done.
      configuring CRON...done.
      Starting OpenNTP time client...done.
      Starting DNS forwarder...done.
      Configuring firewall…...done.   --- LAN Interface stops responding.
      Generating RRD graphs...done.
      Starting CRON... done.
      Bootup complete

      8 ) Shell
      ifconfig de0 down
      ifconfig de0 up         --- LAN Interface starts responding again.
      exit

      This is a default RC3 installation.  No firewall rules have been created.
      Static LAN IP Address
      2.0 RC3 (Jun 22)
      i386

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

        Some kind of driver issue with that particular NIC. You can work around by putting the ifconfig down/up in <shellcmd>, and/or replicate and report upstream on stock FreeBSD to get a proper fix for a future version.</shellcmd>

        1 Reply Last reply Reply Quote 0
        • N
          NOYB
          last edited by

          Interfaces: LAN


          Speed and Duplex: Default (or left blank)
          LAN Interface either never comes up or dies after second firewall config during boot up.

          ifconfig de0
          media: Ethernet autoselect (100baseTX)

          Connected switch shows 100 Full Duplex (Auto)


          Speed and Duplex: autoselect
          LAN Interface either never comes up or dies after second firewall config during boot up.

          ifconfig de0
          media: Ethernet autoselect (100baseTX)

          Connected switch shows 100 Full Duplex (Auto)


          Speed and Duplex:t 100baseTX
          LAN Interface comes up and stayes up troughout boot up.

          ifconfig de0
          media: Ethernet 100baseTX

          Connected switch shows 100 Full Duplex (Auto)


          Speed and Duplex: 100baseTX full-duplex
          LAN Interface comes up and stayes up troughout boot up.

          ifconfig de0
          media: Ethernet 100baseTX <full-duplex>Connected switch shows 100 Full Duplex (Auto)

            • *</full-duplex>
          1 Reply Last reply Reply Quote 0
          • B
            Bill48105
            last edited by

            What build of pfsense? I had no LAN with RC1 with em0 driver if the cable was plugged into gigabit switch during bootup.  If i let it boot then plugged in cable it worked fine.  If I put a 100mbit switch in between it worked.  Upgraded to RC3 & the problem went away so I chocked it up to issue with RC1.
            Bill

            1 Reply Last reply Reply Quote 0
            • N
              NOYB
              last edited by

              Updated Original Post
              2.0 RC3 (Jun 22)

              1 Reply Last reply Reply Quote 0
              • B
                Bill48105
                last edited by

                Ahh so already on RC3. I know it's not a real fix but did you try booting up with cable unplugged & plugging it in after the console menu comes up?
                And realize not ideal but unless you have >100mbit internet connection might just keep it locked at 100mbit. ;)
                Bill

                1 Reply Last reply Reply Quote 0
                • N
                  NOYB
                  last edited by

                  @Bill48105:

                  Ahh so already on RC3. I know it's not a real fix but did you try booting up with cable unplugged & plugging it in after the console menu comes up?
                  And realize not ideal but unless you have >100mbit internet connection might just keep it locked at 100mbit. ;)
                  Bill

                  No, did not try booting with disconnected cable.  Not much point in that now that have it working.

                  The switch it's currently connected to only supports 10/100.  So yeah, it's locked at 100mbit for now.  That may change thoughh to a 1 gbps capable switch.

                  20/5 mbps Frontier (Verizon) FiOS

                  1 Reply Last reply Reply Quote 0
                  • B
                    Bill48105
                    last edited by

                    @NOYB:

                    No, did not try booting with disconnected cable.  Not much point in that now that have it working.

                    The switch it's currently connected to only supports 10/100.  So yeah, it's locked at 100mbit for now.  That may change thoughh to a 1 gbps capable switch.

                    20/5 mbps Frontier (Verizon) FiOS

                    Well the point it is help figure out the root cause of the problem especially if others run into it or if as you said down the road you want to do gigabit & can't because it wasn't resolved. ;)
                    Bill

                    1 Reply Last reply Reply Quote 0
                    • N
                      NOYB
                      last edited by

                      You've already provided that data point.

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