From: David Ahern <dsahern@gmail.com>
To: Francesco Ruggeri <fruggeri@arista.com>
Cc: David Miller <davem@davemloft.net>,
shuah@kernel.org, netdev <netdev@vger.kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] selftest: net: add icmp reply address test
Date: Sat, 2 Nov 2019 11:38:25 -0600 [thread overview]
Message-ID: <06dd5c8e-7eeb-a00f-e437-11897fe01ad1@gmail.com> (raw)
In-Reply-To: <CA+HUmGgKakVpS8UsKWUwm9QdCf+T2Pi1wNS-Kr7NE+TQ8ABGaQ@mail.gmail.com>
On 11/2/19 10:09 AM, Francesco Ruggeri wrote:
> On Sat, Nov 2, 2019 at 8:11 AM David Ahern <dsahern@gmail.com> wrote:
>> On 11/2/19 9:08 AM, Francesco Ruggeri wrote:
>>> I am only using macvlans for N1 in the ipv6 test, where there are 3 nodes.
>>> How do I use veths for that?
>>
>> checkout the connect_ns function. It uses veth to connect ns1 to ns2.
>
> I apologize in advance for being slow ...
> I have 3 namespaces that have to share the same LAN, I am not trying
> 1-1 connections among those namespaces.
>
How would you cable this if it were an actual network with physical nodes?
- bridge on R1 (since it is the gw for H1), with connections to R2 and
H1 into the bridge
- second connection between R1 and R2
- connection between R2 and H2
For the simulation, network namespaces represent physical nodes, veth
pairs act like a cable between the nodes / namespaces and the bridge
makes the LAN.
next prev parent reply other threads:[~2019-11-02 17:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-01 23:34 [PATCH net-next 2/2] selftest: net: add icmp reply address test Francesco Ruggeri
2019-11-02 14:34 ` David Ahern
2019-11-02 15:08 ` Francesco Ruggeri
2019-11-02 15:11 ` David Ahern
2019-11-02 16:09 ` Francesco Ruggeri
2019-11-02 17:38 ` David Ahern [this message]
2019-11-02 18:08 ` Francesco Ruggeri
2019-11-02 22:08 ` Francesco Ruggeri
2019-11-03 16:52 ` David Ahern
2019-11-04 18:14 ` Francesco Ruggeri
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=06dd5c8e-7eeb-a00f-e437-11897fe01ad1@gmail.com \
--to=dsahern@gmail.com \
--cc=davem@davemloft.net \
--cc=fruggeri@arista.com \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shuah@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).