I have a point to point T1 line from one location to another. They both have a cisco router on each end. I was asked to install a firewall on a dsl connection so they can create a VPN and get out to the internet because there is no internet connection on the point to point T1 line. The main office has the internet connection but the remote office does not. All 3 Windows servers gateway point to the point to point T1 router instead of the dsl connection. How can I get at least one server on the dsl gateway without messing up the point to point connection? I need to point the servers towards the dsl connection which has a sonicwall on the dsl. The client does not want to spend any money on anything except for tech time to get it working with what they have. The remote office does not have any access to the internet.
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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
T1 Point to Point connection
- Thread starter bsl1234
- Start date
If I read your question correctly there are 2 easy ways.
1. Change the default Gateway on the servers to the DSL connection and then create static route(s) for the subnet(s) at the second site and point them to the point-to-point Cisco router.
2. Add a static default route on the Cisco T1 router and point it to the DSL router. Also make sure ICMP redirects are enabled on the Cisco T1 router.
In my opinion though the best way would be to add another Ethernet interface to the Cisco T1 router and put the DSL router here on another subnet (/30 point-to-point should suffice). You would obviously need to run either a routing protocol (preferred) or get the static routing tables setup correctly.
Either that or implement some (a) layer-3 switches and put a bit of a design together.
This is all real easy stuff for a network person, so if you are not too familiar with IP routing and routers (& switches) then get someone in.....
Andy
1. Change the default Gateway on the servers to the DSL connection and then create static route(s) for the subnet(s) at the second site and point them to the point-to-point Cisco router.
2. Add a static default route on the Cisco T1 router and point it to the DSL router. Also make sure ICMP redirects are enabled on the Cisco T1 router.
In my opinion though the best way would be to add another Ethernet interface to the Cisco T1 router and put the DSL router here on another subnet (/30 point-to-point should suffice). You would obviously need to run either a routing protocol (preferred) or get the static routing tables setup correctly.
Either that or implement some (a) layer-3 switches and put a bit of a design together.
This is all real easy stuff for a network person, so if you are not too familiar with IP routing and routers (& switches) then get someone in.....
Andy
- Thread starter
- #3
To add a default route in global config (i.e. conf t)add:
router(config)#ip route 0.0.0.0 0.0.0.0 192.168.1.1
To enable ICMP redirects (on by default) add the following to the Ethernet Interface of your router:
router(config-if)#ip redirects
What should happen here is if a device sends an IP packet to the default router and it knows where to forward the packet to, but the next-hop is on the same IP subnet (segment) as the device that send the packet. It will forward the packet but will also send an ICMP redirect to the host informing it that a different gateway on the same subnet should be used. The host can either ignore this ICMP packet and continue sending packets to the default gateway or will update its routing table to reflect this new route. The problem being here is that the host creates /32 host routes so will build a huge local routing table.
If you don't want to implement this 'properly' then personally I would change the default gateway on the hosts and add static routes for the networks on the other end of the T1.
Andy
router(config)#ip route 0.0.0.0 0.0.0.0 192.168.1.1
To enable ICMP redirects (on by default) add the following to the Ethernet Interface of your router:
router(config-if)#ip redirects
What should happen here is if a device sends an IP packet to the default router and it knows where to forward the packet to, but the next-hop is on the same IP subnet (segment) as the device that send the packet. It will forward the packet but will also send an ICMP redirect to the host informing it that a different gateway on the same subnet should be used. The host can either ignore this ICMP packet and continue sending packets to the default gateway or will update its routing table to reflect this new route. The problem being here is that the host creates /32 host routes so will build a huge local routing table.
If you don't want to implement this 'properly' then personally I would change the default gateway on the hosts and add static routes for the networks on the other end of the T1.
Andy
- Status
Similar threads
- Locked
- Question