Date: Fri, 8 Aug 2003 20:24:16 +1000 From: David Lodeiro <dlodeiro@inspired.net.au> To: freebsd-current@freebsd.org Subject: Re: ath0 driver Message-ID: <200308082024.16772.dlodeiro@inspired.net.au> In-Reply-To: <1618623677.1060155480@melange.errno.com> References: <200308062049.18324.dlodeiro@inspired.net.au> <1618623677.1060155480@melange.errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi, > > >The version should be 0.9.5.3 or better (can't remember if I committed .4 > > >or .3). > >Shouldn't that be 0.9.5.2? I run the latest current, and > >hw.ath.hal.version is 0.9.5.2. > >You're right; I committed a slightly older version to FreeBSD than to Linux. >The version The version I have is 0.9.5.2. As to the tcpdump, I get er# tcpdump -i ath0 -y IEEE802_11 tcpdump: data link type DLT_IEEE802_11 tcpdump: listening on ath0 00:18:02.152294 10.0.0.1.netbios-dgm > 10.0.0.255.netbios-dgm: NBT UDP PACKET(138) 00:18:02.152502 10.0.0.1.netbios-dgm > 10.0.0.255.netbios-dgm: NBT UDP PACKET(138) and thats all that comes up. Does this driver support being set up as an access point yet? I figured it did because ifconfig ath0 mediaopt hostap didnt return any errors. Please let me know if Im doing something wrong. Im sure ive got my *.conf files set up right as I have used them before, however I could be wrong. Thanks for the help David > > Ive got a Dlink DWL-G520 that Ive installed into a Freebsd system. Ive > > set up the card with the following00:18:02.152294 10.0.0.1.netbios-dgm > 10.0.0.255.netbios-dgm: NBT UDP PACKET(138) 00:18:02.152502 10.0.0.1.netbios-dgm > 10.0.0.255.netbios-dgm: NBT UDP PACKET(138) > > ifconfig_ath0="inet 10.0.0.1 netmask 255.255.255.0 ssid daves channel 10 > > media DS11 mediaopt hostap" > > > > This system was cvsuped and buildworld about 3 days ago. The card appears > > to be working because when I try to connect with my PDA it shows full > > Link and quality, and when I ifconfig ath0 down , the link and quality > > go down to nothing. > > > > However it doesn't give out dhcp addresses over this interface. Im sure > > my > > > dhcpd.conf is fine because I've used a similar one on a laptop => aka > > wireless access point that worked very well. So I tried to use dstumbler > > to see if it could detect the PDA, however it gives me the following > > error > > > > error: unable to ioctl device socket: Operation now in progress > > > > and it stays that way. > > > > Has anyone had this issue as well or now what it means? > > Verify you have the latest HAL using > > sysctl hw.ath > > The version should be 0.9.5.3 or better (can't remember if I committed .4 > or .3). If you have an old version update. Otherwise you might try > tapping 802.11 frames with tcpdump on the AP to see what's going on: > > tcpdump -i ath0 -y IEEE802_11 > > As to dstumbler, it is intimately tied to the wi driver at the moment. I > have a version that works w/ wi and ath drivers but it's a major rewrite > and incomplete. If someone wants to pick it up I'd be happy to pass the > (incomplete) work on... > > Sam
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200308082024.16772.dlodeiro>