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

sullrich · Feb 21, 2007, 1:03 AM

I really don't see how it could not work.

Run this from a shell:

cat /sbin/dhclient | grep reload

What does the results say?

Selective · Feb 21, 2007, 7:04 AM

it does not say anything:
–----------------------------

Enter an option: 8

cat /sbin/dhclient | grep reload

Binary file (standard input) matches

sullrich · Feb 21, 2007, 6:14 PM

Can someone else please test? This absolutely works for me after 20 hours when normally it would break in 30 minutes…

Krakke · Feb 21, 2007, 7:05 PM

@sullrich:

Can someone else please test? This absolutely works for me after 20 hours when normally it would break in 30 minutes…

Works fine for me, only lost my ip 2 times, and that was before the latest snapshot.

sullrich · Feb 21, 2007, 7:11 PM

@Krakke:

Works fine for me, only lost my ip 2 times, and that was before the latest snapshot.

Great! Almost started to go insane, because I know this fixed my issue. Please, someone else test?

Krakke · Feb 21, 2007, 8:12 PM

@sullrich:

@Krakke:

Works fine for me, only lost my ip 2 times, and that was before the latest snapshot.

Great! Almost started to go insane, because I know this fixed my issue. Please, someone else test?

Im sorry sullrich, went out for a while, when i came back

Feb 21 20:01:24 dhclient[300]: DHCPREQUEST on fxp0 to 172.21.249.50 port 67
Feb 21 20:01:24 dhclient[300]: DHCPACK from 172.21.249.50
Feb 21 20:01:24 dhclient[300]: short write: wanted 21 got 0 bytes
Feb 21 20:01:24 dhclient[300]: short write: wanted 21 got 0 bytes
Feb 21 20:01:24 dhclient[300]: exiting.
Feb 21 20:01:24 dhclient[300]: exiting.

hoba · Feb 21, 2007, 8:46 PM

Atm there is a workaround in pllace that will restart the dhclient when it exits. Does it get restarted?

Krakke · Feb 21, 2007, 8:55 PM

@hoba:

Atm there is a workaround in pllace that will restart the dhclient when it exits. Does it get restarted?

Nope at 20:01:24 it exited, at 21:01 i lost my ip, then i had to do a renew.

sullrich · Feb 21, 2007, 10:31 PM

It can take up to 5 minutes to restart dhclient depending on if check_reload_status is running.

So if you still have trouble please check that check_reload_status is running from a shell by doing:

ps awux | grep check_reload_status

Also, cat /etc/crontab | grep check

sullrich · Feb 21, 2007, 11:01 PM

I found yet another problem. This WAN DHCP issue has been nothing but fun!

Try out a recent snapshot atleast an hour from now.

Selective · Feb 22, 2007, 7:18 PM

damn! snapshot 02-21 is not working :'( :'( :'(
–----------------

Feb 22 20:02:39 dhclient[283]: exiting.
Feb 22 20:02:39 dhclient[283]: exiting.
Feb 22 20:02:39 dhclient[283]: short write: wanted 21 got 0 bytes
Feb 22 20:02:39 dhclient[283]: short write: wanted 21 got 0 bytes
Feb 22 20:02:39 dhclient[283]: DHCPACK from 90.224.168.1
Feb 22 20:02:39 dhclient[283]: DHCPREQUEST on rl0 to 255.255.255.255 port 67
Feb 22 19:59:46 last message repeated 5 times
Feb 22 19:56:08 last message repeated 6 times
Feb 22 19:54:11 last message repeated 4 times
Feb 22 19:53:39 dhclient[283]: DHCPREQUEST on rl0 to 213.67.15.234 port 67
Feb 22 19:44:03 php: : FTP proxy disabled for interface opt2 - ignoring.
Feb 22 19:44:03 php: : FTP proxy disabled for interface opt1 - ignoring.
Feb 22 19:44:03 php: : FTP proxy disabled for interface LAN - ignoring.
Feb 22 19:44:02 check_reload_status: reloading filter

sullrich · Feb 22, 2007, 9:03 PM

@Selective:

damn! snapshot 02-21 is not working :'( :'( :'(

Yes the problem still exists and we have been racking our brains out – literally.

sullrich · Feb 23, 2007, 8:39 PM

Please try http://snapshots.pfsense.com/FreeBSD6/RELENG_1/updates/pfSense-Full-Update-1.0.1-SNAPSHOT-02-21-2007.tgz

Selective · Feb 24, 2007, 10:03 AM

Sorry, not working either (snap 02-21)

–----------------------

Feb 24 05:03:45 dhclient[282]: exiting.
Feb 24 05:03:45 dhclient[282]: exiting.
Feb 24 05:03:45 dhclient[282]: short write: wanted 21 got 0 bytes
Feb 24 05:03:45 dhclient[282]: short write: wanted 21 got 0 bytes
Feb 24 05:03:45 dhclient[282]: DHCPACK from 90.224.168.1
Feb 24 05:03:45 dhclient[282]: DHCPREQUEST on rl0 to 255.255.255.255 port 67
Feb 24 05:02:41 last message repeated 4 times
Feb 24 04:58:09 last message repeated 3 times
Feb 24 04:56:02 last message repeated 3 times
Feb 24 04:55:34 dhclient[282]: DHCPREQUEST on rl0 to 213.67.15.234 port 67
Feb 24 04:45:58 php: : FTP proxy disabled for interface opt2 - ignoring.
Feb 24 04:45:58 php: : FTP proxy disabled for interface opt1 - ignoring.
Feb 24 04:45:58 php: : FTP proxy disabled for interface LAN - ignoring.
Feb 24 04:45:56 check_reload_status: reloading filter

sullrich · Feb 24, 2007, 6:47 PM

At this point reinstall. My dhclient has been rock solid for over 24 hours!

Selective · Feb 25, 2007, 12:03 PM

mine to, but only after i pushed the renew button the first time it died, strange

sullrich · Feb 25, 2007, 10:01 PM

Make that 48 hours. And Vescovo has been running it for 48 hours on 2 wans with 180 second renewal time.

This issue is fixed for sure and verified now by 3 different people.

Selective · Feb 25, 2007, 10:29 PM

Thats nice to hear =)

But just one thing, could you reboot your pfsense and monitor it again ?

My issue always come after a while when pfsense is rebooted, and the issue disappears after i push the renew button.

sullrich · Feb 26, 2007, 12:06 AM

Yes, it has been rebooted once.

yoda715 · Feb 26, 2007, 4:20 AM

Mine has been steady for the last 2 days as well.