D-Link NIC.

[gabriel]

I _am_ certain that it works because I have the pc dual booting
windows and it works there. The problem is I dont know what the
default driver is I should use.

Cheers!


On Sun, 6 Mar 2005 04:35:33 +0530, Subhro <subhro.kar at gmail.com> wrote:
> 
> 
> Indian Institute of Information Technology
> Subhro Sankha Kar
> Block AQ-13/1, Sector V
> Salt Lake City
> PIN 700091
> India
> > -----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#
> >
> > 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.
> 
> Also I strongly feel something fishy in the WLAN interface being detected as
> ndisX instead of wiX. The first thing I would do is use the default driver
> *even* if some documentation says that it is buggy.
> 
> Regards,
> S.
> 
> 
> 


-- 
gabriel,

Member of:
FreeBSD-Announce
FreeBSD-Hardware
FreeBSD-Multimedia
FreeBSD-questions