You are not logged in.

#1 2017-07-29 17:33:40

Tigran
Member
Registered: 2017-07-29
Posts: 21

Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

I have installed an Arch host with virtualbox-headless, and an Arch guest in it with network attached to bridged network to a phisycal interface of host system (enp0s8).
the address of the guest is 192.168.139.212/28

It cannot reach to anywhere outside the host machine. It pings th IP of the host interface  enp0s8 192.168.139.210. It pings all the other guests, attached the same way to the same enp0s8, 192.168.139.211 and 192.168.139.213. But it cannot ping the gateway 192.168.139.209 on the other side of the cable, plugged into enp0s8.
The strangest thing is that all the other guests (WS2008, W7 And Fedora Linux) simply work in exactly the same situation. And  attached to NAT or NAT Network Arch guest works fine, too.

But I've found NO WAY to make it ping the 192.168.139.209 gateway. I've tried different types of virtual NICs in Arch guest setup - AM79C970A, AM79C973, Intel 8254OEM, Intel 82543GC, Intel 82545EM and virtuo-net (I use remotebox as frontend for virtualbox-headless). I've tried booting the guest with fallback initramfs. I've installed vbox guest modules, though I don't think they are of help. No use.

The strangest thing is that the guest 192.168.139.212 successfully places the MAC address of 192.168.139.209 in arp table after pings from or to that, but 192.168.139.209 never can see MAC address of 192.168.139.212. And placing it manually to arp table of 192.168.139.209 never helped, too.

All the vbox modules in host system are correctly installed. Well, everything works BUT Arch guest in bridged mode!

Offline

#2 2017-07-29 17:48:27

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,739

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

What is the host machine?  Has it a firewall?

Is the IP address a static address?  I assume so since you probably cannot see a DHCP server.  Perhaps then the problem is at your router; it may not know how to find your machine.
Is the host machine's IP address static or dynamic?

Also, the /28 address space is a bit unusual.  That says you are using 28 of the 32 IPv4 address bits to identify the network leaving 4 bits to identify a machine on the subnet.  That means the subnet can only contain about 14 machines.  This may be what you want, but it is rare.  209 == 0xd1 and 212 ==0xd4.  With a /28 address, they will both be on the same subnet; 192.168.139.dx.  OTOH, if the router is using /24 (much more common) that could be the issue.


Edit:  Oh yeah, Welcome to Arch Linux big_smile

Last edited by ewaller (2017-07-29 17:49:01)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2017-07-29 18:10:15

Tigran
Member
Registered: 2017-07-29
Posts: 21

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

Thank you for the answer, but, believe me, on the network level everything is set up correctly.

