Wan interface randon disconect
-
Hi, I've been using pfsense for 3 years withought any problem untill now.I updated from the 2.03 version to de 2.1 and now the wan interface disconects itself randomly , mainly with intensibe use like torrent or youtube. I really don't want to go back to the previous version because the new version supports my wifi card and i'm happy with a full pfsense wifi router an also happy leaving my acces point aside. Can somebody help my fix this :)
-
Its probably because latency gets high under load and apinger thinks you are offline when technically you are not. Thats my guess.
Under system advanced > Gateway Monitoring
Maybe try unchecking "State Killing on Gateway Failure and see what happens."
Also maybe try checking "Skip rules when gateway is down"
(I don't have this problem, so I'm only guessing this might be the cause)
-
If the latency is showing high when you are downloading, then increase the values in the advanced section of the gateway parameters (System->Routing)
-
Maybe even better… I've never had to do this.
-
I'm having similar random disconnects (new since 2.1) however I feel my issue is related to IPv6 and/or the 'block bogon' feature being enabled on the WAN interface. I tried un-checking the block private addresses as I know my Motorola cable modem loads some 192* addresses during boot, however this did not fix the issue. I've also experimented with clearing the 'block bogons' option and this did not help either.
The odd thing for me is that even while I am unable to connect I show an IPv6 address on the WAN interface (Cox cable modem, San Diego).
Here is the other, possibly related thread.
http://forum.pfsense.org/index.php/topic,66726.0.html -
It happened again this morning and grabbed the log file. Looks like pfsense thinks my WAN interface is completely disconnecting or perhaps the cable modem is rebooting and pfsense fails to get a new DHCP lease. Again, this behavior is new since the upgrade to 2.1
Sep 26 04:41:15 check_reload_status: Linkup starting sk0 Sep 26 04:41:15 kernel: sk0: 2 link states coalesced Sep 26 04:41:15 kernel: sk0: link state changed to UP Sep 26 04:41:15 kernel: sk0: link state changed to DOWN Sep 26 04:41:15 kernel: sk0: link state changed to UP Sep 26 04:41:15 check_reload_status: Linkup starting sk0 Sep 26 04:41:15 check_reload_status: Linkup starting sk0 Sep 26 04:41:17 php: rc.linkup: DEVD Ethernet detached event for wan Sep 26 04:41:17 php: rc.linkup: DEVD Ethernet attached event for wan Sep 26 04:41:17 php: rc.linkup: HOTPLUG: Configuring interface wan Sep 26 04:41:17 php: rc.linkup: The command '/sbin/ifconfig 'sk0' inet delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address' Sep 26 04:41:17 php: rc.linkup: DEVD Ethernet attached event for wan Sep 26 04:41:17 php: rc.linkup: HOTPLUG: Configuring interface wan Sep 26 04:41:17 php: rc.linkup: The command '/sbin/ifconfig 'sk0' inet delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address' Sep 26 04:41:17 php: rc.linkup: The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf sk0 > /tmp/sk0_output 2> /tmp/sk0_error_output' returned exit code '1', the output was '' Sep 26 04:41:18 check_reload_status: rc.newwanip starting sk0 Sep 26 04:41:18 php: rc.linkup: ROUTING: setting default route to 70.181.x.x Sep 26 04:41:18 php: rc.linkup: Clearing states to old gateway 70.181.x.x. Sep 26 04:41:20 php: rc.newwanip: rc.newwanip: Informational is starting sk0. Sep 26 04:41:20 php: rc.newwanip: rc.newwanip: on (IP address: ) (interface: wan) (real interface: sk0). Sep 26 04:41:20 php: rc.newwanip: rc.newwanip: Failed to update wan IP, restarting... Sep 26 04:41:20 check_reload_status: Configuring interface wan Sep 26 04:41:22 check_reload_status: updating dyndns wan Sep 26 04:41:22 php: rc.linkup: The command '/usr/local/sbin/dhcpd -user dhcpd -group _dhcp -chroot /var/dhcpd -cf /etc/dhcpd.conf -pf /var/run/dhcpd.pid bge0' returned exit code '1', the output was 'Internet Systems Consortium DHCP Server 4.2.5-P1 Copyright 2004-2013 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Wrote 0 deleted host decls to leases file. Wrote 0 new dynamic host decls to leases file. Wrote 78 leases to leases file. Listening on BPF/bge0/00:13:72:81:e0:0f/192.168.1.0/24 Sending on BPF/bge0/00:13:72:81:e0:0f/192.168.1.0/24 Can't bind to dhcp address: Address already in use Please make sure there is no other dhcp server running and that there's no entry for dhcp or bootp in /etc/inetd.conf. Also make sure you are not running HP JetAdmin software, which includes a bootp server. If you did not get this software from ftp.isc.org, please get the latest from ftp.isc.org and install that before requesting help. If you did get thi Sep 26 04:41:22 php: rc.interfaces_wan_configure: The command '/sbin/ifconfig 'sk0' inet delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address' Sep 26 04:41:22 php: rc.interfaces_wan_configure: The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf sk0 > /tmp/sk0_output 2> /tmp/sk0_error_output' returned exit code '1', the output was '' Sep 26 04:41:24 php: rc.dyndns.update: DynDNS (xx.xx.com) There was an error trying to determine the public IP for interface - wan(sk0). Probably interface is not a WAN interface. Sep 26 04:41:37 check_reload_status: updating dyndns WAN Sep 26 04:41:37 check_reload_status: Restarting ipsec tunnels Sep 26 04:41:37 check_reload_status: Restarting OpenVPN tunnels/interfaces Sep 26 04:41:37 check_reload_status: Reloading filter Sep 26 04:41:39 php: rc.dyndns.update: DynDNS (xx.xx.com) There was an error trying to determine the public IP for interface - wan(sk0). Probably interface is not a WAN interface. Sep 26 04:41:40 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan). Sep 26 04:41:40 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan). Sep 26 04:41:40 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan). Sep 26 04:41:40 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan). Sep 26 04:41:40 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan). Sep 26 04:41:40 php: rc.filter_configure_sync: Could not find IPv4 gateway for interface (wan). Sep 26 06:23:28 php: /index.php: Successful login for user 'admin' from: 192.168.1.152 Sep 26 06:23:28 php: /index.php: Successful login for user 'admin' from: 192.168.1.152 Sep 26 06:23:51 php: /status_interfaces.php: The command '/sbin/ifconfig 'sk0' inet delete' returned exit code '1', the output was 'ifconfig: ioctl (SIOCDIFADDR): Can't assign requested address' Sep 26 06:23:51 check_reload_status: rc.newwanip starting sk0 Sep 26 06:23:53 php: rc.newwanip: rc.newwanip: Informational is starting sk0. Sep 26 06:23:53 php: rc.newwanip: rc.newwanip: on (IP address: 70.181.219.xxx) (interface: wan) (real interface: sk0).
-
Hi, today I wiped the hdd and instaled pfsense 2.1 fron clean. I only have squid3 and the upnp service apart fron the standar install.My connection is thoght a contrend CT536+ modem router configured as a bridge wille pfsense makes the PPPOE connection. The system is a PIII 1GHZ with 256Mb based on the intel 810 chipset. The network card are an old linksys 10/100 ethernet card with a liteon chipset for the WAN connection, the integrated intel PRO 100 for the LAN connection and a TP link wifi card based on the atheros 9287 chipset.
Maybe In should change something on this setup??, This is a cuestion for the experts because I'm bery green in managing andvanced firewalls.
I'll see if the problem persists with the new install, and if it persists try the suggested solutions.
Thanks a lot everybody. -
Well, today I'm still having the same problem after the clean install and so I tried the sugested solutions withought luck. One thin I noticied is that when the wan interface falls the "Gateway Monitoring Daemon" also stops and could not be started, on the log it says "ALARM: WAN_PPPOE(192.168.153.1) *** down ***"
then the problem is that the router can't bring up the wan after a failure.
Wel I don't have the necesary knowledge to know what's happening so…..