Keep loosing WAN IP Address - dhclient does not seem to do update

Selective

the new dhclient is working great !
but i have found small bug, under Interfaces my wan says DHCP : down
like this:
–-----------------------
WAN interface (rl0)
Status up
DHCP down
MAC address 00:0a:cd:11:ef:fa
Media 100baseTX <full-duplex>
In/out packets 88231/110810 (21.17 MB/32.31 MB)
In/out errors 0/0
Collisions 0

keep up the good work !</full-duplex>

Selective

i just noticed a very good thing, it looks like with the new dhclient, the OpenVPN problem with "address in use" issue is fixed ! at least on my pfsense !

sullrich

@Selective:

the new dhclient is working great !
but i have found small bug, under Interfaces my wan says DHCP : down
like this:
–-----------------------
WAN interface (rl0)
Status up
DHCP down
MAC address 00:0a:cd:11:ef:fa
Media 100baseTX <full-duplex>In/out packets 88231/110810 (21.17 MB/32.31 MB)
In/out errors 0/0
Collisions 0

keep up the good work !</full-duplex>

Yeah, we are aware of this issue. Should be fixed rather soon. Just keep running that command every 12 hours or so and you will have the latest code. But don't run the command unattended (from cron).

fireseller

Just tried to fetch the newest cvs several times but always got stuck with:

fetch -q -o - http://www.pfsense.com/~sullrich/tools/cvs_sync.sh | sh

Setting CVS_IP to cvs.pfsense.com
Syncing with pfSense.com
Checking out RELENG_1
Connected to cvs.pfsense.com
Updating collection pfSenseHEAD/cvs
Rsync CVSROOT/history
Edit pfSense/etc/inc/service-utils.inc,v
Create pfSense/usr/local/bin/php,v

Any advice?

sullrich

Your being impatient. Let it go… It is still processing php which is every php change ever and is quite large.

fireseller

Ups, sorry bout that. I watched it for about 10 mins ;) Just starting up again.

Thanks alot.

sullrich

Please run the command again. All known issues hopefully are solved.

sullrich

NOTE: you WILL need to reboot afterwards.

Please run again, I just fixed a few more bugs.

dlawley

Yea… my sense box seems pretty happy again.. thank you sir...

sullrich

Good. Others please test. A new snapshot will be uploaded in a couple hours.

fireseller

running great now for around 1 day!

Thanks a lot for the great work!

sullrich

@fireseller:

running great now for around 1 day!

Thanks a lot for the great work!

Awesome! Anyone else?

Selective

Works great ! I think you hit the spot ! ;D

sullrich

@Selective:

Works great ! I think you hit the spot ! ;D

Great! That's 3-4 people that is now fixed. FreeBSD REALLY needs to take a look at their dhclient. It's obvious that it's subpar to ISC's.

Anyone else?

Merry Xmas and happy holidays!

fireseller

Just updated to the latest cvs… No issue for 2 days. I think the right spot was hit ;)

Happy holidays and again - big thanks for the great work!

adrianhensler

I'm new here; so it could be me; but I'm also experiencing the issue. I have to ifconfig up / down every couple hours. I don't see any logs that are showing me errors - any tips on where to look? I installed from the 12-23 build with squid and snort. I also ran the fetch command from above.

I'm all for suggesting it's user error; any tips are welcome. I had a build from early December running and it was up for a couple weeks without issue.

edit with a tiny bit more info - I've looked at the system.log; and it seems to be corrupted near the end.I'm on my second old clunker hard drive; maybe this one's been around the block too many times as well. There's some weird duplication at the end of the log before it turns into an ASCII mess:

Dec 27 02:44:31 chunder snort[775]: Var 'SMTP_SERVERS' defined, value len = 28 chars
Dec 27 02:44:31 chunder snort[775]: Var 'SMTP_SERVERS' defined, value len = 28 chars
Dec 27 02:44:31 chunder snort[775]: , value = [24.89.123.123,192.168.1.1,]
…skipping...
Dec 27 21:53:26 chunder dhclient: execve (/sb, ...): No such file or directory
Dec 27 21:53:26 chunder dhclient: execve (/sb, ...): No such file or directory
Dec 27 21:53:26 chunder dhclient: Listening on BPF/ed0/00:50:8d:f1:3a:9d
Dec 27 21:53:26 chunder dhclient: Sending on BPF/ed0/00:50:8d:f1:3a:9d
Dec 27 21:53:26 chunder dhclient: Can't bind to dhcp address: Address already in use
Dec 27 21:53:26 chunder dhclient: Can't bind to dhcp address: Address already in use
Dec 27 21:53:26 chunder dhclient: Please make sure there is no other dhcp server
Dec 27 21:53:26 chunder dhclient: Please make sure there is no other dhcp server
Dec 27 21:53:26 chunder dhclient: running and that there's no entry for dhcp or
Dec 27 21:53:26 chunder dhclient: running and that there's no entry for dhcp or
Dec 27 21:53:26 chunder dhclient: bootp in /etc/inetd.conf. Also make sure you
Dec 27 21:53:26 chunder dhclient: bootp in /etc/inetd.conf. Also make sure you
Dec 27 21:53:26 chunder dhclient: are not running HP JetAdmin software, which
Dec 27 21:53:26 chunder dhclient: are not running HP JetAdmin software, which
Dec 27 21:53:26 chunder dhclient: includes a bootp server.
Dec 27 21:53:26 chunder dhclient: includes a bootp server.

Does that suggest anything? I'm not aware of any bootp servers running anywhere. Hm.

hoba

Any chance that you are using dhcp on more than 1 interface? The current dhclient-switch doesn't handle multiple dhcp interfaces correctly atm. We need to improve this a bit to handle these kind of situations.

sullrich

@hoba:

Any chance that you are using dhcp on more than 1 interface? The current dhclient-switch doesn't handle multiple dhcp interfaces correctly atm. We need to improve this a bit to handle these kind of situations.

Bad news. Looks like we are going to have to revert back to the previous code. This newer code breaks our multi-wan dhcp.

adrianhensler

Just to follow up on my previous information; I see this in the system.log:

Dec 28 08:39:40 chunder dhclient: execve (/usr/local/sbin/dhclient-script, …): No such file or directory
Dec 28 08:39:40 chunder dhclient: execve (/usr/local/sbin/dhclient-script, ...): No such file or directory
Dec 28 08:39:40 chunder dhclient: /y: not found
Dec 28 08:39:40 chunder dhclient: /y: not found

dhclient-script is in /sbin ?

I'm still using the install from 12-23 and I used the fetch from another thread. Maybe I just made a mess…. Maybe I'll copy that over and see what happens; or maybe I'll get a chance to take a better look at it and see what put it there.

hoba

Investigating this error is riding a dead horse. We have to go back to the previous dhclient due to multi interface dhclient issues with the isc client that can't be worked around. The next snapshot will be back at the "old" openbsd dhclient.