multiple-device questions
What are the plans for UI for controlling multiple-device behavior? Right now nm-applet just connects to all networks that have automatic configurations. This is potentially confusing. A few people have filed bugs or asked questions on this list. If the fastest device does not have a gateway defined (none offered by DHCP, link-local only, or none configured in static config) will NM choose a slower device for the default route? What signaling is given the listeners (like Pidgin or Evolution) when a device goes down but there are other devices up? Is the signaling different when it's the default route (or not) that has gone down? What if, for example, evolution is connected to a mail server on a private network and the default route (on another network) goes down? Would it still receive a signal and go offline? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: multiple-device questions
On Thu, May 15, 2008 at 11:12 AM, Andrew Jorgensen [EMAIL PROTECTED] wrote: What are the plans for UI for controlling multiple-device behavior? Right now nm-applet just connects to all networks that have automatic configurations. This is potentially confusing. A few people have filed bugs or asked questions on this list. If the fastest device does not have a gateway defined (none offered by DHCP, link-local only, or none configured in static config) will NM choose a slower device for the default route? Yes. What signaling is given the listeners (like Pidgin or Evolution) when a device goes down but there are other devices up? NM offeres two ways for applications interested in network state. One is very convenient and easy to use but because of that not very detailed. It only signals changes when networking is disabled, (no active connections and a) connection is activating, activated, disconnected. The other API is a detailed one and is what nm-applet uses, for every change a signal is emitted. As there are many objects involved, it's a bit cumbersome to register all these signal handlers if the application only cares about if a connection is active or not. So in summary, if any application (pidgin, evolution) want, they can have a very detailed view of the state and signals when anything changes, but as of now, they use the simple version. Is the signaling different when it's the default route (or not) that has gone down? See above. What if, for example, evolution is connected to a mail server on a private network and the default route (on another network) goes down? Would it still receive a signal and go offline? See above. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: multiple-device questions
On Thu, 2008-05-15 at 02:12 -0600, Andrew Jorgensen wrote: What are the plans for UI for controlling multiple-device behavior? There's an applet re-write on the table for 0.7.1. The current menu-based design pretty much falls over for multiple devices. Right now nm-applet just connects to all networks that have automatic configurations. This is potentially confusing. A few people have filed bugs or asked questions on this list. Right; though this isn't so much different than current networking systems. If you want complete manual control of your connecitons, then you don't mark those connections as autoconnect, and then you get to manually activate and deactivate those connections as you see fit. If the fastest device does not have a gateway defined (none offered by DHCP, link-local only, or none configured in static config) will NM choose a slower device for the default route? Yes. What signaling is given the listeners (like Pidgin or Evolution) when a device goes down but there are other devices up? As Tambet said, there are two mechanisms: a) Simple overall network state such as DISCONNECTED, CONNECTING, and CONNECTED, which is a composite of all the current device states. If at least one device is connected and there is a default route, the state will be CONNECTED. b) The ActiveConnection API. Each current connection has an ActiveConnection object which clients can use to figure out the state of individual network connections and devices. Each active connection has one or more devices assigned to it, and a device cannot be assigned to more than one active connection. It's important to remember that NM deals with _connections_, not really individual devices, though NM does provide state for individual devices as well. Is the signaling different when it's the default route (or not) that has gone down? Yes; you get org.freedesktop.DBus.PropertyChanged signals for the ActiveConnection objects when their 'default' property changes. Only one ActiveConnection object will have a True 'default' property, and that is the connection that has the default route. What if, for example, evolution is connected to a mail server on a private network and the default route (on another network) goes down? Would it still receive a signal and go offline? VPN connections are also ActiveConnection objects and will exist for the lifetime of the VPN connection. We haven't completely though out how apps should tie into VPN support, but if the app really wanted to, it could store the settings service name and connection ID of the VPN connection it cared about, and track the lifecycle of that VPN connection. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Is this the way NM should work?
On Wednesday 14 May 2008 09:31:47 Ryan Novosielski wrote: In the past, it was simply not possible to have more than one NIC enabled at once. This is something that was desired by many over the years. 0.6.x did not support it, and therefore you got the old behavior. I agree that having multiple NICs enabled at the same time is necessary [I have a need for this on some systems]. However, on a laptop with both a ethernet wired interface and a wireless interface, I only want one of these available at a time. I can use the applet to disable wireless but not wired connections. Perhaps the solution should be to disable wired connection via the applet also (yes, I know ... just pull the plug to disable wired) ... but for completeness ... Gene ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager and rf_kill
I at least restored the previous behavior of marking the device down when wireless is disabled; svn r3666. Again, most drivers should be entering low-power state when down, since you're not expected to be able to do much of anything in !IFF_UP state anyway, irregardless of any other setting of txpower. Thanks, it's much appreciated!K. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: multiple-device questions
Dan Williams wrote: On Thu, 2008-05-15 at 02:12 -0600, Andrew Jorgensen wrote: What are the plans for UI for controlling multiple-device behavior? There's an applet re-write on the table for 0.7.1. The current menu-based design pretty much falls over for multiple devices. Right now nm-applet just connects to all networks that have automatic configurations. This is potentially confusing. A few people have filed bugs or asked questions on this list. Right; though this isn't so much different than current networking systems. If you want complete manual control of your connecitons, then you don't mark those connections as autoconnect, and then you get to manually activate and deactivate those connections as you see fit. If the fastest device does not have a gateway defined (none offered by DHCP, link-local only, or none configured in static config) will NM choose a slower device for the default route? Yes. What signaling is given the listeners (like Pidgin or Evolution) when a device goes down but there are other devices up? As Tambet said, there are two mechanisms: a) Simple overall network state such as DISCONNECTED, CONNECTING, and CONNECTED, which is a composite of all the current device states. If at least one device is connected and there is a default route, the state will be CONNECTED. b) The ActiveConnection API. Each current connection has an ActiveConnection object which clients can use to figure out the state of individual network connections and devices. Each active connection has one or more devices assigned to it, and a device cannot be assigned to more than one active connection. It's important to remember that NM deals with _connections_, not really individual devices, though NM does provide state for individual devices as well. Is the signaling different when it's the default route (or not) that has gone down? Yes; you get org.freedesktop.DBus.PropertyChanged signals for the ActiveConnection objects when their 'default' property changes. Only one ActiveConnection object will have a True 'default' property, and that is the connection that has the default route. That is my issue at the moment, you can't have 2 different isp's default gateways active at the same time without intervention. I'm testing with 2 wired nic's connected to the same LAN, if I do a ping/traceroute stating the interface to use, only the one that has the gateway will reach the internet. I have to issue an ip route replace table main nexthop via gw dev eth0 nexthop via gw2 dev eth1 in order to have both gateways active at the same time. I have not read though all the source yet, got some pointers to the code involved, and I'll see what I can come up with. Jerry ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
