How to do Port Specific VLAN + Routing

[Thiago]

I need to configure routing between two VLANs with the same Port Specific VLAN, something like this:

(SwitchA)10.1.1.1-------tag 100------10.1.1.2(SwitchC)192.168.1.2-----tag 100------192.168.1.1(SwitchB)

How can I do this?

Here is the options that I tried so far:

1- Two VLANs with port specific VLAN. Limitation: Can't enable ipforwarding with this option.
2- Using policies, here is the policies of one of SwitchC's ports, another two would be needed:

Policy applied in the ingress direction:

entry port1-ingress { if {
vlan-id 100;
} then {
permit;
replace-vlan-id 802;
}
}

Policy applied in the egress direction:

entry port1-egress { if {
vlan-id 802;
} then {
permit;
replace-vlan-id 100;
}
}

This somehow didn't work. I don't know why.

There's an option that I thought about but haven't tried it yet:

Using four VLANs:
- Two VLANs with whatever tag but configured with port specific VLAN 100 in the ports connected to the other switches. Those VLANs will have no ip address and learning disabled.
- Two VLANs with ip addresses, each one connected via cable untagged to one of the anterior VLANs.

I think this third option should work but wouldn't be an elegant solution.

Any ideas?

Thanks

[BrandonC]

Hi Thiago,

This ACL did not do what you want, as the VLAN ID will only be replaced on egress (after egress ACLs have been processed). Because of this, the egress ACL will not be hit.

Since PS tags require no IP forwarding on the VLAN, it looks like the physical loopback using four VLANs may be the best option.

-Brandon

[Thiago]

Thanks,

I guess I will really use the physical loopback option.

If I understood correctly, the replace-vlan-id only works in egress, right? Is there any documentation about this besides Conceps Guide?