Hi Johannes, On Sun, 2008-03-23 at 14:00 +0100, Bas Hulsken wrote: > before I blow up the system, I guess this should do the trick? > (remember, I'm not a kernel hacker ;-): ok.. so I decided to just give it a try.. seems to work, this is dmesg upon ifupping the interface: phy0: Selected rate control algorithm 'pid' Registered led device: rt2500pci-phy0:radio rt2500pci MAC changed: 00:0c:f6:14:05:19 rt2500pci filter_flags: 2 ADDRCONF(NETDEV_UP): wlan1: link is not ready when I run hostapd, this is in dmesg: rt2500pci MAC changed: 00:00:00:00:00:00 rt2500pci MAC changed: 00:0c:f6:14:05:19 rt2500pci MAC changed: 00:00:00:00:00:00 rt2500pci MAC changed: 00:0c:f6:14:05:19 rt2500pci filter_flags: 2 rt2500pci filter_flags: 0 rt2500pci MAC changed: 00:00:00:00:00:00 rt2500pci MAC changed: 00:0c:f6:14:05:19 rt2500pci filter_flags: 2 this is immediately on startup of hostapd, after that filter and MAC remain unchanged (at least if my printk catches everything). thanks, Bas -- 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
