From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 From: Alexander Kapshuk Date: Fri, 6 Jul 2018 19:42:11 +0300 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux Topicbox-Message-UUID: d92eb56a-ead9-11e9-9d60-3106f5b1d025 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/index.html I would like to configure a static IP address for the cpu server, so I can drawterm into it from other machines on my home network. My knowledge of networking is limited. I understand that I need to put this: ip/ipconfig -g ether /net/ether0 into my /cfg/$sysname/cpurc. What I don't understand, and am asking for assistance with, is where those three ip addresses in the example above have to come from. Do I add them to the ethernet interface on the host system, or is there a way to do this from within the Plan 9 system? Thanks. Alexander Kapshuk. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: Skip Tavakkolian Date: Fri, 6 Jul 2018 12:25:01 -0700 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="0000000000008925110570599f3b" Subject: Re: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux Topicbox-Message-UUID: d932c70e-ead9-11e9-9d60-3106f5b1d025 --0000000000008925110570599f3b Content-Type: text/plain; charset="UTF-8" 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 (10.0.2.3) and cifs (10.0.2.4). Using "tap" mode, you get to pick the subnet in qemu-ifup script. https://en.wikibooks.org/wiki/QEMU/Networking On Fri, Jul 6, 2018 at 9:43 AM Alexander Kapshuk < alexander.kapshuk@gmail.com> wrote: > 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/index.html > > I would like to configure a static IP address for the cpu server, so I > can drawterm into it from other machines on my home network. > My knowledge of networking is limited. I understand that I need to put > this: > ip/ipconfig -g ether /net/ether0 > > into my /cfg/$sysname/cpurc. > > What I don't understand, and am asking for assistance with, is where > those three ip addresses in the example above have to come from. Do I > add them to the ethernet interface on the host system, or is there a > way to do this from within the Plan 9 system? > > Thanks. > Alexander Kapshuk. > > --0000000000008925110570599f3b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
You could use private network addresses (10.0.0.0/8,=C2=A0 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.=C2=A0 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 (10.0.2.3= ) and cifs (10.0.2.4).=C2=A0 Using "tap" mode, you get to pick th= e subnet in qemu-ifup script.



On Fri, Jul 6, 2018 at 9:43 AM Alexander Kapshuk <alexander.kapshuk@gmail.com> wrot= e:
I've installed Plan 9 in qem= u on Linux as instructed here:
https://9p.io/wiki/plan9/Installing_Pla= n_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/Conf= iguring_a_Standalone_CPU_Server/index.html

I would like to configure a static IP address for the cpu server, so I
can drawterm into it from other machines on my home network.
My knowledge of networking is limited. I understand that I need to put this= :
ip/ipconfig -g <gateway-addr> ether /net/ether0 <ip-addr> <i= p-mask>

into my /cfg/$sysname/cpurc.

What I don't understand, and am asking for assistance with, is where those three ip addresses in the example above have to come from. Do I
add them to the ethernet interface on the host system, or is there a
way to do this from within the Plan 9 system?

Thanks.
Alexander Kapshuk.

--0000000000008925110570599f3b-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: Alexander Kapshuk Date: Sat, 7 Jul 2018 17:33:14 +0300 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux Topicbox-Message-UUID: d942200a-ead9-11e9-9d60-3106f5b1d025 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 19= 2.168.0.0/16). Your /lib/ndb/local file can then be setup around a subnet l= ike 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 (= 10.0.2.3) and cifs (10.0.2.4). Using "tap" mode, you get to pick the subne= t in qemu-ifup script. > > https://en.wikibooks.org/wiki/QEMU/Networking > > > On Fri, Jul 6, 2018 at 9:43 AM Alexander Kapshuk wrote: >> >> 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/index.html >> >> I would like to configure a static IP address for the cpu server, so I >> can drawterm into it from other machines on my home network. >> My knowledge of networking is limited. I understand that I need to put t= his: >> ip/ipconfig -g ether /net/ether0 >> >> into my /cfg/$sysname/cpurc. >> >> What I don't understand, and am asking for assistance with, is where >> those three ip addresses in the example above have to come from. Do I >> add them to the ethernet interface on the host system, or is there a >> way to do this from within the Plan 9 system? >> >> Thanks. >> Alexander Kapshuk. >> From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: In-Reply-To: From: Alexander Kapshuk Date: Sat, 25 Aug 2018 14:20:44 +0300 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux Topicbox-Message-UUID: dcbd27b6-ead9-11e9-9d60-3106f5b1d025 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: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether c6:1c:63:d9:91:1d brd ff:ff:ff:ff:ff:ff inet 10.0.0.1/24 scope global tap0 valid_lft forever preferred_lft forever (2). Started qemu with Bell Labs system image as a regular user like so: qemu-system-x86_64 \ -boot order=3Dd \ -drive file=3D$HOME/Plan9.raw.img,format=3Draw \ -netdev tap,id=3Deth,ifname=3Dtap0,script=3Dno,downscript=3Dno \ -device e1000,netdev=3Deth,mac=3DC6:1C:63:D9:91:1D (3). Put these details into /lib/ndb/local: sys=3Dgnot ether=3Dc61c63d9911d ip=3D10.0.0.2 ipmask=3D255.255.255.0 ipgw= =3D10.0.0.1 dns=3D10.0.0.1 dom=3Dgnot.plan9 (4). And these into /cfg/gnot/termrc ip/ipconfig -g 10.0.0.1 ether /net/ether0 10.0.0.2 255.255.255.0 (5). And rebooted the system. Current state of things: (1). MAC address is recognised: cat /net/ether0/addr c61c63d9911d (2). Still no networking. ping'ing 10.0.0.2 from my Linux host results in all packets being dropped. ip/ping 10.0.0.1 from qemu plan9 sees all packates dropped also. I understand that it is something I am not doing right because of my lack of networking knowledge. In all likelyhood, the answer was given by Skip in his reply to my original email. The 9front wiki article probably too has all the information needed to setup networking in qemu. I am probably just not seeing it. A further tip(s) would be much appreciated. This list's patience for my ignorance is much appreciated. On Sat, Jul 7, 2018 at 5:33 PM Alexander Kapshuk wrote: > > 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 uses 10.0.2.0/24 wh= en using "user mode networking" and provides a virtual dhcp (10.0.2.2), dns= (10.0.2.3) and cifs (10.0.2.4). Using "tap" mode, you get to pick the sub= net in qemu-ifup script. > > > > https://en.wikibooks.org/wiki/QEMU/Networking > > > > > > On Fri, Jul 6, 2018 at 9:43 AM Alexander Kapshuk wrote: > >> > >> 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/index.htm= l > >> > >> I would like to configure a static IP address for the cpu server, so I > >> can drawterm into it from other machines on my home network. > >> My knowledge of networking is limited. I understand that I need to put= this: > >> ip/ipconfig -g ether /net/ether0 > >> > >> into my /cfg/$sysname/cpurc. > >> > >> What I don't understand, and am asking for assistance with, is where > >> those three ip addresses in the example above have to come from. Do I > >> add them to the ethernet interface on the host system, or is there a > >> way to do this from within the Plan 9 system? > >> > >> Thanks. > >> Alexander Kapshuk. > >> From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: hiro <23hiro@gmail.com> Date: Sat, 25 Aug 2018 19:53:31 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux Topicbox-Message-UUID: dd526dc6-ead9-11e9-9d60-3106f5b1d025 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 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: mtu 1500 qdisc noop state DOWN group > default qlen 1000 > link/ether c6:1c:63:d9:91:1d brd ff:ff:ff:ff:ff:ff > inet 10.0.0.1/24 scope global tap0 > valid_lft forever preferred_lft forever > > (2). Started qemu with Bell Labs system image as a regular user like so: > qemu-system-x86_64 \ > -boot order=d \ > -drive file=$HOME/Plan9.raw.img,format=raw \ > -netdev tap,id=eth,ifname=tap0,script=no,downscript=no \ > -device e1000,netdev=eth,mac=C6:1C:63:D9:91:1D > > (3). Put these details into /lib/ndb/local: > sys=gnot ether=c61c63d9911d ip=10.0.0.2 ipmask=255.255.255.0 ipgw=10.0.0.1 > dns=10.0.0.1 > dom=gnot.plan9 > > (4). And these into /cfg/gnot/termrc > ip/ipconfig -g 10.0.0.1 ether /net/ether0 10.0.0.2 255.255.255.0 > > (5). And rebooted the system. > > Current state of things: > (1). MAC address is recognised: > cat /net/ether0/addr > c61c63d9911d > > (2). Still no networking. > ping'ing 10.0.0.2 from my Linux host results in all packets being dropped. > ip/ping 10.0.0.1 from qemu plan9 sees all packates dropped also. > > I understand that it is something I am not doing right because of my > lack of networking knowledge. In all likelyhood, the answer was given > by Skip in his reply to my original email. > The 9front wiki article probably too has all the information needed to > setup networking in qemu. > I am probably just not seeing it. > > A further tip(s) would be much appreciated. > This list's patience for my ignorance is much appreciated. > > On Sat, Jul 7, 2018 at 5:33 PM Alexander Kapshuk > wrote: >> >> 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 uses >> > 10.0.2.0/24 when using "user mode networking" and provides a virtual >> > dhcp (10.0.2.2), dns (10.0.2.3) and cifs (10.0.2.4). Using "tap" mode, >> > you get to pick the subnet in qemu-ifup script. >> > >> > https://en.wikibooks.org/wiki/QEMU/Networking >> > >> > >> > On Fri, Jul 6, 2018 at 9:43 AM Alexander Kapshuk >> > wrote: >> >> >> >> 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/index.html >> >> >> >> I would like to configure a static IP address for the cpu server, so I >> >> can drawterm into it from other machines on my home network. >> >> My knowledge of networking is limited. I understand that I need to put >> >> this: >> >> ip/ipconfig -g ether /net/ether0 >> >> >> >> into my /cfg/$sysname/cpurc. >> >> >> >> What I don't understand, and am asking for assistance with, is where >> >> those three ip addresses in the example above have to come from. Do I >> >> add them to the ethernet interface on the host system, or is there a >> >> way to do this from within the Plan 9 system? >> >> >> >> Thanks. >> >> Alexander Kapshuk. >> >> > > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bakul Shah To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-reply-to: Your message of "Sat, 25 Aug 2018 14:20:44 +0300." References: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19337.1535221652.1@bitblocks.com> Content-Transfer-Encoding: quoted-printable Date: Sat, 25 Aug 2018 11:27:32 -0700 Message-Id: <20180825182739.667A1156E400@mail.bitblocks.com> Subject: Re: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux Topicbox-Message-UUID: ddb02aa6-ead9-11e9-9d60-3106f5b1d025 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 sasha > ip address add 10.0.0.1/24 dev tap0 > > ip addr show dev tap0 > 4: tap0: mtu 1500 qdisc noop state DOWN group > default qlen 1000 > link/ether c6:1c:63:d9:91:1d brd ff:ff:ff:ff:ff:ff > inet 10.0.0.1/24 scope global tap0 > valid_lft forever preferred_lft forever I see that tap0 state is DOWN. Try bringing it up. = If that still doesn't work, run = tcpdump -ni tap0 and tell us what you discover. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 References: <20180825182739.667A1156E400@mail.bitblocks.com> In-Reply-To: <20180825182739.667A1156E400@mail.bitblocks.com> From: Alexander Kapshuk Date: Sat, 25 Aug 2018 22:17:16 +0300 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux Topicbox-Message-UUID: dddca996-ead9-11e9-9d60-3106f5b1d025 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.0.1/24 scope global tap0 valid_lft forever preferred_lft forever inet6 fe80::c41c:63ff:fed9:911d/64 scope link valid_lft forever preferred_lft forever ping -c4 10.0.0.2 PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. >>From 10.0.0.1 icmp_seq=1 Destination Host Unreachable >>From 10.0.0.1 icmp_seq=2 Destination Host Unreachable >>From 10.0.0.1 icmp_seq=3 Destination Host Unreachable >>From 10.0.0.1 icmp_seq=4 Destination Host Unreachable --- 10.0.0.2 ping statistics --- 4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 75ms pipe 4 # In qemu I got this output: arpreq: 10.0.0.1 also has ether address c61c63d9911d # Tcpdump output on Linux host: tcpdump -nS -vv -i tap0 tcpdump: listening on tap0, link-type EN10MB (Ethernet), capture size 262144 bytes 22:12:40.302180 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 16) fe80::c41c:63ff:fed9:911d > ff02::2: [icmp6 sum ok] ICMP6, router solicitation, length 16 source link-address option (1), length 8 (1): c6:1c:63:d9:91:1d 0x0000: c61c 63d9 911d 22:12:47.874535 IP (tos 0x0, ttl 1, id 18152, offset 0, flags [DF], proto UDP (17), length 195) 10.0.0.1.49968 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 22:12:48.875587 IP (tos 0x0, ttl 1, id 18675, offset 0, flags [DF], proto UDP (17), length 195) 10.0.0.1.49968 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 22:12:49.875963 IP (tos 0x0, ttl 1, id 19386, offset 0, flags [DF], proto UDP (17), length 195) 10.0.0.1.49968 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 22:12:50.876052 IP (tos 0x0, ttl 1, id 20194, offset 0, flags [DF], proto UDP (17), length 195) 10.0.0.1.49968 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 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 22:13:26.382153 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.0.0.2 tell 10.0.0.1, length 28 22:13:27.406149 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.0.0.2 tell 10.0.0.1, length 28 22:13:28.430247 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.0.0.2 tell 10.0.0.1, length 28 22:13:29.454154 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.0.0.2 tell 10.0.0.1, length 28 22:13:30.478150 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.0.0.2 tell 10.0.0.1, length 28 Thanks. On Sat, Aug 25, 2018 at 9:29 PM Bakul Shah wrote: > > 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 sasha > > ip address add 10.0.0.1/24 dev tap0 > > > > ip addr show dev tap0 > > 4: tap0: mtu 1500 qdisc noop state DOWN group > > default qlen 1000 > > link/ether c6:1c:63:d9:91:1d brd ff:ff:ff:ff:ff:ff > > inet 10.0.0.1/24 scope global tap0 > > valid_lft forever preferred_lft forever > > I see that tap0 state is DOWN. Try bringing it up. > If that still doesn't work, run > tcpdump -ni tap0 > and tell us what you discover. > From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <20180825182739.667A1156E400@mail.bitblocks.com> From: hiro <23hiro@gmail.com> Date: Sat, 25 Aug 2018 21:28:37 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux Topicbox-Message-UUID: ddf4d8fe-ead9-11e9-9d60-3106f5b1d025 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 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.0.1/24 scope global tap0 > valid_lft forever preferred_lft forever > inet6 fe80::c41c:63ff:fed9:911d/64 scope link > valid_lft forever preferred_lft forever > > ping -c4 10.0.0.2 > PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. > From 10.0.0.1 icmp_seq=1 Destination Host Unreachable > From 10.0.0.1 icmp_seq=2 Destination Host Unreachable > From 10.0.0.1 icmp_seq=3 Destination Host Unreachable > From 10.0.0.1 icmp_seq=4 Destination Host Unreachable > > --- 10.0.0.2 ping statistics --- > 4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 75ms > pipe 4 > > # In qemu I got this output: > arpreq: 10.0.0.1 also has ether address c61c63d9911d > > # Tcpdump output on Linux host: > tcpdump -nS -vv -i tap0 > tcpdump: listening on tap0, link-type EN10MB (Ethernet), capture size > 262144 bytes > 22:12:40.302180 IP6 (hlim 255, next-header ICMPv6 (58) payload length: > 16) fe80::c41c:63ff:fed9:911d > ff02::2: [icmp6 sum ok] ICMP6, router > solicitation, length 16 > source link-address option (1), length 8 (1): c6:1c:63:d9:91:1d > 0x0000: c61c 63d9 911d > 22:12:47.874535 IP (tos 0x0, ttl 1, id 18152, offset 0, flags [DF], > proto UDP (17), length 195) > 10.0.0.1.49968 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 > 22:12:48.875587 IP (tos 0x0, ttl 1, id 18675, offset 0, flags [DF], > proto UDP (17), length 195) > 10.0.0.1.49968 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 > 22:12:49.875963 IP (tos 0x0, ttl 1, id 19386, offset 0, flags [DF], > proto UDP (17), length 195) > 10.0.0.1.49968 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 > 22:12:50.876052 IP (tos 0x0, ttl 1, id 20194, offset 0, flags [DF], > proto UDP (17), length 195) > 10.0.0.1.49968 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 > 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 > 22:13:26.382153 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > 10.0.0.2 tell 10.0.0.1, length 28 > 22:13:27.406149 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > 10.0.0.2 tell 10.0.0.1, length 28 > 22:13:28.430247 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > 10.0.0.2 tell 10.0.0.1, length 28 > 22:13:29.454154 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > 10.0.0.2 tell 10.0.0.1, length 28 > 22:13:30.478150 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > 10.0.0.2 tell 10.0.0.1, length 28 > > Thanks. > On Sat, Aug 25, 2018 at 9:29 PM Bakul Shah wrote: >> >> 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 sasha >> > ip address add 10.0.0.1/24 dev tap0 >> > >> > ip addr show dev tap0 >> > 4: tap0: mtu 1500 qdisc noop state DOWN group >> > default qlen 1000 >> > link/ether c6:1c:63:d9:91:1d brd ff:ff:ff:ff:ff:ff >> > inet 10.0.0.1/24 scope global tap0 >> > valid_lft forever preferred_lft forever >> >> I see that tap0 state is DOWN. Try bringing it up. >> If that still doesn't work, run >> tcpdump -ni tap0 >> and tell us what you discover. >> > > From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bakul Shah To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-reply-to: Your message of "Sat, 25 Aug 2018 22:17:16 +0300." References: <20180825182739.667A1156E400@mail.bitblocks.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <19992.1535226165.1@bitblocks.com> Content-Transfer-Encoding: quoted-printable Date: Sat, 25 Aug 2018 12:42:45 -0700 Message-Id: <20180825194252.46149156E400@mail.bitblocks.com> Subject: Re: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux Topicbox-Message-UUID: de04e618-ead9-11e9-9d60-3106f5b1d025 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 VM. If that doesn't work, as an experiment try adding a static arp. sudo arp -s 10.0.0.2 tcpdump right from the start would be useful. 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: Sat, 25 Aug 2018 23:05:03 +0300 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary="0000000000008c1b5d057448028d" Subject: Re: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux Topicbox-Message-UUID: de13ff0e-ead9-11e9-9d60-3106f5b1d025 --0000000000008c1b5d057448028d Content-Type: text/plain; charset="UTF-8" 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 <23hiro@gmail.com> wrote: > 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 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.0.1/24 scope global tap0 > > valid_lft forever preferred_lft forever > > inet6 fe80::c41c:63ff:fed9:911d/64 scope link > > valid_lft forever preferred_lft forever > > > > ping -c4 10.0.0.2 > > PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data. > > From 10.0.0.1 icmp_seq=1 Destination Host Unreachable > > From 10.0.0.1 icmp_seq=2 Destination Host Unreachable > > From 10.0.0.1 icmp_seq=3 Destination Host Unreachable > > From 10.0.0.1 icmp_seq=4 Destination Host Unreachable > > > > --- 10.0.0.2 ping statistics --- > > 4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 75ms > > pipe 4 > > > > # In qemu I got this output: > > arpreq: 10.0.0.1 also has ether address c61c63d9911d > > > > # Tcpdump output on Linux host: > > tcpdump -nS -vv -i tap0 > > tcpdump: listening on tap0, link-type EN10MB (Ethernet), capture size > > 262144 bytes > > 22:12:40.302180 IP6 (hlim 255, next-header ICMPv6 (58) payload length: > > 16) fe80::c41c:63ff:fed9:911d > ff02::2: [icmp6 sum ok] ICMP6, router > > solicitation, length 16 > > source link-address option (1), length 8 (1): c6:1c:63:d9:91:1d > > 0x0000: c61c 63d9 911d > > 22:12:47.874535 IP (tos 0x0, ttl 1, id 18152, offset 0, flags [DF], > > proto UDP (17), length 195) > > 10.0.0.1.49968 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 > > 22:12:48.875587 IP (tos 0x0, ttl 1, id 18675, offset 0, flags [DF], > > proto UDP (17), length 195) > > 10.0.0.1.49968 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 > > 22:12:49.875963 IP (tos 0x0, ttl 1, id 19386, offset 0, flags [DF], > > proto UDP (17), length 195) > > 10.0.0.1.49968 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 > > 22:12:50.876052 IP (tos 0x0, ttl 1, id 20194, offset 0, flags [DF], > > proto UDP (17), length 195) > > 10.0.0.1.49968 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 > > 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 > > 22:13:26.382153 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > > 10.0.0.2 tell 10.0.0.1, length 28 > > 22:13:27.406149 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > > 10.0.0.2 tell 10.0.0.1, length 28 > > 22:13:28.430247 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > > 10.0.0.2 tell 10.0.0.1, length 28 > > 22:13:29.454154 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > > 10.0.0.2 tell 10.0.0.1, length 28 > > 22:13:30.478150 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > > 10.0.0.2 tell 10.0.0.1, length 28 > > > > Thanks. > > On Sat, Aug 25, 2018 at 9:29 PM Bakul Shah wrote: > >> > >> 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 sasha > >> > ip address add 10.0.0.1/24 dev tap0 > >> > > >> > ip addr show dev tap0 > >> > 4: tap0: mtu 1500 qdisc noop state DOWN group > >> > default qlen 1000 > >> > link/ether c6:1c:63:d9:91:1d brd ff:ff:ff:ff:ff:ff > >> > inet 10.0.0.1/24 scope global tap0 > >> > valid_lft forever preferred_lft forever > >> > >> I see that tap0 state is DOWN. Try bringing it up. > >> If that still doesn't work, run > >> tcpdump -ni tap0 > >> and tell us what you discover. > >> > > > > > > --0000000000008c1b5d057448028d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I thought that the mac address in the qemu command h= ad 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 <23hiro@gmail.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">the qemu error seems helpful: how did you cho= se mac=3DC6: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 <alexander.kapshuk@gmail.com&= gt; wrote:
> 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: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_= fast
> state UP group default qlen 1000
>=C2=A0 =C2=A0 =C2=A0link/ether c6:1c:63:d9:91:1d brd ff:ff:ff:ff:ff:ff<= br> >=C2=A0 =C2=A0 =C2=A0inet 10.0.0.1/24 scope global tap0
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_lft forever
>=C2=A0 =C2=A0 =C2=A0inet6 fe80::c41c:63ff:fed9:911d/64 scope link
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_lft forever
>
> ping -c4 10.0.0.2
> PING 10.0.0.2 (10.0.0.2) 56(84) bytes of data.
> From 10.0.0.1 icmp_seq=3D1 Destination Host Unreachable
> From 10.0.0.1 icmp_seq=3D2 Destination Host Unreachable
> From 10.0.0.1 icmp_seq=3D3 Destination Host Unreachable
> From 10.0.0.1 icmp_seq=3D4 Destination Host Unreachable
>
> --- 10.0.0.2 ping statistics ---
> 4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 7= 5ms
> pipe 4
>
> # In qemu I got this output:
> arpreq: 10.0.0.1 also has ether address c61c63d9911d
>
> # Tcpdump output on Linux host:
> tcpdump -nS -vv -i tap0
> tcpdump: listening on tap0, link-type EN10MB (Ethernet), capture size<= br> > 262144 bytes
> 22:12:40.302180 IP6 (hlim 255, next-header ICMPv6 (58) payload length:=
> 16) fe80::c41c:63ff:fed9:911d > ff02::2: [icmp6 sum ok] ICMP6, rout= er
> solicitation, length 16
>=C2=A0 =C2=A0source link-address option (1), length 8 (1): c6:1c:63:d9:= 91:1d
>=C2=A0 =C2=A0 =C2=A00x0000:=C2=A0 c61c 63d9 911d
> 22:12:47.874535 IP (tos 0x0, ttl 1, id 18152, offset 0, flags [DF], > proto UDP (17), length 195)
>=C2=A0 =C2=A0 =C2=A010.0.0.1.49968 > 239.255.255.250.1900: [udp sum = ok] UDP, length 167
> 22:12:48.875587 IP (tos 0x0, ttl 1, id 18675, offset 0, flags [DF], > proto UDP (17), length 195)
>=C2=A0 =C2=A0 =C2=A010.0.0.1.49968 > 239.255.255.250.1900: [udp sum = ok] UDP, length 167
> 22:12:49.875963 IP (tos 0x0, ttl 1, id 19386, offset 0, flags [DF], > proto UDP (17), length 195)
>=C2=A0 =C2=A0 =C2=A010.0.0.1.49968 > 239.255.255.250.1900: [udp sum = ok] UDP, length 167
> 22:12:50.876052 IP (tos 0x0, ttl 1, id 20194, offset 0, flags [DF], > proto UDP (17), length 195)
>=C2=A0 =C2=A0 =C2=A010.0.0.1.49968 > 239.255.255.250.1900: [udp sum = ok] UDP, length 167
> 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
> 22:13:26.382153 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > 10.0.0.2 tell 10.0.0.1, length 28
> 22:13:27.406149 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > 10.0.0.2 tell 10.0.0.1, length 28
> 22:13:28.430247 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > 10.0.0.2 tell 10.0.0.1, length 28
> 22:13:29.454154 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > 10.0.0.2 tell 10.0.0.1, length 28
> 22:13:30.478150 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has > 10.0.0.2 tell 10.0.0.1, length 28
>
> Thanks.
> On Sat, Aug 25, 2018 at 9:29 PM Bakul Shah <bakul@bitblocks.com> wrote:
>>
>> On Sat, 25 Aug 2018 14:20:44 +0300 Alexander Kapshuk
>> <alexander.kapshuk@gmail.com> 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 sasha
>> > ip address add 10.0.0.1/24 dev tap0
>> >
>> > ip addr show dev tap0
>> > 4: tap0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop stat= e DOWN group
>> > default qlen 1000
>> >=C2=A0 =C2=A0 =C2=A0link/ether c6:1c:63:d9:91:1d brd ff:ff:ff:= ff:ff:ff
>> >=C2=A0 =C2=A0 =C2=A0inet 10.0.0.1/24 scope global tap0=
>> >=C2=A0 =C2=A0 =C2=A0 =C2=A0 valid_lft forever preferred_lft fo= rever
>>
>> I see that tap0 state is DOWN. Try bringing it up.
>> If that still doesn't work, run
>>=C2=A0 =C2=A0 =C2=A0tcpdump -ni tap0
>> and tell us what you discover.
>>
>
>

