Don't see your pool for Nat overload... Im not a nat expert but shouldn't you have

ip nat pool pool30 66.192.112.230 66.192.112.230 netmask 255.255.255.192

HTH, Please rate if so

Regards,

Justin

You can choose an interface (with an ip address assigned to it) or a pool. I have tried both ways...no luck.

Thanks for the reply.

All of the documentation, including the link you provided (bottom of the page Example), shows an access list permitting only the inside networks. My understanding is that the first part of the "ip nat inside source list" command is to identify the inside ip addresses and the second part identifying the outside interface (or pool). I think I should see the access list be hit when I ping from an inside address to an outside address??

Andrew, are you saying that you cannot reach any external addresses from the inside network -- as you have configured it to do?

Or are you saying that you do have connectivity to external addresses, but that you don't see the ACL hitting up?

VL

That's correct, I cannot hit any external addresses from the inside network.

OK, it doesn't work.

Is your routing correct? Do you have a route to the destination networks in your routing table? If not, the router will drop the packet before even trying to do any NATing (order of operations).

Victor

I do not have a static route but there is a local route (directly connected).

1#sho ip route 192.168.100.0

Routing entry for 192.168.100.0/24

Known via "connected", distance 0, metric 0 (connected, via interface)

Routing Descriptor Blocks:

* directly connected, via GigabitEthernet9/45

Route metric is 0, traffic share count is 1

Of course you have a directly connected route to a network that your interface belongs to.

I was asking about a route in the routing table for the destination network.

A router routes a packet based on the destination IP address in the IP datagram header it receives on its interface, unless PBR is being used, which is another story.

Do you have a route to the destination network?

Victor

Yes, this router has a full BGP route table. The destination network is definately known. I can ping the address from the router.

OK.

How about you post the entire config and lets take a closer look at everything?

I meant to ask you about the 'portfast' configs on the L3 interfaces? Why do you have them? Portfast is an STP feature that is applied to L2 interfaces that connect end-users.

Curious, are both those interfaces in an 'up, up' state?

Im also trying to remember if you have to configure the 'no switchport' command to make it an L3 interface on the 7613.

VL

The portfast was leftover from a previous role this interface had. I removed it on both and still no luck.

You do have to execute the no switchport command before you assign an IP address to an interface. Both of the interfaces are up and can be reached via ping.

I will post the entire config tomorrow.

Thanks for your help.