Date: Mon, 7 Mar 2005 11:32:37 -0800 From: gabriel <normal1.lists@gmail.com> To: freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: D-Link NIC. Message-ID: <efb85820503071132e17499c@mail.gmail.com> In-Reply-To: <efb858205030611004d91d4f2@mail.gmail.com> References: <efb858205030513273fea6df1@mail.gmail.com> <422a3b4c.6460c00f.48d7.412b@smtp.gmail.com> <20050306195438.29f69e9d@localhost> <efb858205030611004d91d4f2@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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? Thanks! 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. > > Cheers! > > 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. > > > > > > > > Can anyone provide any insight? > > > > > > > > ndis0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500 > > > > ether 00:11:95:87:8b:e4 > > > > media: IEEE 802.11 Wireless Ethernet autoselect > > > > status: no carrier > > > > ssid "" > > > > channel -1 authmode OPEN powersavemode OFF powersavesleep 100 > > > > rtsthreshold 2312 protmode CTS > > > > wepmode OFF weptxkey 1 > > > > dolores# > > > > How do you set up the NIC? > > > > I use a small script to load and unload the driver: > > > > #!/bin/sh > > > > case "$1" in > > > > start) > > echo "Activating WLAN" > > kldload ndis > > kldload if_ndis > > > > ifconfig ndis0 ssid ec60bfg3b4 wepkey 1:0x12345678911234567891123456 wepmode on > > ifconfig ndis0 inet 192.168.1.49 > > > > route add 0.0.0.0 192.168.1.1 > > ;; > > stop) > > echo "Deactivating WLAN" > > kldunload if_ndis > > kldunload ndis > > ;; > > esac > > > > exit 0 > > > > DHCP works as well, but I don't use it. > > > > > > if I try to use dhcp the ip address will just go to zeroes. :\ > > > > > > > > > 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. > > > > > Also I strongly feel something fishy in the WLAN interface being detected as > > > ndisX instead of wiX. > > > > This is expected behaviour. > > > > Regards > > Fabian > > -- > > http://www.fabiankeil.de > > > > -- > gabriel, > > Member of: > FreeBSD-Announce > FreeBSD-Hardware > FreeBSD-Multimedia > FreeBSD-questions > -- gabriel, Member of: FreeBSD-Announce FreeBSD-Hardware FreeBSD-Multimedia FreeBSD-questions
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?efb85820503071132e17499c>