From: David Ahern <dsa@cumulusnetworks.com>
To: "D'Souza, Nelson" <ndsouza@ciena.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [**EXTERNAL**] Re: VRF with enslaved L3 enabled bridge
Date: Mon, 23 Jul 2018 16:00:20 -0600 [thread overview]
Message-ID: <51e237af-2db6-8905-22c9-9739f7d5a9b0@cumulusnetworks.com> (raw)
In-Reply-To: <F8810C2E-7791-43B8-AB64-6FC843431FEA@ciena.com>
On 7/20/18 1:03 PM, D'Souza, Nelson wrote:
> Setup is as follows:
>
> ethUSB(ingress port) -> mgmtbr0 (bridge) -> mgmtvrf (vrf)
| netns foo
[ test-vrf ] |
| |
[ br0 ] 172.16.1.1 |
| |
[ veth1 ] ============|======= [ veth2 ] lo
| 172.16.1.2 172.16.2.2
|
Copy and paste the following into your environment:
ip netns add foo
ip li add veth1 type veth peer name veth2
ip li set veth2 netns foo
ip -netns foo li set lo up
ip -netns foo li set veth2 up
ip -netns foo addr add 172.16.1.2/24 dev veth2
ip li add test-vrf type vrf table 123
ip li set test-vrf up
ip ro add vrf test-vrf unreachable default
ip li add br0 type bridge
ip li set veth1 master br0
ip li set veth1 up
ip li set br0 up
ip addr add dev br0 172.16.1.1/24
ip li set br0 master test-vrf
ip -netns foo addr add 172.16.2.2/32 dev lo
ip ro add vrf test-vrf 172.16.2.2/32 via 172.16.1.2
Does ping work?
# ping -I test-vrf 172.16.2.2
ping: Warning: source address might be selected on device other than
test-vrf.
PING 172.16.2.2 (172.16.2.2) from 172.16.1.1 test-vrf: 56(84) bytes of data.
64 bytes from 172.16.2.2: icmp_seq=1 ttl=64 time=0.228 ms
64 bytes from 172.16.2.2: icmp_seq=2 ttl=64 time=0.263 ms
and:
# ping -I br0 172.16.2.2
PING 172.16.2.2 (172.16.2.2) from 172.16.1.1 br0: 56(84) bytes of data.
64 bytes from 172.16.2.2: icmp_seq=1 ttl=64 time=0.227 ms
64 bytes from 172.16.2.2: icmp_seq=2 ttl=64 time=0.223 ms
^C
--- 172.16.2.2 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.223/0.225/0.227/0.002 ms
next prev parent reply other threads:[~2018-07-23 23:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9E3A1F70-E009-49DC-B639-B48B28F99C52@ciena.com>
2018-07-20 3:37 ` VRF with enslaved L3 enabled bridge David Ahern
2018-07-20 19:03 ` [**EXTERNAL**] " D'Souza, Nelson
2018-07-20 19:11 ` David Ahern
2018-07-20 21:59 ` [**EXTERNAL**] " D'Souza, Nelson
2018-07-23 22:00 ` David Ahern [this message]
2018-07-24 1:43 ` D'Souza, Nelson
2018-07-24 12:54 ` David Ahern
2018-07-24 15:58 ` D'Souza, Nelson
2018-07-24 16:08 ` D'Souza, Nelson
2018-07-26 0:35 ` D'Souza, Nelson
2018-07-26 0:44 ` D'Souza, Nelson
2018-07-27 23:29 ` D'Souza, Nelson
2018-08-02 23:12 ` D'Souza, Nelson
2018-09-05 18:00 ` D'Souza, Nelson
2018-09-07 0:26 ` David Ahern
[not found] ` <BYAPR04MB3797F5219C2164F3C0B6DE57AD000@BYAPR04MB3797.namprd04.prod.outlook.com>
2018-09-07 16:09 ` David Ahern
2018-09-07 23:42 ` D'Souza, Nelson
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=51e237af-2db6-8905-22c9-9739f7d5a9b0@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=ndsouza@ciena.com \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).