Subject: Re: ath driver and wep
To: Greg Troxel <gdt@ir.bbn.com>
From: Vincent <10.50@free.fr>
List: current-users
Date: 09/30/2005 22:01:16
Greg Troxel a écrit :
> Problem 2: Incoming frames are gibberish. The system thinks the card
> is doing hw wep. On doing 'ifconfig ath0 nwkey 0x[redacted]', packets
> can be exchanged with other systems. On doing 'ifconfig ath0 down'
> and then up, gibberish returns. (I set ssid/chan/nwkey in
> ifconfig.ath0 before the interface comes up.)
That's what I get with 3.99.9. If, when up, I type "ifconfig ath0 down"
then "ifconfig ath0 up", the communication would not resume. I have to
append the key "ifconfig ath0 up nwkey 0xdadadada" and then it works.
I am also constantly experiencing random failures of the link, but
ifwatch somehow takes care of it through a down/up script.
Just as an example,
tail -100 /var/log/messages
Sep 30 21:07:25 vincent /netbsd: ath0: link state changed to UP
Sep 30 21:07:25 vincent /netbsd: ath0: link state changed to DOWN
Sep 30 21:07:26 vincent /netbsd: cbb0: wait took 0.008974s
Sep 30 21:07:27 vincent /netbsd: ath0: interrupting at 11
Sep 30 21:07:28 vincent /netbsd: cbb0: wait took 0.009578s
Sep 30 21:07:28 vincent /netbsd: ath0: interrupting at 11
Sep 30 21:07:28 vincent /netbsd: ath0: link state changed to UP
Sep 30 21:07:27 vincent /usr/sbin/ifwatchd[309]: calling: /etc/athup
ath0 /dev/null 9600
Sep 30 21:07:27 vincent /usr/sbin/ifwatchd[309]: calling: /etc/athup
ath0 /dev/null 9600
Sep 30 21:26:25 vincent /netbsd: ath0: link state changed to DOWN
Sep 30 21:26:25 vincent /usr/sbin/ifwatchd[309]: calling: /etc/athup
ath0 /dev/null 9600
Sep 30 21:26:25 vincent /usr/sbin/ifwatchd[309]: calling: /etc/athup
ath0 /dev/null 9600
Sep 30 21:26:26 vincent /netbsd: cbb0: wait took 0.008943s
Sep 30 21:26:26 vincent /netbsd: ath0: interrupting at 11
Sep 30 21:26:27 vincent /netbsd: ath0: link state changed to UP
Sep 30 21:36:25 vincent /netbsd: ath0: link state changed to DOWN
Sep 30 21:36:26 vincent /netbsd: cbb0: wait took 0.008807s
Sep 30 21:36:26 vincent /netbsd: ath0: interrupting at 11
Sep 30 21:36:27 vincent /netbsd: ath0: link state changed to UP
Sep 30 21:36:25 vincent /usr/sbin/ifwatchd[309]: calling: /etc/athup
ath0 /dev/null 9600
Sep 30 21:36:25 vincent /usr/sbin/ifwatchd[309]: calling: /etc/athup
ath0 /dev/null 9600
Sep 30 21:46:25 vincent /netbsd: ath0: link state changed to DOWN
Sep 30 21:46:26 vincent /netbsd: cbb0: wait took 0.008422s
Sep 30 21:46:26 vincent /netbsd: ath0: interrupting at 11
Sep 30 21:46:27 vincent /netbsd: ath0: link state changed to UP
Sep 30 21:46:25 vincent /usr/sbin/ifwatchd[309]: calling: /etc/athup
ath0 /dev/null 9600
Sep 30 21:46:25 vincent /usr/sbin/ifwatchd[309]: calling: /etc/athup
ath0 /dev/null 9600
Sep 30 21:56:25 vincent /netbsd: ath0: link state changed to DOWN
Sep 30 21:56:26 vincent /netbsd: cbb0: wait took 0.008062s
Sep 30 21:56:26 vincent /netbsd: ath0: interrupting at 11
Sep 30 21:56:27 vincent /netbsd: ath0: link state changed to UP
Sep 30 21:56:25 vincent /usr/sbin/ifwatchd[309]: calling: /etc/athup
ath0 /dev/null 9600
Sep 30 21:56:25 vincent /usr/sbin/ifwatchd[309]: calling: /etc/athup
ath0 /dev/null 9600
Strange, it seems to happen every 10 mn or so, or at least each time
during the 25th second of a minute.
Vincent