On Nov 23,  9:21am, Greg Oster wrote:
} John Nemeth writes:
} > On Nov 10,  4:05pm, Ted Lemon wrote:
} > } 
} > } It may be that you can win by adding the following to your
} > } dhclient.conf:
} > } 
} > } 	send dhcp-client-identifier "cs840999-a";
} > 
} >      Okay, I've been working on it some more (did have a bit of a
} > delay due to a problem with the cable modem).  Anyways, I've read RFC
} > 2132 (DHCP Options), hacked on dhclient, and have come pretty close to
} > duplicating the packet from the Win95 box,
} 
} Having just gotten a cable modem hooked up last week (and, like you, waiting 
} for some cable modem problems to be sorted out) I've got a NetBSD box quite 
} happily doing dhcp/ipf/ipnat to a Shaw@Home cable connection.  My 
} dhclient.conf, in full, looks like:
} 
} interface "ne1" {
}     send dhcp-client-identifier "cs22234-a";
} }

     I tried this.  It didn't work, the server didn't respond at all.
Also, after I tried this, the Win95 box was unable to get a new lease
for a while as well.  Actually, this line violates RFC 2132, which
says that the first byte of the dhcp-client-identifier is a code byte
that specifies what type of identifier it is.

} > This is my current dhclient.conf:
} > 
} > interface "ep0" {
} >         default default-ip-ttl 32;
} >         send dhcp-client-identifier 1:0:a0:24:c8:90:67;
} >         send host-name "CS840999-a";
} > }
} 
} I think the dhcp-client-identifier has to be the "csxxxxx-a" thingy, no?
} (I don't think it cares what ethernet card is hooked up, as I've never had to 
} specify a MAC address anywhere...)

     I was simply duplicating what the Win95 box did, since it works.

}-- End of excerpt from Greg Oster