Hallo Forum,
habe seit 3 Tagen Ubuntu 17.04 drauf (upgrade von 16.10) und gestern ein paar neue updates gezogen (ignoriert welche), alles lief prima.
Heute viel mir dann auf, das der Network Manager mich keine VPN Verbindung aufbauen lässt...oder besser gesagt, ich kann beide (hab 2 VPNs) auswählen und beide haben gleichzeitig ihren Haken gesetzt, obwohl ich nur 1 NIC hab (kein Subinterfaces, vlans etc).
Die VPNs sind nicht wirklich aktiv, nur die Häckchen sind gesetzt und in dem Menüpunkt "Verbindungsinformationen" steht, das nicht meine normale NIC, sondern virbr0 aktiv ist....alle anderen Felder stehen auf "unbekannt". Seltsam finde ich u.a., das ip die virbr0 als DOWN bezeichnet
1 2 3 4 5 6 7 8 9 | 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 94:de:80:a5:8a:9a brd ff:ff:ff:ff:ff:ff inet 192.168.0.13/24 brd 192.168.0.255 scope global enp3s0 valid_lft forever preferred_lft forever 3: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether 52:54:00:d7:8c:9e brd ff:ff:ff:ff:ff:ff 4: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast master virbr0 state DOWN group default qlen 1000 link/ether 52:54:00:d7:8c:9e brd ff:ff:ff:ff:ff:ff |
In's Internet an sich komme ich, verändert hab ich 100% nichts. IP Vergabe ist via DHCP, keine Änderung in der /etc/network/interfaces oder sonstwas. Anbei ein paar Konrollen:
1 2 3 4 5 6 7 8 9 10 11 | ● networking.service - Raise network interfaces Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor preset: enabled) Active: active (exited) since Sat 2017-04-22 21:40:18 CEST; 1h 6min ago Docs: man:interfaces(5) Main PID: 1122 (code=exited, status=0/SUCCESS) CGroup: /system.slice/networking.service Apr 22 21:40:14 DreamPC systemd[1]: Starting Raise network interfaces... Apr 22 21:40:16 DreamPC ifup[1122]: /sbin/ifup: waiting for lock on /run/network/ifstate.enp3s0 Apr 22 21:40:18 DreamPC systemd[1]: Started Raise network interfaces. |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 | ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2017-04-22 21:40:15 CEST; 1h 7min ago Docs: man:NetworkManager(8) Main PID: 1009 (NetworkManager) CGroup: /system.slice/NetworkManager.service └─1009 /usr/sbin/NetworkManager --no-daemon Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0663] device (virbr0): state change: deactivating -> disconnected (reason 'connection-removed') [110 30 38] Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0683] keyfile: add connection in-memory (b5a7f646-379a-4d86-904d-3ffd99239425,"virbr0") Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0694] device (virbr0): Activation: starting connection 'virbr0' (b5a7f646-379a-4d86-904d-3ffd99239425) Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0701] device (virbr0): state change: disconnected -> prepare (reason 'none') [30 40 0] Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0703] device (virbr0): state change: prepare -> config (reason 'none') [40 50 0] Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0704] device (virbr0): state change: config -> ip-config (reason 'none') [50 70 0] Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0707] device (virbr0): state change: ip-config -> ip-check (reason 'ip-config-unavailable') [70 80 5] Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0709] device (virbr0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0710] device (virbr0): state change: secondaries -> activated (reason 'none') [90 100 0] Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0833] device (virbr0): Activation: successful, device activated. |
1 2 3 4 | brctl show bridge name bridge id STP enabled interfaces virbr0 8000.525400d78c9e yes virbr0-nic |
Wenn ich probiere, die virbr0 mittels nmtui zu löschen, passiert nichts (ausser ein paar Syslog Einträge)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 | Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0518] device (virbr0): state change: activated -> deactivating (reason 'connection-removed') [100 110 38] Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0655] audit: op="connection-delete" uuid="8ad02338-6bc4-41ae-91d3-722b097488f0" name="virbr0" pid=5130 uid=0 result="success" Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0663] device (virbr0): state change: deactivating -> disconnected (reason 'connection-removed') [110 30 38] Apr 22 22:44:17 DreamPC vmnet-natd: RTM_NEWLINK: name:virbr0 index:3 flags:0x00001003 Apr 22 22:44:17 DreamPC vmnetBridge: RTM_NEWLINK: name:virbr0 index:3 flags:0x00001003 Apr 22 22:44:17 DreamPC dbus[924]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' Apr 22 22:44:17 DreamPC kernel: [ 3844.713204] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0683] keyfile: add connection in-memory (b5a7f646-379a-4d86-904d-3ffd99239425,"virbr0") Apr 22 22:44:17 DreamPC systemd[1]: Starting Network Manager Script Dispatcher Service... Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0694] device (virbr0): Activation: starting connection 'virbr0' (b5a7f646-379a-4d86-904d-3ffd99239425) Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0701] device (virbr0): state change: disconnected -> prepare (reason 'none') [30 40 0] Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0703] device (virbr0): state change: prepare -> config (reason 'none') [40 50 0] Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0704] device (virbr0): state change: config -> ip-config (reason 'none') [50 70 0] Apr 22 22:44:17 DreamPC vmnet-natd: RTM_NEWLINK: name:virbr0 index:3 flags:0x00001003 Apr 22 22:44:17 DreamPC vmnetBridge: RTM_NEWLINK: name:virbr0 index:3 flags:0x00001003 Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0707] device (virbr0): state change: ip-config -> ip-check (reason 'ip-config-unavailable') [70 80 5] Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0709] device (virbr0): state change: ip-check -> secondaries (reason 'none') [80 90 0] Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0710] device (virbr0): state change: secondaries -> activated (reason 'none') [90 100 0] Apr 22 22:44:17 DreamPC dbus[924]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Apr 22 22:44:17 DreamPC nm-dispatcher: req:1 'down' [virbr0]: new request (2 scripts) Apr 22 22:44:17 DreamPC nm-dispatcher: req:1 'down' [virbr0]: start running ordered scripts... Apr 22 22:44:17 DreamPC nm-dispatcher[5994]: grep: /etc/resolv.conf: No such file or directory Apr 22 22:44:17 DreamPC NetworkManager[1009]: <info> [1492893857.0833] device (virbr0): Activation: successful, device activated. Apr 22 22:44:17 DreamPC nm-dispatcher: req:2 'up' [virbr0]: new request (2 scripts) Apr 22 22:44:17 DreamPC nm-dispatcher: req:2 'up' [virbr0]: start running ordered scripts... Apr 22 22:44:17 DreamPC systemd[1]: Started Network Manager Script Dispatcher Service. Apr 22 22:44:17 DreamPC nm-dispatcher[5994]: grep: /etc/resolv.conf: No such file or directory Apr 22 22:44:17 DreamPC systemd[1]: Reloading OpenBSD Secure Shell server. Apr 22 22:44:17 DreamPC systemd[1]: Reloaded OpenBSD Secure Shell server. Apr 22 22:44:17 DreamPC systemd[1]: Reloading. Apr 22 22:44:17 DreamPC systemd[1]: snapd.refresh.timer: Adding 4h 41min 23.285666s random time. Apr 22 22:44:17 DreamPC systemd[1]: apt-daily.timer: Adding 16min 19.960893s random time. |
Ich bin gerade so ziemlich ratlos, BUG? Neues Feature ? Wie gesagt, gestern ging alles und nun das? Habe ich irgend was dummes übersehen?