I'm trying to do some vlaning, but my two ROS boards are not communicating.

The network is set up as such:

RB112 <- cat5 -> Cisco 3550 <- Fiber optic -> Cisco 6509 <- fiber optic -> Cisco 3550 <- cat5 -> RB112

I have two VLANs of concern. ID's 200 and 84. 200 is untagged and 84 is tagged.

I have configured the Cisco 3550's as such:
I have verified that both vlans are being broadcast on the port:
Both RB112 boards are running ROS 2.9.45

Interface configuration on both routers is identical:
With IP addresses in the same subnet assigned to interface "vlan1" on both RB112 boards, neither router can ping the other. IP addresses in the same subnet assigned to ether1 work normally.

I can only assume that I'm doing something wrong. Any advice appreciated!

Thanks in advance

Any thoughts? Anybody?

Can you assign an IP address on vlan 84 on one of the directly connected 3550s.

It might also be possible that the RB112 doesn't support VLANs (I know in Linux some chipsets don't). I have vlans working just fine with a cisco 2950 and an RB433 LV4.

You can also check the spanning tree on the cisco switch to make sure both vlans are forwarding all the way through the network on all the ports in question.

I never followed up with the solution on this.

The problem was in the configuration of the 6509 switch in the middle. The RB configuration posted above worked fine.

For reference of anybody trying to do anything like this, I would like to note that you MUST use WDS to pass VLAN tags!

For example,

RB <- wireless link -> rb <-ethernet link -> cisco device (or whatever)

The wireless link MUST be some flavor of WDS!

I don't understand why, but it's the ONLY way it will work.

per RFC.! ONly way to bridge a wireless connection per RFC is via WDS!

per RFC.! ONly way to bridge a wireless connection per RFC is via WDS!

Even if you want to ROUTE it, you have to use WDS.

You can just run IPs on the interfaces with AP bridge and station mode.. NO need for WDS in that aspect.