The pfSense Store

Author Topic: Problem with network interface when connected system is down and comes back up  (Read 537 times)

0 Members and 1 Guest are viewing this topic.

Offline /CS

  • Jr. Member
  • **
  • Posts: 78
  • Karma: +0/-0
    • View Profile
Hi all!

I recently upgraded my Soekris 6501 board to the latest version (2.3.2-RELEASE) and the following weird thing started happening some days later.

There is a desktop PC connected directly to one of pfsense's LAN interfaces and sometimes when I turn the PC on it doesn't get an IP from the DHCP server and in general cannot communicate at all with pfsense (it doesn't receive any packets from pfsense). I tried with a laptop and I had the same issue which gets always resolved with a reboot of pfsense. By the way restarting the DHCP server doesn't help. I also assigned a static IP to the PC, which is reserved for it on the DHCP server anyway, but still it doesn't receive any packets from pfsense. I never have issues while the PC is online, so it's something that has to do with the interface changing status (DOWN - UP).

Since I confirmed that pfsense causes the problem, let's focus on that one. First of all, when I turn the PC on the interface looks UP in pfsense, shows only 1 packet sent out with 3 out errors and 0 collisions. The interface is a LAN bridge member. The only change I did on the system after the upgrade was that I tested Snort with LOWMEM pattern match but I had changed it back to AC-BNFA.

System logs:
Aug 14 13:01:56   SnortStartup          8193   Snort START for WAN(28214_em3)...
Aug 14 13:01:56   php-fpm   72011   /rc.start_packages: Restarting/Starting all packages.
Aug 14 13:01:55   check_reload_status   Starting packages
Aug 14 13:01:55   php-fpm   88398   /rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 0.0.0.0 -> - Restarting packages.
Aug 14 13:01:52   php-fpm   88398   /rc.newwanip: Creating rrd update script
Aug 14 13:01:52   php-fpm   88398   /rc.newwanip: Resyncing OpenVPN instances for interface LAN1.
Aug 14 13:01:51   xinetd   24963   Reconfigured: new=0 old=1 dropped=0 (services)
Aug 14 13:01:51   xinetd   24963   readjusting service 6969-udp
Aug 14 13:01:51   xinetd   24963   Swapping defaults
Aug 14 13:01:51   xinetd   24963   Starting reconfiguration
Aug 14 13:01:50   xinetd   24963   Reconfigured: new=0 old=1 dropped=0 (services)
Aug 14 13:01:50   xinetd   24963   readjusting service 6969-udp
Aug 14 13:01:50   xinetd   24963   Swapping defaults
Aug 14 13:01:50   xinetd   24963   Starting reconfiguration
Aug 14 13:01:50   php-fpm   88398   /rc.newwanip: IP has changed, killing states on former IP 0.0.0.0.
Aug 14 13:01:50   php-fpm   88398   /rc.newwanip: rc.newwanip: on (IP address: ) (interface: LAN1[opt4]) (real interface: em0).
Aug 14 13:01:50   php-fpm   88398   /rc.newwanip: rc.newwanip: Info: starting on em0.
Aug 14 13:01:49   check_reload_status      Reloading filter
Aug 14 13:01:49   check_reload_status      rc.newwanip starting em0
Aug 14 13:01:49   php-fpm   88398   /rc.linkup: Hotplug event detected for LAN1(opt4) static IP ( )
Aug 14 13:01:48   kernel      em0: link state changed to UP
Aug 14 13:01:48   check_reload_status      Linkup starting em0


Any ideas for troubleshooting?


/CS

Offline /CS

  • Jr. Member
  • **
  • Posts: 78
  • Karma: +0/-0
    • View Profile
I still have the same issue and I have to reboot pfSense every other day... :(
It seems it also has to do with how many hours the desktop stays powered off. If I turn it on after a few hours ( less than 8 ) usually I don't have problems but when I try after 12hours or so it cannot connect to the network.
Any ideas guys?
« Last Edit: August 25, 2016, 11:54:53 am by /CS »

Offline /CS

  • Jr. Member
  • **
  • Posts: 78
  • Karma: +0/-0
    • View Profile
That's what happens a few hours after the desktop has been turned off. I have no idea what triggers that event in PfSense, is there any way to keep the link state UP?


Aug 25 03:10:35    xinetd    25467    Reconfigured: new=0 old=1 dropped=0 (services)
Aug 25 03:10:35    xinetd    25467    readjusting service 6969-udp
Aug 25 03:10:35    xinetd    25467    Swapping defaults
Aug 25 03:10:35    xinetd    25467    Starting reconfiguration
Aug 25 03:10:34    check_reload_status       Reloading filter
Aug 25 03:10:34    php-fpm    69603    /rc.linkup: Hotplug event detected for LAN1(opt4) static IP ( )
Aug 25 03:10:33    check_reload_status       Linkup starting em0
Aug 25 03:10:33    kernel       em0: link state changed to DOWN
Aug 25 03:10:33    kernel       em0: RX Next to Refresh = 32
Aug 25 03:10:33    kernel       em0: RX Next to Check = 33
Aug 25 03:10:33    kernel       em0: RX discarded packets = 0
Aug 25 03:10:33    kernel       em0: hw rdh = 33, hw rdt = 32
Aug 25 03:10:33    kernel       em0: RX Queue 0 ------
Aug 25 03:10:33    kernel       em0: Tx Descriptors avail failure = 16
Aug 25 03:10:33    kernel       em0: TX descriptors avail = 40
Aug 25 03:10:33    kernel       em0: Tx Queue Status = -2147483648
Aug 25 03:10:33    kernel       em0: hw tdh = 890, hw tdt = 850
Aug 25 03:10:33    kernel       em0: TX Queue 0 ------
Aug 25 03:10:33    kernel       Interface is RUNNING and ACTIVE
Aug 25 03:10:33    kernel       em0: Watchdog timeout Queue[0]-- resetting