From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <20180825182739.667A1156E400@mail.bitblocks.com> In-Reply-To: From: Alexander Kapshuk Date: Sun, 26 Aug 2018 07:56:57 +0300 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="000000000000b8595f05744f7026" Subject: Re: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux Topicbox-Message-UUID: de2ff7f4-ead9-11e9-9d60-3106f5b1d025 --000000000000b8595f05744f7026 Content-Type: text/plain; charset="UTF-8" Understood. I'll give it a try and let you know how I go. Thanks. On Sun, Aug 26, 2018, 00:20 hiro <23hiro@gmail.com> wrote: > nothing in the fqa mentions the tap device's mac address (which linux > generated randomly in order not to conflict with whatever you might be > using on the other side). > > look at the tap device as an ethernet interface that is plugged into > the same L2 switch as the VM's virtual interface. > > you don't want mac address collisions in one L2 network, so yes, use a > different one for the VM. > > --000000000000b8595f05744f7026 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Understood.
I'll give it a try and l= et you know how I go.
Thanks.


On Sun, Au= g 26, 2018, 00:20 hiro <23hiro@gmail= .com> wrote:
nothing in the = fqa mentions the tap device's mac address (which linux
generated randomly in order not to conflict with whatever you might be
using on the other side).

look at the tap device as an ethernet interface that is plugged into
the same L2 switch as the VM's virtual interface.

you don't want mac address collisions in one L2 network, so yes, use a<= br> different one for the VM.

--000000000000b8595f05744f7026--