customers from a widely scattered remote (foreign) network, partially using non RFC 1918 adresses, need access to some of our servers.
Conversely, several of our customers need access to a server in that remote network; they have to be natted too. Our (inside source) adresses can be patted (overloaded) into a single address both sides agreed upon.
It would be nice to overload the foreign client addresses (outside source relative to us) into a single IP address too.
Lacking the overload feature for outside source NAT, instead I have to use a (quite large) pool of NAT adresses for them.
As this NAT network has to be visible in my network (for routing back to the NAT router), I loose a more or less large network for other (real) purposes - although with PAT a single address had been sufficient to "address" the whole remote network!
As to the servers I also use static NAT. The issue are the client addresses. Addresses out of my network have to be translated before reaching the remote net and the ones from remote have to be hidden from my net (as quite a lot of them are non RFC 1918).
I do this by economically overloading all of my (inside source) addresses into a single one fitting into the remote networks.
But for the clients from remote I have to provide a quite large pool of NAT addresses instead of a single (PAT-) one because there is no overlaod feature for "ip nat outside source pool ... list ...".
The propagation of (backward) routes for this NAT pool into my network blocks a large network otherwise usable for real addressing.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...