VLAN tag stripped for Intel adapters

[vijaybharathi]

Host: Linux lena 2.6.18-128.el5 #1 SMP Wed Dec 17 11:41:38 EST 2008 x86_64 x86_64 x86_64 GNU/Linux
Guest: Fedora 14 Linux vijay 2.6.35.6-45.fc14.i686 #1 SMP Mon Oct 18 23:56:17 UTC 2010 i686 i686 i386 GNU/Linux
Virtual Box Version: Version 3.0.14

Problem description:
======================
guest Linux vm with Intel network adapters, doesn't sends the tagged traffic out.
The guest is using Fedora 14 (2.6.25 kernel) with the e1000 driver of following version:

[root@vijay ~]# modinfo e1000
filename: /lib/modules/2.6.35.6-45.fc14.i686/kernel/drivers/net/e1000/e1000.ko
version: 7.3.21-k6-NAPI
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics@intel.com>
srcversion: 68AEB9D8B34E0591820C149

my experiment looks like:
=======================
Create a guest Fedora 14 guest VM and choose Intel Network adapter for Adapter1.
Create a tap interface in host using the command VBoxTunctl -t tap0 -u <userid>
Now set adapter 1 in bridged mode and choose tap0 as the bridging interface.
create another guest as mentioned above and bridge it to tap0.
create vlan interface with vid=100 on eth0 on both the guest.
Assign IP address (say 192.168.170.1, 192.168.170.2) for eth0 interfaces of guest.
Now initiate ping from 192.168.170.1 towards 192.168.170.2.
Do a tcpdump on tap0

Result:
Host unreachable in guest VM.

From 192.168.170.1 icmp_seq=12 Destination Host Unreachable
From 192.168.170.1 icmp_seq=14 Destination Host Unreachable
From 192.168.170.1 icmp_seq=15 Destination Host Unreachable
From 192.168.170.1 icmp_seq=16 Destination Host Unreachable

tcpdump on tap0 doesn't have a VLAN tag in ICMP request.

15:24:08.331231 02:00:20:ee:65:04 > Broadcast, ethertype ARP (0x0806), length 42: arp who-has 192.168.170.2 tell 192.168.170.1
0x0000: ffff ffff ffff 0200 20ee 6504 0806 0001 ..........e.....
0x0010: 0800 0604 0001 0200 20ee 6504 c0a8 aa01 ..........e.....
0x0020: 0000 0000 0000 c0a8 aa02 ..........
15:24:08.331300 02:00:20:ee:65:04 > Broadcast, ethertype ARP (0x0806), length 42: arp who-has 192.168.170.2 tell 192.168.170.1
0x0000: ffff ffff ffff 0200 20ee 6504 0806 0001 ..........e.....
0x0010: 0800 0604 0001 0200 20ee 6504 c0a8 aa01 ..........e.....
0x0020: 0000 0000 0000 c0a8 aa02


Questions:
==========
1. Am i doing something incorrect in my experiment? If so please let me know.
2. Is there a problem with e1000 driver or the way Intel NIC is emulated in VirtualBox?

[hartman.rh]

Any specific reason you're using an ancient VBox version? VBox is at 4.0.8 currently, which may or may not have solved the issue you're experiencing.
No point in wasting time on issues with prehistoric releases, which may not be present in the latest one.

[Sasquatch]

This should help the user a bit more: http://www.google.com/search?client=ope ... 8&oe=utf-8

And, this looks an awful lot like a post make a year ago in which I have posted before. Because of that, I'm locking this thread. I've answered topics about this subject in the link above and I'm sure the TS will find the information useful.