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";
} 
} I am assuming that you aren't going to boot both the Win95 machine and
} the NetBSD machine at once - if so, don't do that.   The reason I
} think that sending that string in the client identifier will work is
} that I suspect your ISP is only willing to let you have one IP
} address, which is fixed to a particular client identifier.   If that
} is the case, you need to send the same identification your Win95 box
} is sending.

     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, but I still don't get any
response from the DHCP server.  Here are more packet samples:

This is from the NetBSD box running 1.3.2, using the latest version of
dhcp from ftp.isc.org:

03:16:52.663913 0:a0:24:c8:90:67 ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 > 255.255.255.255.67: xid:0xefe01a31 vend-rfc1048 T53:1 T61:1.0.160.36.200.144.103 HN:"CS840999-a^@" [tos 0x10] (ttl 16, id 0)

This is from the Win95 box:

23:19:29.976365 0:60:97:bb:ef:31 ff:ff:ff:ff:ff:ff 0800 342: 0.0.0.0.68 > 255.255.255.255.67: xid:0xf0c004c1 vend-rfc1048 T53:1 T61:1.0.96.151.187.239.49 T50:940982552 HN:"CS840999-A^@" (ttl 32, id 6182)

As you can see, they are pretty close, but not exactly the same.  T61
(dhcp-client-identifier) is the ethernet Mac address.  I did try
cheating and using the one from the Win95 box, but that didn't have
any effect.  Anyways, I have a couple of questions: first, what is
"tos" in the NetBSD example; second, what can I do to make them match
even closer, in particular, get rid of "tos" and up the ttl?  BTW, T50
is requested-ip-address, and probably isn't important.  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 made several attempts to up the ttl, but nothing I tried worked.

     BTW, we have discovered that it's possible to get multiple IP
addresses simply by using the same 'host-name'.

} I haven't suggested sending the hostname because I happen to know that
} @Home considers the hostname and client identifier synonymous, and I'm
} assuming that you're using an @Home service, or one that works the

     I'm using Shaw@Home in Canada.

}-- End of excerpt from Ted Lemon