Re: dhclient not setting a default route anymore

[Michael Heldebrant <hmike@portalofevil.com>]

On Sat, 2001-12-01 at 01:12, Adam Lydick wrote:
> I had problems with dhclient on charter as well. Have you tried pump
> (another DHCP client)? It worked for me. I also had a problem with the
> cable modem not bridging more then one machine (it would pick the first
> MAC addy that it saw, and only forward for it) I had to shut the modem
> down for about an hour to clear the ram, although I doubt that this is
> related to your problem.
> 
> My advice: try the "pump" program. If that fails, I'm not quite sure
> what to try next ;)
> 

I've used pump before, it wouldn't renew the lease EVER.  It had
problems trying to send out the request on the wrong interface
consistently.  I've also used dhcpcd previously with some success. 
dh-client worked great up until they switched dhcp servers, ip
addresses, and networks.  I used to get a line as follows:

lease {
  interface "eth0";
  fixed-address 24.10.169.XXX;
  option subnet-mask 255.255.255.128;
  option time-offset -28800;
  option routers 24.10.169.129;
  option domain-name-servers 24.2.204.33,24.2.204.34;
  option host-name "CLEANED";
  option domain-name "rchstr1.mn.home.com";
  option dhcp-lease-time 604800;
  option dhcp-message-type 5;
  option dhcp-server-identifier 65.15.50.10;
  option dhcp-renewal-time 302400;
  option dhcp-rebinding-time 529200;
  renew 6 2001/12/1 16:54:16;
  rebind 2 2001/12/4 07:54:16;
  expire 3 2001/12/5 04:54:16;
}


Now I get:

lease {
  interface "eth0";
  fixed-address 66.188.210.XXX;
  option subnet-mask 255.255.248.0;
  option time-offset 21600;
  option routers 0.0.0.0;
  option domain-name-servers 12.24.250.39,12.24.250.40;
  option host-name "CLEANED";
  option domain-name "home.roc.mn.charter.com";
  option broadcast-address 255.255.255.255;
  option netbios-name-servers 127.0.0.1;
  option dhcp-lease-time 604800;
  option dhcp-message-type 5;
  option dhcp-server-identifier 12.24.250.44;
  renew 2 2001/12/4 18:35:33;
  rebind 5 2001/12/7 09:35:33;
  expire 6 2001/12/8 06:35:33;
}

I'm just wondering if this is "correct" in a networking sense.  I don't
mind setting up a default route script for eth0, I'm just wondering if
there is a more elegant solution seing as how ifup/dh-client used to do
it for me.

--mike