From: Scott Vermillion (scott_ccie_list@it-ag.com)
Date: Tue Oct 09 2007 - 15:37:14 ART
Here is the pertinent text pasted in rather than sending the .pdf:
Workaround #1 for IntelR PRO/1000 GT Desktop Adapter
By default, Intel adapters strip the VLAN tag before passing it up the
stack. If you are using a Microsoft Windows OS and you need to see tagged
frames using your packet
capturing software you will need to use the latest Intel driver and you will
be required to make a registry change. To allow tagged frames to be passed
to your packet capture
software you must go into the registry and either add a registry dword and
value or change the value of the registry key.
The registry dword is MonitorModeEnabled. It should be placed at:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class\{4D36E972-E325-11CE-BF
C1-08002BE10318}\00xx
where xx is the instance of the network adapter that you need to see tags
on. (Check by opening and viewing the name of the adapter).
It should be set to read:
MonitorModeEnabled= 1
Note: ControlSet001 may need to be CurrentControlSet or another 00x number.
For more information, refer to
http://support.intel.com/support/network/sb/CS-005897.htm
Workaround #2 for Broadcom 440x 10/100 Integrated Controller
There is a registry key under
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\control\Class\{4D36E972-E325-11C
E-BFC1-08002bE10318}\0001 that can be set to
cause the driver and chip not to strip the 802.1Q headers. In order to set
that key, you need to find the right instance of the driver in Registry
Editor and set that key for it. You
can do this by doing following:
1. Run the Registry Editor (regedt32)
2. Look for the registry ken mentioned above. If it is found then go to step
4, if it is not found then go to step 3
3. Search for the instance number that contains information about "Broadcom
440x 10/100 Integrated Controller"
4. Right-click on the instance number (eg. 0001) and add a new string value.
5. Enter "PreserveVlanInfoInRxPacket" and give it the value "1".
6. Reboot your system.
This should set you up to be able to capture the VLAN tag information
Workaround #3 forBroadcom NetLink (TM) Gigabit Ethernet
There is a registry key under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet
that can be set to cause the driver and chip not to strip the 802.1Q
headers. In order to
set that key, you need to find the right instance of the driver in Registry
Editor and set that key for it. You can do this by doing following:
1. Run the Registry Editor (regedt32).
2. Search for "TxCoalescingTicks" and ensure this is the only instance that
you have.
3. Right-click on the instance number (eg. 0008) and add a new string value.
4. Enter "PreserveVlanInfoInRxPacket" and give it the value "1".
5. Reboot your system.
This should set you up to be able to capture the VLAN tag information.
For more information, refer to
http://www.networkinstruments.com/support/osup1056.html
-----Original Message-----
From: Scott Vermillion [mailto:scott_ccie_list@it-ag.com]
Sent: Tuesday, October 09, 2007 12:34 PM
To: 'Lora Ganeva'; 'ccielab@groupstudy.com'
Subject: RE: dynamips trunking to real networks
Oh, sorry. I thought when you said "...but I need itL" that it was a typo
and you meant "...but I need ISL."
LOL!
Now I understand. OK, your problem is very likely your NIC, many of which
strip out the dot1q shim header on the inbound direction (esp when Windows
is the OS). Who is the manufacturer of the NIC in your Windows box? There
are registry hacks for both Intel and Broadcom. I can't find the link or I
would post it here. I will unicast you a .pdf file which explains the
registry hacks that are necessary if you have one of those two NICs. Anyone
else interested can unicast me as well...
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Lora
Ganeva
Sent: Tuesday, October 09, 2007 12:00 PM
To: Scott Vermillion; ccielab@groupstudy.com
Subject: RE: dynamips trunking to real networks
Hi Scott,
Thank you for kid support, but i don't want to have ISL:)) As you can see
from
my email, i am just trying to run do1q:)
BR,
Lora
________________________________
From: Scott Vermillion [mailto:scott_ccie_list@it-ag.com]
Sent: Tue 10/9/2007 7:19 PM
To: Lora Ganeva; ccielab@groupstudy.com
Subject: RE: dynamips trunking to real networks
Some good news here Lora, even though it may not be of benefit to you yet.
The 3700s will have ISL support for built-in Ethernet connections whenever
RC2 hits the street:
"chris wrote:
Yep, I have fixed it, it will be available in 0.2.8-RC2"
http://7200emu.hacki.at/viewtopic.php?t=4059&postdays=0&postorder=asc&start=
15
Proof that the developers will take requests into consideration...
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of Lora
Ganeva
Sent: Monday, October 08, 2007 10:07 AM
To: ccielab@groupstudy.com
Subject: dynamips trunking to real networks
Hi everyone,
I am trying to put my lab for R&S with dynamips and windows. And, I
simply cannot make the trunking between the virtual and the real part of
my network. I have tried everything - the switches built-in the
dynamips, switch modules in 3640, 2735 and even 7200. I have upgraded to
the latest win pcap available, but still with no success. Without dot1q
encapsulation everything is OK, but I need itL
Has anyone faced such problems?
Any help will be appreciated:
Win XP , dynamips ver 0.2.7 , winpcap 4.1 beta.
Thanks in advance,
Lora
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:12 ART