> On Monday, October 28, 2013 6:10 AM, Stefan Sperling <[email protected]> wrote: >> On Sun, Oct 27, 2013 at 10:43:05PM -0700, Fred Snurd wrote: >> >> $ sudo ifconfig ath0 nwid <my-id> wpakey <my-password> >> $ ifconfig ath0ath0: flags=8822<BROADCAST,NOTRAILERS,SIMPLEX,MULTICAST> mtu >> 1500 >> lladdr a8:54:b2:23:da:80 >> priority: 4 >> groups: wlan >> media: IEEE802.11 autoselect >> status: no network >> ieee80211: nwid <my-id> >> wpakey <not displayed> wpaprotos wpa1,wpa2 wpaakms psk wpaciphers >> tkip,ccmp wpagroupcipher tkip >> $ >> >> ...which still shows that the link has not changed as expected.> > > The interface isn't marked UP in the flags= line. > So try 'ifconfig ath0 up' here. > > dhclient does this automatically before requesting a lease.
Thanks Stefan & Reyk for replying. Further testing tonight showed that the original /etc/ifstated.conf file did indeed work. I had thought that the link would be re-established quickly, but this was not the case. In fact, re-establishing the link took ~3-4 minutes to complete (but this factors in the time the AP needed to get reinitialized too...). I added logger(1) messages to my ifstated.conf(5) observing that the link state bounces about before stabilizing. I don't know if this peculiarity is associated with the ath(4) driver, WIstron CM9 card, Alix hardware, or the cheap ActionTec AP used. If there is any interest, I can submit a report with more details. I simply would like to take more time determining if there is anything else I can observe. Thanks again for your timely replies.
