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

From	Jaikumar Sharma <jaikumar.sharma@gmail.com>
Newsgroups	linux.debian.user
Subject	Re: In network bonding second nic (eth1) is not pingable while first one (eth0) is always pingable"
Date	2020-08-22 17:00 +0200
Message-ID	<AGD9T-2tL-3@gated-at.bofh.it> (permalink)
References	<AGgZJ-6eH-9@gated-at.bofh.it> <AGhM5-6K3-1@gated-at.bofh.it> <AGzJ0-Au-7@gated-at.bofh.it> <AGAc1-JI-1@gated-at.bofh.it> <AGD9T-2tL-5@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Sat, Aug 22, 2020 at 5:10 PM Dan Ritter <dsr@randomstring.org> wrote:
> You still want bridging, not bonding.
Preferred is bonding, if it works :)
> 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.

 Have to test it with two wired connections connected to Cisco managed switch.

> 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.
Sure, will look into more detail into /etc/network/interfaces/

** earlier mail missed adding debian user list. sorry.

Thanks.

On Sat, Aug 22, 2020 at 8:20 PM Jaikumar Sharma
<jaikumar.sharma@gmail.com> wrote:
>
> On Sat, Aug 22, 2020 at 5:10 PM Dan Ritter <dsr@randomstring.org> wrote:
> > You still want bridging, not bonding.
> Preferred is bonding, if it works :)
> > 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.
>
>  Have to test it with two wired connections connected to Cisco managed switch.
>
> > 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.
> Sure, will look into more detail into /etc/network/interfaces/
>
> Thanks.

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