Cisco ip nat inside access list

Are you just trying to limit which public ip can come in on port 5060? Or are you trying to make a public appear like a private ip on your inside network?

If its the first case, define the nat rule without any acl's. configure an acl on the outside interface limiting the traffic on that port.

If its the second case, I think you might be using that nat command in the wrong direction. The way you have it, it means that any ip in the 79.41.34.x with source port 5060 can go anywhere from the INSIDE to the outside and get it's source nat'd to 192.168.11.250.

The following show an outside nat
http://www.cisco.com/en/US/tech/tk648/tk361/technologies_configuration_example09186a0080093f8e.shtml

as many PCs sen with a random source port the access list will never match unless traffic is sent on port 5060 (kind of what rauenpc said).  Also since your nat pool only has one address you would need to add the overload statement at the end of the NAT entry to allow more than 1 private IP to use the NATed IP at the same time.  try changing the access list and NAT statement:

access-list 100 permit udp 79.41.34.xxx 0.0.0.63 any eq 5060

ip nat inside source list 100 pool VOIP overload

No success my friends...

This is the perspective:

This portforward rule works for outside to inside, but is completed open for all internet:
ip nat inside source static udp 192.168.11.250 5060 57.23.88.xxx 5060 extendable

Now i need to limit it, and only 79.41.34.xxx 0.0.0.63 can pass over this nat rule.
Please post some cisco IOS rules.

I would just add an ACL rule to the outside interface limiting traffic on port 5060 to the source subnet snmp-server 79.41.34.xxx 0.0.0.63.

ip access-list extended OUTSIDE-IN
permit udp 79.41.34.xxx 0.0.0.63 eq 5060 57.23.88.xxx eq 5060
deny udp any eq 5060 57.23.88.xxx eq 5060


The above would permit the 79.41.34.xxx 0.0.0.63 subnet, and deny any other from attempting to come in via port 5060. You more than likely already have an outside acl, to the two lines would need to be added to the existing acl. Once in place, it won't matter that the NAT statement is wide open as the ACL still limits the traffic. You could then also enable logging on the deny rule if you'd like to see who gets denied.

do you have the interface on the outside (the one with the ip address 79.41.34.xxx) configured with "ip nat outside" ?

I'm assuming it's a different router than the one you are using for the other NAT, or on a different interface.

Remove the type rotary from the ip nat pool command.

No success until now, so i tried this simple method like this:

ip nat inside source list 100 interface FastEthernet4.3 overload
access-list 100 permit 79.41.34.xxx 0.0.0.63

All nat inside traffic must pass to access-list 100 right ?

So why when i put: "ip nat inside source static udp 192.168.11.250 5060 57.23.88.xxx 5060 extendable" and anyone can enter, making a bypass the access-list 100 . why?

I also try this rule above, but this port continues open for anyone and not only for acl 100:
ip nat inside source static udp 192.168.11.250 5060 interface FastEthernet4.3 5060

Ideas ?

The ip nat inside get's the public IP translated, so it fail. The solution is getting the IP on the head with ip access-group  on public interface.