freebsd-listen at fabiankeil.de
Sun Mar 6 10:56:41 PST 2005
"Subhro" <subhro.kar at gmail.com> wrote:
> > -----Original Message-----
> > From: owner-freebsd-questions at freebsd.org [mailto:owner-freebsd-
> > questions at 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:
case "$1" in
echo "Activating WLAN"
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
echo "Deactivating WLAN"
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.
More information about the freebsd-questions