Cisco 2651XM NAT issue

[paul.a.facey]

Greeting,

I have configure NAT on my Cisco 2651XM series router OS 12.2(8r).

When I check the NAT table it only shows that UDP traffic is being routed nothing else.

Any Ideas ?

Building configuration...

Current configuration : 1160 bytes
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Gateway
!
boot-start-marker
boot-end-marker
!
enable secret 5
enable password
!
memory-size iomem 15
no network-clock-participate slot 1
no network-clock-participate wic 0
no aaa new-model
ip subnet-zero
ip cef
!
!
!
!
ip ips po max-events 100
no ftp-server write-enable
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
no crypto isakmp ccm
!
!
!
!
interface FastEthernet0/0
 ip address 192.168.13.3 255.255.255.0
 ip nat outside
 ip virtual-reassembly
 duplex auto
 speed auto
!
interface Serial0/0
 no ip address
 shutdown
!
interface FastEthernet0/1
 ip address 10.10.1.1 255.255.255.0
 ip nat inside
 ip virtual-reassembly
 speed auto
 half-duplex
 no mop enabled
!
interface Serial0/1
 no ip address
 shutdown
!
ip classless
!
!
no ip http server
no ip http secure-server
ip nat inside source list 1 interface FastEthernet0/0 overload
!
access-list 1 permit 10.10.1.0 0.0.0.255
!
!
!
control-plane
!
!
!
!
!
!
!
!
!
line con 0
line aux 0
line vty 0 4
 password
 login
!
!
end

[devils_advocate]

Why is Fa0/1 configured for half duplex?

[paul.a.facey]

so..it should not be it should be full duplex which I will correct.

I am starting to believe the problem is the router itself, every time the router is power cycled it comes back to the initial configuration mode as if it has never been setup before.

I execute the configuration and issue the copy run start and the same thing happens on next power cycle it goes into the initial configuration mode.

Any ideas,  I have another identical router, I am going to set that one up and see if it has the same issues.

[paul driver · Accepted solution]

Hello

Try applying a default route!

ip route 0.0.0.0 0.0.0.0 fa0/0 192.168.13.x

res

paul

[paul.a.facey]

I appreciate the help.

I just want to make sure that I understand what the problem was, since I am jumping to another router it was necessary to define the route to the next router which I had not done.

If I have this wrong please feel free to let me know.

Appreciate you assisting this new guy.

V/R

Paul

[paul driver]

Hello

The rtr didn't have the information on where to route external packets too.

When you defined the static default with a nexthop addresss then any traffic originating from your "inside" network was able to be Natted and forwarded onto the next hop router

res

paul