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 strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

new install sr1002 T1 Point to Point issue can't ping devices accross WAN

Status
Not open for further replies.

telecotek1

Vendor
Nov 13, 2007
390
US
If I telnet into the main site I can ping eth0 accross the wan but nothing beyond eth0. The same holds true for ping from the remote sites back to any IP at the main. tracert shows the ping dieing at the oposite wan ip.

Main Site
module t1 1
exit t1
interface ethernet 0
ip address 192.168.1.245 255.255.255.0
qos
exit qos
exit ethernet
interface ethernet 1
qos
exit qos
exit ethernet
interface bundle WAN
link t1 1
encapsulation ppp
ip address 192.168.254.1 255.255.255.0
ip multicast ospfrip2
qos
Press any key to continue (q : quit) :

exit qos
pppconfig mtu-mru-magic mru 1500-1518-4500
pppconfig peer-addr 192.168.254.2
pppconfig src-addr 192.168.254.1
red
exit red
exit bundle
route 192.168.2.0 255.255.255.0 192.168.254.2 10

remote
-------------------------------------------------------------------------------------
module t1 1
clock_source line
exit t1
interface ethernet 0
ip address 192.168.2.250 255.255.255.0
qos
exit qos
exit ethernet
interface ethernet 1
qos
exit qos
exit ethernet
interface bundle WAN
link t1 1
encapsulation ppp
ip address 192.168.254.2 255.255.255.0
ip multicast ospfrip2
qos
exit qos
pppconfig mtu-mru-magic mru 1500-1518-4500
pppconfig peer-addr 192.168.254.1
pppconfig src-addr 192.168.254.2
red
exit red
exit bundle
ip
load_balance per_flow
route 192.168.1.0 255.255.255.0 192.168.254.1 10
route 0.0.0.0 0.0.0.0 192.168.254.1 1
route 0.0.0.0 0.0.0.0 192.168.2.245 1

 
Do the devices at the main site have 192.168.1.245 as their default gateway, and do devices at the remote have 192.168.2.250 as their gateway?
 
i suspect that the "route 0.0.0.0 0.0.0.0 192.168.2.245 1" is causing the problem as you are potentially sending all traffic destined for the main site out of the remote sites lan interface

You only need one route configured on the remote site which will cover all traffic
route 0.0.0.0 0.0.0.0 192.168.254.1 1

The other two need to be deleted
route 192.168.1.0 255.255.255.0 192.168.254.1 10 - this route is doing nothing
route 0.0.0.0 0.0.0.0 192.168.2.245 1 - this route is sending traffic out of the lan interface
 
In the end it was th ip routes that needed to be modified. I also wound up using a much more simplified config too. Thanks guys for checking in tho.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top