On Thu, 2007-08-30 at 12:16 -0400, Dan Williams wrote: > So that's a b*tch and a half to deal with, when there are multiple > devices that actually share certain properties (like frequency). That's > what's happening with libertas for OLPC, and it's not easy to coordinate > between the devices because there's no standard way for each device to > say "I share X, Y, and Z with device A". It would be quite a bit easier > if NM could figure out exactly what attributes would be shared. > > For libertas, everything is shared except for SSID, mode, bitrate, and > possibly encryption settings. Frequency is shared, yet they are two > completely separate WEXT interfaces. Not fun. Yeah, I can see how that's tough. However, this is where the wiphy comes in handy, it's fairly well defined which properties are shared if the devices are linked to a single wiphy. > Right; can somebody attach an 'lshal' run that shows at least one > STA-mode interface and one non-STA-mode interface? Send it to me > privately since I want the whole thing, not just the bits for the > net.interface object only. Sent. > I don't plan on making NM talk to hostapd to do master mode on an > interface for a really, really long time, if ever. That's better left > to other tools. As long as a STA interface _is_ a STA interface (and > doesn't have other properties like "monitor"/"raw") then this will work > fine. Yeah, that's what it should be. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
