Re: Bondging, Bridging, Vlan-ing, Oh My

[Justin Brown <justin brown fandingo org>]

Dan,

Could this be part of the Fedora 20 feature
http://fedoraproject.org/wiki/Features/NetworkManagerBonding?

Do you track RFEs or would you like a Bugzilla issue opened?

Thanks,
Justin

On Tue, Jul 30, 2013 at 1:53 PM, Dan Williams <dcbw redhat com> wrote:
> On Tue, 2013-07-30 at 13:40 -0500, Justin Brown wrote:
> > Dan,
> >
> > I captured the debug output like you requested. The entire file is
> > available at the public link
> > https://docs.google.com/file/d/0B2kqfJjZRVw5ZXNhNUItSDZZUzA/edit?usp=sharing.
> >
> > Looks like the interesting part starts at line 96:
> >
> > NetworkManager[774]: <warn> (vlan25): No support for VLANs on
> > interface bond0 of type Bond
> > NetworkManager[774]: <warn> (vlan25) failed to determine virtual interface name
> > NetworkManager[774]: <warn> (vlan25): No support for VLANs on
> > interface bond0 of type Bond
> > NetworkManager[774]: <warn> (vlan25) failed to determine virtual interface name
> > NetworkManager[774]: <warn> failed to allocate link cache: (-10)
> > Operation not supported
>
> Looks like this is a limitation that we need to correct in the core NM,
> actually.
>
> Dan
>
> > After I wrote to the mailing list the other day, I ended up changing
> > my configuration as a temporary workaround. The configuration is now
> > em1 ---> vlan25 ---> kg25
> >
> > Basically the bond and em2 were removed, and the configurations were
> > minimally changed. This new config works perfectly, but I would still
> > like to get the bond setup.
> >
> > Thanks,
> > Justin
> >
> > On Tue, Jul 30, 2013 at 11:59 AM, Dan Williams <dcbw redhat com> wrote:
> > > On Fri, 2013-07-26 at 15:08 -0500, Justin Brown wrote:
> > > > Coming high off my triumph of configuring an Ethernet NIC with a
> > > > bridge using nothing but keyfiles, I figured that I would try
> > > > something more complicated.
> > > >
> > > > First off, I'll start by saying that I would normally stick to
> > > > network.service or NetworkManager with the ifcfg-rh plugin. However,
> > > > for some time, both methods fail to assign IP addresses to bridges.
> > > > Fedora 18 and 19 both have this problem, and I've previously hacked
> > > > around it by `ifup br0` after boot.
> > > >
> > > > Ok, so here's what I'm trying to do with Fedora 19,
> > > > NetworkManager-0.9.8.2-8.git20130709.fc19.
> > > >
> > > > Two physical interfaces (em1, em2), bonded together (bond0), "grab"
> > > > VLAN 25 (vlan25), and bridge to libvirt (kg25).
> > > >
> > > > em1, em2 ---> bond0 ---> vlan25 ---> kg25 (192.168.25.10/24)
> > > >
> > > > Before I list the keyfiles, I want to state the results. Almost
> > > > everything works, except the vlan25 interface. The physical interfaces
> > > > come up, the bond is created and has the proper slaves, and kg25
> > > > bridge is created with the proper IP address.
> > > >
> > > > NetworkManager "sees" the connection (nmcli c), but I cannot activate it.
> > > >
> > > >         nmcli c up id vlan25
> > > >         Error: Connection activation failed: Failed to determine
> > > > connection's virtual interface name
> > > >
> > > > Looking through the journal, this is the only error as well.
> > > >
> > > > I have been using https://fedoraproject.org/wiki/Networking to
> > > > configure NetworkManager, and I don't see any issues with my
> > > > configuration.
> > > >
> > > > On a separate note, is there any ability to control the miimon value
> > > > and bonding mode in NM 0.9.8, or do I need to wait for
> > > > Features/NetworkManagerBonding in Fedora 20?
> > > >
> > > >
> > > > Any help or guidance would be greatly appreciated.
> > >
> > > Any chance you could do something like:
> > >
> > > systemctl mask NetworkManager
> > > systemctl stop NetworkManager
> > > /usr/sbin/NetworkManager --no-daemon --log-level=debug
> > >
> > > and then let it run and grab the output, and mail it to me?  Feel free
> > > to mail it privately if you'd rather all that information not show up on
> > > public lists.
> > >
> > > Dan
> > >
> > > > Thanks,
> > > > Justin
> > > >
> > > > #####################################
> > > > [connection]
> > > > id=em1
> > > > uuid=7974cee9-c454-4d0f-93b1-37f93de2ae92
> > > > type=802-3-ethernet
> > > > master=923eddca-eaf1-4595-b363-0e02ed1515a2
> > > > slave-type=bond
> > > >
> > > > [802-3-ethernet]
> > > > mac-address=00:1e:4f:fc:3e:02
> > > >
> > > > #####################################
> > > > [connection]
> > > > id=em2
> > > > uuid=5756ba21-2bd1-4371-a011-6968a0406db2
> > > > type=802-3-ethernet
> > > > master=923eddca-eaf1-4595-b363-0e02ed1515a2
> > > > slave-type=bond
> > > >
> > > > [802-3-ethernet]
> > > > mac-address=00:1e:4f:fc:3e:04
> > > >
> > > > #####################################
> > > > [connection]
> > > > id=bond0
> > > > uuid=923eddca-eaf1-4595-b363-0e02ed1515a2
> > > > type=bond
> > > > interface-name=bond0
> > > >
> > > > [bond]
> > > > interface-name=bond0
> > > >
> > > > #####################################
> > > > [connection]
> > > > id=vlan25
> > > > uuid=efcd39e6-9d19-4fec-97b3-8c16d6115474
> > > > type=vlan
> > > > master=71abc14f-fd97-4d62-9a2b-6d07e8a2801c
> > > > slave-type=bridge
> > > > interface-name=vlan25
> > > >
> > > > [vlan]
> > > > parent=bond0
> > > > id=25
> > > > interface-name=vlan25
> > > >
> > > > #####################################
> > > > [connection]
> > > > id=kg25
> > > > uuid=71abc14f-fd97-4d62-9a2b-6d07e8a2801c
> > > > type=bridge
> > > > autoconnect=true
> > > > interface-name=kg25
> > > >
> > > > [bridge]
> > > > interface-name=kg25
> > > >
> > > > [ipv4]
> > > > method=manual
> > > > dns=192.168.0.101;192.168.0.103;
> > > > addresses1=192.168.25.10;192.168.25.1;
> > > > _______________________________________________
> > > > networkmanager-list mailing list
> > > > networkmanager-list gnome org
> > > > https://mail.gnome.org/mailman/listinfo/networkmanager-list