Duplicate packets with host networking

[Cristian Bradiceanu]

Using host networking in VirtualBox attached to LAN interface there are duplicate ICMP packets while pinging the guest IP address (which is in the same /24 as guest):

64 bytes from 172.20.40.12: icmp_seq=0 ttl=255 time=0.459 ms
64 bytes from 172.20.40.12: icmp_seq=0 ttl=254 time=0.464 ms (DUP!)
64 bytes from 172.20.40.12: icmp_seq=1 ttl=255 time=0.425 ms
64 bytes from 172.20.40.12: icmp_seq=1 ttl=254 time=0.549 ms (DUP!)
64 bytes from 172.20.40.12: icmp_seq=2 ttl=255 time=0.386 ms
64 bytes from 172.20.40.12: icmp_seq=2 ttl=254 time=0.391 ms (DUP!)

The same happens with Windows XP and OpenSolaris guests.

If the host is rebooted (shutdown -i6 in Solaris, shutdown -r in Windows), after restart networking is not working from and to the guest.

[Cristian Bradiceanu]

OpenSolaris log file

[Cristian Bradiceanu]

OpenSolaris XML

[Cristian Bradiceanu]

XP log

[Cristian Bradiceanu]

XP XML

[Cristian Bradiceanu]

Host is Solaris 10 5/08, 64-bit.

# uname -a SunOS r1 5.10 Generic_137112-08 i86pc i386 i86pc

[Ramshankar Venkataraman]

The network connection dropping problem has been fixed already in 2.1.0.

As for duplicate packets, I take it you're using VLAN interfaces with PPAs like rge123000? Will investigate.

[Cristian Bradiceanu]

Network connection dropping is fixed in 2.1.0.

Yes, I am using VLAN interfaces (bge0, bge0:1, bge2000, bge4000). Regardless of interface attached to there are duplicate packets seen from hosts in the same broadcast domain.

There is also a Intel PRO/1000 GT interface NIC but I cannot use that with VirtualBox. When shutting down a machine the whole Solaris box crashes and reboots. This might be a different problem (e1000g driver with 82541PI controller?) but I thought it's worth mentioning here.

[Ramshankar Venkataraman]

I don't get any duplicate packets using VLANs when pinging the host->guest or guest->host or remote->host or guest->remote machine.

Could you please attach ifconfig -a output from both host and guest and which interface you have assigned to the guest.

Are zones involved?

Also output of (as root/sudo).

ifconfig <interface-you-give-to-guest> modlist

[Cristian Bradiceanu]

ifconfig -a on Solaris host:

lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1

inet 127.0.0.1 netmask ff000000

bge0: flags=201100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4,CoS> mtu 1500 index 2

inet 172.20.40.3 netmask ffffff00 broadcast 172.20.40.255

bge0:1: flags=201100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4,CoS> mtu 1500 index 2

inet XX.XX.XX.XX netmask ffffffe0 broadcast XX.XX.XX.XX

bge2000: flags=201100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4,CoS> mtu 1500 index 3

inet XX.XX.XX.XX netmask ffffffc0 broadcast XX.XX.XX.XX

bge4000: flags=201100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4,CoS> mtu 1500 index 4

inet 89.37.227.35 netmask ffffffe0 broadcast 89.37.227.63

ifconfig -a on CentOS 5.2 guest, attached to bge4000 hostif:

eth0 Link encap:Ethernet HWaddr 08:00:27:86:18:89

inet addr:89.37.227.37 Bcast:89.37.227.63 Mask:255.255.255.224 inet6 addr: fe80::a00:27ff:fe86:1889/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:481241 errors:0 dropped:0 overruns:0 frame:0 TX packets:327712 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:104602818 (99.7 MiB) TX bytes:119716305 (114.1 MiB) Base address:0xc010 Memory:f0000000-f0020000

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:2173464 errors:0 dropped:0 overruns:0 frame:0 TX packets:2173464 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:887378971 (846.2 MiB) TX bytes:887378971 (846.2 MiB)

Solaris zones are not involved.

host# ifconfig bge4000 modlist 0 arp 1 ip 2 vboxflt 3 bge

Ping from Solaris host to Linux guest:

$ ping -s 89.37.227.37 64 2 PING 89.37.227.37: 64 data bytes 72 bytes from c2.bradiceanu.net (89.37.227.37): icmp_seq=0. time=1.02 ms 72 bytes from c2.bradiceanu.net (89.37.227.37): icmp_seq=1. time=0.801 ms

---

2 packets transmitted, 2 packets received, 0% packet loss round-trip (ms) min/avg/max/stddev = 0.801/0.911/1.02/0.16

ping from guest to host:

$ ping -c 2 89.37.227.35 PING 89.37.227.35 (89.37.227.35) 56(84) bytes of data. 64 bytes from 89.37.227.35: icmp_seq=1 ttl=255 time=0.757 ms 64 bytes from 89.37.227.35: icmp_seq=2 ttl=255 time=0.928 ms

--- 89.37.227.35 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1008ms rtt min/avg/max/mdev = 0.757/0.842/0.928/0.090 ms

Ping from a different host on the same VLAN (IP 89.37.227.33) to guest:

$ ping -s 89.37.227.37 56 4 PING 89.37.227.37: 56 data bytes 64 bytes from c2.bradiceanu.net (89.37.227.37): icmp_seq=0. time=1.41 ms 64 bytes from c2.bradiceanu.net (89.37.227.37): icmp_seq=0. time=1.72 ms 64 bytes from c2.bradiceanu.net (89.37.227.37): icmp_seq=1. time=0.582 ms 64 bytes from c2.bradiceanu.net (89.37.227.37): icmp_seq=1. time=0.640 ms

---

2 packets transmitted, 4 packets received, 2.00 times amplification round-trip (ms) min/avg/max/stddev = 0.582/1.09/1.72/0.56

ping from Linux guest to 89.37.227.33:

$ ping -c 2 89.37.227.33 PING 89.37.227.33 (89.37.227.33) 56(84) bytes of data. 64 bytes from 89.37.227.33: icmp_seq=1 ttl=255 time=0.478 ms 64 bytes from 89.37.227.33: icmp_seq=1 ttl=255 time=0.496 ms (DUP!) 64 bytes from 89.37.227.33: icmp_seq=2 ttl=255 time=0.471 ms

--- 89.37.227.33 ping statistics --- 2 packets transmitted, 2 received, +1 duplicates, 0% packet loss, time 1003ms rtt min/avg/max/mdev = 0.471/0.481/0.496/0.027 ms

Duplicates are seen from LAN to guest, from guest to LAN, but not from host to guest or guest to host. Same results if guest is attached to bge0 with 172.20.40.x IP address. There are no duplicates between any two hosts on any of the interfaces, except to and from guest. I tried with XP, Linux and FreeBSD guests with same results.

[Ramshankar Venkataraman]

Eh, correct me if I'm wrong, but if you can ping public class A 89.37.227.37 and you have the same address to a machine on the VLAN you should be getting 2 ICMP replies, one VLAN tagged from the guest and one from the external host. Same for the guest to LAN/external scenario.