Is there any reason that you cannot run more than 1 vlan tag on an ethernet interface on an RB411 or 433?
We have been trying to configure a simple vlan trunk over wireless. We are using ROS 5.9, but have also tested with 4.17 with same results. I won’t go into all the details of the configuration, but we were having issues getting any kind of link.
So we tried to root cause the issue. We reset the system configuration on the RB411 to stock and then did the following:
- Assigned IP address 192.168.1.1/24 to ether1
- Created a vlan1 with id 1 on ether1
- Assigned an IP address 10.10.10.1/24 to vlan1
- On a Windows 7 64 pc, we changed the vlan id of the ethernet interface to 1 and set the IP address to 10.10.10.18/24
- Cross connect the pc to the RB411.
No bridging, not wireless, just trying to get the vlan tagging to work on the ethernet port.
Ping works fine and link is persistent.
Then we add vlan2 with id of 2 and IP address of 10.10.20.1/24 to ether1
Without changing the vlan tag on the PC, we start ping again. This time ping runs for about 30 seconds and then stops. We lose all connections to the RB411. Have to change the vlan id back to 0 to connect again.
Ran wireshark, no indication of issue. Turned on debug log for RB411, no indication of issue.
Is there any reason that you cannot run more than 1 vlan tag on an ethernet interface of an RB411 or 433? Does this have something to do with MTU or ARP? Seems like the 30 second delay before failing would indicate some type of table update issue.
