This page describes how to bond a computers copper and wifi interface. This (should) provide a seamless takeover from a clients (laptop/desktop) copper cable to a wifi cable and vice versa. This is especially usefull when running an ssh session to some other device.

If the ordinary setup is used, the copper connection and the wifi connection have a different

stop regular means of network configuration to prevent it from messing up things:

  • /etc/init.d/network-manager stop
  • /etc/init.d/networking stop

Start the bonding module. Chosen is mode '1' or “active-backup” modprobe bonding mode=1 max_bonds=2 miimon=100 primary=enp9s0

Associate the wifi card with the access point:

  • iwconfig wlp5s0 essid myessid key da_secret_key

make both copper (here enp9s0) and wifi(wlp5s0) slave of bond 0

  • ifenslave bond0 enp9s0 wlp5s0
  • dhclient bond0

Of cause, all this should land somewhere in the networking scripts.

  • cat /proc/net/bonding/bond0

shows the setup

  • Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
  • Bonding Mode: fault-tolerance (active-backup)
  • Primary Slave: None
  • Currently Active Slave: enp9s0
  • 'MII Status: up
  • 'MII Polling Interval (ms): 100
  • 'Up Delay (ms): 0
  • 'Down Delay (ms): 0
  • 'Slave Interface: enp9s0
  • 'MII Status: up
  • 'Speed: 100 Mbps
  • 'Duplex: full
  • 'Link Failure Count: 11
  • 'Permanent HW addr: 00:23:8b:xx:xx:xx
  • 'Slave queue ID: 0
  • Slave Interface: wlp5s0 * MII Status: down
  • Speed: Unknown * Duplex: Unknown
  • Link Failure Count: 10 * Permanent HW addr: 00:22:fa:xx:xx:xx
  • Slave queue ID: 0

More on bonding ethernet nic's can be found in linuxfoundation/bonding.

  • bond_copper_wifi.txt
  • Last modified: 2019/04/09 22:04
  • by gijs