On Wed, 2005-04-06 at 12:07 +0200, Thomas Hood wrote: > What is really needed is for netapplet to grok logical interfaces. > Currently when I click on the netapplet icon I get a list of physical > interfaces, labelled "Network Connections". If I click on one of these > names then netapplet seems to run (via netdaemon) "ifup <physiface>" or > "ifdown <physiface>" on these; then ifup uses its internal mapping > mechanism to assign a logical interface. SFAICT netapplet has no > awareness of logical interfaces or mapping. Below "Network Connections" > it displays a list of "Wireless Networks". If I click on these items > then netapplet sends out iwconfig commands. SFAICT this ignores the > information provided on "wireless" option lines in logical interface > definitions and reconfigures Wi-Fi cards directly.
Yes. I'm unsure how to present logical interfaces in a reasonable way. ifupdown allows you to assign any logical interface to any physical interface, which allows a great deal of flexibility but is a bit of a UI nightmare. I'd prefer not to provide a second level of menus listing every logical interface if at all possible. > I don't know whether or not netapplet is aware that changing wireless > parameters can have consequences for whether or not "Network > Connections" should be up or not. E.g., if there are no access points > in range then wlan0 should be brought down, but netapplet does not bring > down wlan0 when I try the experiment. Indeed, I find that netapplet > does not succeed in switching wireless networks at all. But that is > another bug. Netapplet doesn't attempt to provide any sort of network control policy - networkmanager behaves more like this. This is a design decision rather than a bug. It leaves policy up to the underlying infrastructure (ifupdown and stuff like ifplugd) and allows the user to override some automatic decisions. I can't reproduce your issues with switching wireless networks. This may be a driver issue - ISTR that orinoco_cs doesn't like switching networks while the interface is up. Could you open a new bug for that issue? -- Matthew Garrett | [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
