D-Link NIC.

[gabriel]

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 at fabiankeil.de> wrote:
> "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:
> 
> #!/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