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

Groups > linux.debian.user > #226412

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

Show all headers | View raw

Jaikumar Sharma wrote: 
> On Fri, Aug 21, 2020 at 9:30 PM Dan Ritter <dsr@randomstring.org> wrote:
> > You don't want a bond, you want a bridge.
> >
> > Bonding takes two interfaces that talk to the same switch on the
> > other side, and makes them into one bond nic. You need support
> > on the switch, too, which is unlikely in a D-Link 8-port unless
> > it has a management interface -- I think they don't bother under
> > 16 or 24 ports, and even then it's an extra-cost option.
> Just see this webpage on
> https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13/html/advanced_overcloud_customization/overcloud-network-interface-bonding
> it says :
> 
> bond_mode=active-backup
> 
> This mode offers active/standby failover where the standby NIC resumes
> network operations when the active connection fails. Only one MAC
> address is presented to the physical switch. This mode does not
> require any special switch support or configuration,and works when the
> links are connected to separate switches. This mode does not provide
> load balancing.
> 
> ** This mode does not require any special switch support or
> configuration -- stated in the above para.
> Now, with this is not really clear where the problem is?

You still want bridging, not bonding.

WiFi doesn't have a cable, so it can't tell you when the
connection goes away, and it can't decide by itself to bring up
a connection. You need a management program that will pick a
network from SSID, negotiate any necessary encryption, and do
all that with a MAC address that does not conflict with another
one on the network.

The bond driver itself can't do that. You might be able to get a
higher-order system to take care of it --
/etc/network/interfaces *may* be able to figure out a way,
Network Manager might handle this case -- but I'll bet you a
shiny nickel you will have reliability issues that are much
worse than just connecting it to the wired ethernet and leaving
it alone.

-dsr-

Back to linux.debian.user | Previous | Next — Previous in thread | 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