Subject: Re: DHCP with Linksys firewall
To: None <netbsd-help@netbsd.org>
From: James K. Lowden <jklowden@schemamania.org>
List: netbsd-help
Date: 01/08/2002 19:51:37
On Tue, Jan 08, 2002 at 03:12:15PM -0800, Tracy Nelson wrote:
> From: "Andy R" <quadreverb@yahoo.com>
> > o Do you have any errors reported from dhcp in your
> > /var/log/messages file?
> 
> I do now!  I was playing with the 'media' option of ifconfig and set my
> interface to 10base2 and started getting "network is down" errors.  Now I
> have it set to AUI (weird, because it's a 10baseT connection, but the driver
> won't accept '10baseT' or 'UTP') and those errors have gone away.  It still
> doesn't work, though.  What I'm seeing is something like this:
> 
> dhclient: DHCPDISCOVER on 255.255.255.255 port 67 interval 3
> dhclient: DHCPDISCOVER on 255.255.255.255 port 67 interval 7
> dhclient: DHCPDISCOVER on 255.255.255.255 port 67 interval 7
> dhclient: DHCPDISCOVER on 255.255.255.255 port 67 interval 9
> dhclient: DHCPDISCOVER on 255.255.255.255 port 67 interval 5
> dhclient: no DHCPOFFERS received.
> dhclient: no working leases in persistent database, sleeping

Tracy, 

Which driver is that?  

Your ifconfig.xxx has to indicate the right media type (or autodetect
has to work), so DHCP can find a server and get an address.  Not to
find the wire is not to get the address.  

BTW, you don't need an ip address for the driver to talk to the
Ethernet or for tcpdump to work.  If there's any traffic at all on the
wire, tcpdump will tell you if you're connected to it.  

HTH and regards, 

--jkl