Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Let say an ISP gives me, and I have an internal network of If I run a webserver on say and have that statically mapped to, is there any problem with also making my nat overload IP for general outgoing traffic that originates from anywhere in the network on Cisco IOS?

Logically it seems like it should work fine, but I have never tried it.

share|improve this question
up vote 3 down vote accepted

Yeah, This is referred to in Cisco documentation as Static Nat Translations with Overload. Its certainly one of the most common configurations with residential NAT.

I'd suggest doing the standard assignment of inside/outside interfaces

ip nat pool IPPOOL netmask
ip access-list standard NAT_POOL
ip nat inside source list NAT_POOL pool IPPOOL overload
ip nat inside source static tcp 80 interface X/X 80

I should point out that this configuration has no guarantee in using a specific IP, but you could easily just narrow the pool and adjust the source-static rule appropriately

share|improve this answer

That's perfectly fine... and also quite usual, when you only have a single public IP address and still want something to be accessible from outside your LAN.

I'm actually doing it on my home router (Cisco 877) at this very same moment :-)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.