oh, I see; You want to be sure that your NIC has enabled priority & VLAN.
If you have Wireshark then you can capture traffic; Ethernet frames with VLAN id will be larger than those without;
You can use advanced ping using source of the interface with Vlan; and run debug ip icmp;
Remember that Native in dot1q means that there is no extra info added to frames;
default Native Vlan is Vlan 1
Ethernet with Vlan info = 114 bytes
Ethernet without Vlan info = 74 bytes
Test Run could be performed on MS Loopback and GNS3. MS Loopback NIC does not support 802.1Q for sure; so if you ping from MS loopback to rotuer and capture frames; then compare those to frames captured when pining from router to MS loopback; I bet you those will be different in size;
I wonder if there is another way to tell Vlan id from captured packets/frames with Wireshark.
this is what the scenario that i am using.....
when i ping form PC to Switch (192.168.50.2 or 51.2), it works.
but when ping form switch to router or PC to router, it does not work.
Just for information....
PC to Switch (f0/9) configured as trunk
VLAN1, VLAN 50 & 51 are UP.......
i don't know where did i wrong??????? is it possible my NIC does not support 802.1q????
First of all, I think you have 2 routers on stick; 1st at Router and 2nd at switch; right?
Router-on-stick === Switch is usually done with L2 switch;
Router === L3 switch example, router-on-stick is the L3 switch, not router (router is just gateway, WAN).
at L3 you can use assign IPs to Interfaces or to Vlans (SVI);
Now, when you ping from PC, you using MS loopback. To figure it out why Pings work or not from Windows CMD to switch, look at Windows routing table; (Route Print from cmd); Same thing for other pings, show ip route on cisco devices will show you routes and default gateways.
You would need another 2 PCs connected to Switch to test your pings appropriately;
To test your dot.1Q and router-on-stick, make your L3 Sw just L2 device;
switchport mode trunk
switchport access vlan 50
switchport access vlan 51
you need PCs plug into fa0/2 and 0/3 with IPs in correct vlans;
in my documents, I have at least 3 examples of inter-Vlan routing for PT; search for those;
i already used my switch as L2......i didn't used IP routing at my switch.......just configure VLAN 50 & 51.....and applied those vlan to int f0/10 & 11.....ip add on switch is just to check ping from laptop to switch....
i also connect my desktop in vlan 50 (int f0/10) and ping to router but it didn't work....
i talked to HP also, they said ur NIC support 802.1q & it is enable as well.....
i don't understand where i am wrong???????????? is there any mistake in confuguration?????????
Inter-Vlan routing with L3 switch can be done 2 ways: over Vlans (SVI) and interfaces (with no switchport)
No need for router here;
Router-on-stick is based on router with sub-interfaces connected to L2 switch;
There are several configurations for this method (native vlan 1 or other vlan #)
Use just your L3 switch with laptop and desktop; no router; set ip routing and point PCs gateways to IPs on Vlans;
make sure switch ports are in access vlan #;
copy your run config from switch
see my test document; I make it more readable later;
Inter-vlan L3.txt.zip 2.4 K
i already perform intervlan routing on L3 devices by applying IP ROUTING and it works...my laptop can ping to my desktop & vice versa....i put both, in different VLAN....
but when i perform router on stick, i coun't get ping from router to switch or switch to router.....i used c3350 as L2 device... i just want to find out what the reasion, why i cant ping from switch to router or vice versa.....
1) is there any problem with configuration ?????????????
2) or, my NIC card does not support 802.1q???????
3) or somethig else??????
i am usng HP laptop with win 7....my NIC card is "realtek PCIe GBE family Controller"
yesterday, i again check with HP and they said your NIC is compitible with 802.1q......
if, anybody has perform router-on-stick by using real switch and gns3.....pl send me detail of it????????????????????????
if what you ping is showing in routing table (as destination network), you should be able to ping OK
Run debug ip packets and debug ip icmp on switch and router;
ping from switch to rotuer; what happens? what is your output?
what is the source address and destintaion IP of pings ?
what is outgoing interface ?
does switch or router have destination IP in routing table?
are there encap errors? does pings gets to rotuer ?
if ping reaches router, can router send those back to the source?
Find out if vlan tagging is really suported (don't trust HP) from here (select your chip id to see more info)
my understanding is that you are running GNS3 on your laptop, with a virtual router interface connected to a cloud which is mapped to a physical NIC, which then connects to the physical switch. On the switch, this port is configured as a port and the router port is configured as a router on a switch i.e. sub-interfaces?
Is it also correct that when you make it an access port and put the IP address on the physical router port (Fa0/0), you can ping both ways without an issue?
The good news is...I have the same problem. The bad news is that I am not sure what the root cause is other than it being the physical NIC. Try this as a workaround:
Make the VLAN you are trying to PING on the native VLAN on both ends of the link e.g.
switchport trunk native vlan 50
encapsulation dot1q 50 native
This effectively removes the tags from traffic on VLAN 50 whilst maintaining the rest of the config so you can confirm what is happening. (By the way, my advice would be to use a subinterface to match the VLAN so its easier to troubleshoot i.e. VLAN 50 on fa0/0.50).
Obviously, this only works on that one VLAN! I tried the priotity and VLAN setting and adding VLANs and all sorts with a persistent PING in the background with no joy.
Lots of reading online suggests people have had this issue and upgraded drivers or OS and it's resolved, or the other way around.
Hope this gives you some ideas of how to progress. Email me at sirdotvegaskidatgmaildotcom if anybody finds the proper fix.