On Sat, 2009-03-14 at 10:03 -0400, Derek Atkins wrote: > Dan Williams <[email protected]> writes: > > > either. There's a lot more to the NM D-Bus API than just the device > > itself and whether that device is connected or not. > > True. However in some cases that's all that's important. For > example if you want to run a VPN over your non-NM-aware device, > you need to tell NM that the network is up so it can enable VPN > support. > > Being able to tell NM "hey, there's a network here -- enable VPN" > is definitely a worthwhile feature to have, and IMHO less work > than "you need to make NM aware of your custom network hardware > so it can manage that hardware".
The better solution is, of course, to get that VPN fully supported in NM, becuase again, unless it is, you have (a) a completely different network configuration UI and path, (b) probably no user/system connection split, (c) no ability to control access to the connection with stuff like PK, and (d) artificial D-Bus API information that simply cannot be guaranteed. Dan _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
