NetworkManager Bond wifi Ethernet

Einrichten des lokalen Netzes, Verbindung zu anderen Computern und Diensten.
Antworten
kocj
Beiträge: 5
Registriert: 09.02.2018 05:10:52

NetworkManager Bond wifi Ethernet

Beitrag von kocj » 09.02.2018 14:15:36

Nach einigen versuchen ist es mir gelungen mit Hilfe von mncli einen wifi ethernet bond zusammenzustellen. So bin ich vorgegangen.

Setup master and slaves

Code: Alles auswählen

# nmcli con add type bond ifname wifiether mode active-backup
# nmcli con add type wifi ifname wlp3s0 ssid ganesha master wifiether
# nmcli con add type ethernet ifname enp0s25 master wifiether
Add the wifi-security section.

Code: Alles auswählen

# nano /etc/NetworkManager/system-connections/bond-slave-wlp3s0
[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
psk=xxxxxxxx
Add primary option to [bond] section.

Code: Alles auswählen

# nano /etc/NetworkManager/system-connections/bond-wifiether
primary=enp0s25

# nmcli con reload
Bring up the slave, the master gets activated also.

Code: Alles auswählen

# nmcli con up bond-slave-wlp3s0 
# nmcli con up bond-slave-enp0s25
# reboot
Das funktioniert soweit auch gut, Ich habe nur eine IP Adresse wie ich wünsche, wenn ich den Ethernet Kable anschließe wird automatisch umgeschaltet.

Die Probleme entstehen wenn ich den Router neu starte, dann kommt keine wifi Verbindung mehr zustande.
Auch ein manuelles nmcli con up bond-slave-wlp3s0 hilft nicht weiter. Mit den syslog Ausdruck kann ich nichts anfangen kann.

Hier der teil wenn ich den Router neu starte.

Code: Alles auswählen

Feb  9 20:19:27 lakshmi kernel: [  631.590697] wifiether: link status definitely down for interface wlp3s0, disabling it
Feb  9 20:19:27 lakshmi NetworkManager[817]: <warn>  [1518178767.3197] sup-iface[0x563b1def5d30,wlp3s0]: connection disconnected (reason -4)
Feb  9 20:19:27 lakshmi NetworkManager[817]: <info>  [1518178767.3559] device (wlp3s0): supplicant interface state: completed -> disconnected
Feb  9 20:19:27 lakshmi gnome-shell[2011]: JS LOG: An active wireless connection, in infrastructure mode, involves no access point?
Feb  9 20:19:27 lakshmi gnome-shell[1243]: JS LOG: An active wireless connection, in infrastructure mode, involves no access point?
Feb  9 20:19:27 lakshmi NetworkManager[817]: <info>  [1518178767.4236] device (wlp3s0): supplicant interface state: disconnected -> scanning
Feb  9 20:19:29 lakshmi kernel: [  633.630756] e1000e: enp0s25 NIC Link is Down
Feb  9 20:19:29 lakshmi kernel: [  633.690778] wifiether: link status definitely down for interface enp0s25, disabling it
Feb  9 20:19:29 lakshmi kernel: [  633.690846] wifiether: now running without any active interface!
Feb  9 20:19:32 lakshmi kernel: [  636.386305] e1000e: enp0s25 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Feb  9 20:19:32 lakshmi kernel: [  636.386314] e1000e 0000:00:19.0 enp0s25: 10/100 speed: disabling TSO
Feb  9 20:19:32 lakshmi NetworkManager[817]: <info>  [1518178772.0792] device (enp0s25): link connected
Feb  9 20:19:32 lakshmi NetworkManager[817]: <info>  [1518178772.1112] device (wifiether): link connected
Feb  9 20:19:32 lakshmi kernel: [  636.418880] wifiether: link status definitely up for interface enp0s25, 100 Mbps full duplex
Feb  9 20:19:32 lakshmi kernel: [  636.418883] wifiether: making interface enp0s25 the new active one
Feb  9 20:19:32 lakshmi kernel: [  636.419017] wifiether: first active interface up!
Feb  9 20:19:35 lakshmi kernel: [  640.186412] e1000e: enp0s25 NIC Link is Down
Feb  9 20:19:35 lakshmi kernel: [  640.274300] wifiether: link status definitely down for interface enp0s25, disabling it
Feb  9 20:19:35 lakshmi kernel: [  640.274337] wifiether: now running without any active interface!
Feb  9 20:19:37 lakshmi kernel: [  641.858013] e1000e: enp0s25 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Feb  9 20:19:37 lakshmi kernel: [  641.858017] e1000e 0000:00:19.0 enp0s25: 10/100 speed: disabling TSO
Feb  9 20:19:37 lakshmi NetworkManager[817]: <info>  [1518178777.5508] device (enp0s25): link connected
Feb  9 20:19:37 lakshmi NetworkManager[817]: <info>  [1518178777.6345] device (wifiether): link connected
Feb  9 20:19:37 lakshmi kernel: [  641.942199] wifiether: link status definitely up for interface enp0s25, 100 Mbps full duplex
Feb  9 20:19:37 lakshmi kernel: [  641.942201] wifiether: making interface enp0s25 the new active one
Feb  9 20:19:37 lakshmi kernel: [  641.942331] wifiether: first active interface up!
Feb  9 20:19:42 lakshmi kernel: [  646.342162] e1000e: enp0s25 NIC Link is Down
Feb  9 20:19:42 lakshmi kernel: [  646.426022] wifiether: link status definitely down for interface enp0s25, disabling it
Feb  9 20:19:42 lakshmi kernel: [  646.426057] wifiether: now running without any active interface!
Feb  9 20:19:42 lakshmi NetworkManager[817]: <warn>  [1518178782.6630] device (wlp3s0): link timed out.
Feb  9 20:19:42 lakshmi NetworkManager[817]: <info>  [1518178782.6631] device (wlp3s0): state change: activated -> failed (reason 'ssid-not-found') [100 120 53]
Feb  9 20:19:42 lakshmi NetworkManager[817]: <warn>  [1518178782.6678] device (wifiether): failed to release bond slave wlp3s0
Feb  9 20:19:42 lakshmi NetworkManager[817]: <info>  [1518178782.6689] device (wlp3s0): released from master device wifiether
Feb  9 20:19:42 lakshmi NetworkManager[817]: <warn>  [1518178782.6692] device (wlp3s0): Activation: failed for connection 'bond-slave-wlp3s0'
Feb  9 20:19:42 lakshmi NetworkManager[817]: <info>  [1518178782.6708] device (wlp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Feb  9 20:19:42 lakshmi NetworkManager[817]: <info>  [1518178782.6776] device (wlp3s0): set-hw-addr: set MAC address to 72:AB:F4:CA:FA:E3 (scanning)
Feb  9 20:19:42 lakshmi NetworkManager[817]: <info>  [1518178782.6833] device (wlp3s0): released from master device wifiether
Feb  9 20:19:42 lakshmi NetworkManager[817]: <info>  [1518178782.7109] device (wlp3s0): supplicant interface state: scanning -> disabled
Feb  9 20:19:42 lakshmi NetworkManager[817]: <info>  [1518178782.7398] device (wlp3s0): supplicant interface state: disabled -> inactive
Feb  9 20:19:43 lakshmi kernel: [  647.997683] e1000e: enp0s25 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Feb  9 20:19:43 lakshmi kernel: [  647.997686] e1000e 0000:00:19.0 enp0s25: 10/100 speed: disabling TSO
Feb  9 20:19:43 lakshmi NetworkManager[817]: <info>  [1518178783.6905] device (enp0s25): link connected
Feb  9 20:19:43 lakshmi NetworkManager[817]: <info>  [1518178783.7834] device (wifiether): link connected
Feb  9 20:19:43 lakshmi kernel: [  648.089993] wifiether: link status definitely up for interface enp0s25, 100 Mbps full duplex
Feb  9 20:19:43 lakshmi kernel: [  648.090001] wifiether: making interface enp0s25 the new active one
Feb  9 20:19:43 lakshmi kernel: [  648.090243] wifiether: first active interface up!
Feb  9 20:19:52 lakshmi kernel: [  657.038698] wifiether: Removing slave wlp3s0
Feb  9 20:19:52 lakshmi kernel: [  657.038971] wifiether: Releasing backup interface wlp3s0
Feb  9 20:19:52 lakshmi NetworkManager[817]: <info>  [1518178792.7859] device (wlp3s0): supplicant interface state: inactive -> disabled
Feb  9 20:19:54 lakshmi kernel: [  658.965508] e1000e: enp0s25 NIC Link is Down
Feb  9 20:19:54 lakshmi kernel: [  659.053330] wifiether: link status definitely down for interface enp0s25, disabling it
Feb  9 20:19:54 lakshmi kernel: [  659.053368] wifiether: now running without any active interface!
Feb  9 20:19:56 lakshmi kernel: [  660.649026] e1000e: enp0s25 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Feb  9 20:19:56 lakshmi kernel: [  660.649029] e1000e 0000:00:19.0 enp0s25: 10/100 speed: disabling TSO
Feb  9 20:19:56 lakshmi NetworkManager[817]: <info>  [1518178796.3425] device (enp0s25): link connected
Feb  9 20:19:56 lakshmi NetworkManager[817]: <info>  [1518178796.4188] device (wifiether): link connected
Feb  9 20:19:56 lakshmi kernel: [  660.725293] wifiether: link status definitely up for interface enp0s25, 100 Mbps full duplex
Feb  9 20:19:56 lakshmi kernel: [  660.725295] wifiether: making interface enp0s25 the new active one
Feb  9 20:19:56 lakshmi kernel: [  660.725420] wifiether: first active interface up!
Feb  9 20:20:05 lakshmi NetworkManager[817]: <info>  [1518178805.6649] device (wlp3s0): set-hw-addr: set MAC address to 72:AB:F4:CA:FA:E3 (scanning)
Dieser abschnitt entsteht wenn ich den slave manuell starte.

Code: Alles auswählen

Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4732] device (wlp3s0): Activation: starting connection 'bond-slave-wlp3s0' (f9ac0b4d-5748-4bf8-acbf-306aec5344bd)
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4734] audit: op="connection-activate" uuid="f9ac0b4d-5748-4bf8-acbf-306aec5344bd" name="bond-slave-wlp3s0" pid=3674 uid=0 result="success"
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4736] device (wlp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4740] device (wlp3s0): set-hw-addr: reset MAC address to 60:57:18:C0:01:66 (preserve)
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4752] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4817] device (wlp3s0): Activation: (wifi) access point 'bond-slave-wlp3s0' has security, but secrets are required.
Feb  9 20:27:33 lakshmi kernel: [ 1117.764715] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4822] device (wlp3s0): state change: config -> need-auth (reason 'none') [50 60 0]
Feb  9 20:27:33 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4877] device (wlp3s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb  9 20:27:33 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4905] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4919] device (wlp3s0): Activation: (wifi) connection 'bond-slave-wlp3s0' has security, and secrets exist.  No new secrets needed.
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4924] Config: added 'ssid' value 'ganesha'
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4928] Config: added 'scan_ssid' value '1'
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4933] Config: added 'key_mgmt' value 'WPA-PSK'
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4936] Config: added 'auth_alg' value 'OPEN'
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.4940] Config: added 'psk' value '<hidden>'
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.5069] device (wlp3s0): supplicant interface state: disabled -> inactive
Feb  9 20:27:33 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:33 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:33 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:33 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:33 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:33 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:33 lakshmi NetworkManager[817]: <info>  [1518179253.5548] device (wlp3s0): supplicant interface state: inactive -> scanning
Feb  9 20:27:34 lakshmi kernel: [ 1118.861749] wlp3s0: authenticate with 00:1c:c2:15:a6:31
Feb  9 20:27:34 lakshmi NetworkManager[817]: <info>  [1518179254.5842] device (wlp3s0): supplicant interface state: scanning -> authenticating
Feb  9 20:27:34 lakshmi kernel: [ 1118.866798] wlp3s0: send auth to 00:1c:c2:15:a6:31 (try 1/3)
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi kernel: [ 1118.958754] wlp3s0: authenticated
Feb  9 20:27:34 lakshmi kernel: [ 1118.961785] wlp3s0: associate with 00:1c:c2:15:a6:31 (try 1/3)
Feb  9 20:27:34 lakshmi NetworkManager[817]: <info>  [1518179254.6811] device (wlp3s0): supplicant interface state: authenticating -> associating
Feb  9 20:27:34 lakshmi kernel: [ 1119.065812] wlp3s0: associate with 00:1c:c2:15:a6:31 (try 2/3)
Feb  9 20:27:34 lakshmi kernel: [ 1119.080155] wlp3s0: RX AssocResp from 00:1c:c2:15:a6:31 (capab=0x431 status=0 aid=1)
Feb  9 20:27:34 lakshmi kernel: [ 1119.081381] wlp3s0: associated
Feb  9 20:27:34 lakshmi kernel: [ 1119.081444] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
Feb  9 20:27:34 lakshmi NetworkManager[817]: <info>  [1518179254.8036] device (wlp3s0): supplicant interface state: associating -> associated
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi NetworkManager[817]: <info>  [1518179254.8342] device (wlp3s0): supplicant interface state: associated -> 4-way handshake
Feb  9 20:27:34 lakshmi NetworkManager[817]: <info>  [1518179254.8614] device (wlp3s0): supplicant interface state: 4-way handshake -> completed
Feb  9 20:27:34 lakshmi NetworkManager[817]: <info>  [1518179254.8614] device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'ganesha'.
Feb  9 20:27:34 lakshmi NetworkManager[817]: <info>  [1518179254.8615] device (wlp3s0): state change: config -> ip-config (reason 'none') [50 70 0]
Feb  9 20:27:34 lakshmi NetworkManager[817]: <info>  [1518179254.8617] device (wifiether): bond slave wlp3s0 was enslaved
Feb  9 20:27:34 lakshmi NetworkManager[817]: <info>  [1518179254.8618] device (wlp3s0): Activation: connection 'bond-slave-wlp3s0' enslaved, continuing activation
Feb  9 20:27:34 lakshmi NetworkManager[817]: <info>  [1518179254.8643] device (wlp3s0): state change: ip-config -> secondaries (reason 'none') [70 90 0]
Feb  9 20:27:34 lakshmi NetworkManager[817]: <info>  [1518179254.8646] device (wlp3s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi NetworkManager[817]: <info>  [1518179254.8719] device (wlp3s0): Activation: successful, device activated.
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Feb  9 20:27:34 lakshmi gnome-control-c[3652]: ((libnm-core/nm-setting-ip-config.c:1247)): assertion '<dropped>' failed
Zuletzt geändert von kocj am 10.02.2018 06:28:32, insgesamt 1-mal geändert.

Jana66
Beiträge: 3505
Registriert: 03.02.2016 12:41:11

Re: NetworkManager Bond wifi Ethernet

Beitrag von Jana66 » 09.02.2018 16:04:18

Es geht darum, die Slaves nicht erneut zu starten, während das Gesamtgebilde »bond0« aktiviert wird. Der Parameter »bond-give-a-chance 20« lässt den WLAN-Geräten ein wenig Zeit, um sich mit den Accesspoints zu verbinden.
http://www.linux-magazin.de/ausgaben/2014/07/bonding/
K. A. wie man das mit nmcli (oder systemd) realisiert.
Wenn keiner was sagt, wird sich nichts ändern. Wenn alle nur reden ebenfalls nicht.

kocj
Beiträge: 5
Registriert: 09.02.2018 05:10:52

Re: NetworkManager Bond wifi Ethernet

Beitrag von kocj » 10.02.2018 06:26:02

Nach ein paar Experimenten weis ich etwas mehr.

Das wifi Interface wird bei einem Router Neustart oder Reboot deaktiviert. Ich vermute dass das durch den totalen verbindungslos-abbruch ausgelöst wird.

Es ist relativ einfach den Bond wider zu "Bleleben": Den Master deaktivieren und die slaves wieder hochbringen, dann ist alles wieder beim alten.

Code: Alles auswählen

# nmcli c down bond-wifiether
# nmcli con up bond-slave-wlp3s0
# nmcli con up bond-slave-enp0s25
Versuche den Syslog zu interpretieren

Code: Alles auswählen

link timed out.
state change: activated -> failed (reason 'ssid-not-found')
Das ist wohl richtig da der Router gerade neu startet.

Code: Alles auswählen

failed to release bond slave wlp3s0
device (wlp3s0): released from master device wifiether
Die frage ist Eigenschaften einzustellen sind damit NetworkManager den Salve nicht entlasst.

Code: Alles auswählen

Removing slave wlp3s0
wifiether: Releasing backup interface wlp3s0
the permanent HWaddr of wlp3s0 - 60:57:18:c0:01:66 - is still in use by wifiether - set the HWaddr of wlp3s0 to a different address to avoid conflicts
Hier vermute ich den Teufel begraben, weil am ende das wifi Interface deaktiviert ist.

Folgendes ist erfolglos verlaufen:

Globale einstellungen in NetworkManager.conf

Code: Alles auswählen

[connection]
ipv4.dhcp-timeout=120
ipv6.dhcp-timeout=120
connection.auth-retries=0

[device]
match-device=wlp3s0
carrier-wait-timeout=120 >> delays startup
Wobei carrier-wait-timeout dem give-bond-a-change-20 entsprechen sollte

Verbindungs- Einstellungen in bond-slave-wlp3s0

Code: Alles auswählen

[connection]
autoconnect-retries=0 >> unendlich
getaway-ping-timeout=30 

Jana66
Beiträge: 3505
Registriert: 03.02.2016 12:41:11

Re: NetworkManager Bond wifi Ethernet

Beitrag von Jana66 » 10.02.2018 10:59:36

kocj hat geschrieben: ↑ zum Beitrag ↑
10.02.2018 06:26:02
Es ist relativ einfach den Bond wider zu "Bleleben": Den Master deaktivieren und die slaves wieder hochbringen, dann ist alles wieder beim alten.
Löse doch das Startproblem korrekt mittels systemd units: https://wiki.archlinux.org/index.php/Wireless_bonding

Bezüglich MAC-Adresse:
My solution was to use the wireless MAC for the bond and put the wired interface in promiscuous mode.
http://r.outlyer.net/linux:bonding
Wenn keiner was sagt, wird sich nichts ändern. Wenn alle nur reden ebenfalls nicht.

kocj
Beiträge: 5
Registriert: 09.02.2018 05:10:52

Re: NetworkManager Bond wifi Ethernet

Beitrag von kocj » 10.02.2018 11:48:58

Weitere fortschritte

Ein simples wifi aus - wifi an, oder tiefer greifendes service network-manager restart bringt den wifi Slave wider zum leben.

Könnte es sein das der bond-slave-wlps03 beim Verbindungs- Abbruch nicht richtig beendet wird?

Code: Alles auswählen

root@lakshmi:/etc/NetworkManager# nmcli d
DEVICE     TYPE      STATE         CONNECTION         
wifiether  bond      connected     bond-wifiether     
enp0s25    ethernet  connected     bond-slave-enp0s25 
wlp3s0     wifi      disconnected  --                 
lo         loopback  unmanaged     --      
Die Zeile wlp3s0 wifi disconnected scheint die Mutter des Übels zu sein. Weil der Physische Adapter abgeschaltet ist kann sich der Slave nicht verbinden???...

kocj
Beiträge: 5
Registriert: 09.02.2018 05:10:52

Re: NetworkManager Bond wifi Ethernet

Beitrag von kocj » 10.02.2018 12:24:54

@jana66 danke für deine Unterstützung.

Ich möchte den NetworkManager behalten der ist sonst schön "handsfree" und bei Gnome tief verwurzelt wie ich verstanden habe.

Leider funktioniert noch keiner dieser Ansätze reibungslos.

Sollte eigentlich Standard beim Laptop sein, durch eine active-backup bond werden keine Downloads abgebrochen, weniger IP Adressen verwendet.

kocj
Beiträge: 5
Registriert: 09.02.2018 05:10:52

Re: NetworkManager Bond wifi Ethernet

Beitrag von kocj » 12.02.2018 08:21:30

Riesen schritt weiter!

Die option fail_over_mac=1 löst fast alle Probleme, sogar VBox über "gebridgen" Adapter funktioniert unterbrechungsfrei.

Code: Alles auswählen

nano /etc/NetworkManager/system-connections/bond-wifiether

[bond]
primary=enp0s25
fail_over_mac=1
Hier die bonding Einstellungen für interessierte.

Code: Alles auswählen

root@lakshmi:~# cat /proc/net/bonding/wifiether
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: fault-tolerance (active-backup) (fail_over_mac active)
Primary Slave: enp0s25 (primary_reselect always)
Currently Active Slave: wlp3s0
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: wlp3s0
MII Status: up
Speed: Unknown
Duplex: Unknown
Link Failure Count: 0
Permanent HW addr: 60:57:18:c0:01:66
Slave queue ID: 0

Slave Interface: enp0s25
MII Status: down
Speed: Unknown
Duplex: Unknown
Link Failure Count: 3
Permanent HW addr: 68:f7:28:9b:14:0a
Slave queue ID: 0
Down Delay (ms): 0
So sieht das kabelziehen im log aus.

Code: Alles auswählen

Feb 12 14:52:38 lakshmi kernel: [ 3041.369204] e1000e: enp0s25 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 12 14:52:38 lakshmi kernel: [ 3041.369207] e1000e 0000:00:19.0 enp0s25: 10/100 speed: disabling TSO
Feb 12 14:52:38 lakshmi NetworkManager[637]: <info>  [1518418358.9022] device (enp0s25): link connected
Feb 12 14:52:38 lakshmi NetworkManager[637]: <info>  [1518418358.9024] device (wifiether): link connected
Feb 12 14:52:38 lakshmi kernel: [ 3041.461308] wifiether: link status definitely up for interface enp0s25, 100 Mbps full duplex
Feb 12 14:52:38 lakshmi kernel: [ 3041.461310] wifiether: making interface enp0s25 the new active one
Feb 12 14:52:48 lakshmi kernel: [ 3050.697925] e1000e: enp0s25 NIC Link is Down
Feb 12 14:52:48 lakshmi kernel: [ 3050.725786] wifiether: link status definitely down for interface enp0s25, disabling it
Feb 12 14:52:48 lakshmi kernel: [ 3050.725788] wifiether: making interface wlp3s0 the new active one
Feb 12 14:54:12 lakshmi kernel: [ 3135.268961] e1000e: enp0s25 NIC Link is Up 100 Mbps Full Duplex, Flow Control: Rx/Tx
Feb 12 14:54:12 lakshmi kernel: [ 3135.268965] e1000e 0000:00:19.0 enp0s25: 10/100 speed: disabling TSO
Feb 12 14:54:12 lakshmi NetworkManager[637]: <info>  [1518418452.7980] device (enp0s25): link connected
Feb 12 14:54:12 lakshmi NetworkManager[637]: <info>  [1518418452.7982] device (wifiether): link connected
Feb 12 14:54:12 lakshmi kernel: [ 3135.369290] wifiether: link status definitely up for interface enp0s25, 100 Mbps full duplex
Feb 12 14:54:12 lakshmi kernel: [ 3135.369292] wifiether: making interface enp0s25 the new active one
Verbleiben Probleme, nach standby oder Signal Abbruch verbindet sich der WIFI slave nicht. WIFI aus, WIFI an schaft hier abhilfe.

Interessanter weis fehlt in Gnome network-manager applet nur mein Hotspot ganesha!
Hier den log, vielleicht weis wer mehr. Die ersten Zeilen könnten Aufschluss geben.

Code: Alles auswählen

Router reboot wifi only

Feb 12 13:17:02 lakshmi NetworkManager[5361]: <warn>  [1518412622.7684] sup-iface[0x55740d230d40,wlp3s0]: connection disconnected (reason -4)
Feb 12 13:17:02 lakshmi NetworkManager[5361]: <info>  [1518412622.8014] device (wlp3s0): supplicant interface state: completed -> disconnected
Feb 12 13:17:02 lakshmi kernel: [ 6913.506881] wifiether: link status definitely down for interface wlp3s0, disabling it
Feb 12 13:17:02 lakshmi kernel: [ 6913.506911] wifiether: now running without any active interface!
Feb 12 13:17:02 lakshmi gnome-shell[1392]: JS LOG: An active wireless connection, in infrastructure mode, involves no access point?
Feb 12 13:17:02 lakshmi NetworkManager[5361]: <info>  [1518412622.8737] device (wlp3s0): supplicant interface state: disconnected -> scanning
Feb 12 13:17:18 lakshmi NetworkManager[5361]: <warn>  [1518412638.1143] device (wlp3s0): link timed out.
Feb 12 13:17:18 lakshmi NetworkManager[5361]: <info>  [1518412638.1143] device (wlp3s0): state change: activated -> failed (reason 'ssid-not-found') [100 120 53]
Feb 12 13:17:18 lakshmi NetworkManager[5361]: <warn>  [1518412638.1203] device (wifiether): failed to release bond slave wlp3s0
Feb 12 13:17:18 lakshmi NetworkManager[5361]: <info>  [1518412638.1217] device (wlp3s0): released from master device wifiether
Feb 12 13:17:18 lakshmi NetworkManager[5361]: <warn>  [1518412638.1219] device (wlp3s0): Activation: failed for connection 'bond-slave-wlp3s0'
Feb 12 13:17:18 lakshmi NetworkManager[5361]: <info>  [1518412638.1236] device (wlp3s0): state change: failed -> disconnected (reason 'none') [120 30 0]
Feb 12 13:17:18 lakshmi NetworkManager[5361]: <info>  [1518412638.1332] device (wlp3s0): set-hw-addr: set MAC address to 7A:A8:BA:0D:8F:40 (scanning)
Feb 12 13:17:18 lakshmi NetworkManager[5361]: <info>  [1518412638.1400] device (wlp3s0): released from master device wifiether
Feb 12 13:17:18 lakshmi NetworkManager[5361]: <info>  [1518412638.1664] device (wlp3s0): supplicant interface state: scanning -> disabled
Feb 12 13:17:18 lakshmi NetworkManager[5361]: <info>  [1518412638.1800] device (wlp3s0): supplicant interface state: disabled -> inactive
Feb 12 13:17:28 lakshmi kernel: [ 6938.877797] wifiether: Removing slave wlp3s0
Feb 12 13:17:28 lakshmi kernel: [ 6938.878066] wifiether: Releasing backup interface wlp3s0
Feb 12 13:17:28 lakshmi NetworkManager[5361]: <info>  [1518412648.2103] device (wlp3s0): supplicant interface state: inactive -> disabled

wifi off

Feb 12 13:18:04 lakshmi NetworkManager[5361]: <info>  [1518412684.2176] manager: WiFi hardware radio set disabled
Feb 12 13:18:04 lakshmi NetworkManager[5361]: <info>  [1518412684.2177] device (wlp3s0): state change: disconnected -> unavailable (reason 'none') [30 20 0]
Feb 12 13:18:04 lakshmi NetworkManager[5361]: <info>  [1518412684.2179] device (wlp3s0): released from master device wifiether
Feb 12 13:18:04 lakshmi NetworkManager[5361]: <info>  [1518412684.2196] audit: op="radio-control" arg="wireless-enabled:0" pid=1392 uid=1000 result="success"
Feb 12 13:18:04 lakshmi NetworkManager[5361]: <info>  [1518412684.2198] manager: WiFi now disabled by radio killswitch

wifi on 

Feb 12 13:18:10 lakshmi NetworkManager[5361]: <info>  [1518412690.3883] manager: WiFi hardware radio set enabled
Feb 12 13:18:10 lakshmi kernel: [ 6981.095845] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
Feb 12 13:18:10 lakshmi kernel: [ 6981.096474] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
Feb 12 13:18:10 lakshmi kernel: [ 6981.162747] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
Feb 12 13:18:10 lakshmi kernel: [ 6981.163217] iwlwifi 0000:03:00.0: L1 Enabled - LTR Enabled
Feb 12 13:18:10 lakshmi kernel: [ 6981.194635] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Feb 12 13:18:10 lakshmi NetworkManager[5361]: <info>  [1518412690.4900] audit: op="radio-control" arg="wireless-enabled:1" pid=1392 uid=1000 result="success"
Feb 12 13:18:10 lakshmi NetworkManager[5361]: <info>  [1518412690.4903] manager: WiFi now enabled by radio killswitch
Feb 12 13:18:10 lakshmi NetworkManager[5361]: <info>  [1518412690.5410] sup-iface[0x55740d1c2d30,wlp3s0]: supports 5 scan SSIDs
Feb 12 13:18:10 lakshmi NetworkManager[5361]: <info>  [1518412690.5420] device (wlp3s0): supplicant interface state: starting -> ready
Feb 12 13:18:10 lakshmi NetworkManager[5361]: <info>  [1518412690.5421] device (wlp3s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Feb 12 13:18:10 lakshmi kernel: [ 6981.247558] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.1830] device (wlp3s0): supplicant interface state: ready -> inactive
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.1863] policy: auto-activating connection 'bond-slave-wlp3s0'
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.1872] device (wlp3s0): Activation: starting connection 'bond-slave-wlp3s0' (a7a2018c-30e4-4b65-bd49-0cd985307b2e)
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.1874] device (wlp3s0): state change: disconnected -> prepare (reason 'none') [30 40 0]
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3008] device (wlp3s0): set-hw-addr: reset MAC address to 60:57:18:C0:01:66 (preserve)
Feb 12 13:18:14 lakshmi kernel: [ 6985.011976] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3226] device (wlp3s0): supplicant interface state: inactive -> disabled
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3415] device (wlp3s0): supplicant interface state: disabled -> inactive
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3418] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3419] device (wlp3s0): Activation: (wifi) access point 'bond-slave-wlp3s0' has security, but secrets are required.
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3420] device (wlp3s0): state change: config -> need-auth (reason 'none') [50 60 0]
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3447] device (wlp3s0): state change: need-auth -> prepare (reason 'none') [60 40 0]
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3451] device (wlp3s0): state change: prepare -> config (reason 'none') [40 50 0]
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3454] device (wlp3s0): Activation: (wifi) connection 'bond-slave-wlp3s0' has security, and secrets exist.  No new secrets needed.
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3454] Config: added 'ssid' value 'ganesha'
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3454] Config: added 'scan_ssid' value '1'
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3454] Config: added 'key_mgmt' value 'WPA-PSK'
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3454] Config: added 'psk' value '<hidden>'
Feb 12 13:18:14 lakshmi kernel: [ 6985.083728] wlp3s0: authenticate with 00:1c:c2:15:a6:31
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3853] device (wlp3s0): supplicant interface state: inactive -> authenticating
Feb 12 13:18:14 lakshmi kernel: [ 6985.089794] wlp3s0: send auth to 00:1c:c2:15:a6:31 (try 1/3)
Feb 12 13:18:14 lakshmi kernel: [ 6985.094155] wlp3s0: authenticated
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.3953] device (wlp3s0): supplicant interface state: authenticating -> associating
Feb 12 13:18:14 lakshmi kernel: [ 6985.099960] wlp3s0: associate with 00:1c:c2:15:a6:31 (try 1/3)
Feb 12 13:18:14 lakshmi kernel: [ 6985.105144] wlp3s0: RX AssocResp from 00:1c:c2:15:a6:31 (capab=0x431 status=0 aid=1)
Feb 12 13:18:14 lakshmi kernel: [ 6985.106791] wlp3s0: associated
Feb 12 13:18:14 lakshmi kernel: [ 6985.106861] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.4076] device (wlp3s0): supplicant interface state: associating -> associated
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.4199] device (wlp3s0): supplicant interface state: associated -> 4-way handshake
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.4283] device (wlp3s0): supplicant interface state: 4-way handshake -> completed
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.4284] device (wlp3s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'ganesha'.
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.4286] device (wlp3s0): state change: config -> ip-config (reason 'none') [50 70 0]
Feb 12 13:18:14 lakshmi kernel: [ 6985.134015] wlp3s0: deauthenticating from 00:1c:c2:15:a6:31 by local choice (Reason: 3=DEAUTH_LEAVING)
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.4532] device (wifiether): enslaved bond slave wlp3s0
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.4532] device (wlp3s0): Activation: connection 'bond-slave-wlp3s0' enslaved, continuing activation
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <warn>  [1518412694.4546] sup-iface[0x55740d1c2d30,wlp3s0]: connection disconnected (reason -3)
Feb 12 13:18:14 lakshmi kernel: [ 6985.157727] wifiether: Enslaving wlp3s0 as a backup interface with a down link
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.4549] device (wlp3s0): state change: ip-config -> secondaries (reason 'none') [70 90 0]
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.4552] device (wlp3s0): state change: secondaries -> activated (reason 'none') [90 100 0]
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.4621] device (wlp3s0): Activation: successful, device activated.
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.4831] device (wlp3s0): supplicant interface state: completed -> disconnected
Feb 12 13:18:14 lakshmi gnome-shell[1392]: JS LOG: An active wireless connection, in infrastructure mode, involves no access point?
Feb 12 13:18:14 lakshmi NetworkManager[5361]: <info>  [1518412694.5453] device (wlp3s0): supplicant interface state: disconnected -> scanning
Feb 12 13:18:15 lakshmi kernel: [ 6986.274747] wlp3s0: authenticate with 00:1c:c2:15:a6:31
Feb 12 13:18:15 lakshmi NetworkManager[5361]: <info>  [1518412695.5759] device (wlp3s0): supplicant interface state: scanning -> authenticating
Feb 12 13:18:15 lakshmi kernel: [ 6986.280327] wlp3s0: send auth to 00:1c:c2:15:a6:31 (try 1/3)
Feb 12 13:18:15 lakshmi kernel: [ 6986.287767] wlp3s0: authenticated
Feb 12 13:18:15 lakshmi NetworkManager[5361]: <info>  [1518412695.5886] device (wlp3s0): supplicant interface state: authenticating -> associating
Feb 12 13:18:15 lakshmi kernel: [ 6986.291905] wlp3s0: associate with 00:1c:c2:15:a6:31 (try 1/3)
Feb 12 13:18:15 lakshmi kernel: [ 6986.296934] wlp3s0: RX AssocResp from 00:1c:c2:15:a6:31 (capab=0x431 status=0 aid=1)
Feb 12 13:18:15 lakshmi kernel: [ 6986.298096] wlp3s0: associated
Feb 12 13:18:15 lakshmi NetworkManager[5361]: <info>  [1518412695.5990] device (wlp3s0): supplicant interface state: associating -> associated
Feb 12 13:18:15 lakshmi NetworkManager[5361]: <info>  [1518412695.6055] device (wlp3s0): supplicant interface state: associated -> 4-way handshake
Feb 12 13:18:15 lakshmi NetworkManager[5361]: <info>  [1518412695.6140] device (wlp3s0): supplicant interface state: 4-way handshake -> completed
Feb 12 13:18:15 lakshmi NetworkManager[5361]: <info>  [1518412695.6401] device (wifiether): link connected
Feb 12 13:18:15 lakshmi kernel: [ 6986.344209] wifiether: link status definitely up for interface wlp3s0, 0 Mbps full duplex
Feb 12 13:18:15 lakshmi kernel: [ 6986.344226] wifiether: making interface wlp3s0 the new active one
Feb 12 13:18:15 lakshmi kernel: [ 6986.344659] wifiether: first active interface up!
Könnte auch ein Treiber Problem sein.

