Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #226365

In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"

Show all headers | View raw

Hi folks,

I'm using Debian 10 (point release 5) and i've set up the bonding for
eth0 and eth1 in 'active-backup' mode, i'm using virtualbox VM for
testing it, if i disconnect cable (virtually from first ethernet -
eth0) ping to bond0 IP stops and if i disconnect it from eth1 and
reconnect on eth0 ping again start working. Do not really know what is
wrong!

Problem in [1] (searched mail archives) is same but no solution is
given there or user did not respond further on it, he/she might have
found the solution already, though there are some tests which i've
performed as mentioned in [1] and without bonding (dual network mode)
I can ping both IP from remote.
In this setup i'm using a D-Link 8 port switch to connect eth0 using
ethernet cable and eth1 is connected on wireless adapter of my laptop.

Does somebody know what may be wrong?

[2] bonding output:
user@myhost:~$ cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

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

Slave Interface: eth0
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 08:00:27:be:86:95
Slave queue ID: 0

Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 08:00:27:3a:6e:db
Slave queue ID: 0

[3] configuration : /etc/network/interfaces
user@myhost:~$ cat /etc/network/interfaces
# this file describes the network interfaces available on your system
# and how to activate them. for more information, see interfaces(5).

# the loopback network interface
auto lo
iface lo inet loopback

auto bond0
iface bond0 inet static
address 192.168.0.140
netmask 255.255.255.0
gateway 192.168.0.1
bond-slaves eth0 eth1
bond-mode active-backup
bond-miimon 100
bond-primary eth0
bond-downdelay 200
bond-updelay 200
post-up route add -net 224.0.0.0 netmask 240.0.0.0 dev bond0

Thank you.

Note : As soon as one interface cable is disconnected another
interface becomes active interfaces - this is visible.

Regards,

[1] https://lists.debian.org/debian-user/2012/01/msg01790.html
[2] bonding output
[3] network configuration under /etc/network/interfaces

Back to linux.debian.user | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

In network bonding second nic (eth1) is not pingable while first one  (eth0) is always pingable" Jaikumar Sharma <jaikumar.sharma@gmail.com> - 2020-08-21 17:20 +0200
  Re: In network bonding second nic (eth1) is not pingable while first  one (eth0) is always pingable" Dan Ritter <dsr@randomstring.org> - 2020-08-21 18:10 +0200
    Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable" deloptes <deloptes@gmail.com> - 2020-08-21 19:40 +0200
    Re: In network bonding second nic (eth1) is not pingable while first  one (eth0) is always pingable" Jaikumar Sharma <jaikumar.sharma@gmail.com> - 2020-08-22 07:50 +0200
      Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable" deloptes <deloptes@gmail.com> - 2020-08-22 09:50 +0200
    Re: In network bonding second nic (eth1) is not pingable while first  one (eth0) is always pingable" Jaikumar Sharma <jaikumar.sharma@gmail.com> - 2020-08-22 13:20 +0200
      Re: In network bonding second nic (eth1) is not pingable while first  one (eth0) is always pingable" Dan Ritter <dsr@randomstring.org> - 2020-08-22 13:50 +0200
        Re: In network bonding second nic (eth1) is not pingable while first  one (eth0) is always pingable" Lee <ler762@gmail.com> - 2020-08-22 14:30 +0200
          Re: In network bonding second nic (eth1) is not pingable while first  one (eth0) is always pingable" Dan Ritter <dsr@randomstring.org> - 2020-08-22 14:50 +0200
            Re: In network bonding second nic (eth1) is not pingable while first  one (eth0) is always pingable" Lee <ler762@gmail.com> - 2020-08-22 16:00 +0200
              Re: In network bonding second nic (eth1) is not pingable while first  one (eth0) is always pingable" Jaikumar Sharma <jaikumar.sharma@gmail.com> - 2020-08-22 17:10 +0200
        Re: In network bonding second nic (eth1) is not pingable while first  one (eth0) is always pingable" Jaikumar Sharma <jaikumar.sharma@gmail.com> - 2020-08-22 17:00 +0200
          Re: In network bonding second nic (eth1) is not pingable while first  one (eth0) is always pingable" Dan Ritter <dsr@randomstring.org> - 2020-08-22 18:10 +0200
            Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable" deloptes <deloptes@gmail.com> - 2020-08-23 21:20 +0200
              Re: In network bonding second nic (eth1) is not pingable while first  one (eth0) is always pingable" Jaikumar Sharma <jaikumar.sharma@gmail.com> - 2020-08-24 11:30 +0200
                Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable" deloptes <deloptes@gmail.com> - 2020-08-24 22:10 +0200
              Re: In network bonding second nic (eth1) is not pingable while first  one (eth0) is always pingable" Andy Smith <andy@strugglers.net> - 2020-08-24 13:20 +0200
            Re: In network bonding second nic (eth1) is not pingable while first  one (eth0) is always pingable" Jaikumar Sharma <jaikumar.sharma@gmail.com> - 2020-08-24 11:50 +0200

csiph-web