Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 11 Mar 2005 20:02:53 +0100
From:      Fabian Keil <freebsd-listen@fabiankeil.de>
To:        gabriel <normal1.lists@gmail.com>
Cc:        freebsd-questions <freebsd-questions@freebsd.org>
Subject:   Re: D-Link NIC.
Message-ID:  <20050311200253.21058e38@localhost>
In-Reply-To: <efb85820503071132e17499c@mail.gmail.com>
References:  <efb858205030513273fea6df1@mail.gmail.com> <422a3b4c.6460c00f.48d7.412b@smtp.gmail.com> <20050306195438.29f69e9d@localhost> <efb858205030611004d91d4f2@mail.gmail.com> <efb85820503071132e17499c@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
gabriel <normal1.lists@gmail.com> wrote:

> Okay, so I've managed to get the Wless nic talking to the Access Point
> (per the logs) but I'm having problems getting an ip address. Check
> out the dhclient output:
> 
> dolores# dhclient -v ndis0
> Internet Systems Consortium DHCP Client V3.0.1
> Copyright 2004 Internet Systems Consortium.
> All rights reserved.
> For info, please visit http://www.isc.org/products/DHCP
> 
> Listening on BPF/ndis0/00:11:95:87:8b:e4
> Sending on   BPF/ndis0/00:11:95:87:8b:e4
> Sending on   Socket/fallback
> DHCPDISCOVER on ndis0 to 255.255.255.255 port 67 interval 4
> DHCPDISCOVER on ndis0 to 255.255.255.255 port 67 interval 11
> DHCPDISCOVER on ndis0 to 255.255.255.255 port 67 interval 14
> DHCPDISCOVER on ndis0 to 255.255.255.255 port 67 interval 13
> DHCPDISCOVER on ndis0 to 255.255.255.255 port 67 interval 19
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> dolores#
> 
> here's the ifconfig ndis0 output:
> 
> ndis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         inet6 fe80::211:95ff:fe87:8be4%ndis0 prefixlen 64 scopeid 0x4 
>         inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
>         ether 00:11:95:87:8b:e4
>         media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps)
>         status: associated
>         ssid normal1@gmail.com 1:normal1@gmail.com
>         channel 8 authmode OPEN powersavemode OFF powersavesleep 100
>         rtsthreshold 2312 protmode CTS
>         wepmode MIXED weptxkey 1
>         wepkey 1:104-bit
> 
> Anyone that has experienced this before? Any ideas?

As you can read below, I already assumed, that you don't
have "device bpf" in your kernel. Can you confirm or deny it?
 
> On Sun, 6 Mar 2005 11:00:58 -0800, gabriel <normal1.lists@gmail.com> wrote:
> > Thats a good script. How did you install the ndis driver/wrapper? -
> > Cause I think some of the problem may be there.
 
> > On Sun, 6 Mar 2005 19:54:38 +0100, Fabian Keil
> > <freebsd-listen@fabiankeil.de> wrote:
> > > "Subhro" <subhro.kar@gmail.com> wrote:
> > >
> > > > > -----Original Message-----
> > > > > From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-
> > > > > questions@freebsd.org] On Behalf Of gabriel
> > > > > Sent: Sunday, March 06, 2005 2:57
> > > > > To: freebsd-questions
> > > > > Subject: Re: D-Link NIC.

> > > > Are you positive that the DHCP function of your AP works perfectly? I am
> > > > asking thing because I have come across a couple of routers which happily
> > > > routes packets to static IPs but messes everything up as soon as it is asked
> > > > to handle DHCP.
> > >
> > > I guess the DHCP server is working, but Gabriel's kernel is lacking "device bpf"
> > > which is needed for dhclient.
> > >
> > > Otherwise the IP is set to 0.0.0.0 without error message, just as described.

Regards
Fabian
-- 
http://www.fabiankeil.de



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050311200253.21058e38>