Cisco ASA 5505, secondary IP on inside interface, same subnet

Greetings,

I have need to have my ASA5505 listen on 2 IP addresses in the same subnet on the INSIDE interface (VLAN1).

The reason - another device with this secondary IP is being removed and I need to have the ASA listen on *both* its own IP and the IP of the device removed, at least until I find every device using the old gateway IP.

Example:
ASA (inside, VLAN1): 192.168.1.1 255.255.255.0

Old device "X":  192.168.1.10 255.255.255.0

I need something similar to (in router-speak):
int vlan 1
  ip address 192.168.1.1 255.255.255.0
  ip address 192.168.1.10 255.255.255.0 secondary
snowdog_2112Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Henk van AchterbergConnect With a Mentor Sr. Technical ConsultantCommented:
The ASA can only have on IP address on the inside interface.

Maybe you can use other solutions like a layer 3 switch or second (cheap) router.
0
 
Jan SpringerCommented:
You need to put the other subnet in its own vlan and dot1q the interface.
0
 
snowdog_2112Author Commented:
They are in the SAME subnet as mentioned in OP.  Thanks for quick response though.

Both devices have IP's in 192.168.1.0/24.

The old device is gone and won't be replaced, so I need the ASA to "own" 2 IP's on the same subnet - if only for a short while (months, perhaps).
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
Gareth GudgerCommented:
0
 
snowdog_2112Author Commented:
Nope.

Again - the secondary IP is on the SAME SUBNET as the primary.  I can't route from one to the other, and even if I wanted to, I can't VLAN it, since both IP's are in the middle of the same /24.

I have a hunch that it is somehow related to NAT - the devices pointing to 192.168.1.10 (the old IP, which has an arp alias on the ASA) are not being NAT'd or unNAT'd properly.
0
 
snowdog_2112Author Commented:
Love Cisco...

HATE Cisco!

The ASA is "not a router", so for small businesses who might possibly need some routing features, you need an ASA for $500 and another "real router" for another $500-1000.

Or...a $200 Netgear.

At least on an ASA you can type exec commands in conf mode without "do <command>", unlike Cisco routers.

Fair trade-off....maybe.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.