Connection problems after the WAN connection fails



  • I experienced the following

    the network users were not able to connect to the internet after the wan connection lost and regained its connection

    the wan is connected to a router and gets via dhcp an address and gateway/dns information

    after the wan link disconnects (cable failure) and reconnects (cable plugged in), pfsense  does not re-initialise the link nor its tables and the console starts showing arprequest failures forever … pfsense does not recover from this state (even after reconnecting the cable)

    the only way to get rid of this status is by rebooting the pfsense machine

    I had no time yet to check if the same happens with other connectivity situations but i fear the same is true ... can this be validated and if it is a bug, can it be put as a bug so it can be resolved?

    by the way, with version 1.2.2 I don't have this problem ... so it is definitely a regression

    Philip Van Cleven



  • Please show your system log and what type on NICs you have.



  • this is the log

    I unplugged the cable and waited for about 15 seconds
    the connection did come back this time but I will insert the log anyway

    Mar 2 16:30:08 apinger: Starting Alarm Pinger, apinger(31624)
    Mar 2 16:30:08 check_reload_status: reloading filter
    Mar 2 16:30:06 apinger: Exiting on signal 15.
    Mar 2 16:30:06 check_reload_status: reloading filter
    Mar 2 16:30:06 php: : ROUTING: change default route to 192.168.20.1
    Mar 2 16:30:06 dnsmasq[57845]: using nameserver 203.144.207.49#53
    Mar 2 16:30:06 dnsmasq[57845]: using nameserver 203.144.207.29#53
    Mar 2 16:30:06 dnsmasq[57845]: reading /etc/resolv.conf
    Mar 2 16:30:05 apinger: alarm canceled: GW_WAN(192.168.20.1) *** down ***
    Mar 2 16:30:04 php: : rc.newwanip: on (IP address: 192.168.20.106) (interface: wan) (real interface: ste0).
    Mar 2 16:30:04 php: : rc.newwanip: Informational is starting ste0.
    Mar 2 16:30:04 dhclient[16079]: bound to 192.168.20.106 – renewal in 43200 seconds.
    Mar 2 16:30:04 check_reload_status: rc.newwanip starting ste0
    Mar 2 16:30:04 dhclient: Creating resolv.conf
    Mar 2 16:30:04 dhclient: /sbin/route add default 192.168.20.1
    Mar 2 16:30:04 dhclient: Adding new routes to interface: ste0
    Mar 2 16:30:04 dhclient: New Routers (ste0): 192.168.20.1
    Mar 2 16:30:04 dhclient: New Broadcast Address (ste0): 192.168.20.255
    Mar 2 16:30:04 dhclient: New Subnet Mask (ste0): 255.255.255.0
    Mar 2 16:30:04 dhclient: New IP Address (ste0): 192.168.20.106
    Mar 2 16:30:04 dhclient: ifconfig ste0 inet 192.168.20.106 netmask 255.255.255.0 broadcast 192.168.20.255
    Mar 2 16:30:04 dhclient: Starting add_new_address()
    Mar 2 16:30:04 dhclient: REBOOT
    Mar 2 16:30:04 dhclient[16079]: DHCPACK from 192.168.20.1
    Mar 2 16:30:04 dhclient[16079]: DHCPREQUEST on ste0 to 255.255.255.255 port 67
    Mar 2 16:30:03 dhclient: PREINIT
    Mar 2 16:30:02 php: : HOTPLUG: Configuring interface wan
    Mar 2 16:30:02 php: : DEVD Ethernet attached event for wan
    Mar 2 16:30:02 check_reload_status: Linkup starting ste0
    Mar 2 16:30:02 kernel: ste0: link state changed to UP
    Mar 2 16:29:45 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:45 php: : Could not find gateway for interface(wan).
    Mar 2 16:29:45 php: : ERROR! PPTP enabled but could not resolve the $pptpdtarget
    Mar 2 16:29:44 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:44 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:43 check_reload_status: reloading filter
    Mar 2 16:29:42 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:41 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:40 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:38 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:38 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:37 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:37 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:37 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:36 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:36 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:36 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:35 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:34 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:34 kernel: arpresolve: can't allocate llinfo for 192.168.20.1
    Mar 2 16:29:33 apinger: ALARM: GW_WAN(192.168.20.1) *** down ***
    Mar 2 16:29:25 dhclient[12176]: exiting.
    Mar 2 16:29:25 dhclient[12176]: exiting.
    Mar 2 16:29:25 dhclient[12176]: connection closed
    Mar 2 16:29:25 dhclient[12176]: connection closed
    Mar 2 16:29:25 php: : DEVD Ethernet detached event for wan
    Mar 2 16:29:24 kernel: ste0: link state changed to DOWN
    Mar 2 16:29:24 check_reload_status: Linkup starting ste0

    I will try later tonight when no real users are on the link and wait for 30 min before reconnecting


Log in to reply