Re: NM refuses to manage a VLAN
On Tue, 15 Jul 2014 11:12:42 -0500 Dan Williams wrote: > nmcli con mod "my-wifi" ipv4.method manual ipv4.addresses > "192.168.1.2/24, 10.10.1.5/8" wifi.ssid "blahblah" > If you try out F21 or RHEL7, are these issues solved? Indeed, it works on NetworkManager-0.9.9.1-13.git20140326.4dba720.el7, thanks a lot! -- Pete ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM refuses to manage a VLAN
On Tue, 2014-07-15 at 09:08 -0600, Pete Zaitcev wrote: > On Fri, 11 Jul 2014 14:45:43 -0500 > Dan Williams wrote: > > > > > > [root@elanor network-scripts]# nmcli c up id vlan-ethgray > > > > > Error: Connection activation failed: Device not managed by > > > > > NetworkManager or unavailable > > > Could this be the issue? > > I tinkered with it a bit more and figured it out. Apparently, I cannot > migrate piecemeal. The parent device must be managed by NM before > a VLAN on it can be managed. Once that was fixed, everything worked > pretty much as expected, with just a few small bugs. Yeah, NM needs to know certain things about the parent interface before it can be used with VLANs. Unfortunately, due to the nature of VLANs (eg, they have a parent interface) that's necessary at this time. > I think the most super annoying part is that address cannot be set > from the shell, because connections are only created with the default > method, dhcp. The nmcli c mod cannot switch two properties at a I believe we've fixed that earlier this year, so RHEL7 and F21 have the ability: nmcli con mod "my-vlan" ipv4.method manual ipv4.addresses "192.168.1.2/24, 10.10.1.5/8" > time. Also, one cannot set method first and then ipv4.addresses, > ipv6.addresses (I forgot what happens if you try). So, one must > either do the "nmcli c edit xxx" thing, or hand-edit the connection > and then "nmcli c reload". NM 0.9.9.1+ should allow any number of options with 'con mod': nmcli con mod "my-wifi" ipv4.method manual ipv4.addresses "192.168.1.2/24, 10.10.1.5/8" wifi.ssid "blahblah" > Other funny buglet that I remember is that if you create a VLAN > using e.g. > nmcli c add type Vlan ifname ethmain.3 con-name ethmain.3 autoconnect yes > dev ethmain id 3 > it still won't work, because HWADDR must be set. I believe we've fixed that earlier this year too; all that should be necessary these days is *either* the parent interface name (eg, "dev ethmain") or the parent hardware address. If you try out F21 or RHEL7, are these issues solved? Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM refuses to manage a VLAN
On Fri, 11 Jul 2014 14:45:43 -0500 Dan Williams wrote: > > > > [root@elanor network-scripts]# nmcli c up id vlan-ethgray > > > > Error: Connection activation failed: Device not managed by > > > > NetworkManager or unavailable > Could this be the issue? I tinkered with it a bit more and figured it out. Apparently, I cannot migrate piecemeal. The parent device must be managed by NM before a VLAN on it can be managed. Once that was fixed, everything worked pretty much as expected, with just a few small bugs. I think the most super annoying part is that address cannot be set from the shell, because connections are only created with the default method, dhcp. The nmcli c mod cannot switch two properties at a time. Also, one cannot set method first and then ipv4.addresses, ipv6.addresses (I forgot what happens if you try). So, one must either do the "nmcli c edit xxx" thing, or hand-edit the connection and then "nmcli c reload". Other funny buglet that I remember is that if you create a VLAN using e.g. nmcli c add type Vlan ifname ethmain.3 con-name ethmain.3 autoconnect yes dev ethmain id 3 it still won't work, because HWADDR must be set. Anyhow, thanks a lot for the help. -- P ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM refuses to manage a VLAN
On Fri, 11 Jul 2014 14:45:43 -0500 Dan Williams wrote: > Do you have NM_CONTROLLED=no > in /etc/sysconfig/network-scripts/ifcfg-ethmain.4? Removing that file makes no difference. Here's the console capture: [root@elanor zaitcev]# ls /etc/NetworkManager/ dispatcher.d dnsmasq.d NetworkManager.conf system-connections VPN [root@elanor zaitcev]# ls /etc/NetworkManager/system-connections/ [root@elanor zaitcev]# rm /etc/sysconfig/network-scripts/ifcfg-ethmain.4 [root@elanor zaitcev]# ip link delete dev ethmain.4 [root@elanor zaitcev]# systemctl mask NetworkManager <--- already masked, so no console output [root@elanor zaitcev]# /usr/sbin/NetworkManager --log-level=debug [1405260297.790837] [config/nm-config.c:304] read_config(): Reading config file '/etc/NetworkManager/NetworkManager.conf' [root@elanor zaitcev]# systemctl stop radvd < too noisy in logs otherwise [root@elanor zaitcev]# nmcli dev DEVICE TYPE STATE wlp1s0 wifi disconnected ethmainethernet unmanaged lo loopback unmanaged ethmain.2 vlan unmanaged ethmain.3 vlan unmanaged ethmain.4 vlan unmanaged ethmain.5 vlan unmanaged < woops, ethmain.4 floated up somehow, let's kill it again [root@elanor zaitcev]# ip link delete dev ethmain.4 [root@elanor zaitcev]# nmcli dev DEVICE TYPE STATE wlp1s0 wifi disconnected ethmainethernet unmanaged lo loopback unmanaged ethmain.2 vlan unmanaged ethmain.3 vlan unmanaged ethmain.5 vlan unmanaged [root@elanor zaitcev]# nmcli c up id vlan-ethgray Error: Connection activation failed: Device not managed by NetworkManager or unavailable [root@elanor zaitcev]# killall NetworkManager Messages file: http://www.zaitcev.us/things/messages.nm.02 But basically it's the same story. Device removal: Jul 13 08:05:34 elanor NetworkManager[26437]: [1405260334.724967] [platform/nm-platform.c:1969] log_link(): signal: link removed: ethmain.4 (15) Jul 13 08:05:34 elanor NetworkManager[26437]: [1405260334.727207] [platform/nm-linux-platform.c:2856] handle_udev_event(): UDEV event: action 'remove' subsys 'net' device 'ethmain.4' Jul 13 08:05:52 elanor NetworkManager[26437]: [1405260352.89416] [platform/nm-platform.c:485] nm_platform_link_get_ifindex(): link not found: ethmain.4 Jul 13 08:05:52 elanor NetworkManager[26437]: [1405260352.89494] [platform/nm-platform.c:956] nm_platform_vlan_add(): link: adding vlan 'ethmain.4' parent 2 vlanid 4 vlanflags 0 Jul 13 08:05:52 elanor NetworkManager[26437]: [1405260352.96545] [platform/nm-linux-platform.c:253] get_kernel_object(): get_kernel_object for link: ethmain.4 (16, family 0) Jul 13 08:05:52 elanor NetworkManager[26437]: [1405260352.9] [platform/nm-platform.c:1969] log_link(): signal: link added: ethmain.4 (16) Jul 13 08:05:52 elanor NetworkManager[26437]: [1405260352.97828] [devices/nm-device.c:7086] nm_device_update_hw_address(): (ethmain.4): hardware address is 00:23:54:9F:BE:A5 Jul 13 08:05:52 elanor NetworkManager[26437]: [1405260352.97942] [devices/nm-device-vlan.c:92] update_initial_hw_address(): (ethmain.4): read initial MAC address 00:23:54:9F:BE:A5 Jul 13 08:05:52 elanor NetworkManager[26437]: (ethmain.4): carrier is OFF Jul 13 08:05:52 elanor NetworkManager[26437]: [1405260352.98238] [devices/nm-device-vlan.c:532] constructed(): (ethmain.4): kernel ifindex 16 Jul 13 08:05:52 elanor NetworkManager[26437]: (ethmain.4): VLAN ID 4 with parent ethmain Jul 13 08:05:52 elanor NetworkManager[26437]: (ethmain.4): new VLAN device (driver: '8021q' ifindex: 16) Jul 13 08:05:52 elanor NetworkManager[26437]: (ethmain.4): exported as /org/freedesktop/NetworkManager/Devices/7 Jul 13 08:05:52 elanor NetworkManager[26437]: (ethmain.4): No existing connection detected. Jul 13 08:05:52 elanor NetworkManager[26437]: [1405260352.107049] [nm-manager.c:1474] system_create_virtual_devices(): creating virtual devices... Jul 13 08:05:52 elanor NetworkManager[26437]: connection /org/freedesktop/NetworkManager/Settings/0 failed to activate: (2) Device not managed by NetworkManager or unavailable Jul 13 08:05:52 elanor NetworkManager[26437]: [1405260352.115628] [platform/nm-linux-platform.c:1333] event_notification(): netlink event (type 16) for link: ethmain (2, family 0) Jul 13 08:05:52 elanor NetworkManager[26437]: [1405260352.115841] [platform/nm-linux-platform.c:253] get_kernel_object(): get_kernel_object for link: ethmain (2, family 0) Jul 13 08:05:52 elanor NetworkManager[26437]: [1405260352.118589] [platform/nm-linux-platform.c:2856] handle_udev_event(): UDEV event: action 'add' subsys 'net' device 'ethmain.4' Jul 13 08:05:52 elanor NetworkManager[26437]: [1405260352.118860] [platform/nm-platform.c:1969] log_link(): signal: link added: ethmain.4 (16) Jul 13 08:05:52 elanor NetworkManager[26437]: [1405260352.122765] [platform/nm-linux-platform.c:1333] event_notification(): netlink event (type 16) for link: ethmain.4 (16, fa
Re: NM refuses to manage a VLAN
On Fri, 2014-07-11 at 08:23 -0600, Pete Zaitcev wrote: > On Thu, 10 Jul 2014 12:58:20 -0500 > Dan Williams wrote: > > > > [root@elanor network-scripts]# nmcli c up id vlan-ethgray > > > Error: Connection activation failed: Device not managed by NetworkManager > > > or unavailable > > > I tried to reproduce this with that RPM version from F20 (and even on > > i686!) but cannot. But in any case, could you: > > > > systemctl mask NetworkManager > > systemctl stop NetworkManager > > /usr/sbin/NetworkManager --no-daemon --log-level=debug > > > > and then try to reproduce the issue? Then we'll see if the logs > > elucidate anything. > > Full log is here: > http://www.zaitcev.us/things/messages.nm.01 Could this be the issue? Jul 11 07:46:01 elanor NetworkManager[21005]: ifcfg-rh: parsing /etc/sysconfig/network-scripts/ifcfg-ethmain.4 ... Jul 11 07:46:01 elanor NetworkManager[21005]: ifcfg-rh: read connection 'System ethmain.4' Jul 11 07:46:01 elanor NetworkManager[21005]: ifcfg-rh: Ignoring connection 'System ethmain.4' / device 'ethmain.4' due to NM_CONTROLLED/BRIDGE/VLAN. Do you have NM_CONTROLLED=no in /etc/sysconfig/network-scripts/ifcfg-ethmain.4? Also, " Ignoring connection 'System ethmain' / device '00:23:54:9f:be:a5' due to NM_CONTROLLED/BRIDGE/VLAN." implies that the VLAN interface will also be ignored, because it'll have the same MAC as the parent. Dan > The segment at the moment of the problem (nmcli c up id vlan-ethgray) > looks like this: > > Jul 11 07:49:03 elanor NetworkManager[21005]: [1405086543.479459] > [platform/nm-platform.c:956] nm_platform_vlan_add(): link: adding vlan > 'ethmain.4' parent 2 vlanid 4 vlanflags 0 > Jul 11 07:49:03 elanor systemd-sysctl: Overwriting earlier assignment of > kernel/sysrq in file '/etc/sysctl.d/99-sysctl.conf'. > Jul 11 07:49:03 elanor radvd[4223]: attempting to reread config file > Jul 11 07:49:03 elanor radvd[4223]: no linklocal address configured for > ethmain.4 > Jul 11 07:49:03 elanor radvd[4223]: resuming normal operation > Jul 11 07:49:03 elanor radvd[4223]: attempting to reread config file > Jul 11 07:49:03 elanor radvd[4223]: no linklocal address configured for > ethmain.4 > Jul 11 07:49:03 elanor radvd[4223]: resuming normal operation > Jul 11 07:49:03 elanor NetworkManager[21005]: [1405086543.492995] > [platform/nm-linux-platform.c:253] get_kernel_object(): get_kernel_object for > link: ethmain.4 (13, family 0) > Jul 11 07:49:03 elanor NetworkManager[21005]: [1405086543.493109] > [platform/nm-platform.c:1969] log_link(): signal: link added: ethmain.4 (13) > Jul 11 07:49:03 elanor NetworkManager[21005]: [1405086543.494238] > [devices/nm-device.c:7086] nm_device_update_hw_address(): (ethmain.4): > hardware address is 00:23:54:9F:BE:A5 > Jul 11 07:49:03 elanor NetworkManager[21005]: [1405086543.494415] > [devices/nm-device-vlan.c:92] update_initial_hw_address(): (ethmain.4): read > initial MAC address 00:23:54:9F:BE:A5 > Jul 11 07:49:03 elanor NetworkManager[21005]: (ethmain.4): carrier is > OFF > Jul 11 07:49:03 elanor NetworkManager[21005]: [1405086543.494720] > [devices/nm-device-vlan.c:532] constructed(): (ethmain.4): kernel ifindex 13 > Jul 11 07:49:03 elanor NetworkManager[21005]: (ethmain.4): VLAN ID 4 > with parent ethmain > Jul 11 07:49:03 elanor NetworkManager[21005]: (ethmain.4): new VLAN > device (driver: '8021q' ifindex: 13) > Jul 11 07:49:03 elanor NetworkManager[21005]: (ethmain.4): exported as > /org/freedesktop/NetworkManager/Devices/7 > Jul 11 07:49:03 elanor NetworkManager[21005]: (ethmain.4): No existing > connection detected. > > So... nmcli knows that connection exists, and NM daemon brings up the > right interface, but when the info circles back to NM daemon from kernel, > it cannot find the connection? > > I tried this: > nmcli c mod id vlan-ethgray 802-3-ethernet.mac-address 00:23:54:9F:BE:A5 > > But it made no difference. > > -- Pete ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM refuses to manage a VLAN
On Thu, 10 Jul 2014 12:58:20 -0500 Dan Williams wrote: > > [root@elanor network-scripts]# nmcli c up id vlan-ethgray > > Error: Connection activation failed: Device not managed by NetworkManager > > or unavailable > I tried to reproduce this with that RPM version from F20 (and even on > i686!) but cannot. But in any case, could you: > > systemctl mask NetworkManager > systemctl stop NetworkManager > /usr/sbin/NetworkManager --no-daemon --log-level=debug > > and then try to reproduce the issue? Then we'll see if the logs > elucidate anything. Full log is here: http://www.zaitcev.us/things/messages.nm.01 The segment at the moment of the problem (nmcli c up id vlan-ethgray) looks like this: Jul 11 07:49:03 elanor NetworkManager[21005]: [1405086543.479459] [platform/nm-platform.c:956] nm_platform_vlan_add(): link: adding vlan 'ethmain.4' parent 2 vlanid 4 vlanflags 0 Jul 11 07:49:03 elanor systemd-sysctl: Overwriting earlier assignment of kernel/sysrq in file '/etc/sysctl.d/99-sysctl.conf'. Jul 11 07:49:03 elanor radvd[4223]: attempting to reread config file Jul 11 07:49:03 elanor radvd[4223]: no linklocal address configured for ethmain.4 Jul 11 07:49:03 elanor radvd[4223]: resuming normal operation Jul 11 07:49:03 elanor radvd[4223]: attempting to reread config file Jul 11 07:49:03 elanor radvd[4223]: no linklocal address configured for ethmain.4 Jul 11 07:49:03 elanor radvd[4223]: resuming normal operation Jul 11 07:49:03 elanor NetworkManager[21005]: [1405086543.492995] [platform/nm-linux-platform.c:253] get_kernel_object(): get_kernel_object for link: ethmain.4 (13, family 0) Jul 11 07:49:03 elanor NetworkManager[21005]: [1405086543.493109] [platform/nm-platform.c:1969] log_link(): signal: link added: ethmain.4 (13) Jul 11 07:49:03 elanor NetworkManager[21005]: [1405086543.494238] [devices/nm-device.c:7086] nm_device_update_hw_address(): (ethmain.4): hardware address is 00:23:54:9F:BE:A5 Jul 11 07:49:03 elanor NetworkManager[21005]: [1405086543.494415] [devices/nm-device-vlan.c:92] update_initial_hw_address(): (ethmain.4): read initial MAC address 00:23:54:9F:BE:A5 Jul 11 07:49:03 elanor NetworkManager[21005]: (ethmain.4): carrier is OFF Jul 11 07:49:03 elanor NetworkManager[21005]: [1405086543.494720] [devices/nm-device-vlan.c:532] constructed(): (ethmain.4): kernel ifindex 13 Jul 11 07:49:03 elanor NetworkManager[21005]: (ethmain.4): VLAN ID 4 with parent ethmain Jul 11 07:49:03 elanor NetworkManager[21005]: (ethmain.4): new VLAN device (driver: '8021q' ifindex: 13) Jul 11 07:49:03 elanor NetworkManager[21005]: (ethmain.4): exported as /org/freedesktop/NetworkManager/Devices/7 Jul 11 07:49:03 elanor NetworkManager[21005]: (ethmain.4): No existing connection detected. So... nmcli knows that connection exists, and NM daemon brings up the right interface, but when the info circles back to NM daemon from kernel, it cannot find the connection? I tried this: nmcli c mod id vlan-ethgray 802-3-ethernet.mac-address 00:23:54:9F:BE:A5 But it made no difference. -- Pete ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM refuses to manage a VLAN
On Fri, 2014-07-04 at 08:24 -0600, Pete Zaitcev wrote:
> Dear All:
>
> I am trying to migrate an existing setup. To that end, I defined
> a connection with "nmcli c add type vlan". Result is like this:
>
> [root@elanor network-scripts]# nmcli conn show configured
> NAME UUID TYPE TIMESTAMP-REAL
> vlan-ethgray 098fcf3f-1801-4cfa-a8d4-85346bcd4083 vlan never
> [root@elanor network-scripts]# nmcli conn show configured id vlan-ethgray
> connection.id: vlan-ethgray
> connection.uuid:098fcf3f-1801-4cfa-a8d4-85346bcd4083
> connection.interface-name: ethmain.4
> connection.type:vlan
> connection.autoconnect: yes
> connection.timestamp: 0
> connection.read-only: no
> connection.permissions:
> connection.zone:--
> connection.master: --
> connection.slave-type: --
> connection.secondaries:
> connection.gateway-ping-timeout:0
> 802-3-ethernet.port:--
> 802-3-ethernet.speed: 0
> 802-3-ethernet.duplex: --
> 802-3-ethernet.auto-negotiate: yes
> 802-3-ethernet.mac-address: --
> 802-3-ethernet.cloned-mac-address: --
> 802-3-ethernet.mac-address-blacklist:
> 802-3-ethernet.mtu: auto
> 802-3-ethernet.s390-subchannels:
> 802-3-ethernet.s390-nettype:--
> 802-3-ethernet.s390-options:
> ipv4.method:manual
> ipv4.dns:
> ipv4.dns-search:
> ipv4.addresses: { ip = 192.168.132.1/24, gw = 0.0.0.0
> }
> ipv4.routes:
> ipv4.ignore-auto-routes:no
> ipv4.ignore-auto-dns: no
> ipv4.dhcp-client-id:--
> ipv4.dhcp-send-hostname:yes
> ipv4.dhcp-hostname: --
> ipv4.never-default: no
> ipv4.may-fail: no
> ipv6.method:manual
> ipv6.dns:
> ipv6.dns-search:
> ipv6.addresses: { ip = fd2d:acfb:74cc:5::1/64, gw =
> :: }; { ip = fe80:0:0:5::1/64, gw = :: }
> ipv6.routes:
> ipv6.ignore-auto-routes:no
> ipv6.ignore-auto-dns: no
> ipv6.never-default: yes
> ipv6.may-fail: no
> ipv6.ip6-privacy: -1 (unknown)
> ipv6.dhcp-hostname: --
> vlan.interface-name:ethmain.4
> vlan.parent:ethmain
> vlan.id:4
> vlan.flags: 0 (NONE)
> vlan.ingress-priority-map:
> vlan.egress-priority-map:
> [root@elanor network-scripts]#
>
> Then, I make sure that device alias is deleted:
>
> [root@elanor network-scripts]# ip link delete dev ethmain.4
> [root@elanor network-scripts]# nmcli dev
> DEVICE TYPE STATE
> ethmainethernet unmanaged
> lo loopback unmanaged
> ethmain.2 vlan unmanaged
> ethmain.3 vlan unmanaged
> ethmain.5 vlan unmanaged
> [root@elanor network-scripts]#
>
> So far, so good. But then...
>
> [root@elanor network-scripts]# nmcli c up id vlan-ethgray
> Error: Connection activation failed: Device not managed by NetworkManager or
> unavailable
>
> Oops!
>
> [root@elanor network-scripts]# nmcli dev
> DEVICE TYPE STATE
> ethmainethernet unmanaged
> lo loopback unmanaged
> ethmain.2 vlan unmanaged
> ethmain.3 vlan unmanaged
> ethmain.4 vlan unmanaged
> ethmain.5 vlan unmanaged
>
> So, NM creates the correct alias (visible with ip link or ip addr),
> but bails before setting any addresses on it. This happens with
> NetworkManager-0.9.9.0-40.git20131003.fc20.i686.
>
> Any ideas how this could be fixed?
Hi,
I tried to reproduce this with that RPM version from F20 (and even on
i686!) but cannot. But in any case, could you:
systemctl mask NetworkManager
systemctl stop NetworkManager
/usr/sbin/NetworkManager --no-daemon --log-level=debug
and then try to reproduce the issue? Then we'll see if the logs
elucidate anything.
Thanks!
Dan
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
NM refuses to manage a VLAN
Dear All:
I am trying to migrate an existing setup. To that end, I defined
a connection with "nmcli c add type vlan". Result is like this:
[root@elanor network-scripts]# nmcli conn show configured
NAME UUID TYPE TIMESTAMP-REAL
vlan-ethgray 098fcf3f-1801-4cfa-a8d4-85346bcd4083 vlan never
[root@elanor network-scripts]# nmcli conn show configured id vlan-ethgray
connection.id: vlan-ethgray
connection.uuid:098fcf3f-1801-4cfa-a8d4-85346bcd4083
connection.interface-name: ethmain.4
connection.type:vlan
connection.autoconnect: yes
connection.timestamp: 0
connection.read-only: no
connection.permissions:
connection.zone:--
connection.master: --
connection.slave-type: --
connection.secondaries:
connection.gateway-ping-timeout:0
802-3-ethernet.port:--
802-3-ethernet.speed: 0
802-3-ethernet.duplex: --
802-3-ethernet.auto-negotiate: yes
802-3-ethernet.mac-address: --
802-3-ethernet.cloned-mac-address: --
802-3-ethernet.mac-address-blacklist:
802-3-ethernet.mtu: auto
802-3-ethernet.s390-subchannels:
802-3-ethernet.s390-nettype:--
802-3-ethernet.s390-options:
ipv4.method:manual
ipv4.dns:
ipv4.dns-search:
ipv4.addresses: { ip = 192.168.132.1/24, gw = 0.0.0.0 }
ipv4.routes:
ipv4.ignore-auto-routes:no
ipv4.ignore-auto-dns: no
ipv4.dhcp-client-id:--
ipv4.dhcp-send-hostname:yes
ipv4.dhcp-hostname: --
ipv4.never-default: no
ipv4.may-fail: no
ipv6.method:manual
ipv6.dns:
ipv6.dns-search:
ipv6.addresses: { ip = fd2d:acfb:74cc:5::1/64, gw = ::
}; { ip = fe80:0:0:5::1/64, gw = :: }
ipv6.routes:
ipv6.ignore-auto-routes:no
ipv6.ignore-auto-dns: no
ipv6.never-default: yes
ipv6.may-fail: no
ipv6.ip6-privacy: -1 (unknown)
ipv6.dhcp-hostname: --
vlan.interface-name:ethmain.4
vlan.parent:ethmain
vlan.id:4
vlan.flags: 0 (NONE)
vlan.ingress-priority-map:
vlan.egress-priority-map:
[root@elanor network-scripts]#
Then, I make sure that device alias is deleted:
[root@elanor network-scripts]# ip link delete dev ethmain.4
[root@elanor network-scripts]# nmcli dev
DEVICE TYPE STATE
ethmainethernet unmanaged
lo loopback unmanaged
ethmain.2 vlan unmanaged
ethmain.3 vlan unmanaged
ethmain.5 vlan unmanaged
[root@elanor network-scripts]#
So far, so good. But then...
[root@elanor network-scripts]# nmcli c up id vlan-ethgray
Error: Connection activation failed: Device not managed by NetworkManager or
unavailable
Oops!
[root@elanor network-scripts]# nmcli dev
DEVICE TYPE STATE
ethmainethernet unmanaged
lo loopback unmanaged
ethmain.2 vlan unmanaged
ethmain.3 vlan unmanaged
ethmain.4 vlan unmanaged
ethmain.5 vlan unmanaged
So, NM creates the correct alias (visible with ip link or ip addr),
but bails before setting any addresses on it. This happens with
NetworkManager-0.9.9.0-40.git20131003.fc20.i686.
Any ideas how this could be fixed?
-- Pete
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
