Re: Network-manager and VLAN
https://bugzilla.gnome.org/show_bug.cgi?id=681109 - Original Message - > From: "Dan Williams" > To: "Pavel Simerda" > Cc: "Neuer User" , networkmanager-list@gnome.org > Sent: Friday, August 3, 2012 10:56:24 PM > Subject: Re: Network-manager and VLAN > > On Mon, 2012-07-30 at 18:30 -0500, Dan Williams wrote: > > On Fri, 2012-07-27 at 08:56 -0400, Pavel Simerda wrote: > > > Hi, > > > > > > > Thanks for the answer, but as I said, I am using Ubuntu and do > > > > not > > > > have > > > > the rhel configuration scripts. > > > > > > > > I have finally managed to get a VLAN connection working with > > > > the > > > > following keyfile: > > > > > > > > [connection] > > > > id=VLAN1 > > > > uuid=ed3b2385-9016-45c6-a277-fa7e5be8fe9d > > > > type=vlan > > > > > > > > [vlan] > > > > parent=eth0 > > > > id=1 > > > > > > > > [ipv6] > > > > method=auto > > > > > > > > [ipv4] > > > > method=auto > > > > > > Thanks for your example config file. > > > > > > > 1. There seems to be no autoconnect feature for VLAN > > > > connections. If > > > > I > > > > insert the cable, nm does not automatically start the VLAN > > > > connection. > > > > For normal wired connections this works. > > > > > > Please file a bugreport at bugzilla.gnome.org. > > > > Yeah, would be good to have a bug to track this. It *might* be the > > case > > that because eth0 isn't up when the auto-activation checks get run, > > that > > the VLAN gets disqualified for activation. It also might be the > > case > > that we're missing a call to schedule_activate_check() in > > nm-policy.c > > when the VLAN device finally shows up, since NM may have to create > > the > > device on startup. VLAN devices are only created automatically if > > a > > connection exists for them that has autoconnect=true, BTW. > > > > But a bug would be good to track this. > > So I did test this yesterday with 0.9.6 git master and it works > there; > I'm not aware of any recent changes to VLAN autoconnect so I'd expect > it > to work in earlier versions as well. What's supposed to happen is: > > 1) if a VLAN connection exists, and is autoconnect=true, and it's > parent > interface exists, then the VLAN interface will be created and the > connection started [1] > > 2) if a VLAN connection exists, and is autoconnect=true, but the > parent > interface does not yet exist, nothing will happen until the parent > interface appears, upon which (1) happens > > 3) if a VLAN connection exists, and is autoconnect=false, and its > parent > interface exists, nothing will happen until the connection is > manually > started by the user, at which point the VLAN interface will be > created > and the connection started > > Note that you do not need a carrier to *create* the VLAN interface. > A > carrier is only required to activate the VLAN connection. > > So if that's not what's happening here, any chance we could > get /var/log/messages or wherever syslog directs NetworkManager's > output? > > Dan > > > > > 2. I hoped that nm-applet would at least show these > > > > connections, so > > > > that > > > > one can start or stop a connection without being able to edit > > > > the > > > > connection details. Unfortunately, this seems not to be the > > > > case. > > > > > > > > If I see all of this correctly, then the only way to start or > > > > stop a > > > > connection every time a cable is connected, is to issue > > > > > > > > nmcli con up id VLAN1 > > > > > > > > at the command line. > > > > > > This could be worked around with the dispatcher scripts. > > > > At the moment, due to the above bug, this may be the case. But we > > should fix this. > > > > Aso, we should add a keyfile testcase for VLANs. That serves both > > as a > > testcase and an example, actually :) So that's a double-win. > > > > Dan > > > > > > > VLAN=yes > > > > > TYPE=Vlan > > > > > DEVICE=eth9.43 > > > > > PHYSDEV=eth9 > > > > > > > > > > ONBOOT=yes > > > > > BOOTPROTO=static > > > > > IPADDR=192.168.43.149 > > > > > NETMASK=255.255.255.0 > > > > > > Thanks also for the original one. > > > > > > https://fedoraproject.org/wiki/Tools/NetworkManager/VLAN > > > > > > Cheers, > > > > > > Pavel > > > ___ > > > networkmanager-list mailing list > > > networkmanager-list@gnome.org > > > https://mail.gnome.org/mailman/listinfo/networkmanager-list > > > > > > ___ > > networkmanager-list mailing list > > networkmanager-list@gnome.org > > https://mail.gnome.org/mailman/listinfo/networkmanager-list > > > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-manager and VLAN
On Mon, 2012-07-30 at 18:30 -0500, Dan Williams wrote: > On Fri, 2012-07-27 at 08:56 -0400, Pavel Simerda wrote: > > Hi, > > > > > Thanks for the answer, but as I said, I am using Ubuntu and do not > > > have > > > the rhel configuration scripts. > > > > > > I have finally managed to get a VLAN connection working with the > > > following keyfile: > > > > > > [connection] > > > id=VLAN1 > > > uuid=ed3b2385-9016-45c6-a277-fa7e5be8fe9d > > > type=vlan > > > > > > [vlan] > > > parent=eth0 > > > id=1 > > > > > > [ipv6] > > > method=auto > > > > > > [ipv4] > > > method=auto > > > > Thanks for your example config file. > > > > > 1. There seems to be no autoconnect feature for VLAN connections. If > > > I > > > insert the cable, nm does not automatically start the VLAN > > > connection. > > > For normal wired connections this works. > > > > Please file a bugreport at bugzilla.gnome.org. > > Yeah, would be good to have a bug to track this. It *might* be the case > that because eth0 isn't up when the auto-activation checks get run, that > the VLAN gets disqualified for activation. It also might be the case > that we're missing a call to schedule_activate_check() in nm-policy.c > when the VLAN device finally shows up, since NM may have to create the > device on startup. VLAN devices are only created automatically if a > connection exists for them that has autoconnect=true, BTW. > > But a bug would be good to track this. So I did test this yesterday with 0.9.6 git master and it works there; I'm not aware of any recent changes to VLAN autoconnect so I'd expect it to work in earlier versions as well. What's supposed to happen is: 1) if a VLAN connection exists, and is autoconnect=true, and it's parent interface exists, then the VLAN interface will be created and the connection started [1] 2) if a VLAN connection exists, and is autoconnect=true, but the parent interface does not yet exist, nothing will happen until the parent interface appears, upon which (1) happens 3) if a VLAN connection exists, and is autoconnect=false, and its parent interface exists, nothing will happen until the connection is manually started by the user, at which point the VLAN interface will be created and the connection started Note that you do not need a carrier to *create* the VLAN interface. A carrier is only required to activate the VLAN connection. So if that's not what's happening here, any chance we could get /var/log/messages or wherever syslog directs NetworkManager's output? Dan > > > 2. I hoped that nm-applet would at least show these connections, so > > > that > > > one can start or stop a connection without being able to edit the > > > connection details. Unfortunately, this seems not to be the case. > > > > > > If I see all of this correctly, then the only way to start or stop a > > > connection every time a cable is connected, is to issue > > > > > > nmcli con up id VLAN1 > > > > > > at the command line. > > > > This could be worked around with the dispatcher scripts. > > At the moment, due to the above bug, this may be the case. But we > should fix this. > > Aso, we should add a keyfile testcase for VLANs. That serves both as a > testcase and an example, actually :) So that's a double-win. > > Dan > > > > > VLAN=yes > > > > TYPE=Vlan > > > > DEVICE=eth9.43 > > > > PHYSDEV=eth9 > > > > > > > > ONBOOT=yes > > > > BOOTPROTO=static > > > > IPADDR=192.168.43.149 > > > > NETMASK=255.255.255.0 > > > > Thanks also for the original one. > > > > https://fedoraproject.org/wiki/Tools/NetworkManager/VLAN > > > > Cheers, > > > > Pavel > > ___ > > networkmanager-list mailing list > > networkmanager-list@gnome.org > > https://mail.gnome.org/mailman/listinfo/networkmanager-list > > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-manager and VLAN
Thanks! - Original Message - > From: "Neuer User" > To: networkmanager-list@gnome.org > Sent: Friday, August 3, 2012 9:13:36 AM > Subject: Re: Network-manager and VLAN > > Thanks a lot for all the answers. > > I tried to add some comments, but the gmane server responded always > that > the current load was too high. > > Anyway, I followed your advise and opened three bugs: > > https://bugzilla.gnome.org/show_bug.cgi?id=681109 > https://bugzilla.gnome.org/show_bug.cgi?id=681107 > https://bugzilla.gnome.org/show_bug.cgi?id=681108 > > Kind regards > > Michael > > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-manager and VLAN
Thanks a lot for all the answers. I tried to add some comments, but the gmane server responded always that the current load was too high. Anyway, I followed your advise and opened three bugs: https://bugzilla.gnome.org/show_bug.cgi?id=681109 https://bugzilla.gnome.org/show_bug.cgi?id=681107 https://bugzilla.gnome.org/show_bug.cgi?id=681108 Kind regards Michael ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-manager and VLAN
> From: "Dan Williams" > Well, at least we want to make that an *option*. Pragmatically, this > is > Linux, and I don't think we'll ever achieve 100% coverage, and I > don't > think we *want* to either (if we did, NM would be a pile of > unmaintainable hacks). Yep. An option for anyone and *the* option for Fedora and those who already decided. > Instead, I believe our goal is to make NM useful enough, easy enough, > and understandable enough, that people *want* to use NM rather than > wading through a bunch of scripts. We don't want to force NM upon > people; instead we need to make NM *better* than the existing options > so > that it's a no-brainer choice. There will always be people that want > to > tinker and do something else or have so totally crack-rock use-cases > that we have no hope of easily supporting them, and that's fine. > That's > what software is about. I agreed even before you wrote it. Pavel ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-manager and VLAN
On Fri, 2012-07-27 at 08:56 -0400, Pavel Simerda wrote: > Hi, > > > Thanks for the answer, but as I said, I am using Ubuntu and do not > > have > > the rhel configuration scripts. > > > > I have finally managed to get a VLAN connection working with the > > following keyfile: > > > > [connection] > > id=VLAN1 > > uuid=ed3b2385-9016-45c6-a277-fa7e5be8fe9d > > type=vlan > > > > [vlan] > > parent=eth0 > > id=1 > > > > [ipv6] > > method=auto > > > > [ipv4] > > method=auto > > Thanks for your example config file. > > > 1. There seems to be no autoconnect feature for VLAN connections. If > > I > > insert the cable, nm does not automatically start the VLAN > > connection. > > For normal wired connections this works. > > Please file a bugreport at bugzilla.gnome.org. Yeah, would be good to have a bug to track this. It *might* be the case that because eth0 isn't up when the auto-activation checks get run, that the VLAN gets disqualified for activation. It also might be the case that we're missing a call to schedule_activate_check() in nm-policy.c when the VLAN device finally shows up, since NM may have to create the device on startup. VLAN devices are only created automatically if a connection exists for them that has autoconnect=true, BTW. But a bug would be good to track this. > > 2. I hoped that nm-applet would at least show these connections, so > > that > > one can start or stop a connection without being able to edit the > > connection details. Unfortunately, this seems not to be the case. > > > > If I see all of this correctly, then the only way to start or stop a > > connection every time a cable is connected, is to issue > > > > nmcli con up id VLAN1 > > > > at the command line. > > This could be worked around with the dispatcher scripts. At the moment, due to the above bug, this may be the case. But we should fix this. Aso, we should add a keyfile testcase for VLANs. That serves both as a testcase and an example, actually :) So that's a double-win. Dan > > > VLAN=yes > > > TYPE=Vlan > > > DEVICE=eth9.43 > > > PHYSDEV=eth9 > > > > > > ONBOOT=yes > > > BOOTPROTO=static > > > IPADDR=192.168.43.149 > > > NETMASK=255.255.255.0 > > Thanks also for the original one. > > https://fedoraproject.org/wiki/Tools/NetworkManager/VLAN > > Cheers, > > Pavel > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-manager and VLAN
On Fri, 2012-07-27 at 11:31 -0400, Pavel Simerda wrote: > > It isn't documented (perhaps in the literate source), but ifupdown > > supports tagged interfaces transparently. If you want an ethernet > > interfaces on VLAN 5, this will do the trick: > > > > iface iface.X inet ... > > The long-term goal for many distros is to switch to NetworkManager only. At > least we should make NetworkManager standalone in the common networking cases > covered by ifcfg-rh, ifupdown and similar. Well, at least we want to make that an *option*. Pragmatically, this is Linux, and I don't think we'll ever achieve 100% coverage, and I don't think we *want* to either (if we did, NM would be a pile of unmaintainable hacks). Instead, I believe our goal is to make NM useful enough, easy enough, and understandable enough, that people *want* to use NM rather than wading through a bunch of scripts. We don't want to force NM upon people; instead we need to make NM *better* than the existing options so that it's a no-brainer choice. There will always be people that want to tinker and do something else or have so totally crack-rock use-cases that we have no hope of easily supporting them, and that's fine. That's what software is about. Dan > Does this actually work without ifupdown? > > Cheers, > > Pavel > ___ > networkmanager-list mailing list > networkmanager-list@gnome.org > https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-manager and VLAN
On Fri, 2012-07-27 at 11:31 -0400, Pavel Simerda wrote: > > It isn't documented (perhaps in the literate source), but ifupdown > > supports tagged interfaces transparently. If you want an ethernet > > interfaces on VLAN 5, this will do the trick: > > > > iface iface.X inet ... > > The long-term goal for many distros is to switch to NetworkManager only. At > least we should make NetworkManager standalone in the common networking cases > covered by ifcfg-rh, ifupdown and similar. > > Does this actually work without ifupdown? Only if the VLAN interface has already been created. ifupdown automatically adds it if one has configured a subinterface looking thing that doesn't exist. Ross signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-manager and VLAN
> It isn't documented (perhaps in the literate source), but ifupdown > supports tagged interfaces transparently. If you want an ethernet > interfaces on VLAN 5, this will do the trick: > > iface iface.X inet ... The long-term goal for many distros is to switch to NetworkManager only. At least we should make NetworkManager standalone in the common networking cases covered by ifcfg-rh, ifupdown and similar. Does this actually work without ifupdown? Cheers, Pavel ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-manager and VLAN
On Thu, 2012-07-26 at 16:18 +0200, Neuer User wrote: > I am using Ubuntu, so I cannot take rhel configuration files. The > Ubuntu/Debian ifupdown plugin seems to lack vlan support. So the only > way to have network manager recognize and manage my VLANs should them be > by directly creating a corresponding keyfile in system-connections. It isn't documented (perhaps in the literate source), but ifupdown supports tagged interfaces transparently. If you want an ethernet interfaces on VLAN 5, this will do the trick: iface iface.X inet ... When you bring this up, ifupdown will look for an interface named "iface.X", and if it fails to find one, will create a new link, using VLAN ID X on iface, and name it "iface.X". Depending on what you want, you might be able to get close by combining that with NM's ifupdown managed mode. Ross signature.asc Description: This is a digitally signed message part ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-manager and VLAN
Hi, > Thanks for the answer, but as I said, I am using Ubuntu and do not > have > the rhel configuration scripts. > > I have finally managed to get a VLAN connection working with the > following keyfile: > > [connection] > id=VLAN1 > uuid=ed3b2385-9016-45c6-a277-fa7e5be8fe9d > type=vlan > > [vlan] > parent=eth0 > id=1 > > [ipv6] > method=auto > > [ipv4] > method=auto Thanks for your example config file. > 1. There seems to be no autoconnect feature for VLAN connections. If > I > insert the cable, nm does not automatically start the VLAN > connection. > For normal wired connections this works. Please file a bugreport at bugzilla.gnome.org. > 2. I hoped that nm-applet would at least show these connections, so > that > one can start or stop a connection without being able to edit the > connection details. Unfortunately, this seems not to be the case. > > If I see all of this correctly, then the only way to start or stop a > connection every time a cable is connected, is to issue > > nmcli con up id VLAN1 > > at the command line. This could be worked around with the dispatcher scripts. > > VLAN=yes > > TYPE=Vlan > > DEVICE=eth9.43 > > PHYSDEV=eth9 > > > > ONBOOT=yes > > BOOTPROTO=static > > IPADDR=192.168.43.149 > > NETMASK=255.255.255.0 Thanks also for the original one. https://fedoraproject.org/wiki/Tools/NetworkManager/VLAN Cheers, Pavel ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-manager and VLAN
Am 27.07.2012 04:16, schrieb Weiping Pan: >> Michael > 1 verify that you use ifcfg-rh plugin > cat /etc/NetworkManager/NetworkManager.conf > [main] > plugins=ifcfg-rh > Thanks for the answer, but as I said, I am using Ubuntu and do not have the rhel configuration scripts. I have finally managed to get a VLAN connection working with the following keyfile: [connection] id=VLAN1 uuid=ed3b2385-9016-45c6-a277-fa7e5be8fe9d type=vlan [vlan] parent=eth0 id=1 [ipv6] method=auto [ipv4] method=auto I am not sure whether this is the 100% correct way to do it. There are two drawbacks taht I have noticed so far: 1. There seems to be no autoconnect feature for VLAN connections. If I insert the cable, nm does not automatically start the VLAN connection. For normal wired connections this works. 2. I hoped that nm-applet would at least show these connections, so that one can start or stop a connection without being able to edit the connection details. Unfortunately, this seems not to be the case. If I see all of this correctly, then the only way to start or stop a connection every time a cable is connected, is to issue nmcli con up id VLAN1 at the command line. Is this correct or is there another way? Thanks Michael > 2 /etc/sysconfig/network-scripts/ifcfg-vlan43 > > VLAN=yes > TYPE=Vlan > DEVICE=eth9.43 > PHYSDEV=eth9 > > ONBOOT=yes > BOOTPROTO=static > IPADDR=192.168.43.149 > NETMASK=255.255.255.0 > > hth > > thanks > Weipin gPan >> P.S.: Already asked on the ubuntu bugtracker. People over there are very >> helpful but lack deep internal knowledge about network manager. (see >> here >> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1029273?comments=all) >> >> >> P.P.S.: Version is 0.9.4, so should include VLAN support according to >> release notes. >> >> ___ >> networkmanager-list mailing list >> networkmanager-list@gnome.org >> https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Network-manager and VLAN
On 07/26/2012 10:18 PM, Neuer User wrote: Hello Could someone please post a working "keyfile" configuration for a VLAN device? I am trying to have network manager manage also my VLAN connections. As there is no GUI support by nm-applet so far, I am stuck. I am using Ubuntu, so I cannot take rhel configuration files. The Ubuntu/Debian ifupdown plugin seems to lack vlan support. So the only way to have network manager recognize and manage my VLANs should them be by directly creating a corresponding keyfile in system-connections. I am grateful for any help. Michael 1 verify that you use ifcfg-rh plugin cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifcfg-rh 2 /etc/sysconfig/network-scripts/ifcfg-vlan43 VLAN=yes TYPE=Vlan DEVICE=eth9.43 PHYSDEV=eth9 ONBOOT=yes BOOTPROTO=static IPADDR=192.168.43.149 NETMASK=255.255.255.0 hth thanks Weipin gPan P.S.: Already asked on the ubuntu bugtracker. People over there are very helpful but lack deep internal knowledge about network manager. (see here https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1029273?comments=all) P.P.S.: Version is 0.9.4, so should include VLAN support according to release notes. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Network-manager and VLAN
Hello Could someone please post a working "keyfile" configuration for a VLAN device? I am trying to have network manager manage also my VLAN connections. As there is no GUI support by nm-applet so far, I am stuck. I am using Ubuntu, so I cannot take rhel configuration files. The Ubuntu/Debian ifupdown plugin seems to lack vlan support. So the only way to have network manager recognize and manage my VLANs should them be by directly creating a corresponding keyfile in system-connections. I am grateful for any help. Michael P.S.: Already asked on the ubuntu bugtracker. People over there are very helpful but lack deep internal knowledge about network manager. (see here https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1029273?comments=all) P.P.S.: Version is 0.9.4, so should include VLAN support according to release notes. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
