From: David Ahern <dsa@cumulusnetworks.com>
To: linmiaohe <linmiaohe@huawei.com>,
shrijeet@gmail.com, davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Mingfangsen <mingfangsen@huawei.com>
Subject: Re: [PATCH net v3] net: vrf: Fix ping failed when vrf mtu is set to 0
Date: Sun, 7 Apr 2019 20:51:05 -0700 [thread overview]
Message-ID: <22ff0d05-c1af-ad08-4cae-39dec91eff47@cumulusnetworks.com> (raw)
In-Reply-To: <b32ed160-6c7f-fb8e-aa14-11d935a1cb15@huawei.com>
On 4/7/19 7:04 PM, linmiaohe wrote:
> 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 IPV6_MIN_MTU, 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 ETH_MAX_MTU.
>
> 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>
> ---
Reviewed-by: David Ahern <dsahern@gmail.com>
next prev parent reply other threads:[~2019-04-08 3:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 2:04 linmiaohe
2019-04-08 3:51 ` David Ahern [this message]
2019-04-08 5:49 ` David Miller
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=22ff0d05-c1af-ad08-4cae-39dec91eff47@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=davem@davemloft.net \
--cc=linmiaohe@huawei.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®