Bridge with alias interface
Hello, I'm wondering if NM can setup a bridge using an alias interface (ie eth0:0)? Nathanael ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: device not connecting with type=unknown
On Thu, 2015-10-15 at 17:02 -0500, Alex Ferm wrote: > I have an embedded arm device running network-manager 1.0.6 with a usb > ethernet gadget that I want to automatically connect using DHCP. > NetworkManager shows the device type as unknown rather than ethernet, > and I was unable to connect with a connection who's type was set to > ethernet. I changed it to generic and was able to connect. I do have the > autoconnect flag set to "true", but I have to manually connect using nmcli. > > Is there any way I can get it to autoconnect? This device is intended to > be headless with the network being the main method of communication. So you said "gadget"... There's a couple ways things identify themselves, so lets see what yours does. What is the output of: cat /sys/class/net//type cat /sys/class/net//uevent I'll bet when you cat the uevent file, you see DEVTYPE=gadget ? Currently NM only recognizes ethernet interfaces that don't set DEVTYPE (which includes almost all of them) as real ethernet, because various "virtual" types are the ones that set devtype and we don't want to treat them as actual physical ethernet. Gadget is somewhat special though, so maybe NM needs an update to treat 'gadget' as ethernet. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: IPv6 with DHCP -- how is default route set?
On Wed, 2015-10-21 at 11:23 +0200, Tore Anderson wrote: > * Thomas Haller > > > "Automatic, DHCP only" will not use RA at all. > > Which means this variant really shouldn't exist at all, or at the very > least not in a GUI where users might deviced into believing it would > ever be expected to produce a working network attachment. > > FWIW I can only imagine three truly useful modes: > > * Automatic SLAAC/DHCPv6 (the default) > * Static/manual config > * Disabled Yes, at some point here we should simply alias the "DHCP" option to "Automatic". Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: IPv6 with DHCP -- how is default route set?
On Tue, 2015-10-20 at 22:38 +0300, Andrei Borzenkov wrote: > 20.10.2015 21:23, Eloy Paris пишет: > > > > Do we not send router solicitation messages to avoid having to wait for > > the next router advertisement message, which could happen who knows > > when? > > > > Yes. I do not know if NM does it. NM sends an RS at various points during the connection activation process. There used to be some issues with that (like, 0.9.10) but we've fixed those for 1.0.x series. If you wireshark you should see them. Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: IPv6 with DHCP -- how is default route set?
* Thomas Haller > "Automatic, DHCP only" will not use RA at all. Which means this variant really shouldn't exist at all, or at the very least not in a GUI where users might deviced into believing it would ever be expected to produce a working network attachment. FWIW I can only imagine three truly useful modes: * Automatic SLAAC/DHCPv6 (the default) * Static/manual config * Disabled Tore ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: IPv6 with DHCP -- how is default route set?
On Tue, 2015-10-20 at 19:29 -0400, Chuck Anderson wrote: > On Tue, Oct 20, 2015 at 06:25:09PM -0400, Eloy Paris wrote: > > On Tue, Oct 20, 2015 at 04:43:55PM -0400, Stuart Gathman wrote: > > > > > On 10/20/2015 02:28 PM, Eloy Paris wrote: > > > > > > > Are these delays normal; do they depend on the frequency of > > > > router > > > > advertisements? If so, can NM not elicit a router > > > > advertisements by > > > > sending a router solicitation? If that is what is supposed to > > > > happen > > > > then I don't understand the delays. In contrast, IPv4 > > > > configuration > > > > is immediate. > > > > > > > > > Part of the problem is NM groups together route discovery and > > > > > SLAAC, > > > > > this makes it unusable for us in our ipv6 only clusters. I'm > > > > > in > > > > > the process of fixing this now so you can still have proper > > > > > route > > > > > discovery and use dhcpv6 or static addressing and then you'll > > > > > get > > > > > the immediate ipv6 configuration. Thanks, > > > > > > > > That'd be nice; I look forward to this in a future NM release. > > > > > > I just set radvd frequency to 10 secs. Still not "instant", but > > > fast > > > enough for government work, and not too much overhead. > > > > That's a good "workaround". Another one is to use SLAAC, which > > seems > > to result in instantaneous configuration under NM. The problem is > > on > > corporate network environments where the IT folks have configured > > the > > network for stateful configuration (DHCPv6) -- in those > > environments it > > is not possible for a regular employee (my case, for example) to > > change > > the frequency of RA messages, or to move to SLACC from DHCPv6. > > NetworkManager SHOULD send a Router Solicitation when the network > interface comes up, and the router should respond with a Router > Advertisement quickly. I don't know if that is what happens. NetworkManager is certainly supposed to send router solitations and it usually does. Everything else would be a bug. Could you turn of debug-logging and provide the logfile to find out why it takes so long? /etc/NetworkManager/NetworkManager.conf [logging] level=DEBUG domains=ALL and restart NM. then `journalctl -u NetworkManager` And/Or: Didn't you see the RS requests when looking at the tcpdump output? Can you see on the wire-level the messages and does it indicate what's wrong? Thanks, Thomas 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
