DHCLIENT loose lease, dies (WAN)



  • Hello!
    Once again back with a problem.

    Me and my friend both run 1.2.3-release. (fresh install)
    We have different ISP´s.
    We have no problems with our win xp/win 7/debian boxes.

    1. after every reboot, dhclient gets an initial IP-lease on the WAN interface. (working as intended)
    2. half the lease time goes by, but dhclient does nothing, no try to renew (nothing in the log, nothing with wireshark)
    3. the full lease time expires, same thing, no try to renew
    4. obiously, this leads to a lost IP on the wan interface. nothing gets done (shouldnt there be some kind of watchdog -> "omg omg no WAN ip, restart dhclient em0"??)
    5. I have to manually either go into the WAN-nic page and do "renew ip" , or go into execute command and do "dhclient em0"

    So far, this can be solved with a crontab entry like "@reboot /sbin/dhclient em0", but still, irritating as h***.

    Now to the BIG trouble:
    6. really random, 2 hrs~1 day after the "dhclient em0", this happens:
    Dec 20 17:09:53 dhclient[278]: connection closed
    Dec 20 17:09:53 dhclient[278]: exiting.

    7. well, dhclient is now completely dead. No renew of WAN IP, go back to (5)…. (that is, my connection is completely dead until I manually do a "dhclient em0")

    Obviously, this is a big problem, one of the core functions does not work.. My iptv,phone,and all workstations loose their internet connection.

    Any ideas? We´re out of them, so the alternative seems to be to look at another system (ebox, monowall, etc etc).



  • Does dhclient die between 1) and 3)?

    Are you reporting that both you and your friend see this problem OR is it just you that sees this problem?

    Are you running some form of PPP over the WAN link?

    Have you tried using a different type of interface (e.g. fxp, bge, …) on the WAN interface?

    Presumably your WAN link connects to a mode of some sort. Is there any sort of log on that device that you could examine to see if there is a correlation between events on the "modem" and dhclient exiting?

    The dhclient man page doesn't clearly specify a cause for dhclient exiting. Perhaps it exits if there is some form of link transition.



  • Thanks for your input.
    @wallabybob:

    Are you reporting that both you and your friend see this problem OR is it just you that sees this problem?

    Yes: Both me and my friend run pfsense, on different hardware, on different locations, different ISP´s.
    We both have this same problem.

    @wallabybob:

    Does dhclient die between 1) and 3)?

    Good point, have to check this. Googled a bit and found this:
    http://cvstrac.pfsense.com/tktview?tn=349
    A bit old, but that seems to be a good explanation to why i have to do a "dhclient em0"…

    @wallabybob:

    Are you running some form of PPP over the WAN link?

    No, nothing like that.

    @wallabybob:

    Have you tried using a different type of interface (e.g. fxp, bge, …) on the WAN interface?

    How do I do that? As I understand it, em0 gets it´s "name" from the type of NIC I´m using, in other words, the idea is to switch NIC?
    The NIC´s are INTEL PRO/1000, so I would find it strange if thats the problem.

    @wallabybob:

    Presumably your WAN link connects to a mode of some sort. Is there any sort of log on that device that you could examine to see if there is a correlation between events on the "modem" and dhclient exiting?

    No, no modem.
    We both have LAN/ethernet connection all the way into our appartments :)

    @wallabybob:

    The dhclient man page doesn't clearly specify a cause for dhclient exiting. Perhaps it exits if there is some form of link transition.

    Indeed this seems like a very strange behaviour.

    Next note: My ISP gives me 2 public ip´s.
    -I use one for pfsense (in order to have my consoles, computers, phones, yada yada, routed out onto internet),
    -One for my debian (lenny) box. (in order to give that server a public IP without the need of portforwarding and so on, also to have the server even working (now that pfsense doesnt :P)

    The debian box now has 14 days of uptime w/o problems.
    So I think that that´s enough to eliminate the ISP as the problem.. The problem clearly lies inside freeBSD and/or pfsense :(

    Also, the 2.0-alpha version seems to be working w/o problem.. (No need to restart dhclient at boot, had it running for ~24 hrs w/o any dhclient problems)
    But I dont really want to run the alpha in "live" envrionment. (one problem I have with the 2.0 build/snapshot i downloaded is that I cant even change from 192.168.1.0 -> 192.168.0.0 on the LAN, that breaks some of the firewall/nat:ing :P so it seems to still be in serious alpha-state)

    I have also been in contact with my ISP several times, as I find it ridiculous that they deliver a 100/100 Mbit line to me, but cannt offer me more than 2 public IP´s. But thats how it is, they cant give me more IP´s, so I´m stuck with needing some kind of NAT-solution :(



  • @basse:

    I have also been in contact with my ISP several times, as I find it ridiculous that they deliver a 100/100 Mbit line to me, but cannt offer me more than 2 public IP´s. But thats how it is, they cant give me more IP´s, so I´m stuck with needing some kind of NAT-solution :(

    I recently saw a projection that IP V4 address space would run out in 2011. Possibly there is some form of pressure on ISPs to keep down their requirements for new IP V4 addresses.

    @basse:

    @wallabybob:

    Have you tried using a different type of interface (e.g. fxp, bge, …) on the WAN interface?

    How do I do that? As I understand it, em0 gets it´s "name" from the type of NIC I´m using, in other words, the idea is to switch NIC?
    The NIC´s are INTEL PRO/1000, so I would find it strange if thats the problem.

    Maybe you had some problem specific to a particular interface type (e.g. vr) and changing to another interface type (if you had more than one on your system) might cause an interesting change in behaviour. Maybe changing the WAN interface (e.g. em0 to em1) might cause an interesting change in behaviour.

    You say your ISP allocates you two public IPs. Are these on the same subnet? If so, presumably pfSense sees DHCP renewal requests from Linux box. I wonder if that might have some correlation with dhclient exiting.


Log in to reply