Static routes to a second internal network

[Piloria]

we have a cisco 1603
with an isdn BRI and an internal lan port
i have been using the Cisco config manager

i can configure every thing except a correct static route
we have 2 internal networks
PC's in one network 10.0.0.0
Servers in another 192.168.0.0
With a network gateway connecting the two (dont ask why but we are in the middle of an ip address changeover)

all i want to do is put in a static route on the cisco
(which is in the 192 network)
so that it will comunicate with the PC's

i thought this would be simple enough but.....
when i try and do this throuhh the config manager it wont allow me to put in the network gateway address (IP address greyed out) for the next hop.
when i have tried using telnet and doing an
ip route 10.0.0.0 255.0.0.0 192.168.0.1
it just buggers up the ISDN configuration.

i am assuming i am doing this completely wrong but i am not a cisco person

 

[mgooder]

Logon to the cisco 1603, go to enable mode, (type en and the prompt after you logon). type show config and post the results. Also what is the ip address of the gateway for the PCs and servers?

Rico

 

[Frenchie2069]

You can not achieve this with a static route.

What you need to do is add 2 addresses to the internal interface, one in each network. These addresses will become the default gateway address for devices in each network.

I am not sure how to do this in Config Maker, but you can do it manually by logging in to the router and typing:

configure terminal
interface Ethernet0
ip address 10.x.y.z 255.255.255.0 secondary

(replace x.y.z with an address that is available in your PC network). Then press Ctrl-Z. If you are happy that this is working type in:

copy running-config startup-config

to save the config to NVRAM. If it is not working then you can either type reload (to reboot it and restore the previous config) or power off and back on again.

If you can find a way to add a secondary address to the interface in Config Maker that would obviously be much easier.

HTH,
Michael.

 

[ChrisAC]

Of course you can do this with static routes. These is no reason that putting in static routes should mess up your ISDN config.

ip route <dest_network> <mask> <gateway_address>

Post the config here with all the relevant details and we'll take a look.

Chris.



**********************
Chris Andrew, CCNA, CCSA
chris@iproute.co.uk
**********************

 

[Piloria]

! ******************************************************************
! Fakename.cfg - Cisco router configuration file
! Automatically created by Cisco ConfigMaker v2.6 Build 6
! 08 August 2003, 02:24:09 PM
!
! Hostname: Fakename
! Model: 1603
! ******************************************************************
!
service timestamps debug uptime
service timestamps log uptime
service password-encryption
no service tcp-small-servers
no service udp-small-servers
!
hostname Fakename
!
enable password fakeagain
!
no ip name-server
!
isdn switch-type basic-net3
!
ip subnet-zero
no ip domain-lookup
ip routing
!
interface Dialer 1
description connected to Internet
ip address 20.20.20.20 255.255.255.0
no ip directed-broadcast
no ip split-horizon
encapsulation ppp
dialer in-band
dialer idle-timeout 60
dialer string 555999999
dialer hold-queue 10
dialer load-threshold 10
dialer-group 1
ppp authentication chap pap callin
ppp chap hostname Fakename
ppp chap password fakepwd
ppp pap sent-username Fakename password fakepwd
ppp multilink
snapshot client 15 360 suppress-statechange-update dialer
no cdp enable
!
interface Ethernet 0
no shutdown
description connected to EthernetLAN
ip address 192.168.0.1 255.255.255.0
no ip directed-broadcast
keepalive 10
!
interface BRI 0
no shutdown
description connected to Internet
no ip address
no ip directed-broadcast
dialer rotary-group 1
!
! Dialer Control List 1
!
no dialer-list 1
dialer-list 1 protocol ip permit
!
router rip
version 2
network 192.168.0.0
passive-interface Dialer 1
no auto-summary
!
!
ip classless
!
! IP Static Routes
ip route 0.0.0.0 0.0.0.0 Dialer 1
no ip http server
snmp-server community public RO
no snmp-server location
no snmp-server contact
!
line console 0
exec-timeout 0 0
password fakepwd
login
transport input none
!
line vty 0 4
password fakepwd
login
!
end

 

[tschouten]

Config maker stinks, I wish it was never made (personal opinion). I don't see your 10.0.0.0 network in the config, so I am assuming this is off of another router? You may want to try adding Network 10.0.0.0 to your RIP configuration. Remember if you are just adding an ip route you need to make a route in both directions of traffic. From 10.0.0.0 to 192.168.0.0 as well as from 192.168.0.0 to 10.0.0.0 otherwise the packets are going to try to go out your gateway of last resort (because the router won't know where to place the returning packets) which you have set as your dialer. This is why you experience some problems with the single ip route configuration.

Hope that helps you out.

 

[Piloria]

i dont want to be using this as the default gateway between networks. our network is just fine as it is.
we have routing from the 10 to the 192 and backa again at the moment.
all i want to do is let the router know how to get to the 10 network via the current gateway (i.e. a static route)

i will scrubb the config and set it up again and then see if i ca add the static route again (as i tried before) and see if it buggers the isdn connection

 

[ChrisAC]

Take RIP off the router. There is no need for it! Then just add a route to the 10.0.0.0 network using ..

ip route 10.0.0.0 255.0.0.0 <gateway_ip>

On the router that connects the 192.168 network to the 10.0 network put a default route (to the internet) via the ethernet address of the 1603. The clients on the 10.0 network should have a default route via the router that connects the networks. Therefore the clients on this network will send out internet traffic to thier default route (network router) which will then send it to the 1603 which should then trigger the ISDN.

Last point, ditch config maker. It sucks!

Chris.


**********************
Chris Andrew, CCNA, CCSA
chris@iproute.co.uk
**********************

 

[tschouten]

Aggrees with Chris on all points.