There is no firewall for 192.168.139.208/28 between the host system and gateway;
IP address is static and configured through systemd-networkd (it pings 192.168.139.210, as I've mentioned before);
There is a reason to use /28 instead of /24.
No, the router does not use /24, it uses /28, too. I've had mentioned  that all the other guests OSs (W7, WS2008 and Fedora Linux) under JUST THE SAME CONDITIONS in the same Arch host system, even with the same IP, work fine, but not the Arch guest under Arch host!

I have been with Arch for 5 years already, just didn't have a chance to address to community, all the issues before had been settled by reading, not writing)

Well, between these two posts I've had an idea to install the LTS kernel to guest, as it used the latest 4.12.3-1 and i learned here https://github.com/manjaro/packages-core/issues/75 this kernel is not really good with virtbox;
but alas! Nothing changed.

Any help and ideas appreciated.

Offline

#4 2017-07-29 18:18:48

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,739

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

Fair enough.   I did miss that it is an Arch host.  That other guests work on the same host is important information.  I assume you have checked the route on the the Arch guest and compared it to those of the other guests.
Also, I assume that the hostname is configured and is unique?

Just looking for the low hanging fruit.

Last edited by ewaller (2017-07-29 18:19:41)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#5 2017-07-29 18:30:58

Tigran
Member
Registered: 2017-07-29
Posts: 21

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

I've went through all those low hanging before screaming to help)
Checked and rechecked everything for two days. Nothing found I could correct myself.

I have even tried a different pfysical NIC on the host system, assuming some possible minor compatibility issues between the NIC driver and vbox modules (there are two Nvidia and two Broadcom Gbit NICs there), but nothing changed.

Well I've also  installed LTS kernel both on host and guest, just to avoid future brand new kernel issues, and by now have no more ideas but sitting on the riverbank looking forward for an enemy corpse passing along))

Offline

#6 2017-07-30 15:49:21

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

For clarity :

you have a subnet 192.168.139.208/28

209 is router gateway to other networks
210 is a physical interface on the host that is setup as a bridge .

Guests use a virtual interface to connect to the physical bridge using addressess 211 and up.

2 windows guests and a fedora guest can handle this setup, but an archlinux guest at 212 can't .



This kinda feels like the bridge should actually be a router instead of  a bridge, but it's your setup .

Could it have something to do with promiscuous mode ?

AL has it off by default, maybe the others have it on for virtual interfaces ?

Last edited by Lone_Wolf (2017-07-30 15:50:50)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#7 2017-07-30 17:05:07

Tigran
Member
Registered: 2017-07-29
Posts: 21

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

Thank you for a reply,

1. Yes. everything is understood correctly. The setup is just what you've described.
2. I've tried the promiscuous mode for Arch guest, it didn't help. And, all the other guests are happily bridging without turning the promisc mode on on the guest bridge. I mean the setup of Vbox bridging mode in Networking section of guest setup.

But, you've gifted me an idea, thank you! I should have tried it - to turn the host system into a router and try to reach the network through a separate NIC. It will cost me 4 extra public IPs (sincerely, I use public addresses, the 192.168.x.xt is brough just for privacy reason), but it's still worth a try.
I'll check that setup, it will probably work, because I can reach the host system itself from inside of Arch guest.

But it's a kind of workaround, the mystery of Nonworking Arch Guest Bridge still persists.

Offline

#8 2017-07-31 12:24:38

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

It will cost me 4 extra public IPs (sincerely, I use public addresses, the 192.168.x.xt is brough just for privacy reason), but it's still worth a try.
I'll check that setup, it will probably work, because I can reach the host system itself from inside of Arch guest.

That suggests your setup is more complicated then I assumed (in a typical bridging setup you'd need the gateway to connect to the host)
You may not need those extra public addresses, but we'll need  a full description of the network setup to help further.

Obfuscating the first 2 numbers of the ipv4 addresses should be enough to protect the real addresses while giving enough network info to help out.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#9 2017-07-31 16:33:19

Tigran
Member
Registered: 2017-07-29
Posts: 21

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

Well, the setup is just what I've specified before. I am trying to make the bridge work, but it does not forward the packets from Arch guest to the gateway, connected to the NIT, that is attached to the Arch guest's bridged virtual NIC.

The full description of the network is as such:

The gateway NIC IP is x.x.139.209/28
The host system NIC, IP x.x.139.210/28, connected directly to gateway x.x.139.209/28 NIC to NIC.
The guests:
1. Windows 7, virtual NIC, local IP x.x.139.211/28, in bridged mode, attached to abovementioned host NIC with IP x.x.139.210/28 connected to gateway
2. Windows Server 2008, virtual NIC, local IP x.x.139.212/28, in bridged mode, attached the same way as above.
3. Fedora Linux, virtual NIC, local IP x.x.139.213/28, in bridged mode, attached the same way as above.
All these three guests have excellent networking, Internet access, everything one can dream of.
And,
4.-th guest, Arch Linux, virtual NIC, local IP x.x.139.214/28, in bridged mode, attached the same way as above.
Arch guest is capable of reaching everything within the host system box, including the host system NIC  x.x.139.210/28 itself, as well as x.x.139.211/28,  x.x.139.212/28 and x.x.139.213/28 guests,
BUT! It cannot reach the gateway IP x.x.139.210/28, what is just the problem.
I am ready to deliver any further details.

Offline

#10 2017-08-01 13:06:19

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

I assumed your host had 2 physical nics, one of which was bridged .
This is a common setup and makes sure all host - guest network access goes through the router (Iand the router firewall ).

Now i think you have 1 nic that is managed by VBox .
This would mean the host doesn't have it's own NIC, but shares the nic with the guests.


Does this diagram match your setup ?

Sorry, no idea how to get  a thumbnail here (apart from creating a smaller separate version manually).


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#11 2017-08-01 14:28:23

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,739

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

Lone_Wolf wrote:

Now i think you have 1 nic that is managed by VBox .
This would mean the host doesn't have it's own NIC, but shares the nic with the guests.

It is fairly common to have one NIC that has multiple addresses -- one for the host, one for the guest.  True for IPv4 and, I am pretty sure, IPv6 as well.  In this way, the guest appears directly on the LAN and is, to the casual observer, an independent machine.

Tigran,
This brings up a question.  If things are set up the way we think they are, there should be two IP addresses on the host NIC.  Have you verified that with ip addr  ?

Edit: And what are you using to control the network on the host?  And on the guest?  (systemd, NetworkManager, Netctl)?  Is this the same tool you used on non Arch distributions?
I am wondering if something unique to whatever is controlling the network on the guest Arch system could be upsetting the NIC setting of it's guest.

Last edited by ewaller (2017-08-01 14:32:03)


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#12 2017-08-02 11:01:07

Tigran
Member
Registered: 2017-07-29
Posts: 21

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

Lone_Wolf wrote:

I assumed your host had 2 physical nics, one of which was bridged .
This is a common setup and makes sure all host - guest network access goes through the router (Iand the router firewall ).

Now i think you have 1 nic that is managed by VBox .
This would mean the host doesn't have it's own NIC, but shares the nic with the guests.

Does this diagram match your setup ?

Thank you for continuing efforts to help.
Yes, the diagram correctly reflects my setup. The physical nic is bridged by VBox for all four guests.

Offline

#13 2017-08-02 11:38:34

Tigran
Member
Registered: 2017-07-29
Posts: 21

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

ewaller wrote:

It is fairly common to have one NIC that has multiple addresses -- one for the host, one for the guest.  True for IPv4 and, I am pretty sure, IPv6 as well.  In this way, the guest appears directly on the LAN and is, to the casual observer, an independent machine.

Tigran,
This brings up a question.  If things are set up the way we think they are, there should be two IP addresses on the host NIC.  Have you verified that with ip addr  ?

The IPs of VBox guests are not seen inside the host system by tools like iproute2 (the part of which ip utility is) on the NIC bridged by VBox. Though they still persist while the guests are running and can be accessed right the way they would be set up as multiple IPs on the same host NIC.

ewaller wrote:

And what are you using to control the network on the host?  And on the guest?  (systemd, NetworkManager, Netctl)?  Is this the same tool you used on non Arch distributions?
I am wondering if something unique to whatever is controlling the network on the guest Arch system could be upsetting the NIC setting of it's guest.

The network on host and Arch guest are both controlled by systemd-networkd. The configs are

Host:

[Match]
Name=enp6s4f1

[Network]
Address=x.x.139.210/28
Gateway=x.x.139.209

Guest:

[Match]
Name=enp0s3

[Network]
Address=x.x.139.214/28
Gateway=x.x.139.209

Fedora guest setup is the following:

TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp0s3
ONBOOT=yes
AUTOCONNECT_PRIORITY=-999
DEVICE=enp0s3
IPADDR=x.x.139.213
PREFIX=28
GATEWAY=x.x.139.209
DNS1=8.8.8.8
IPV6_PRIVACY=no

Both Windoze guests networking is configured the usual way. They are x.x.139.211 and 212

Offline

#14 2017-08-02 14:20:11

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

output of ip addr and ip route on host ?

do things change If you setup networking manually on the archlinux guest ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#15 2017-08-02 17:30:36

Tigran
Member
Registered: 2017-07-29
Posts: 21

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

Lone_Wolf wrote:

output of ip addr and ip route on host ?

Here they are:

[******@VHOSTS ~]$ ip ad ls
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp0s8: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:1b:24:93:35:4f brd ff:ff:ff:ff:ff:ff
3: enp0s9: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:1b:24:93:35:50 brd ff:ff:ff:ff:ff:ff
4: enp6s4f0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 00:1b:24:93:35:4d brd ff:ff:ff:ff:ff:ff
5: enp6s4f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:1b:24:93:35:4e brd ff:ff:ff:ff:ff:ff
    inet x.x.139.210/28 brd x.x.139.223 scope global enp6s4f1
       valid_lft forever preferred_lft forever
    inet6 fe80::21b:24ff:fe93:354e/64 scope link
       valid_lft forever preferred_lft forever
6: vboxnet0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff


[******@VHOSTS ~]$ ip ro ls
default via x.x.139.209 dev enp0s8 proto static
x.x.139.208/28 dev enp6s4f1 proto kernel scope link src x.x.139.210

The same inside the Arch guest

[******@ARCH_MX ~]$ ip ad ls
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 08:00:27:3d:1b:bf brd ff:ff:ff:ff:ff:ff
    inet x.x.139.214/28 brd x.x.139.223 scope global enp0s3
       valid_lft forever preferred_lft forever
    inet6 fe80::a00:27ff:fe3d:1bbf/64 scope link
       valid_lft forever preferred_lft forever


default via x.x.139.209 dev enp0s3 proto static
x.x.139.208/28 dev enp0s3 proto kernel scope link src x.x.139.214

Virtual NIC enp0s3 of the guest ARCH_MX is attached by VBox bridge to physical NIC enp6s4f1 of the host VHOSTS running VBox.

Lone_Wolf wrote:

do things change If you setup networking manually on the archlinux guest ?

No, nothing changes, everything stays right the same.

Offline

#16 2017-08-03 08:02:15

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

That atleast gives  a possible explanation why the AL guest doesn't have full network and the other guests do :
The AL guest uses a different networking setup then your other guests .

I expect enp0s8 , enp0s9 and enp6s4f0 are used by the windows and fedora guests .
How are they created ?

If you are not sure, temp disable all VBox services , reboot and verify if those interfaces are present.


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#17 2017-08-07 13:30:14

Tigran
Member
Registered: 2017-07-29
Posts: 21

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

Sorry for long delay, I was out of office.

Though the answer is NO. ALL THE GUESTS ARE SETUP JUST IN THE SAME WAY. Not to different NIC, nor in different mode, just different IPs. They are all bridged in absolutely identical way to enp6s4f1 NIC the Arch guest is bridged to, but all the three guests can send and receive packets to cable, and Arch cannot.

Offline

#18 2017-08-07 13:32:27

Tigran
Member
Registered: 2017-07-29
Posts: 21

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

And enp0s8 , enp0s9 and enp6s4f0 are physical NICs in host bow, they are not used at all, just present.

Offline

#19 2017-08-07 14:30:01

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

OK, so your host has 4 network cards .
Their mac addresses are very similar, this lead me to assume wrongly they were one card .

Is vboxnet0 created by you / specific virtualbox services / using something like VTE ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#20 2017-08-07 18:53:44

Tigran
Member
Registered: 2017-07-29
Posts: 21

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

I have created vboxnet0 by virtualbox services while experimenting with different types of vbox networking. As far as I remember, it was under use in NAT Network networking type, now it's unused, too.

Offline

#21 2017-08-07 21:05:54

CarbonChauvinist
Member
Registered: 2012-06-16
Posts: 412
Website

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

Might this be an issue with packet forwarding?


"the wind-blown way, wanna win? don't play"

Offline

#22 2017-08-07 21:53:35

brebs
Member
Registered: 2007-04-03
Posts: 3,742

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

Tigran wrote:

while experimenting with different types of vbox networking.

VirtualBox's networking is insane, with multiple types, all unsatisfactory.

Use qemu, then you'll be back in normality and be able to use normal Linux networking.

Offline

#23 2017-08-08 10:29:18

Tigran
Member
Registered: 2017-07-29
Posts: 21

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

CarbonChauvinist wrote:

Might this be an issue with packet forwarding?

Nope. First, I have surely put 1 into ip_forward. Second, if I woldn't, it would affect all guests, not just Arch.

Offline

#24 2017-08-08 10:30:38

Tigran
Member
Registered: 2017-07-29
Posts: 21

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

brebs wrote:
Tigran wrote:

while experimenting with different types of vbox networking.

VirtualBox's networking is insane, with multiple types, all unsatisfactory.

Use qemu, then you'll be back in normality and be able to use normal Linux networking.

Thank you for your opinion, but I have to stay within VBox.

Offline

#25 2017-08-08 12:50:20

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: Bridged NIC in guest Arch under Vbox Arch can't get to net out of host

Tigran,

After checking the doc linked by brebs i agree with calling Vbox networking insane .
However, atleast 2 options for providing network to VBox VMs WITHOUT Vbox managed insanities are mentioned.

Paravirtualized network adapter (virtio-net)
The "Paravirtualized network adapter (virtio-net)" is special. If you select this, then VirtualBox does not virtualize common networking hardware (that is supported by common guest operating systems out of the box). Instead, VirtualBox then expects a special software interface for virtualized environments to be provided by the guest, thus avoiding the complexity of emulating networking hardware and improving network performance.

https://wiki.archlinux.org/index.php/Libvirt#Networks


Incase you need more then libvirt can provide , option 2 :

VDE networking
https://www.virtualbox.org/manual/ch06.html#network_vde
https://wiki.archlinux.org/index.php/QE … _with_VDE2


Either method provide a networking framework that is not limited to one hypervisor but is designed to work with all.

Last edited by Lone_Wolf (2017-08-08 12:51:23)


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

Board footer

Powered by FluxBB