From: linmiaohe <linmiaohe@huawei.com>
To: David Ahern <dsa@cumulusnetworks.com>,
Shrijeet Mukherjee <shrijeet@gmail.com>, <davem@davemloft.net>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: Mingfangsen <mingfangsen@huawei.com>
Subject: [PATCH net v2] net: vrf: Fix ping failed when vrf mtu is set to 0
Date: Sun, 7 Apr 2019 14:46:26 +0800 [thread overview]
Message-ID: <c0ee938d-479d-5c92-93ce-e06c24057b62@huawei.com> (raw)
From: Miaohe Lin <linmiaohe@huawei.com>
When the mtu of a vrf device is set to 0, it would cause ping
failed. So I think we should limit vrf mtu in a reasonable range
to solve this problem. I set dev->min_mtu to 1280, so it will
works for both ipv4 and ipv6. And if dev->max_mtu still be 0
can be confusing, so I set dev->max_mtu to 0xFFFFU.
Here is the reproduce step:
1.Config vrf interface and set mtu to 0:
3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
master vrf1 state UP mode DEFAULT group default qlen 1000
link/ether 52:54:00:9e:dd:c1 brd ff:ff:ff:ff:ff:ff
2.Ping peer:
3: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel
master vrf1 state UP group default qlen 1000
link/ether 52:54:00:9e:dd:c1 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.1/16 scope global enp4s0
valid_lft forever preferred_lft forever
connect: Network is unreachable
3.Set mtu to default value, ping works:
PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
64 bytes from 10.0.0.2: icmp_seq=1 ttl=64 time=1.88 ms
Fixes: ad49bc6361ca2 ("net: vrf: remove MTU limits for vrf device")
Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
---
V1->V2:
- fix patch commit message
- adjust to work for ipv6
drivers/net/vrf.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/net/vrf.c b/drivers/net/vrf.c
index 7c1430ed0244..4d35d37f225a 100644
--- a/drivers/net/vrf.c
+++ b/drivers/net/vrf.c
@@ -43,6 +43,12 @@
#define FIB_RULE_PREF 1000 /* default preference for FIB rules */
+/* The MTU is really irrelevant for VRF except for odd cases, so limit it
+ * to a reasonable range which both works for IPV4 and IPV6.
+ */
+#define VRF_MIN_MTU 1280 /* same as IPV6_MIN_MTU */
+#define VRF_MAX_MTU 0xFFFFU /* same as IP_MAX_MTU */
+
static unsigned int vrf_net_id;
struct net_vrf {
@@ -1274,8 +1280,8 @@ static void vrf_setup(struct net_device *dev)
/* default to no qdisc; user can add if desired */
dev->priv_flags |= IFF_NO_QUEUE;
- dev->min_mtu = 0;
- dev->max_mtu = 0;
+ dev->min_mtu = VRF_MIN_MTU;
+ dev->max_mtu = VRF_MAX_MTU;
}
static int vrf_validate(struct nlattr *tb[], struct nlattr *data[],
--
2.19.1
next reply other threads:[~2019-04-07 6:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-07 6:46 linmiaohe [this message]
2019-04-07 14:30 ` David Ahern
2019-04-08 1:58 ` linmiaohe
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=c0ee938d-479d-5c92-93ce-e06c24057b62@huawei.com \
--to=linmiaohe@huawei.com \
--cc=davem@davemloft.net \
--cc=dsa@cumulusnetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingfangsen@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=shrijeet@gmail.com \
/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
all inboxes | Powered by JetHome®