This is the result of my quest to find the reason why I couldn't roam
with any mac80211 driver (tested with iwl3945 and b43).
When you use dhclient for dhcp, the (very old) default dhclient-script
brings the interface down and then up again after it receives a DHCPNAK
(and on some other occasions). With the ieee80211 stack, this never
caused any problems.
However, with mac80211, after the interface has been brought down and
then up again, the "RUNNING" flag in ifconfig disappears and no data is
being transmitted. Due to dhclient's weird behaviour, this makes any
mac80211 driver unusable with dhclient and the (very old) default script.
I had no difficulty fixing this problem (once I found it), simply remove
the word 'down' from all ifconfig-lines in dhclient-script.
My question is, should this be considered a bug in mac80211?
IMO, when an interface is brought down and then up again, one of the
following things should happen:
1) Everything works as before
2) Nothing works, but the card disassociates from the network.
The current behaviour (card stays associated, but no data is transmitted
any more) is unintuitive and costed me much time.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
