From: Arne Fitzenreiter <arne_f@ipfire.org>
To: network@lists.ipfire.org
Subject: [network] [PATCH] Improve MTU handling on bridges
Date: Wed, 19 Oct 2016 20:28:22 +0000 [thread overview]
Message-ID: <1476908902-6833-1-git-send-email-arne_f@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 865 bytes --]
When the MTU of a bridge is changed, device_set_mtu will
now change the MTU of all ports in that bridge, too.
This does not seem to be 100% necessary, but it makes it
clearer and probably avoids some other bugs.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
---
src/functions/functions.device | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/src/functions/functions.device b/src/functions/functions.device
index 571b1fb..a261335 100644
--- a/src/functions/functions.device
+++ b/src/functions/functions.device
@@ -659,6 +659,14 @@ device_set_mtu() {
assert device_exists ${device}
+ # Handle bridges differently
+ if device_is_bridge ${device}; then
+ local port
+ for port in $(bridge_get_members ${device}); do
+ device_set_mtu ${port} ${mtu}
+ done
+ fi
+
log INFO "Setting MTU of ${device} to ${mtu}"
local up
--
2.6.3
reply other threads:[~2016-10-19 20:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1476908902-6833-1-git-send-email-arne_f@ipfire.org \
--to=arne_f@ipfire.org \
--cc=network@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox