After we recently landed NM 1.1.93 to Ubuntu 16.04 desktop, I started
working on back-porting it to Vivid/15.04 for use by Ubuntu Touch which
is still currently pinned to a 0.9.10 version of NM.
Very little needed to be changed to get it running.
One thing to note is that most of the devices running Touch are on older
kernels ( mako is the oldest at 3.4, some are 3.10 ), so all output the
message:
18:19:56 <warn> device (wlan0): The kernel does not support extended
IFA_FLAGS needed by NM for IPv6 private addresses. This feature is not
available
During testing, we ran into problems with OpenVPN that seem to be
related to the re-factored netlink logic in NMLinuxPlatform and the
older kernels we're running.
We see two failures, the first occurs when the VPN connection triggers
an IPv6 address add. As the VPN specifies a unique Internal Address and
Internal Point to Point address (or peer address), the latter is used by
NM to build the IFA_ADDRESS attribute appended to the NEWADDR message.
The kernel rejects this with EINVAL.
Running 0.9.10x, the address is added, it just doesn't include the peer
address, and uses address for the IFA_ADDRESS attribute.
We also see quite a few of the same types of add IPv6 address failures
happening on a periodic basis with no VPN involved, which are probably
triggerd by lease renewals.
I was able to patch 1.1.93 to mimic the 0.9.10 behavior ( ie. never use
peer_address for IFA_ADDRESS ) and the errors in syslog disapper. That
said, I'm not 100% the IPv6 configuration was ever *working* properly,
however with this path our syslog isn't flooded with errors.
The second failure is adding an IPv4 address that already exists. The
old code base had explicit handling for this case ( EEXISTS ) and would
treat the operation as SUCCESS. When I added extra logic to handle
EEXISTS in do_add_addroute ( in nm-linux-platform.c ), the IPv4 error
also disappeared, and I found that the VPN was now properly configured.
On some of our newer devices, this IPv4 error doesn't occur, however the
workaround appears to be a no-op on these devices.
At minimum, the second problem is a blocker for our next update. We
could probably live without the peer_address change, however as stated,
it results in failures being logged.
I've attached a sanitized syslog which shows the errors in question when
a VPN is started.
Any help is much appreciated.
Regards,
/tony
IFA_FLAGS error
18:19:56 <warn> [1462918796.8308] device (wlan0): The kernel does not support
extended IFA_FLAGS needed by NM for IPv6 private addresses. This feature is not
available
IP address assigned to wlan9
18:19:58 <error> [1462918798.6541] platform-linux: do-add-ip6-address[22:
xxx::xxxx:xxxx:xxxx:xxxx]: failure 22 (Invalid argument)
18:19:59 <info> [1462918799.2161] address 192.168.1.18
18:19:59 <info> [1462918799.2162] plen 24 (255.255.255.0)
18:19:59 <info> [1462918799.2163] gateway 192.168.1.1
18:19:59 <info> [1462918799.2164] server identifier 192.168.1.1
18:19:59 <info> [1462918799.2165] lease time 86400
18:19:59 <info> [1462918799.2167] nameserver '192.168.1.1'
18:19:59 <info> [1462918799.2167] dhcp4 (wlan0): state changed unknown -> bound
18:19:59 <info> [1462918799.2326] device (wlan0): state change: ip-config ->
ip-check (reason 'none') [70 80 0]
18:19:59 <info> [1462918799.2417] device (wlan0): state change: ip-check ->
secondaries (reason 'none') [80 90 0]
18:19:59 <info> [1462918799.2440] device (wlan0): state change: secondaries ->
activated (reason 'none') [90 100 0]
18:19:59 <info> [1462918799.2464] manager: NetworkManager state is now
CONNECTED_LOCAL
18:19:59 <info> [1462918799.2693] manager: NetworkManager state is now
CONNECTED_GLOBAL
18:19:59 <info> [1462918799.2699] policy: set 'hyperion' (wlan0) as default
for IPv4 routing and DNS
18:19:59 <info> [1462918799.2706] DNS: starting dnsmasq...
18:19:59 <warn> [1462918799.2800] dnsmasq[0x8c1eb0]: dnsmasq not found on the
bus. The nameserver update will be sent when dnsmasq appears
18:19:59 <info> [1462918799.2801] dns-mgr: Writing DNS information to
/sbin/resolvconf
18:19:59 <info> [1462918799.3990] device (wlan0): Activation: successful,
device activated.
18:19:59 <info> [1462918799.4424] dnsmasq[0x8c1eb0]: dnsmasq appeared as :1.58
18:19:59 <info> [1462918799.4437] dns-mgr: Writing DNS information to
/sbin/resolvconf
VPN Started...
18:21:54 <info> [1462918914.7516]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",0]:
Started the VPN service, PID 4053
18:21:54 <info> [1462918914.8237]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",0]:
Saw the service appear; activating connection
18:21:54 <debug> [1462918914.8244]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",0]:
requesting VPN secrets pass #1
18:21:54 <info> [1462918914.8278]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",0]:
VPN plugin: state changed: init (1)
18:21:54 <debug> [1462918914.8438]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",0]:
asking service if additional secrets are required
18:21:54 <debug> [1462918914.8657]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",0]:
service indicated no additional secrets required
18:21:54 <debug> [1462918914.8675]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",0]:
Calling old Connect function as not all agents support interactive secrets
18:21:54 <info> [1462918914.8854]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",0]:
VPN plugin: state changed: starting (3)
18:21:58 <debug> [1462918918.2741] platform-linux: error reading
/sys/class/net/tun0/owner: Failed to open file '/sys/class/net/tun0/owner': No
such file or directory
18:21:58 <debug> [1462918918.2746] platform-linux: error reading
/sys/class/net/tun0/group: Failed to open file '/sys/class/net/tun0/group': No
such file or directory
18:21:58 <debug> [1462918918.2751] platform-linux: error reading
/sys/class/net/tun0/tun_flags: Failed to open file
'/sys/class/net/tun0/tun_flags': No such file or directory
18:21:58 <debug> [1462918918.2756] platform: signal: link added: 28: tun0
<NOARP,DOWN;pointopoint,multicast,noarp> mtu 1500 arp 65534 tun* not-init
driver tun
18:21:58 nm-openvpn[4067]:
/usr/lib/NetworkManager/nm-openvpn-service-openvpn-helper --tun -- tun0 1500
1558 xx.xxx.xx.xx 255.255.192.0 init
18:21:58 <debug> [1462918918.2881] platform-linux: error reading
/sys/class/net/tun0/phys_port_id: Failed to open file
'/sys/class/net/tun0/phys_port_id': No such file or directory
18:21:58 <debug> [1462918918.2908] platform-linux: sysctl: reading
'/sys/class/net/tun0/dev_id': '0x0'
18:21:58 <debug> [1462918918.2953] platform-linux: sysctl: reading
'/sys/class/net/tun0/owner': '-1'
18:21:58 <debug> [1462918918.2988] platform-linux: sysctl: reading
'/sys/class/net/tun0/group': '-1'
18:21:58 <debug> [1462918918.2991] platform-linux: sysctl: reading
'/sys/class/net/tun0/tun_flags': '0x2001'
18:21:58 <debug> [1462918918.4139] platform-linux: UDEV event: action 'add'
subsys 'net' device 'tun0' (28); seqnum=4071
18:21:58 <debug> [1462918918.4146] platform: signal: link changed: 28: tun0
<NOARP,DOWN;pointopoint,multicast,noarp> mtu 1500 arp 65534 tun* init driver tun
18:21:58 <info> [1462918918.4275]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",0]:
VPN connection: (IP Config Get) reply received.
18:21:58 <info> [1462918918.4419]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
VPN connection: (IP4 Config Get) reply received
18:21:58 <info> [1462918918.4717]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
VPN connection: (IP6 Config Get) reply received
18:21:58 <info> [1462918918.4764]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: VPN Gateway: xx.xxx.xx.xx
18:21:58 <info> [1462918918.4766]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Tunnel Device: tun0
18:21:58 <info> [1462918918.4768]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: IPv4 configuration:
18:21:58 <info> [1462918918.4769]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Internal Gateway: xx.xxx.xx.x
18:21:58 <info> [1462918918.4770]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Internal Address: xx.xxx.xx.xx
18:21:58 <info> [1462918918.4771]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Internal Prefix: 18
18:21:58 <info> [1462918918.4772]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Internal Point-to-Point Address: xx.xxx.xx.xx
18:21:58 <info> [1462918918.4772]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Maximum Segment Size (MSS): 0
18:21:58 <info> [1462918918.4773]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Static Route: xx.xxx.xx.0/21 Next Hop: xx.xxx.xx.1
18:21:58 <info> [1462918918.4774]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Static Route: xx.xxx.xx.0/24 Next Hop: xx.xxx.xx.1
18:21:58 <info> [1462918918.4775]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Static Route: xxx.xxx.xx.0/20 Next Hop: xx.xxx.xx.1
.
<bunch of IPv4 routes removed for brevity>
.
18:21:58 <info> [1462918918.4854]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Forbid Default Route: yes
18:21:58 <info> [1462918918.4855]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Internal DNS: xx.xxx.xx.x
18:21:58 <info> [1462918918.4856]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: DNS Domain: 'buildd'
18:21:58 <info> [1462918918.4858]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: IPv6 configuration:
18:21:58 <info> [1462918918.4858]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Internal Address: 2xxx:xxx:xxxx:xxxx::xxx:xxxx
18:21:58 <info> [1462918918.4859]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Internal Prefix: 64
18:21:58 <info> [1462918918.4860]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Internal Point-to-Point Address: 2xxx:xxx:xxxx:xxxx::1
18:21:58 <info> [1462918918.4861]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Maximum Segment Size (MSS): 0
18:21:58onnection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Static Route: 2xxx:xxx:xxxx::/48 Next Hop: 2xxx:xxx:xxxx:xxxx::1
18:21:58onnection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Static Route: 2xxx:xxx:xxxx::/47 Next Hop: 2xxx:xxx:xxxx:xxxx::1
18:21:58onnection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Static Route: 2xxx:xxx:xxxx::/47 Next Hop: 2xxx:xxx:xxxx:xxxx::1
18:21:58onnection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Static Route: 2xxx:xx:4000::/44 Next Hop: 2xxx:xxx:xxxx:xxxx::1
18:21:58 <info> [1462918918.4865]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: Forbid Default Route: yes
18:21:58 <info> [1462918918.4865]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
Data: DNS Domain: 'buildd'
18:21:58 <debug> [1462918918.4866]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
setting firewall zone (default) for 'tun0'
18:21:58 <info> [1462918918.4869]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
VPN plugin: state changed: started (4)
18:21:58 <debug> [1462918918.4887] platform: link: setting up 'tun0' (28)
18:21:58 <debug> [1462918918.4888] platform-linux: link: change 28: flags: set
0x1/0x1 ([up] / [up])
18:21:58 <debug> [1462918918.4900] platform-linux: do-request-link: 28
18:21:58 <debug> [1462918918.4902] platform: signal: link changed: 28: tun0
<NOARP,UP,LOWER_UP;pointopoint,multicast,noarp,up,running,lowerup> mtu 1500 arp
65534 tun* init driver tun
18:21:58 <debug> [1462918918.4906] platform-linux: do-change-link[28]: success
changing link: success
<successful IPv4 route log messages removed>
18:21:58address: adding or updating IPv6 address:
2xxx:xxx:xxxx:xxxx::xxx:xxxx/64 lft forever pref forever lifetime
129-0[4294967295,4294967295] ptp xxxx:xxx:xxxx:xxxx::1 dev 28 src unknown
18:21:58 <debug> [1462918918.5441] platform-linux: netlink: recvmsg: error
message from kernel: Invalid argument (22) for request 115
18:21:58 <error> [1462918918.5442] platform-linux: do-add-ip6-address[28:
2xxx:xxx:xxxx:xxxx::xxx:xxxx]: failure 22 (Invalid argument)
18:21:58 <debug> [1462918918.5445] platform: route: adding or updating IPv6
route: xxx:xx:x000::/44 via 2xxx:xxxx:xxxx:xxxx::1 dev 28 metric 50 mss 0 src
vpn
18:21:58 <debug> [1462918918.5446] platform-linux: netlink: recvmsg: error
message from kernel: No route to host (113) for request 117
18:21:58 <error> [1462918918.5447] platform-linux: do-add-ip6-route[28:
xxx:xx:x000::/44 50]: failure 113 (No route to host)
18:21:58 <debug> [1462918918.5449] platform: route: adding or updating IPv6
route: 2xxx:xxx:xxxx::/47 via 2xxx:xxxx:xxxx:xxxx::1 dev 28 metric 50 mss 0 src
vpn
18:21:58 <debug> [1462918918.5451] platform-linux: netlink: recvmsg: error
message from kernel: No route to host (113) for request 119
18:21:58 <error> [1462918918.5451] platform-linux: do-add-ip6-route[28:
2xxx:xxx:xxxx::/47 50]: failure 113 (No route to host)
18:21:58 <debug> [1462918918.5454] platform: route: adding or updating IPv6
route: 2xxx:xxx:xxxx::/47 via 2xxx:xxxx:xxxx:xxxx::1 dev 28 metric 50 mss 0
src vpn
18:21:58 <debug> [1462918918.5455] platform-linux: netlink: recvmsg: error
message from kernel: No route to host (113) for request 121
18:21:58 <error> [1462918918.5456] platform-linux: do-add-ip6-route[28:
2xxx:xxx:xxxx::/47 50]: failure 113 (No route to host)
18:21:58 <debug> [1462918918.5458] platform: route: adding or updating IPv6
route: 2xxx:xxx:xxxx::/48 via 2xxx:xxxx:xxxx:xxxx::1 dev 28 metric 50 mss 0
src vpn
18:21:58 <debug> [1462918918.5459] platform-linux: netlink: recvmsg: error
message from kernel: No route to host (113) for request 123
18:21:58 <error> [1462918918.5460] platform-linux: do-add-ip6-route[28:
2xxx:xxx:xxxx::/48 50]: failure 113 (No route to host)
18:21:58 <debug> [1462918918.5467] platform-linux: sysctl: reading
'/proc/sys/net/ipv6/conf/wlan0/mtu': '1500'
18:21:58 <debug> [1462918918.5469] platform: address: adding or updating IPv4
address: 192.168.1.18/24 lft 86281sec pref 86281sec lifetime 129-0[86281,86281]
dev 22 src unknown
18:21:58 <debug> [1462918918.5470] platform-linux: netlink: recvmsg: error
message from kernel: File exists (17) for request 125
18:21:58 <error> [1462918918.5471] platform-linux: do-add-ip4-address[22:
192.168.1.18/24]: failure 17 (File exists)
18:21:58 <debug> [1462918918.5472] platform: route: deleting IPv4 route
192.168.1.0/24, metric=600, ifindex 22 dev wlan0
18:21:58 <debug> [1462918918.5474] platform: signal: route 4 removed:
192.168.1.0/24 via 0.0.0.0 dev 22 metric 600 mss 0 src rtprot-kernel scope link
pref-src 192.168.1.18
18:21:58 <debug> [1462918918.5475] platform-linux: do-delete-ip4-route[22:
192.168.1.0/24 600]: success
18:21:58 <debug> [1462918918.5476] platform: route: adding or updating IPv4
route: xx.xxx.xx.xx/32 via 192.168.1.1 dev 22 metric 600 mss 0 src vpn
18:21:58 <debug> [1462918918.5478] platform-linux: netlink: recvmsg: error
message from kernel: No such process (3) for request 127
18:21:58 <error> [1462918918.5478] platform-linux: do-add-ip4-route[22:
xx.xxx.xx.xx/32 600]: failure 3 (No such process)
18:21:58 <debug> [1462918918.5495] platform: route: adding or updating IPv4
route: 0.0.0.0/0 via 192.168.1.1 dev 22 metric 600 mss 0 src user
18:21:58 <debug> [1462918918.5496] platform-linux: netlink: recvmsg: error
message from kernel: No such process (3) for request 129
18:21:58 <error> [1462918918.5497] platform-linux: do-add-ip4-route[22:
0.0.0.0/0 600]: failure 3 (No such process)
18:21:58 <debug> [1462918918.5503] platform: address: adding or updating IPv6
address: xxxx::xxxx:xxxx:xxx:xxxx/64 lft forever pref forever lifetime
129-0[4294967295,4294967295] dev 22 flags permanent src unknown
18:21:58 <debug> [1462918918.5505] platform-linux: netlink: recvmsg: error
message from kernel: Invalid argument (22) for request 130
18:21:58 <error> [1462918918.5507] platform-linux: do-add-ip6-address[22:
xxxx::xxxx:xxxx:xxxx:xxxx]: failure 22 (Invalid argument)
18:21:58 <info> [1462918918.5509]
vpn-connection[0x996148,975b1a22-a63d-482c-beb7-5d7b5a64ca06,"us.xx.xx.com",28:(tun0)]:
VPN connection: (IP Config Get) complete
18:21:58 <debug> [1462918918.5524] platform-linux: sysctl: reading
'/proc/sys/net/ipv6/conf/tun0/accept_ra': '1'
18:21:58 <debug> [1462918918.5527] platform-linux: sysctl: reading
'/proc/sys/net/ipv6/conf/tun0/accept_ra_defrtr': '1'
18:21:58 <debug> [1462918918.5529] platform-linux: sysctl: reading
'/proc/sys/net/ipv6/conf/tun0/accept_ra_pinfo': '1'
18:21:58 <debug> [1462918918.5531] platform-linux: sysctl: reading
'/proc/sys/net/ipv6/conf/tun0/accept_ra_rtr_pref': '1'
18:21:58 <debug> [1462918918.5534] platform-linux: sysctl: reading
'/proc/sys/net/ipv6/conf/tun0/disable_ipv6': '0'
18:21:58 <debug> [1462918918.5536] platform-linux: sysctl: reading
'/proc/sys/net/ipv6/conf/tun0/hop_limit': '64'
18:21:58 <debug> [1462918918.5538] platform-linux: sysctl: reading
'/proc/sys/net/ipv6/conf/tun0/use_tempaddr': '-1'
18:21:59 <debug> [1462918919.1672] platform-linux: sysctl: setting
'/proc/sys/net/ipv6/conf/tun0/disable_ipv6' to '0' (current value is identical)
18:21:59 <debug> [1462918919.1675] platform-linux: sysctl: setting
'/proc/sys/net/ipv6/conf/tun0/use_tempaddr' to '-1' (current value is identical)
18:21:59 <debug> [1462918919.1679] platform-linux: sysctl: setting
'/proc/sys/net/ipv6/conf/tun0/hop_limit' to '64' (current value is identical)
18:21:59 <debug> [1462918919.1682] platform-linux: sysctl: setting
'/proc/sys/net/ipv6/conf/tun0/accept_ra_pinfo' to '1' (current value is
identical)
18:21:59 <debug> [1462918919.1685] platform-linux: sysctl: setting
'/proc/sys/net/ipv6/conf/tun0/accept_ra_rtr_pref' to '1' (current value is
identical)
18:21:59 <debug> [1462918919.1701] platform-linux: sysctl: setting
'/proc/sys/net/ipv6/conf/tun0/accept_ra' to '1' (current value is identical)
18:21:59 <debug> [1462918919.1704] platform-linux: sysctl: setting
'/proc/sys/net/ipv6/conf/tun0/accept_ra_defrtr' to '1' (current value is
identical)
18:21:59 <debug> [1462918919.1734] platform: address: adding or updating IPv4
address: xx.xxx.xx.xx/18 lft forever pref forever lifetime
130-0[4294967295,4294967295] dev 28 src unknown
18:21:59 <debug> [1462918919.1737] platform-linux: netlink: recvmsg: error
message from kernel: File exists (17) for request 131
18:21:59 <error> [1462918919.1740] platform-linux: do-add-ip4-address[28:
xx.xxx.xx.xx/18]: failure 17 (File exists)
_______________________________________________
networkmanager-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/networkmanager-list
