Cisco IOS Simple help.

B

bigstusexy

2[H]4U
Joined
Jan 28, 2002
Messages
3,194
I need some help, basically I need to set a static route on a cisco router... problem is that I don't know that much about IOS yet. I know how to set static routes in windows, in RRAS and the knowledge behind it in general.

I know all the passwords just need to know what id type. Anyone want to talk me through what to do after I use the enable password? I thought it would be

ip route dest mask gateway (ip route 10.18.0.0 255.255.0.0 172.18.100.1)

IOS Version 11.3(10)T
Running on a 2600

Nothing would be a problem too since I won't write the running config till I am sure everything is OK.
 
post a "sh run" and tell us what you're trying to route where.


if you're trying to route 10.18.0.0/16 to next hop 172.18.100.1 it would be:

conf t

ip route 10.18.0.0 255.255.0.0 172.18.100.1

make sure that the 172.18.100.1 isn;t the ip address of your local interface on that router, it has to be the next hop address on that 172.18.100.1 network.
 
Code: 
Building configuration...

Current configuration:
!
version 11.3
service config
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname NHS
!
!
!
!
process-max-time 200
!
interface Ethernet0/0
 ip address 172.18.1.254 255.255.0.0
 no cdp enable
!
interface Serial0/0
 ip address 192.168.35.254 255.255.255.0
 no ip route-cache
 no ip mroute-cache
 no fair-queue
!
interface Serial0/1
 ip address 192.168.36.254 255.255.255.0
 no ip route-cache
 no ip mroute-cache
 no fair-queue
!
ip classless
no ip forward-protocol udp tftp
no ip forward-protocol udp domain
no ip forward-protocol udp time
no ip forward-protocol udp netbios-ns
no ip forward-protocol udp netbios-dgm
no ip forward-protocol udp tacacs
ip route 0.0.0.0 0.0.0.0 192.168.36.253
ip route 0.0.0.0 0.0.0.0 192.168.35.253
!
dialer-list 1 protocol ip permit
dialer-list 1 protocol ipx permit
!
line con 0
 exec-timeout 0 0
line aux 0
line vty 0 4
 login
!
end

I removed three lines dealing with passwords.

Yeah its not I'll give you a quick diagram.

|Main office 172.16.x.x|(Router 172.16.1.250 * 192.168.1.1)<--192.168.x.x via T1 -->(Router 192.168.35.254 & 36.254)|Remote office 172.18.x.x (windows router 172.18.100.1 10.18..0.1)|Lab 10.18.x.x|

Hope you understand that. Basically the 10.18 netowrk was seperate from our local 172 networks, we decided to join with with turning their server into a router, the only thing is that the gateway for the local 172.18 network doesn't know how to get back to the 10.18 network thanks to no dynamic routing, heck it doesn't even get route lists from the main router which as been updated with these routes.
 
Tried it and it works, the only thing now is I can't get to the serial interface ips thusly only to the local net. The lab router has a static default route of 0.0.0.0 0.0.0.0 172.18.1.254.

Should I be throwing all unknown traffic at 18.1.254? From there i should throw all its unknown traffic over the serials and thusly to teh core router which knows about this subnet getting it back and forth to the interent.... Because I can't ping across the router leaves me to believe that I've got my route wrong somewhere, at least I can ping the 172.18 side of the route



pinging from outer to 10.18 router works
pinging from 10.18 router to 172.18 network works.
ping to 192.168.36.254 from 10.18 fails.


Sometimes I dislike windows... I didn't check which interface it was going to put the route on, so it put it on the inside interface and not the outside... WRONG!



wr mem.
 
Ok, just a cursory look over what you wrote....it looks like the 10.18.xxx.xxx network didn't know how to get to 192.168.35 and 192.168.36 networks. Whatever default route you set up on the windows router isn't pointing in the direction of 172.18 network. Just add a static route into the windows router pointing in the correct direction and it should work.
 
Its actually works now, because the route was put on the wrong interface on the windows box it wasn't working. When yo type in ping, it will ping using whatever (maybe all I'm not sure) interfaces, the route back to the server/router worked at least because the Cicso router's route was correct. As soon as I placed it on the outside interface (where it should have been in the first place) it all works flawlessly. I was working remotely and all clients are either firewalled or off so I couldn't test to and from clients on the network but I'm sure they will be fine. Haven't written the config yet until I get hands on actual clients.

Thanks for all your help. Now hopefully the drop was done for the final building and I can get that one done too.
 
You must log in or register to reply here.
Back
Top