From: Marco Gaiarin <gaio@sv.lnf.it>
To: lartc@vger.kernel.org
Subject: Re: Buferbloat, ethernet hardware parameters and LACP bonds...
Date: Sat, 27 Mar 2021 17:46:21 +0000 [thread overview]
Message-ID: <20210327174621.GA42768@lilliput.linux.it> (raw)
In-Reply-To: <20210224115935.GI3883@sv.lnf.it>
Mandi! Grant Taylor
In chel di` si favelave...
> > It is not possible to set hardware parameters in bond and/or in bond
> > members?!
> I don't know.
> Try running the appropriate commands against the interfaces and bypass
> system initialization scripts. -- My gut tells me that the system
> initialization scripts don't apply things properly (or at all) when it's a
> bond.
I come back on this, after i've had the time to setup a test system.
Doing some test lead me to an answer, and you are right.
Reading debian /usr/share/doc/ifenslave/README.Debian.gz:
Using ifup on a master interface will call ifup for all slaves that are
flagged with allow-bondX. (bondX being replaced by the master interface
name). This will allow for extra setup for special slave interfaces.
so effectively it is not sufficient to setup the bond in
/etc/network/interfaces with the list of enslaved interfaces, but you
have to add to enslaved interfaces stanza the 'allow-bondX' keyword,
so they are effectively run.
Sorry. And thanks.
--
dott. Marco Gaiarin GNUPG Key ID: 240A3D66
Associazione ``La Nostra Famiglia'' http://www.lanostrafamiglia.it/
Polo FVG - Via della Bontà, 7 - 33078 - San Vito al Tagliamento (PN)
marco.gaiarin(at)lanostrafamiglia.it t +39-0434-842711 f +39-0434-842797
Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
http://www.lanostrafamiglia.it/index.php/it/sostienici/5x1000
(cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)
prev parent reply other threads:[~2021-03-27 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 11:59 Buferbloat, ethernet hardware parameters and LACP bonds Marco Gaiarin
2021-02-24 16:47 ` Grant Taylor
2021-03-27 17:46 ` Marco Gaiarin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210327174621.GA42768@lilliput.linux.it \
--to=gaio@sv.lnf.it \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.