--0000000000008c1b5d057448028d-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <20180825182739.667A1156E400@mail.bitblocks.com> From: hiro <23hiro@gmail.com> Date: Sat, 25 Aug 2018 22:59:44 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux Topicbox-Message-UUID: de20ef8e-ead9-11e9-9d60-3106f5b1d025 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. 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-- 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 16:45:55 +0300 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset="UTF-8" Subject: Re: [9fans] Static ip configuration for a standalone cpu server in qemu on Linux Topicbox-Message-UUID: de3ce73e-ead9-11e9-9d60-3106f5b1d025 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 scope link valid_lft forever preferred_lft forever And the qemu command using the mac address given in the fqa example: qemu-system-x86_64 \ -boot order=d \ -drive file=$HOME/Plan9.raw.img,format=raw \ -netdev tap,id=eth,ifname=tap0,script=no,downscript=no \ -device e1000,netdev=eth,mac=52:54:00:00:EE:03 And the ether= attribute removed from /lib/ndb/local, Both pings below work now. ping 10.0.0.2 # Linux ip/ping 10.0.0.1 # Plan 9 tcpdump -nS -vv -i tap0 tcpdump: listening on tap0, link-type EN10MB (Ethernet), capture size 262144 bytes 16:35:00.265147 IP (tos 0x0, ttl 1, id 46876, offset 0, flags [DF], proto UDP (17), length 195) 10.0.0.1.48952 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 16:35:01.266364 IP (tos 0x0, ttl 1, id 47164, offset 0, flags [DF], proto UDP (17), length 195) 10.0.0.1.48952 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 16:35:02.266828 IP (tos 0x0, ttl 1, id 47770, offset 0, flags [DF], proto UDP (17), length 195) 10.0.0.1.48952 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 16:35:03.267406 IP (tos 0x0, ttl 1, id 48737, offset 0, flags [DF], proto UDP (17), length 195) 10.0.0.1.48952 > 239.255.255.250.1900: [udp sum ok] UDP, length 167 16:35:28.213321 IP (tos 0x0, ttl 255, id 5, offset 0, flags [none], proto ICMP (1), length 64) 10.0.0.2 > 10.0.0.1: ICMP echo request, id 46534, seq 24833, length 44 16:35:28.213374 IP (tos 0x0, ttl 64, id 2728, offset 0, flags [none], proto ICMP (1), length 64) 10.0.0.1 > 10.0.0.2: ICMP echo reply, id 46534, seq 24833, length 44 16:35:29.212816 IP (tos 0x0, ttl 255, id 6, offset 0, flags [none], proto ICMP (1), length 64) 10.0.0.2 > 10.0.0.1: ICMP echo request, id 46534, seq 24834, length 44 16:35:29.212873 IP (tos 0x0, ttl 64, id 2867, offset 0, flags [none], proto ICMP (1), length 64) 10.0.0.1 > 10.0.0.2: ICMP echo reply, id 46534, seq 24834, length 44 16:35:30.223989 IP (tos 0x0, ttl 255, id 7, offset 0, flags [none], proto ICMP (1), length 64) 10.0.0.2 > 10.0.0.1: ICMP echo request, id 46534, seq 24835, length 44 16:35:30.224042 IP (tos 0x0, ttl 64, id 2906, offset 0, flags [none], proto ICMP (1), length 64) 10.0.0.1 > 10.0.0.2: ICMP echo reply, id 46534, seq 24835, length 44 16:35:31.223030 IP (tos 0x0, ttl 255, id 8, offset 0, flags [none], proto ICMP (1), length 64) 10.0.0.2 > 10.0.0.1: ICMP echo request, id 46534, seq 24836, length 44 16:35:31.223086 IP (tos 0x0, ttl 64, id 3895, offset 0, flags [none], proto ICMP (1), length 64) 10.0.0.1 > 10.0.0.2: ICMP echo reply, id 46534, seq 24836, length 44 16:35:32.222034 IP (tos 0x0, ttl 255, id 9, offset 0, flags [none], proto ICMP (1), length 64) 10.0.0.2 > 10.0.0.1: ICMP echo request, id 46534, seq 24837, length 44 16:35:32.222090 IP (tos 0x0, ttl 64, id 4241, offset 0, flags [none], proto ICMP (1), length 64) 10.0.0.1 > 10.0.0.2: ICMP echo reply, id 46534, seq 24837, length 44 16:35:33.233714 IP (tos 0x0, ttl 255, id 10, offset 0, flags [none], proto ICMP (1), length 64) 10.0.0.2 > 10.0.0.1: ICMP echo request, id 46534, seq 24838, length 44 16:35:33.233769 IP (tos 0x0, ttl 64, id 4545, offset 0, flags [none], proto ICMP (1), length 64) 10.0.0.1 > 10.0.0.2: ICMP echo reply, id 46534, seq 24838, length 44 On to the standalone CPU + auth server setup instructions now. Thanks very much for all your help. On Sun, Aug 26, 2018 at 7:56 AM Alexander Kapshuk wrote: > > 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. >>