Keep loosing WAN IP Address - dhclient does not seem to do update
-
It does not solve it, it simply works around the issue for the time being. Anyone else tested?
-
i know, but i think there is two errors,
first, when it failes to update the wan ip, that have been "solved" with the script.
but the second with "short write" will not be solved by this, i think. -
i can confirm that the new script (rc.newwanip) is working great !!! ;D :D ;D
-
Yay! Anyone else?
-
Sorry but the new script is NOT running great, after 1 day again the connection got lost:
Dec 20 05:59:32 last message repeated 3 times
Dec 20 05:59:12 dhcpd: send_packet: Permission denied
Dec 20 05:52:02 last message repeated 2 times
Dec 20 05:51:51 dhcpd: send_packet: Permission denied
Dec 20 01:52:17 dhclient[268]: exiting.
Dec 20 01:52:17 dhclient[268]: exiting.
Dec 20 01:52:17 dhclient[268]: short write: wanted 21 got 0 bytes
Dec 20 01:52:17 dhclient[268]: short write: wanted 21 got 0 bytes
Dec 20 01:52:17 dhclient[268]: DHCPACK from 10.215.0.1
Dec 20 01:52:17 dhclient[268]: DHCPREQUEST on xl1 to 255.255.255.255 port 67
Dec 20 01:50:24 dhclient[268]: DHCPREQUEST on xl1 to 10.215.0.1 port 67
Dec 20 01:49:37 last message repeated 24 times
Dec 20 01:38:42 last message repeated 14 times
Dec 20 01:29:57 last message repeated 4 times
Dec 20 01:28:08 last message repeated 2 times
Dec 20 01:27:48 dhclient[268]: DHCPREQUEST on xl1 to 10.215.0.1 port 67
Dec 20 01:01:03 php: : phpDynDNS: No Change In My IP Address and/or 25 Days Has Not Past. Not Updating Dynamic DNS Entry.
Dec 20 01:01:03 php: : DynDns: Cached IP: 84.75.14.209
Dec 20 01:01:03 php: : DynDns: Current WAN IP: 84.75.14.209
Dec 20 01:01:03 php: : DynDns: _detectChange() starting.
Dec 20 01:01:03 php: : DynDns: updatedns() starting
Dec 20 01:01:03 php: : DynDns: Running updatedns()This is starting to be render PFSense unusable for me. Every 30 bucks router can keep the ip from my isp for several months (last setup). Is it not possible to use the dhclient from the pre 1.0 versions???
Sorry for no better news.
-
As this problem gives biggest headaches to me, I've decided to use my linux server to run this via cronjob every minute:
wget -q –no-check-certificate --user=XXX --password=XXX --post-data "interface=wan&submit=Renew" http://IPOFPFSENSEGUI/status_interfaces.php -O /dev/null
This works fine for now. Hopefully the real solution to repair the dhclient will soon be there…
Cheers
fireseller -
Sorry but the new script is NOT running great, after 1 day again the connection got lost:
Dec 20 05:59:32 last message repeated 3 times
Dec 20 05:59:12 dhcpd: send_packet: Permission denied
Dec 20 05:52:02 last message repeated 2 times
Dec 20 05:51:51 dhcpd: send_packet: Permission denied
Dec 20 01:52:17 dhclient[268]: exiting.
Dec 20 01:52:17 dhclient[268]: exiting.
Dec 20 01:52:17 dhclient[268]: short write: wanted 21 got 0 bytes
Dec 20 01:52:17 dhclient[268]: short write: wanted 21 got 0 bytes
Dec 20 01:52:17 dhclient[268]: DHCPACK from 10.215.0.1
Dec 20 01:52:17 dhclient[268]: DHCPREQUEST on xl1 to 255.255.255.255 port 67
Dec 20 01:50:24 dhclient[268]: DHCPREQUEST on xl1 to 10.215.0.1 port 67
Dec 20 01:49:37 last message repeated 24 times
Dec 20 01:38:42 last message repeated 14 times
Dec 20 01:29:57 last message repeated 4 times
Dec 20 01:28:08 last message repeated 2 times
Dec 20 01:27:48 dhclient[268]: DHCPREQUEST on xl1 to 10.215.0.1 port 67
Dec 20 01:01:03 php: : phpDynDNS: No Change In My IP Address and/or 25 Days Has Not Past. Not Updating Dynamic DNS Entry.
Dec 20 01:01:03 php: : DynDns: Cached IP: 84.75.14.209
Dec 20 01:01:03 php: : DynDns: Current WAN IP: 84.75.14.209
Dec 20 01:01:03 php: : DynDns: _detectChange() starting.
Dec 20 01:01:03 php: : DynDns: updatedns() starting
Dec 20 01:01:03 php: : DynDns: Running updatedns()This is starting to be render PFSense unusable for me. Every 30 bucks router can keep the ip from my isp for several months (last setup). Is it not possible to use the dhclient from the pre 1.0 versions???
Sorry for no better news.
Then use a 30$ router! I am interested in constructive feedback, not Mr. Obvious taglines!
-
Sorry sullrich
My apologies. I'm sticking with PFSense. You're doing great work.
-
Unfortunately we are using the same dhclient that we used prior to 1.0. So nothing has changed in this regard.
But I do have an idea. Give me some moments, I would like to test ISC-DHCLIENT again and see how much work it's going to be to dump the OpenBSD dhclient that FreeBSD imported.
-
Thx alot. Due to the workaround I've got plenty of time now. Please let me know when there's something I can contribute / test in order to help.
I'll watch this thread anyway.Cheers
-
From a shell, issue this command (full installations only!):
fetch -q -o - http://www.pfsense.com/~sullrich/tools/cvs_sync.sh | sh
Sit back and let it do it's thing.
After it is done, issue shutdown -r now or reboot from the webConfigurator or option #5.
-
Hi sullrich
I've just issued:
fetch -q -o - http://www.pfsense.com/~sullrich/tools/cvs_sync.sh | shand got:
Setting CVS_IP to cvs.pfsense.com
Cannot find cvsup, pkg_add in progress
Cannot find cvs, fetching static cvs…
/usr/bin/cvs 100% of 1528 kB 187 kBps
Syncing with pfSense.com
Checking out RELENG_1
Connected to cvs.pfsense.com
Updating collection pfSenseHEAD/cvs
Mkdir CVSROOT
Create CVSROOT/.#activitymail
Create CVSROOT/.#avail
Create CVSROOT/.#checkoutlist
Create CVSROOT/.#ciabot_cvs.pl
Create CVSROOT/.#commitinfo
Create CVSROOT/.#config
Create CVSROOT/.#cvs_acls.pl
Create CVSROOT/.#cvswrappers
Create CVSROOT/.#editinfo
Create CVSROOT/.#loginfo
Create CVSROOT/.#modules
Create CVSROOT/.#notify
Create CVSROOT/.#precia.pl
Create CVSROOT/.#rcsinfo
Create CVSROOT/.#rel_check.php
Create CVSROOT/.#taginfo
Create CVSROOT/.#test_commit.php
Create CVSROOT/.#verifymsg
Mkdir CVSROOT/CVSROOT
Create CVSROOT/CVSROOT/cfg.pm
Create CVSROOT/CVSROOT/cfg_local.pm
SetAttrs CVSROOT/CVSROOT
Mkdir CVSROOT/Emptydir
SetAttrs CVSROOT/Emptydir
Create CVSROOT/activitymail
Create CVSROOT/activitymail,v
Create CVSROOT/avail
Create CVSROOT/avail,v
Create CVSROOT/cfg.pm
Create CVSROOT/cfg_local.pm
Create CVSROOT/checkoutlist
Create CVSROOT/checkoutlist,v
Create CVSROOT/ciabot_cvs.pl
Create CVSROOT/ciabot_cvs.pl,v
Create CVSROOT/commitinfo
Create CVSROOT/commitinfo,v
Mkdir CVSROOT/commitlogs
Create CVSROOT/commitlogs/misc
SetAttrs CVSROOT/commitlogs
Create CVSROOT/config
Create CVSROOT/config,v
Create CVSROOT/cvs_acls.pl
Create CVSROOT/cvs_acls.pl,v
Create CVSROOT/cvswrappers
Create CVSROOT/cvswrappers,v
Create CVSROOT/editinfo
Create CVSROOT/editinfo,v
Create CVSROOT/history
Detailer failed: Network write failure: Invalid argument
Will retry at 13:23:48Somethings wrong?
-
You can cancel your upgrade for now. We found some remaining issues with the new dhclient (some things still have to be changed due to different syntax). It's working on reboot though. We'll test some more things later and post when we have a new version to try.
-
okey. Just rebooted. Everything works as before…
-
Everything should be working. We really need ppl to test Optional WAN + DHCP more than anything at this point. We are using the same code for dhclient as m0n0 1.3b1 now so I think it is correct.
-
Have you made an update to the cvs?
-
Yes, rerun the command I mentioned prior.
-
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 0keep up the good work !</full-duplex>
-
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 !
-
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 0keep 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).