Subject: Re: introducing ath(4) and the FreeBSD 802.11 layer
To: Bruce J.A. Nourish <firstname.lastname@example.org>
From: David Young <email@example.com>
Date: 10/13/2003 18:50:01
On Mon, Oct 13, 2003 at 12:42:35PM -0700, Bruce J.A. Nourish wrote:
> On Mon, Oct 13, 2003 at 04:36:22AM -0500, David Young wrote:
> > I have just committed my port of FreeBSD's Atheros chipset driver,
> > ath(4). The driver supports 802.11a/b/g multimode cards made by
> > manufacturers such as D-Link and Linksys. Virtually every 802.11a radio
> > manufactured today contains the Atheros chipset.
> Wohoo! Thanks!
> I have a couple of questions:
> * When I run "wiconfig ath0", I get:
> wiconfig: SIOCGWAVELAN: Invalid argument
> NIC serial number: [ ]
> Station name: [ telstar.bjan.net ]
> SSID for IBSS creation: [ mordor ]
> Current netname (SSID): [ ]
> Desired netname (SSID): [ mordor ]
> Current BSSID: [ 00:00:00:00:00:00 ]
> Channel list: [ 2 3 4 5 6 7 8 9 10 11 12 ]
> IBSS channel: [ 1 ]
> Current channel: [ 65535 ]
> Comms quality/signal/noise: [ 0 0 0 ]
> Promiscuous mode: [ Off ]
> Port type: [ 1 ]
> MAC address: [ 00:0c:41:16:a7:95 ]
> TX rate (selection): [ 0 ]
> TX rate (actual speed): [ 0 ]
> Beacon Interval (current) [msec]: [ 0 ]
> Maximum data length: [ 2312 ]
> RTS/CTS handshake threshold: [ 2312 ]
I will look into it.
> * I want to join a WEP encrypted network. I think the commands to
> bring the interface up should look like this:
> # ifconfig ath0 nwid mordor
> # ifconfig ath0 nwkey <hex key>
> # ifconfig ath0 up
> # dhclient ath0
> Firstly, is this generally correct? This is my first time with
> 802.11 on BSD.
> Secondly, ifconfig rejects my 26-digit hex key, presumably for bieng
> too long. Where should I look to fix this?
I have fixed this bug. Do a cvs update.
David Young OJC Technologies
firstname.lastname@example.org Urbana, IL * (217) 278-3933