With the tap device up:
ip addr show dev tap0
4: tap0: mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
link/ether 9a:44:ad:1f:39:d9 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.1/24 scope global tap0
valid_lft forever preferred_lft forever
inet6 fe80::9844:adff:fe1f:39d9/64 scop
Understood.
I'll give it a try and let you know how I go.
Thanks.
On Sun, Aug 26, 2018, 00:20 hiro <23h...@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)
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 w
I thought that the mac address in the qemu command had to be the same as
the link/ether address of the tap device.
Should I make one up and use that in the qemu command?
Thanks.
On Sat, Aug 25, 2018, 22:49 hiro <23h...@gmail.com> wrote:
> the qemu error seems helpful: how did you chose mac=C6:1C
On Sat, 25 Aug 2018 22:17:16 +0300 Alexander Kapshuk
wrote:
> 22:13:25.356189 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has
> 10.0.0.2 tell 10.0.0.1, length 28
As Hiro mentioned it is strange that both sides have the same
mac addr as that will confuse them both. Pick a different one
for
the qemu error seems helpful: how did you chose mac=C6:1C:63:D9:91:1D
in the qemu command? i see no mention in the fqa that it should be the
same as the hypervisor's interface!
On 8/25/18, Alexander Kapshuk wrote:
> Thanks Hiro and Bakul for your prompt responses.
>
> Here's what I've got to repo
Thanks Hiro and Bakul for your prompt responses.
Here's what I've got to report...
I brought tap0 as user root:
ip link set dev tap0 up
ip addr show dev tap0
4: tap0: mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
link/ether c6:1c:63:d9:91:1d brd ff:ff:ff:ff:ff:ff
inet 10.0.
On Sat, 25 Aug 2018 14:20:44 +0300 Alexander Kapshuk
wrote:
> I am trying to follow the instructions given here:
>
> http://fqa.9front.org/fqa3.html#3.3.1.4.4
> 3.3.1.4.4 - Linux TAP
>
> Here's what I've done so far:
> (1). Set up a tap0 device as user root:
> ip tuntap add dev tap0 mode tap user
what is the output of (1) after you did (7)
i am counting the 2nd 1 is a 6 (obviously).
On 8/25/18, Alexander Kapshuk wrote:
> I am trying to follow the instructions given here:
>
> http://fqa.9front.org/fqa3.html#3.3.1.4.4
> 3.3.1.4.4 - Linux TAP
>
> Here's what I've done so far:
> (1). Set up a
I am trying to follow the instructions given here:
http://fqa.9front.org/fqa3.html#3.3.1.4.4
3.3.1.4.4 - Linux TAP
Here's what I've done so far:
(1). Set up a tap0 device as user root:
ip tuntap add dev tap0 mode tap user sasha
ip address add 10.0.0.1/24 dev tap0
ip addr show dev tap0
4: tap0:
Thanks. I'll give that a try.
On Fri, Jul 6, 2018 at 10:37 PM Skip Tavakkolian
wrote:
>
> You could use private network addresses (10.0.0.0/8, 172.16.0.0/12 or
> 192.168.0.0/16). Your /lib/ndb/local file can then be setup around a subnet
> like 192.168.9.0/24. According to the following, qemu
You could use private network addresses (10.0.0.0/8, 172.16.0.0/12 or
192.168.0.0/16). Your /lib/ndb/local file can then be setup around a subnet
like 192.168.9.0/24. According to the following, qemu uses 10.0.2.0/24
when using "user mode networking" and provides a virtual dhcp (10.0.2.2),
dns (1
I've installed Plan 9 in qemu on Linux as instructed here:
https://9p.io/wiki/plan9/Installing_Plan_9_on_Qemu/index.html
Now I'm in the process of converting it into a standalone cpu server.
I'm following the instructions given here:
https://9p.io/wiki/plan9/Configuring_a_Standalone_CPU_Server/ind
13 matches
Mail list logo
