Cisco Static Route Question

[yukon10]

I have two Cisco 1601's that are connected via T1. I didn't set these routers up and I do not know much about cisco. What I'm tryin to accomplish is add some new static routes without messing up the routes thats in their now. Is there a command where I can look at the routing tables as they are now? I put in new Wireless network at both locations that uses a different ip scheme and I can talk locally to my base network, but I can't get through my T1 because I need to add some routes. Can anyone tell me the basic procedure for adding the new routes without messing up the routes that are in place now? thanks in advance

 

[vipergg]

If you look at the running config you'll see the current static routes in the config , as long as you don't delete the current ones you won't break whats there . You can then just add the new static routes . You can also do a "show ip route static " command to see what is setup.

 

[yukon10]

hmm this is what I get

S 192.168.2.0/24 [1/0] via 10.100.100.2
S* 0.0.0.0/0 is directly connected, Ethernet0

my goal is to make it where my 172.16.31.0 can access the 192.168.2.0 network on the other side of my T1

right now my 192.168.1.0 and 172.16.31.0 are on one side and

192.168.2.0 and 172.16.32.0 are on the other

192.168.1.0 and 192.168.2.0 can talk now, but my 172.16.*.* can only talk to the local side.

 

[lgarner]

You've given 1/2 of the equation. Does the remote router have a route to 172.16.0.0/16 via your local router?

If your local router's T1 interface is 10.100.100.1, then the remote side should have:

S 192.168.1.0/24 [1/0] via 10.100.100.1
S 172.16.0.0/16 [1/0] via 10.100.100.1

 

[yukon10]

Right now the remote has this

S 192.168.1.0/24 [1/0] via 10.100.100.1
S* 0.0.0.0/0 is directly connected, Ethernet0

 

[lgarner]

Each router needs to know how to route all traffic that it must handle.

Your local router is fine, assuming that 192.168.2.0 is the only remote network.

Your remote router needs a static route to 172.16.0.0/16 via 10.100.100.1.

 

[avilov]

if your 192.168.1.0 and 172.16.31.0 can talk now than you have some sort of router in front of your cisco. what is that?

you would need to add static route there as well.

on 1st cisco you need to add the following
ip route 172.16.32.0 255.255.255.0 10.100.100.2


and

ip route 172.16.31.0 255.255.255.0 10.100.100.1

to the other

 

[yukon10]

S 192.168.2.0/24 [1/0] via 10.100.100.2
172.16.0.0/24 is subnetted, 1 subnets
S 172.16.32.0 [1/0] via 10.100.100.2
S* 0.0.0.0/0 is directly connected, Ethernet0



S 192.168.1.0/24 [1/0] via 10.100.100.1
172.16.0.0/24 is subnetted, 1 subnets
S 172.16.31.0 [1/0] via 10.100.100.1
S* 0.0.0.0/0 is directly connected, Ethernet0

 

[yukon10]

I have a Sonicwall TZ 170 on both ends as my firewall and router, and the Cisco's just Link the T1.. Sorry to not throw this in from the beginning. I appreciate you guys time

 

[lgarner]

So... is it working? From the routes that you show above the 4 networks should be communicating now. If not, then there's something else at work, like an ACL.

 

[yukon10]

Sonicwall TZ 170
IP 192.168.1.*
WLAN 172.16.31.*
CISCO is
IP 192.168.1.2**



REMOTE IS
Sonicwall TZ 170
IP 192.168.2.*
WLAN 172.16.32.*
CISCO is
IP 192.168.2.2**

 

[yukon10]

I think i have the Cisco down, but do I need the same routes in the Sonicwall?

 

[avilov]

if your sonic fw has default route pointing to the cisco you should be fine if not you need to add a static route.

 

[yukon10]

My default route points to my Cisco 1700 which is my internet gateway.. then i have the following Static routes entered

172.16.32.0 255.255.255.0 192.168.1.2** WLAN
192.168.2.0 255.255.255.0 192.168.1.2** LAN

 

[lgarner]

If the Sonicwall's default route is the connected Cisco, then you don't need static routes on it. It will forward every packet to the Cisco that's not destined for a connected network.

The Cisco will need a static route to the local wireless network, though, since it has no way of knowing what's on the other side of the sonicwall.

Example:
! route to remote wireless via T1
ip route 172.16.31.0 255.255.255.0 10.100.100.1
! route to remote LAN via T1
ip route 192.168.1.0 255.255.255.0 10.100.100.1
! route to local wireless via sonicwall
ip route 172.16.32.0 255.255.255.0 192.168.2.2

 

[yukon10]

Now my Default route is going to my internet Gateway which is a different T1 than my pt. to pt. So my default route is not the Cisco 1601 which is my pt. to pt.

 

[yukon10]

S 192.168.1.0/24 [1/0] via 10.100.100.1
172.16.0.0/24 is subnetted, 2 subnets
S 172.16.32.0 [1/0] via 192.168.2.50
S 172.16.31.0 [1/0] via 10.100.100.1
S* 0.0.0.0/0 is directly connected, Ethernet0

this is on my remote side now

correct or no?

 

[lgarner]

I'd suggest picking up a primer on routing. Then you'll have an understanding of what it is and how to set it up, and the details won't be confusing.

Basically, each router has to know which connected neighbor to send a packet to in order to help that packet along it's path. If the default route isn't correct, then another route must be added.

So, the Sonicwall must know which neighbor will handle packets for the remote LAN, and which will handle those destined for other networks. If you draw it out, you'll be able to see which routes need to be added.

 

[yukon10]

Well I put the other routes in for Local and they work fine, its just the Wireless routes that i'm having problems with, but thanks for everyones help. I'll just poke at it a while.

 

[lgarner]

That's the best way. Like I said, if you break it down to small steps, it'll seem logical.

I did want to add one thing that can be a "gotcha": Communication is 2-way. Remember to check both sides completely, since an apparent failure from point A to point B might really be a problem from B to A.