pfSense router won't link after power off

  • I have custom "QOTOM-Q355G4 Pfsense Firewall Router Fanless Intel core I5 5200U" router connected to Sonic 1GB up-link

    I believe this router would re-link all interfaces after power outage before, before version 2.4.4. It was not the case today :( I had 8 hours long power outage, so my UPS ran out of juice.

    After power restored, I notice that my network was dead.

    I needed to find out if this was fiber problem or the router.
    Connected a laptop directly to the fiber box and it got connected immediately.

    So it pointed to the router problem.
    WAN and LAN Ethernet connections on the router had only yellow lights and no green.
    Tried reboot without success.

    So I suspected h/w failure. Took my router off, connected it to a display, keyboard and mouse and ... it booted up OK.

    I connected it back again and it initialized all interfaces fine.
    Then I, by mistake turned off UPS box, and observed all snafu again.

    The router would not re-initialize interfaces, and no green lights on ports. As soon as I cut power to fiber box - all ports started blinking green again.

    What was very annoying that I could not ssh to the router.

    As I mentioned, IIRC this used to work fine on version before 2.4.4


    1. Has anybody seen similar problems ?
    2. Is there any way to avoid this in the future by forcing some settings in pfSense?

    Thx in advance.

  • Netgate Administrator

    Those interfaces are just the NICs assigned directly? No PPPoE? No VLANs?

    I'm not aware of any issues affecting 2.4.4 if so. What does the system log show when it powers but does not link?

    What does ifconfig show?


  • No PPPoE and No VLANs
    NICs assigned directly.

    Below is my ifconfig output -
    And system log -
    (not sure how to read it)

    I think above this line:
    Nov 29 08:37:43 syslogd kernel boot file is /boot/kernel/kernel
    is when power was restored.

    Thx for looking.

  • @stephenw10 did you see anything interesting ?

  • Looks like you have additional packages. Snort maybe?

    What’s with those arp log entries?

  • @bbrendon
    what type of logs would you like to see ?

    how snort can prevent successful re-initializing interfaces linking after power off?

  • Netgate Administrator

    Which interfaces are which there? igb0-2 show as active with a 1Gbps link using auto-select. Only igb3 is down there.

    The system logs are hard to read with all that Snort messaging but they too show igb0 (which looks like WAN) coming up:
    Nov 29 08:47:48 kernel igb0: link state changed to UP

    What does the lack of a green LED signify on that box?

    Where are you actually seeing the interfaces as not linked?


  • @stephenw10

    "WAN and LAN Ethernet connections on the router had only yellow lights and no green."

  • Netgate Administrator

    Yes I read that but what do those LEDs mean on that box?

    The link appears to be UP so maybe green is just data?

    Is the lack of green LED the only place you see the link as down?


  • @stephenw10
    The way I observed it , when only yellow lights are on and green is not, WAN was not linked (if this is right term), was not assigning IPs and was not assignable via ssh.

    And I saw that after 2 soft and hard reboots.

  • Netgate Administrator

    Presumably the yellow LED comes on when you connect the cable? That is more likely to be LINK. The green LED may indicate 1Gbps. Or it may flash for data. Or both.

    Run ifconfig at the console when it is in that state. I assumed that's what you posted above but if that's the case it is linked fine.


  • @stephenw10

    That's not easy. I have to connect display in order to do so, but then I can't connect to 1GB cable.

    (wish it had IPMI)

  • Netgate Administrator

    Well we need to see what it's actually failing to do. The output you posted above looks like there is no problem.


Log in to reply