- Community Home
- >
- Networking
- >
- Switching and Routing
- >
- HPE Aruba Networking & ProVision-based
- >
- Forward 802.1ad QinQ frames on tagged vlans on Pro...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2017 05:38 AM
09-22-2017 05:38 AM
Forward 802.1ad QinQ frames on tagged vlans on ProCurve 2810
Hi,
I'd like to use 802.1ad VLANs on top of 802.1Q VLANs; the switch only needs to understand 802.1Q (I think).
If I send 802.1ad-tagged frames on an untagged port, the switch will insert the 802.1Q-tag when the frame leaves on a tagged port just fine, but it drops frames going the other way (i.e. coming in on a tagged port, doesn't matter whether they leave tagged or untagged).
The frame with both tags lists the 802.1Q tag first, then the 802.1ad tag (which isn't what the wikipedia pages calls "typical", but should imho work better with devices that don't support 802.1ad).
tcpdump on the system attached to the untagged port:
00:25:90:XX:XX:XX > ff:ff:ff:ff:ff:ff,
ethertype 802.1Q-QinQ (0x88a8), length 46: vlan 180, p 0,
ethertype ARP, Ethernet (len 6), IPv4 (len 4),
Request who-has 10.180.0.7 tell 10.180.0.8, length 28
(response missing)
tcpdump on the system attached to the tagged (vlan 11) port:
00:25:90:XX:XX:XX > ff:ff:ff:ff:ff:ff, ethertype 802.1Q (0x8100), length 64: vlan 11, p 0, ethertype 802.1Q-QinQ, vlan 180, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.180.0.7 tell 10.180.0.8, length 42 0c:c4:7a:XX:XX:XX > 00:25:90:XX:XX:XX, ethertype 802.1Q (0x8100), length 50: vlan 11, p 0, ethertype 802.1Q-QinQ, vlan 180, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.180.0.7 is-at 0c:c4:7a:XX:XX:XX, length 28
The systems are both linux (debian stable); for the tagged port the linux box has a vlan11 (802.1Q) on the ethernet device and a vlan180 (802.1ad) on the vlan11 device; I also disabled txvlan and vxlan offloading features to make sure they don't interfere with the order.
Is there any way I can tell the switch to forward those packets? As far as I can tell it doesn't need to actually understand 8021.ad for this, is just needs to handle the outer tag.
(The same setup works just fine on an Aruba 2530 switch)