Hotplug event detected - Driving me crazy



  • Hi all,

    I was wondering if you can help me. I am having frequent  "Hotplug event detected" for both my interfaces (lan and wan) and it is driving me crazy, I am almost giving up on pfense.

    Here are the system logs:

    Time Process PID Message
    May 16 06:03:41 php-fpm 13153 /index.php: Successful login for user …
    May 16 03:05:00 check_reload_status Reloading filter
    May 16 03:05:00 php-fpm 65340 /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.168.0.254 )
    May 16 03:04:58 kernel bge0: link state changed to DOWN
    May 16 03:04:58 check_reload_status Linkup starting bge0
    May 16 02:10:16 check_reload_status Reloading filter
    May 16 02:10:16 php-fpm 10340 /rc.newwanip: rc.newwanip: on (IP address: 192.168.0.254) (interface: LAN[lan]) (real interface: bge0).
    May 16 02:10:16 php-fpm 10340 /rc.newwanip: rc.newwanip: Info: starting on bge0.
    May 16 02:10:15 check_reload_status Reloading filter
    May 16 02:10:15 check_reload_status rc.newwanip starting bge0
    May 16 02:10:15 php-fpm 10340 /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.168.0.254 )
    May 16 02:10:14 kernel bge0: link state changed to UP
    May 16 02:10:14 check_reload_status Linkup starting bge0
    May 16 01:01:10 php-cgi rc.dyndns.update: ….
    May 15 23:43:55 check_reload_status Reloading filter
    May 15 23:43:55 php-fpm 10340 /rc.linkup: Hotplug event detected for LAN(lan) static IP (192.168.0.254 )
    May 15 23:43:54 kernel bge0: link state changed to DOWN
    May 15 23:43:54 check_reload_status Linkup starting bge0

    May 15 15:42:39 php-fpm 94503 /rc.newwanip: rc.newwanip: on (IP address: 192.168.25.101) (interface: WAN[wan]) (real interface: re0).
    May 15 15:42:39 php-fpm 94503 /rc.newwanip: rc.newwanip: Info: starting on re0.
    May 15 15:42:38 check_reload_status Reloading filter
    May 15 15:42:38 check_reload_status rc.newwanip starting re0
    May 15 15:42:38 php-fpm 94503 /rc.linkup: Hotplug event detected for WAN(wan) static IP (192.168.25.101 )
    May 15 15:42:37 php-fpm 94503 /rc.linkup: Hotplug event detected for WAN(wan) static IP (192.168.25.101 )
    May 15 15:42:37 kernel re0: link state changed to UP
    May 15 15:42:37 check_reload_status Linkup starting re0
    May 15 15:42:36 check_reload_status Reloading filter
    May 15 15:42:36 php-fpm 94503 /rc.newwanip: rc.newwanip: on (IP address: 192.168.25.101) (interface: WAN[wan]) (real interface: re0).
    May 15 15:42:36 php-fpm 94503 /rc.newwanip: rc.newwanip: Info: starting on re0.
    May 15 15:42:36 kernel re0: link state changed to DOWN
    May 15 15:42:36 check_reload_status Linkup starting re0
    May 15 15:42:35 check_reload_status Reloading filter
    May 15 15:42:35 check_reload_status rc.newwanip starting re0
    May 15 15:42:35 php-fpm 94503 /rc.linkup: Hotplug event detected for WAN(wan) static IP (192.168.25.101 )
    May 15 15:42:34 kernel re0: link state changed to UP
    May 15 15:42:34 check_reload_status Linkup starting re0

    At this right moment my LAN interface is down! If I put it up manually or if I reboot the pfsense it comes back online.

    My config:

    PfSense 2.3.4
    ML110G5
    2 network interfaces: 1 onboard and 1 offboard

    WAN: re0
    LAN: bge0

    How is it connected:

    WAN: pfsense -> modem
    LAN: pfsense -> unmanaged switch (DLINK)

    Any help is highly welcome! I have a iptables firewall in the same network and this is not happening there.

    Thanks in advance!



  • Well as the log says: it looks like you lose the link on this interface.
    This can be for a variety of reasons. The most common is a bad cable.



  • But with both interfaces? The cables have been tested before going in production.


  • Rebel Alliance Developer Netgate

    It's still possible. Could also be whatever you're plugged into. Something is causing it to lose link.



  • and 1 offboard

    Could this be a USB based network adapter that is causing the problem?

    • a broken cable
    • a burned port
    • a broken solder point
    • USB legacy mode in the BIOS (if the network LAN Port is USB based!)
    • dust in the LAN port and not all contacts are closed or come together
    • electrical hit or stroke to that LAN port?
    • auto negotiation mismatch or auto sensing problem


  • Energy Efficient Ethernet (EEE) turning off the port? New energy features can dynamically change the port rate or even turn off the port while idle. It's not completely off, but pretty close.



  • Good point.
    It can also be the switch/device on the other side of the link.

    I recently was doing long term tests of a device and was wondering why i got a link down every few hours.
    On my device I had EEE disabled, but the switch (dell X1018) chose to ignore the remote side advertising EEE as disabled and enabled it anyway.