New York facility (Users, packaging, warehousing, etc) will be systematically moving to a new Location. Current EDI host resides in New York Facility at IP 172.30.7.200. A new EDI is setup and will be deployed to the new Location and configured with a new 172.30.10.200.
A change to the DNS record will resolve 80% of connectivity issues from LAN devices to the new EDI host. However, there are rogue devices such as hand held scanners statically configured to connect to the Current EDI host IP address rather than FQDN.
I'm looking for some ideas how I can fool or NAT translate on the destination to the 172.30.7.0 host, say 172.30.7.200 when these packets come in from New York, Washington or California. I need these packets to be redirected to 172.30.10.200.
Being that the New York network is a flat 172.30.7.0 subnet, I don't know how I can utilize both the inside and outside interface to accomplish this goal!
Perhaps I would need to create a second routable VLAN (172.30.11.0/24), place the inside interface into the 172.30.7.0 subnet and the outside into the 172.30.11.0/24 subnet, and static route back into the MPLS interface at IP 172.30.7.1, where 172.30.10.0/24 will be found in the BGP routing table?
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...