Charles wrote: > Actually, I do have a comment or two :).
Good ! :-) > It looks like your ISP's > DHCP server is not allowing you to renew a lease, but instead is > giving you a new lease with the same IP. This is strange behavior, > and is what's causing your problem...as far as dhclient is concerned, > it's lease renewal was rejected (the first DHCPREQUEST and the > DHCPNAK, above), so it had to ask for a completely new lease (the > second DHCPDISCOVER, and the DHCPOFFER, DHCPREQUEST, and DHCPACK, > above). Very interesting! > I'd wager a guess that your ISP is lacking a bit in the "clue" > department...have you had any other problems with them? I suppose it > could also be wacky behavior by a windows DHCP server...they tend to > have other "not quite correct" observed behavior, like spitting the > DHCP broadcast packets out *EVERY* interface...it's not correct > behavior, but if you're not watching the traffic on the wire, you > wouldn't necessarily know it's happening. Do you know if your ISP is > an NT or unix shop? I have no idea whether my ISP is Unix or Windows, but I'm not sure I want to mess with them and help them fix their DHCP. My ISP swbell.net is Southwestern Bell. They have contracted with Prodigy for new DSL users, who have to use PPPOE. I have DHCP service grandfathered. My IP stayed constant for most of the entire time I have had DSL until about a year ago, when their dhclient server broke. When they fixed it, for a day or so I had new IPs, and then it stabilized and has not changed in the last year. I like having a more- or-less fixed IP. As I said earlier, it is a "poor man's static IP". Since I have the domain name fractint.org, and have www.fractint.org hosted by a friend, I have asked the administrator of the fractint.org host to make tim.fractint.org to point to my IP. Since he doesn't have an automated way for me to update that IP, this only works because it rarely changes. I have only had to ask him to change it once in more than two years :-) However the behavior you mentioned does make a problem with seawall as we have discussed. From what you are describing, if my ISP's DHCP server were working right, the seawall problem of the network reloading, and hence requiring a seawall restart, would not happen. But my adding the "seawall restart" line in dhclient-exit-hooks makes everything OK. I think I will let sleeping dogs lie, unless you can see any way my ISP having the right DHCP behavior would help me. Thanks, looks like I can tell Tom Eastep there is not really a Dachstein/Seawall issue after all. In another message I asked folks to report how their DHCLIENT setup works. We'll see if the behavior I reported is unique to me or not. Tim _______________________________________________ Leaf-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-user
