[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5797
  • Last Modified:

Cisco Getting TTL expired in transit. Traffic bouncing from one router to another back and forth

Setting up a new network while trying to keep the old one going in unison. This is a little difficult to describe...
Traffic from server 172.16.101.93 should go out router 172.16.0.3 to router 192.168.1.253 then to router 192.168.10.1 and on to server 192.168.10.81

Doing a "tracert" from a server on the 172.16.101.x subnet which is in another state (Ohio) and below are the results I get...
C:\>tracert 192.168.10.81

Tracing route to aldsvrapp1.aldik.com [192.168.10.81]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  out of state router.com [172.16.0.3]
  2    59 ms    59 ms    59 ms  10.1.0.10 <My router 192.168.1.253
  3    60 ms    60 ms    60 ms  10.1.0.9 <172.16.0.3 router
  4   118 ms   118 ms   119 ms  10.1.0.10
  5   119 ms   119 ms   119 ms  10.1.0.9
  6   177 ms   177 ms   177 ms  10.1.0.10

The tracert about it just bounces between router 192.168.1.253 and 172.16.0.3 or 10.1.0.10 and 10.1.0.9
 
Here is the config of 10.1.0.10... or 192.168.1.253

interface FastEthernet0/0
 description Internal LAN
 ip address 192.168.2.254 255.255.255.0 secondary
 ip address 192.168.3.1 255.255.255.0 secondary
 ip address 192.168.1.253 255.255.255.0
 ip nat inside
 ip route-cache flow
 ip policy route-map www
 speed auto
 full-duplex
!
interface Serial0/1
 description T1 to Milford
 ip address 10.1.0.10 255.255.255.252
 ip route-cache flow
 no ip mroute-cache
 service-module t1 timeslots 1-24
!
interface BVI1
 ip address 68.88.37.16 255.255.255.0
 ip nat outside
 ip route-cache flow
!
ip nat inside source list 1 interface BVI1 overload
no ip http server
ip flow-export source FastEthernet0/0
ip flow-export version 5
ip flow-export destination 192.168.1.121 9996
ip classless
ip route 0.0.0.0 0.0.0.0 Serial0/1
ip route 10.11.3.0 255.255.255.0 192.168.1.1
ip route 10.11.4.0 255.255.255.0 192.168.1.1
ip route 10.11.7.0 255.255.255.0 192.168.1.1
ip route 10.11.9.0 255.255.255.0 192.168.1.1
ip route 10.11.11.0 255.255.255.0 192.168.1.1
ip route 172.16.0.0 255.255.0.0 10.1.0.9
ip route 172.16.101.93 255.255.255.255 192.168.1.1
ip route 192.168.40.0 255.255.255.0 192.168.1.1
!
!
access-list 1 permit 192.168.1.0 0.0.0.255
access-list 120 deny   tcp any 172.16.101.0 0.0.0.255 eq www
access-list 120 deny   tcp any 172.16.101.0 0.0.0.255 eq ftp
access-list 120 deny   tcp any 192.168.3.0 0.0.0.255 eq www
access-list 120 deny   tcp any 192.168.2.0 0.0.0.255 eq www
access-list 120 permit tcp any any eq www
access-list 130 permit ip any any
!
route-map www permit 10
 match ip address 120
 set ip next-hop 68.88.37.1
!
route-map www permit 20
 match ip address 130
 set ip next-hop 10.1.0.9
!
snmp-server ifindex persist
!
bridge 1 protocol ieee
bridge 1 route ip


I'm guessing I need some sort of IP route to get it to hop over to 192.168.10.1

I hoping I explained the network layout well enough to troubleshoot
0
andersenks
Asked:
andersenks
1 Solution
 
Galtar99Commented:
Either you have a default route of one router point to another router and vice versa, or your routing table has some problems accomplish the same thing.  It's a routing loop.  Check all your routing tables and fix as needed.  Two routers should never have each other as the default route.
0
 
Don JohnstonInstructorCommented:
Your default route is sending the packets back towards their source.



0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now