I am a newbie with VLANs, so this question may be a little basic!
I am about to implement NAT with Route-Maps to allow traffic with some ports to be translated to source address x1, and traffic with other ports to be translated to source address x2 on the public side of the router.
On the private side (NAT inside) I also have multiple subnets with only one physical port, so I was looking at configuring subinterfaces on the private side. However between the router and the various hosts we have an unmanaged switch that does not support VLANs. Therefore I am assuming that if the router were to VLAN tag (e.g 802.1Q) the frame, the switch would not remove the tag and it would arrive at the host which wouldn't recognise the frame.
Hence I am looking at secondary addressing on the router to get around this. My question: having a secondary address on the router (which will not require NAT) will still allow the same source address to be translated to different public source address dependent on the port number, if my Route-Map configuration is correct - there won't be any failure on the secondary address to not NAT if it isn't configured in the Route-Map?
I think logically there will be no problem, but I just want to check in case someone is aware of an issue.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...