Making eth1 a fallover/backup network connection


phoebus

Recommended Posts

Due to recent hardware network issues I'd like my eth1 (motherboard network) to serve as a backup to my main network connection eth0 (NIC) and can't seem to get it right.

 

I've assigned my Unraid a static IP locally to help with bookmarks etc. But when I disconnect the eth0 cable I can never connect. I've looked but can't seem to find the settings I need to change. Any advice welcome.

 

screencapture-chrome-extension-fdpohaocaechififmbbbbbknoalclacl-capture-html-2021-11-24-20_54_24.thumb.png.7c791da1b8eacc7bb3e022fa888ff21d.png

Edited by phoebus
Problem emerged
Link to comment
  • phoebus changed the title to Making eth1 a fallover/backup network connection

Okay so despite adding eth1 to bonding members eth0 I still have been losing my internet connection. I have also upgraded to the latest Unraid Beta.

 

I keep getting

 

Nov 25 22:16:03 Unraid kernel: r8169 0000:03:00.0 eth1: rtl_rxtx_empty_cond == 0 (loop: 42, delay: 100).
Nov 25 22:16:14 Unraid kernel: r8169 0000:03:00.0 eth1: rtl_txcfg_empty_cond == 0 (loop: 42, delay: 100).

 

r8169 is eth1 so I thought that if eth0 is fine it should be okay.

 

It always seems to happen around 9pm at night, I'd been using it all day. And when I reopen my laptop where I'm logged into my Unraid dashboard and/or the Windows VM running on it it tends to, but not always, fix itself.

 

The Intel NIC seemed to be okay but after an error I thought that bonding the flakey r8169 motherboard device to eth0 it would mean that if one fell out then the other would kick in and I'd have a stable connection.

 

Any thoughts?

 

unraid-diagnostics-20211125-2216.zip

Link to comment

Okay so the mystery deepens as now I am getting spammed by these messgaes several times per minute

 

Nov 26 18:05:35 Unraid kernel: bond0: (slave eth0): link status definitely up, 1000 Mbps full duplex
Nov 26 18:05:35 Unraid kernel: bond0: (slave eth0): making interface the new active one
Nov 26 18:05:35 Unraid kernel: device eth0 entered promiscuous mode
Nov 26 18:05:35 Unraid kernel: bond0: active interface up!
Nov 26 18:05:35 Unraid kernel: br0: port 1(bond0) entered blocking state
Nov 26 18:05:35 Unraid kernel: br0: port 1(bond0) entered forwarding state
Nov 26 18:06:07 Unraid kernel: e1000e 0000:05:00.0 eth0: Reset adapter unexpectedly
Nov 26 18:06:07 Unraid kernel: bond0: (slave eth0): link status definitely down, disabling slave
Nov 26 18:06:07 Unraid kernel: device eth0 left promiscuous mode
Nov 26 18:06:07 Unraid kernel: bond0: now running without any active interface!
Nov 26 18:06:07 Unraid kernel: br0: port 1(bond0) entered disabled state
Nov 26 18:06:11 Unraid kernel: e1000e 0000:05:00.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.