Jana66
Beiträge: 3505
Registriert: 03.02.2016 12:41:11

Re: NetworkManager Bond wifi Ethernet

Beitrag von Jana66 » 12.02.2018 17:29:32

Mal mit bonding options (Tabelle 11) spielen (Zeiten, Modi)? https://developer.gnome.org/NetworkMana ... nmcli.html
Ansonsten systemd: viewtopic.php?f=30&t=168625&p=1164748#p1164498 Ist noch tiefer im System verankert als Gnomes NetworkManager. :wink:
Vielleicht solltest du vergleichsweise einen anderen WLAN-Adapter (anderer Hersteller, andere Frmware) probieren?

Insgesamt finde ich interessant, was du mit dem Netzwerkmanager "auf die Beine stellst". :THX:
(Obwohl ich Teaming/Bonding unter Nutzung von WLAN eher mit rein "akademischem Interesse" betrachte als praktisch sinnvoll wie standardisiertes LACP über mehrere Ethernetports. Okay, ein Accesspoint mit 2 Uplinks mag unter (wenigen) Umständen sinnvoll sein. Dann bitte ohne Netzwerkmanager. Das was du tust, wäre m. E. auch mit Bridging und Spanning Tree Protocol oder unterschiedlichen Metriken von (dynamischen) Routen möglich. Gut, Umschalten auf Backup-Verbindung könnte etwas länger dauern.)
Wenn keiner was sagt, wird sich nichts ändern. Wenn alle nur reden ebenfalls nicht.

Benutzeravatar
unitra
Beiträge: 348
Registriert: 15.06.2002 21:09:38
Lizenz eigener Beiträge: MIT Lizenz
Wohnort: Kölle

Re: NetworkManager Bond wifi Ethernet

Beitrag von unitra » 14.02.2018 15:42:52

Nicht alles was technisch möglich ist, ist auch sinnvoll. WLAN und Ethernet Schnittstellen "bonden". :facepalm: Mal ganz ehrlich, verschwende die Zeit nicht mit so Etwas.

Antworten