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!

Point to Point cant talk to internet

Status
Not open for further replies.

t7fire

MIS
Jan 13, 2007
24
US
Greetings,

We have just added a new site with a p2p T1. I can pass traffic over the t1 both ways, however i cant pass traffic from far end to the internet. Below is our config. Our Main site uses FreeBSD (192.168.1.3) as our internet router. We pass two networks over this T1 is 10.10.x.x (phone system) 192.168.1.x/24 (main office network). Our new network at the remote site is 192.168.10.x/23 We pass all traffic from the Remote Site to the Main site and plan to break out the different traffic at the Main Site.

I did not config these routers as I am just starting to learn cisco.

How do I tell the router to use 192.168.1.3 to pass internet traffic

Router1 (Main Office)

memory-size iomem 25
ip subnet-zero
!
!
no ip domain lookup
!
!
!
!
class-map match-any voip
match ip rtp 11000 13000
match ip dscp ef
match ip dscp cs5
class-map match-any voipin
match ip dscp ef
match access-group 106
!
!
policy-map voip
class voipin
set precedence 5
policy-map Voip1
class voip
priority 1000
class class-default
fair-queue
!
!
!
interface FastEthernet0
description connected to Neil St. LAN_2
ip address 192.168.1.254 255.255.255.0 secondary
ip address 10.10.10.30 255.255.255.0
service-policy input voip
service-policy output Voip1
speed auto
full-duplex
!
interface Serial0
description connected to chkenrtr
bandwidth 1536
ip address 172.16.10.1 255.255.255.252
service-policy input voip
encapsulation ppp
service-module t1 clock source internal
service-module t1 remote-alarm-enable
!
!
ip classless
ip route 10.10.30.0 255.255.255.0 Serial0
ip route 192.168.10.0 255.255.254.0 Serial0
no ip http server
!
access-list 106 permit udp any any eq 2944
access-list 106 permit tcp any any eq 2944
access-list 106 permit udp any any eq 3000
access-list 106 permit udp any any eq 4029
access-list 106 permit tcp any any eq 4029
access-list 106 permit tcp any any eq 1720
snmp-server community public RO
snmp-server enable traps tty




Router2 (Remote Site)
ip subnet-zero
no ip domain-lookup
!
!
!
interface Ethernet0/0
description connected to Kenyon Rd. LAN
ip address 10.10.30.1 255.255.255.0
!
interface Serial0/0
description connected to chneilrtr
ip address 172.16.10.2 255.255.255.252
ip rtp header-compression
ip rtp reserve 16384 100 1000
encapsulation ppp
no ip mroute-cache
bandwidth 1536
service-module t1 remote-alarm-enable
!
interface Ethernet0/1
ip address 192.168.10.254 255.255.254.0
!
ip classless
ip route 0.0.0.0 0.0.0.0 Serial0/0
snmp-server community public RO
 
That should just be a matter of adding an ip route, but I'm slightly confused by what you said. Do you want all your traffic at passed to the main site including Internet traffic or do you have an Internet connection somewhere at the remote site?
 
i think hes saying he wants all traffic to go to the main site.. and the main site can decide what to do with it

so basically youll need

ip route 0.0.0.0 0.0.0.0 Serial0
 
That is correct, from the remote site, I want to pass all traffic to the main site. There is a plan to add a internet circuit but it will not land in time. The trafic flow goes as follows

Remote Site PC (192.168.10.xx - Remote Site Router (192.168.10.254) - Remote Site T1 - Main Site T1 - Main site router (192.168.1.254)

From the remote site I can talk to the 192.168.1.x network but I cant pass traffic to the internet (192.168.1.3) I have tried

ip route 192.168.1.0 255.255.255.0 192.168.1.3

but I am not sure that is correct
 
to go to the internet you will need a default route

because the internet is not 192.168.1.3 even though that is your gateway to the internet.. as far as your remote router is concerned the internet is 0.0.0.0 0.0.0.0 serial0
which is basically saying any route that i dont know pass this way...

your main site already knows about your remote networks so nothing should need to be changed at the main site.
 
All traffic is passing from the remote site to the main site (see Router2 config) the problem lies at the main site route of how to tell that router what to do with traffic

Ping from remote site

C:\>tracert
Tracing route to [64.233.167.99]
over a maximum of 30 hops:

1 2 ms 3 ms 3 ms 192.168.10.254
2 7 ms 7 ms 7 ms 172.16.10.1
3 172.16.10.1 reports: Destination host unreachable.

Trace complete.

C:\>
 
so what do your clients at the main site use as their default gateway?

your main router doesn't have a default route or rotuing protocol so it doesn't know where google is...
you need to stick a default route pointing to either your gateway router/proxyserver or the next hop address of your isp
 
you need to add a default route to the main site router,

conf t;
mainsite router# add route 0.0.0.0 0.0.0.0 192.168.1.3

then this device should route the traffic to the internet.
 
You will need a default route out to the internet. A problem I have seen is that the remote end sometime needs a route back to you as well. I use the term I'm knocking but no-one is letting me in.

Type show ip route after inserting your route statement and review the output to verify your routing table. Good Luck!

“Reserve your right to think, for even to think wrongly is better than not to think at all”

CCNA,CCNP,Network+
Tek-TIP Member 19,650
[americanflag]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top