Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot route with PTP Line 1

Status
Not open for further replies.
Feb 4, 2005
7
0
0
US
I have a 1.5 Mb PTP line between my facility and a facility about 45 miles away. I have two cisco 2600 series routers with a csu dsu card in each.

I have the PTP line setup with a 172.16.2.1 and 172.16.2.2 on each end. On router A I have a 10.1.0.0 network connected in the fa 0/0 port. In router B I have a 192.168.1.0 network setup. From router B I can ping router A which is 10.1.125.3 but I cannot ping anything else past that. From Router A it is the same the router IP is 192.168.1.10 I can ping that but nothing else past it.

I am going crazy and am not a Cisco expert. Could someone please help.

Here is the config for Router A

memory-size iomem 25
ip subnet-zero
!
!
!
!
interface Serial0
ip address 172.16.2.1 255.255.255.0
!
interface FastEthernet0
ip address 10.1.125.3 255.255.0.0
speed auto
half-duplex
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.16.2.2
ip route 192.168.1.0 255.255.255.0 172.16.2.2
no ip http server
!
dialer-list 1 protocol ip permit
dialer-list 1 protocol ipx permit
!
line con 0
transport input none
line aux 0
line vty 0 4
password cisco
login
!
no scheduler allocate

Here is the show ip route for A


Gateway of last resort is 172.16.2.2 to network 0.0.0.0

172.16.0.0/24 is subnetted, 1 subnets
C 172.16.2.0 is directly connected, Serial0
10.0.0.0/16 is subnetted, 1 subnets
C 10.1.0.0 is directly connected, FastEthernet0
S 192.168.1.0/24 [1/0] via 172.16.2.2
S* 0.0.0.0/0 [1/0] via 172.16.2.2





Here is the config for router B

ip subnet-zero
no ip finger
!
!
!
!
interface FastEthernet0/0
ip address 192.168.1.10 255.255.255.0
duplex auto
speed auto
!
interface Serial0/0
ip address 172.16.2.2 255.255.255.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 172.16.2.1
ip route 10.1.0.0 255.255.0.0 Serial0/0
ip http server
!
!
line con 0
transport input none
line aux 0
line vty 0 4
password cisco
login
!
end

Now for the IP route


Gateway of last resort is 172.16.2.1 to network 0.0.0.0

172.16.0.0/24 is subnetted, 1 subnets
C 172.16.2.0 is directly connected, Serial0/0
10.0.0.0/16 is subnetted, 1 subnets
S 10.1.0.0 is directly connected, Serial0/0
C 192.168.1.0/24 is directly connected, FastEthernet0/0
S* 0.0.0.0/0 [1/0] via 172.16.2.1


 
If the routers can commuicate, it's more likely that the devices on either network do not have routes to the remote network. They need either specific static routes to the remote network via the local router or default gateways of the local router.

ie. If a device on LAN A on say 10.1.125.100 wanted to send a ping to a device on LAN B on say 172.16.2.100, it would need to know that to get to LAN B, it would have to route that traffic via router A.

route add 172.16.2.0 mask 255.255.255.0 10.1.125.3 -p

For the device on LAN B to reply, it would have to know that to route to LAN A, it would use router B as its gateway to that remote network.

route add 10.1.0.0 mask 255.255.0.0 172.16.2.2 -p

Also note that if you have this ..

ip route 0.0.0.0 0.0.0.0 172.16.2.2

then you don't also need this ..

ip route 192.168.1.0 255.255.255.0 172.16.2.2

.. as the default route covers this.

Chris.

**********************
Chris A.C, CCNA, CCSA
**********************
 
Chris,

Thanks that fixed me up. I should have known that. I was to concerned about my lack of knowledge with CISCO to worry about what I already knew.

THANKS YOU SAVED ME FROM LOOSING ANY MORE HAIR!!!!!!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top