Subject: Re: ath driver and wep
To: Greg Troxel <firstname.lastname@example.org>
From: Daniel Carosone <email@example.com>
Date: 10/03/2005 13:21:24
Content-Type: text/plain; charset=us-ascii
On Sun, Oct 02, 2005 at 08:34:21PM -0400, Greg Troxel wrote:
> Daniel Carosone <firstname.lastname@example.org> writes:
> > It fits with my observations, too, though not with the conclusions I
> > had been drawing from these observations.
> After reading your note it seems we agree at least mostly.
> > Now, maybe setting the address first is enough to cause the interface
> > to be up when the 40-bit key is set. I'll try to test that case soon
> > by leaving the address off the first line.
> That would be good to check; I am quite sure setting the address
> brings the interface up. Note that normal usage of ifconfig.foo0 is
> to have address/mask and not 'up'.
Yeah, it was basically a question of how ifconfig parses its command
line and issues ioctl's to the driver in order..
> > It used to be the case that I could reboot the
> > AP, and ath would re-connect to it automatically; that isn't happening
> > anymore as of my most recent -current for some (other) reason.
> I wonder if there is some unrelated issue with the state machine that
> requires an ath reset to associate again.
Not sure what it is, but it's unrelated. It happens on at least ral(4),
too. I need to try wi(4) again since ath(4) started losing this way.
> > > My understanding of cardbus on NetBSD is that normal behavior for
> > > network devices is to power off the slot when the interface is down.
> > Not just network devices, all pcmcia/cardbus cards.
> So does a serial port get powered off when not open (and not WOPEN)?
> What about a device with serial and ethernet? If so, that's neat.
Absolutely. The other slot in the same laptop is normally occupied by
a 3com 10/100 ethernet and modem combo. Because the modem is wired to
the internal speaker, I can hear it tick each time it is powered up;
this happens for device probing, ttyflags during rc, and whenever I
open the tty or bring up the ethernet.
There have been tweaks and improvements to the details (power up wait
times, for example) over the years, but it's worked this way in NetBSD
basically since pcmcia/cardbus support was added.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)
-----END PGP SIGNATURE-----