[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9c01855e-fc0b-4bad-8522-232b71617121@kernel.org>
Date: Sun, 21 Jan 2024 17:38:35 -0700
From: David Ahern <dsahern@...nel.org>
To: Ben Greear <greearb@...delatech.com>, netdev <netdev@...r.kernel.org>
Cc: David Ahern <dsahern@...il.com>
Subject: Re: Having trouble with VRF and ping link local ipv6 address.
On 1/21/24 5:29 PM, Ben Greear wrote:
> Hello,
>
> I am trying to test pinging link-local IPv6 addresses across a VETH
> pair, with each VETH
> in a VRF, but having no good luck.
This is covered by ipv6_ping_vrf in
tools/testing/selftests/net/fcnal-test.sh As I recall you can run just
those tests with `-t ping6` and see the commands with -v. -P will pause
after each test so you can see the setup and run the ping command manually.
>
> Anyone see what I might be doing wrong?
>
>
> [root@ ]# ip -6 addr show dev rddVR5
> 161: rddVR5@...VR4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> noqueue master _vrf15 state UP group default qlen 1000
> inet6 fe80::8088:c8ff:fe31:16ea/64 scope link
> valid_lft forever preferred_lft forever
>
> [root@ ]# ip -6 addr show dev rddVR4
> 160: rddVR4@...VR5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
> noqueue master _vrf14 state UP group default qlen 1000
> inet6 fe80::d064:9eff:fead:2156/64 scope link
> valid_lft forever preferred_lft forever
>
> [root@ ]# ip -6 route show table 15
> anycast fe80:: dev rddVR5 proto kernel metric 1024 pref medium
> local fe80::8088:c8ff:fe31:16ea dev rddVR5 proto kernel metric 0 pref
> medium
> fe80::/64 dev rddVR5 proto kernel metric 256 pref medium
> fe80::/64 dev rddVR5 metric 1024 pref medium
> ff00::/8 dev rddVR5 metric 256 pref medium
>
> [root@ ]# ip -6 route show table 14
> local fe80::d064:9eff:fead:2156 dev rddVR4 proto kernel metric 0 pref
> medium
> fe80::/64 dev rddVR4 proto kernel metric 256 pref medium
> multicast ff00::/8 dev rddVR4 proto kernel metric 256 pref medium
>
> [root@ ]# ip vrf exec _vrf15 ping -6 fe80::d064:9eff:fead:2156
LLAs are local to a device. Give it a device context (%<dev name> after
the address).
Powered by blists - more mailing lists