Stefan Rompf wrote:
Am Sonntag 15 Januar 2006 16:51 schrieb Johannes Berg:
Isn't that rather a question of having good user-space tools that make
deactivating one type of interface and activating another seamless?
Well, it's always easy to point to userspace. However, unregister_netdev()
initiates a lot of actions. IPv4 addresses and routes are removed, same for
IPv6, IPX, Appletalk etc. Stacked VLAN devices are recursively unregistered
(even though I have not tried yet if it works when I create VLANs over 802.3
emulated wlan interfaces ;-), udev bloat runs. And all this stuff has to be
restored by the nifty new configuration utility, possibly including ifindex
and future protocols.
This is from my usage pattern that I want to go into monitor mode on current
channel, look at some packets and return to the association without losing
layer 3 configuration.
So after all, it is IMHO way less painful to handle a mode change in the
kernel.
To do what you describe I would create a monitor mode device, switch
channel, then destroy it. All the time you leave the station device
unchanged, though you probably need to disable it. This may not be
possible with all devices--i.e. for those that require different
firmware to do monitoring you will be restricted to a single virtual
device and/or operating mode.
Sam
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
