03-05-2015 05:10 PM - edited 03-07-2019 10:57 PM
I have an older cisco firewall that has multiple secondary address on a single interface.
untagged, L2 connections on all switches off the main interface.
My issue is, I can't seem to route back to the secondary addresses assigned to the port.
devices can only see the primary address. If, from the firewall box, I "ping 10.x.x.1 source 10.x.x.10" , this works. Otherwise they fail on a regular ping.
It's seems to only advertise on the primary network. which is a 192.x.x.x.
Is there a set of commands that would force the secondary addresses to advertise in the same fashion as the primary?
03-05-2015 06:07 PM
That is the correct behavior. By default the device uses the primary IP address of the out going interface as the source, which is 192.x.x.x. If you want it to be from 10.x.x.10 address (which is the secondary IP) you need to source it from that IP.
HTH
03-06-2015 06:08 PM
If I get your meaning on this I believe you will find the answer to your question in a previous thread:
This solution will allow you to do port forwarding off of your secondary addresses while having the host answer on that address.
Hope this helps!
Cheers,
Sam
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide