Date: Tue, 19 Jun 2007 12:21:53 +0800 From: "Sepherosa Ziehau" <sepherosa@gmail.com> To: "Ian FREISLICH" <ianf@clue.co.za> Cc: Rui Paulo <rpaulo@fnop.net>, freebsd-current@freebsd.org Subject: Re: ath(4) problems after sam_wifi merge Message-ID: <ea7b9c170706182121x1c9386d6l5aabead13f40a8a0@mail.gmail.com> In-Reply-To: <E1I0HNU-0000YQ-Rg@clue.co.za> References: <rpaulo@fnop.net> <86d4zupje9.wl%rpaulo@fnop.net> <E1I0HNU-0000YQ-Rg@clue.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/18/07, Ian FREISLICH <ianf@clue.co.za> wrote: > ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > ether 00:17:f2:50:66:16 > inet 10.0.0.18 netmask 0xffffff00 broadcast 10.0.0.255 > media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/24Mbps) > status: associated > ssid cluelan channel 13 (2472 Mhz 11g) bssid 00:11:50:0b:c5:a6 > authmode WPA privacy ON deftxkey UNDEF TKIP 3:128-bit txpowmax 35 > bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 > roam:rssi11g 14 roam:rate11g 5 protmode CTS burst roaming MANUAL > bintval 100 > > In a MacBook Pro. After recent wireless commits the interface has > become somewhat unstable. I'm using WPA with wpa_supplicant. > Interestingly, it's more stable at home than at work. The symptoms > I see are that even though the interface has an IP address and there > is a default route, after some time of inactivity I'll start seeing Sam has committed a fix for the inactivity problem when wpa_supplicant is used. Have you pulled in that fix? > "no route to host" error messages even though it thinks it's still > associated with the AP. Best Regards, sephe -- Live Free or Die
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ea7b9c170706182121x1c9386d6l5aabead13f40a8a0>