[c-nsp] NAT Shot in the Dark

[Keegan Holley]

On Sat, Dec 11, 2010 at 5:09 PM, Sean Granger <sgranger at randfinancial.com>wrote:

> Hey guys,
>
> Random headscratcher, never had to do anything like this before, so it's
> all theory.
> I've moved a device from 192.168.1.110 to 192.168.35.110.
>
> When hosts inside of the .1 subnet try to access it at the "old" address,
> how do I force them to go to the new address ... NAT on it's own doesn't
> seem to do the trick (outside local 192.168.1.110, global 192.168.35.110)
> ..... do I have to policy route this thing and force it out of the other
> vlan interface?
>
> I know it's dirty either way, but my developers can't change all of the
> systems that directly address to the original IP in time and the move had to
> happen today.
>
> Thoughts?
>
> Ethernet really isn't IP aware so there isn't a way that I'm aware of to
redirect users to an IP in a different subnet that exists in the same
broadcast domain.  can you migrate the remaining devices to the new subnet?
 If so, it seems the easiest thing to do would be to configure a secondary
address on the interface so the .1 address can still be used and then focus
on migrating the remaining devices.