Keep loosing WAN IP Address - dhclient does not seem to do update
-
Considering that none of the other devs can reproduce this, maybe you can help us nail this down.
-
Aye, Im trying. Looks like dhclient is trying to renew before lease expires. It's throwing everything out of wack. Dyndns, snort, WAN access to my box. Trying to determine pattern.
-
I like what you guys are doing ;D this is from my pfbox, ISP BBB(Bredbandsbolaget) Sweden 100/10 mbit
1.0.1-SNAPSHOT-02-09-2007
Feb 13 08:14:21 php: : Informational: DHClient spawned /etc/rc.newwanip and the new ip is wan - 85.226.176.x.
Feb 13 08:14:18 php: : Informational: rc.newwanip is starting.
Feb 13 08:14:17 check_reload_status: rc.newwanip starting
Feb 13 08:14:15 dhclient[67394]: bound to 85.226.176.x – renewal in 1800 seconds.
Feb 13 08:14:14 dhclient[67394]: DHCPACK from 172.21.249.50
Feb 13 08:14:14 dhclient[67394]: DHCPREQUEST on fxp0 to 172.21.249.50 port 67
Feb 13 07:44:24 dnsmasq[456]: using nameserver 195.54.122.198#53
Feb 13 07:44:24 dnsmasq[456]: using nameserver 195.54.122.200#53
Feb 13 07:44:24 dnsmasq[456]: using nameserver 195.54.122.199#53
Feb 13 07:44:24 dnsmasq[456]: using nameserver 81.26.227.3#53
Feb 13 07:44:24 dnsmasq[456]: reading /etc/resolv.conf
Feb 13 07:44:24 check_reload_status: updating dyndns
Feb 13 07:44:22 check_reload_status: reloading filter
Feb 13 07:44:21 php: : Configuring slbd
Feb 13 07:44:21 php: : Resyncing configuration for all packages.
Feb 13 07:44:20 php: : Creating rrd update script
Feb 13 07:44:20 php: : Informational: DHClient spawned /etc/rc.newwanip and the new ip is wan - 85.226.176.x.
Feb 13 07:44:18 php: : Informational: rc.newwanip is starting.
Feb 13 07:44:17 check_reload_status: rc.newwanip starting
Feb 13 07:44:14 dhclient[67314]: bound to 85.226.176.x – renewal in 1800 seconds.
Feb 13 07:44:14 dhclient: /sbin/route add default 85.226.176.1
Feb 13 07:44:14 dhclient: New Routers (fxp0): 85.226.176.1
Feb 13 07:44:14 dhclient: New Broadcast Address (fxp0): 85.226.176.255
Feb 13 07:44:14 dhclient: New Subnet Mask (fxp0): 255.255.255.0
Feb 13 07:44:14 dhclient: New IP Address (fxp0): 85.226.176.x
Feb 13 07:44:14 dhclient[67314]: DHCPACK from 85.226.176.3
Feb 13 07:44:14 dhclient[67314]: DHCPREQUEST on fxp0 to 255.255.255.255 port 67
Feb 13 07:44:12 dhclient[67314]: DHCPOFFER from 85.226.176.3
Feb 13 07:44:12 dhclient[67314]: DHCPDISCOVER on fxp0 to 255.255.255.255 port 67 interval 7
-Renew-
Feb 13 00:41:09 dhclient[248]: exiting.
Feb 13 00:41:09 dhclient[248]: exiting.
Feb 13 00:41:09 dhclient[248]: short write: wanted 21 got 0 bytes
Feb 13 00:41:09 dhclient[248]: short write: wanted 21 got 0 bytes
Feb 13 00:41:09 dhclient[248]: DHCPACK from 172.21.249.50
Feb 13 00:41:09 dhclient[248]: DHCPREQUEST on fxp0 to 172.21.249.50 port 67
Feb 13 00:11:32 dnsmasq[456]: using nameserver 195.54.122.199#53
Feb 13 00:11:32 dnsmasq[456]: using nameserver 81.26.227.3#53
Feb 13 00:11:32 dnsmasq[456]: using nameserver 195.54.122.204#53
Feb 13 00:11:32 dnsmasq[456]: using nameserver 195.54.122.198#53
Feb 13 00:11:32 dnsmasq[456]: reading /etc/resolv.conf
Feb 13 00:11:19 check_reload_status: updating dyndns
Feb 13 00:11:16 check_reload_status: reloading filter
Feb 13 00:11:16 php: : Configuring slbd
Feb 13 00:11:16 php: : Resyncing configuration for all packages.
Feb 13 00:11:15 php: : Creating rrd update script
Feb 13 00:11:15 php: : Informational: DHClient spawned /etc/rc.newwanip and the new ip is wan - 85.226.176.x.
Feb 13 00:11:12 php: : Informational: rc.newwanip is starting.
Feb 13 00:11:12 check_reload_status: rc.newwanip starting
Feb 13 00:11:10 dhclient[248]: bound to 85.226.176.x – renewal in 1800 seconds.
Feb 13 00:11:09 dhclient[248]: DHCPACK from 172.21.249.50
Feb 13 00:11:09 dhclient[248]: DHCPREQUEST on fxp0 to 172.21.249.50 port 67
Feb 13 00:01:45 dnsmasq[456]: using nameserver 195.54.122.199#53
Feb 13 00:01:45 dnsmasq[456]: using nameserver 81.26.227.3#53
Feb 13 00:01:45 dnsmasq[456]: using nameserver 195.54.122.204#53
Feb 13 00:01:45 dnsmasq[456]: using nameserver 195.54.122.198#53
Feb 13 00:01:45 dnsmasq[456]: reading /etc/resolv.conf
Feb 12 23:41:18 check_reload_status: updating dyndns
Feb 12 23:41:15 check_reload_status: reloading filter
Feb 12 23:41:15 php: : Configuring slbd
Feb 12 23:41:15 php: : Resyncing configuration for all packages.
Feb 12 23:41:14 php: : Creating rrd update script
Feb 12 23:41:14 php: : Informational: DHClient spawned /etc/rc.newwanip and the new ip is wan - 85.226.176.x.
Feb 12 23:41:12 kernel: pflog0: promiscuous mode disabled
Feb 12 23:41:12 php: : Informational: rc.newwanip is starting.
Feb 12 23:41:11 check_reload_status: rc.newwanip starting
Feb 12 23:41:09 dhclient[248]: bound to 85.226.176.x – renewal in 1800 seconds.
Feb 12 23:41:09 dhclient[248]: DHCPACK from 172.21.249.50
Feb 12 23:41:09 dhclient[248]: DHCPREQUEST on fxp0 to 172.21.249.50 port 67 -
Since I started this thread I guess I should mention that I'm no longer having the problem. The problem went away but I'm still running a stock 1.0.1 load. Thinking more and more the root cause was my service provider…
-
Everyone that is experiencing this problem, are you running miniupnpd on any interface? It seems to be that when I run upnp I experience this problem. Im running more test to confirm.
Feb 13 16:29:51 last message repeated 160 times
Feb 13 16:19:51 last message repeated 160 times
Feb 13 16:09:51 last message repeated 160 times
Feb 13 15:59:51 last message repeated 160 times
Feb 13 15:49:51 last message repeated 160 times
Feb 13 15:39:51 last message repeated 160 times
Feb 13 15:29:51 last message repeated 160 times
Feb 13 15:19:51 last message repeated 160 times
Feb 13 15:09:51 last message repeated 160 times
Feb 13 14:59:51 last message repeated 160 times
Feb 13 14:49:51 last message repeated 160 times
Feb 13 14:39:51 last message repeated 160 times
Feb 13 14:29:51 last message repeated 160 times
Feb 13 14:19:51 last message repeated 167 times
Feb 13 14:09:51 last message repeated 161 times
Feb 13 13:59:21 last message repeated 160 times
Feb 13 13:49:21 last message repeated 32 times
Feb 13 13:47:21 last message repeated 15 times
Feb 13 13:46:51 miniupnpd[20009]: sendto(udp_notify): No buffer space available
Feb 13 13:46:43 dhclient[272]: exiting.
Feb 13 13:46:43 dhclient[272]: exiting.
Feb 13 13:46:43 dhclient[272]: short write: wanted 21 got 0 bytes
Feb 13 13:46:43 dhclient[272]: short write: wanted 21 got 0 bytes
Feb 13 13:46:21 last message repeated 95 times
Feb 13 13:46:43 dhclient[272]: DHCPACK from 68.87.68.13
Feb 13 13:46:43 dhclient[272]: DHCPREQUEST on sis0 to 68.87.68.13 port 67
Feb 13 13:40:51 last message repeated 161 times
Feb 13 13:32:03 dnsmasq[642]: using nameserver 68.87.68.162#53
Feb 13 13:32:03 dnsmasq[642]: using nameserver 68.87.74.162#53
Feb 13 13:32:03 dnsmasq[642]: reading /etc/resolv.conf
Feb 13 13:30:21 last message repeated 167 times
Feb 13 13:20:21 last message repeated 33 times
Feb 13 13:17:51 last message repeated 15 times
Feb 13 13:17:21 miniupnpd[20009]: sendto(udp_notify): No buffer space available -
No, not running any extras at all, everything is clean and simple !
-
Everyone having this problem, please try this from a shell:
fetch -o /etc/ http://www.pfsense.com/~sullrich/devd.conf ; killall devd ; devd
-
Tried that, and 1.0.1-SNAPSHOT-02-14-2007
Feb 14 20:32:46 dhclient[256]: exiting.
Feb 14 20:32:46 dhclient[256]: exiting.
Feb 14 20:32:46 dhclient[256]: short write: wanted 21 got 0 bytes
Feb 14 20:32:46 dhclient[256]: short write: wanted 21 got 0 bytes
Feb 14 20:32:46 dhclient[256]: DHCPACK from 172.21.249.50
Feb 14 20:32:46 dhclient[256]: DHCPREQUEST on fxp0 to 172.21.249.50 port 67
Feb 14 20:32:37 dhcpd: uid lease 192.168.1.245 for client 00:07:e9:b0:d6:26 is duplicate on 192.168.1/24 -
We've established that dhclient is terminating prematurely for some reason. We're working hard to nail this down. Trouble is I'm the only developer experiencing this issue, but we are working on it.
-
Hi.
My connection failed again but the logs went away during my lunch.
Is not possible to fetch old logs ?I deactivated the firewall interface and then activated again and everything works.
-
Everyone please update to the latest snapshot and see if that solves your disconnects.
http://snapshots.pfsense.com/FreeBSD6/RELENG_1/updates/
-
@sdale:
Everyone please update to the latest snapshot and see if that solves your disconnects.
http://snapshots.pfsense.com/FreeBSD6/RELENG_1/updates/
What has changed that would fix it?
-
Bill's patch. I'm running 2-14 and I haven't had an issue yet. Wondering if anyone else will with the new snapshot.
-
Sorry, no luck =(
Snapshot 02-14-2007:–---------------------
Feb 18 11:59:18 dhclient[271]: exiting.
Feb 18 11:59:18 dhclient[271]: exiting.
Feb 18 11:59:18 dhclient[271]: short write: wanted 21 got 0 bytes
Feb 18 11:59:18 dhclient[271]: short write: wanted 21 got 0 bytes
Feb 18 11:59:18 dhclient[271]: DHCPACK from 90.224.168.1
Feb 18 11:59:18 dhclient[271]: DHCPREQUEST on rl0 to 255.255.255.255 port 67
Feb 18 11:58:37 last message repeated 5 times
Feb 18 11:54:02 last message repeated 3 times
Feb 18 11:52:00 last message repeated 3 times
Feb 18 11:51:28 dhclient[271]: DHCPREQUEST on rl0 to 213.67.15.234 port 67
Feb 18 11:41:51 php: : FTP proxy disabled for interface opt2 - ignoring.
Feb 18 11:41:51 php: : FTP proxy disabled for interface opt1 - ignoring.
Feb 18 11:41:51 php: : FTP proxy disabled for interface LAN - ignoring.
Feb 18 11:41:50 check_reload_status: reloading filter
Feb 18 11:41:44 check_reload_status: updating dyndns
Feb 18 11:41:41 php: : FTP proxy disabled for interface opt2 - ignoring.
Feb 18 11:41:41 php: : FTP proxy disabled for interface opt1 - ignoring.
Feb 18 11:41:41 php: : FTP proxy disabled for interface LAN - ignoring. -
Sorry, no luck =(
Snapshot 02-14-2007:–---------------------
Feb 18 11:59:18 dhclient[271]: exiting.
Feb 18 11:59:18 dhclient[271]: exiting.
Feb 18 11:59:18 dhclient[271]: short write: wanted 21 got 0 bytes
Feb 18 11:59:18 dhclient[271]: short write: wanted 21 got 0 bytes
Feb 18 11:59:18 dhclient[271]: DHCPACK from 90.224.168.1
Feb 18 11:59:18 dhclient[271]: DHCPREQUEST on rl0 to 255.255.255.255 port 67
Feb 18 11:58:37 last message repeated 5 times
Feb 18 11:54:02 last message repeated 3 times
Feb 18 11:52:00 last message repeated 3 times
Feb 18 11:51:28 dhclient[271]: DHCPREQUEST on rl0 to 213.67.15.234 port 67
Feb 18 11:41:51 php: : FTP proxy disabled for interface opt2 - ignoring.
Feb 18 11:41:51 php: : FTP proxy disabled for interface opt1 - ignoring.
Feb 18 11:41:51 php: : FTP proxy disabled for interface LAN - ignoring.
Feb 18 11:41:50 check_reload_status: reloading filter
Feb 18 11:41:44 check_reload_status: updating dyndns
Feb 18 11:41:41 php: : FTP proxy disabled for interface opt2 - ignoring.
Feb 18 11:41:41 php: : FTP proxy disabled for interface opt1 - ignoring.
Feb 18 11:41:41 php: : FTP proxy disabled for interface LAN - ignoring.Do you see anything in the filter logs showing blocked packets around this time?
Also, anyone having this problem, please run this from a shell:
fetch -o /etc/inc http://www.pfsense.com/~sullrich/filter.inc
-
no, i have not seen any blocked packets that could have something to do with this, but i am one of those
who are affected by the "promiscuous mode disabled", and therefore my firwall logs stops after a while.isn´t there a way to catch the dhclient message and "restart" dhclient when its terminating, just as a workaround until you pinned down the problem ?
-
We already have code to detect this but it doesnt appear to be working.
-
Good news!
I was able to replicate this problem thanks to sdale and Vescovo.
Vescovo had the final fix and it has been commited. Please upgrade to a snapshot about an hour from this message.
-
Good news!
I was able to replicate this problem thanks to sdale and Vescovo.
Vescovo had the final fix and it has been commited. Please upgrade to a snapshot about an hour from this message.
I think you forgot to wave your magic voodoo wand, problem still exists ;). I think the problem lies in the rc.newwanip not catching the interface being assigned 0.0.0.0 IP address.
-