cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
522
Views
0
Helpful
8
Replies

Routing probs

advnettech
Level 1
Level 1

I have a network 10.26.7.0 on SideB connected to SideA via 2 1601R with a HDLC connection. SideA has ip scheme of 10.166.53.0 subnets on both SideA & SideB is 255.255.255.0 The HDLC is 192.168.245.1,2

On SideA we also have a firewall 10.166.53.101.

Is it possible to run them all on the 10.166.53.0 scheme?

Rip is enabled but do I still need to use static routing on all the routers?

Is it possible to route between the nets to be able to go to a machine on either side of the HDLC (ie.. 10.166.53.33 connect to 10.26.7.194?

I apologize for my ignorance I got dumped into this mess and I'm flying by the seat of my pants.

8 Replies 8

lgijssel
Level 9
Level 9

Hello,

Your first question is not clear to me:

1: Is it possible to run them all on the 10.166.53.0 scheme? What do want to do with this IP-range?

2: Rip is enabled but do I still need to use static routing on all the routers? When using a routing protocol, the need for static routes is reduced. Rip is not the best choice though. I would recommend EIGRP or OSPF. Of these two, eigrp is the easiest to configure. I assume that you will still need one static default route pointing to the firewall. (ip route 0.0.0.0 0.0.0.0 10.166.53.101)

3: Is it possible to route between the nets to be able to go to a machine on either side of the HDLC (ie.. 10.166.53.33 connect to 10.26.7.194?

Yes, this is exactly what routing is about.

Regards,

Leo

?3. I can ping from router to router fine. But when I try to ping from say routerA(10.166.53.251) to 10.26.7.194 I get no replys. Traceroute shows it goes to RouterB serial port but no farther. Ip Routing is turned on.

Here's the 2 configs

! ******************************************************************

! Cisco1601.cfg - Cisco router configuration file

! Automatically created by Cisco ConfigMaker v2.6 Build 6

! Thursday, February 26, 2004, 03:50:33 AM

!

! Hostname: Cisco1601

! Model: 1601

! ******************************************************************

!

service timestamps debug uptime

service timestamps log uptime

service password-encryption

no service tcp-small-servers

no service udp-small-servers

!

hostname Cisco1601

!

enable password 7 14041B071A0138

!

no ip name-server

!

ip subnet-zero

no ip domain-lookup

ip routing

!

interface Ethernet 0

no shutdown

description connected to Internet

ip address 10.166.53.251 255.255.255.0

keepalive 10

!

interface Serial 0

no description

no ip address

shutdown

!

interface Serial 1

no shutdown

description connected to Hickey

service-module t1 clock source line

service-module t1 data-coding normal

service-module t1 remote-loopback full

service-module t1 framing esf

service-module t1 linecode b8zs

service-module t1 lbo none

service-module t1 remote-alarm-enable

ip address 10.10.10.1 255.255.255.252

encapsulation hdlc

!

router rip

version 2

network 10.0.0.0

passive-interface Ethernet 0

auto-summary

!

!

ip classless

!

! IP Static Routes

ip route 0.0.0.0 0.0.0.0 Ethernet 0

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 7 071C2840580C0B

login

!

line vty 0 4

password 7 071C2840580C0B

login

!

! The following commands are not recognized by Cisco ConfigMaker

! and are therefore appended here.

!

no service single-slot-reload-enable

ip default-gateway 10.166.53.101

!

end

! ******************************************************************

! Hickey.cfg - Cisco router configuration file

! Automatically created by Cisco ConfigMaker v2.6 Build 6

! Thursday, February 26, 2004, 03:53:56 AM

!

! Hostname: Hickey

! Model: 1601

! ******************************************************************

!

service timestamps debug uptime

service timestamps log uptime

service password-encryption

no service tcp-small-servers

no service udp-small-servers

!

hostname Hickey

!

enable password 7 095F47050F0005

!

no ip name-server

!

ip subnet-zero

no ip domain-lookup

ip routing

!

interface Ethernet 0

no shutdown

description connected to EthernetLAN

ip address 10.26.7.251 255.255.255.0

keepalive 10

!

interface Serial 0

no description

no ip address

shutdown

!

interface Serial 1

no shutdown

description connected to Cisco1601

service-module t1 clock source line

service-module t1 data-coding normal

service-module t1 remote-loopback full

service-module t1 framing esf

service-module t1 linecode b8zs

service-module t1 lbo none

service-module t1 remote-alarm-enable

ip address 10.10.10.2 255.255.255.252

encapsulation hdlc

!

router rip

version 2

network 10.0.0.0

no auto-summary

!

!

ip classless

!

! IP Static Routes

ip route 10.26.7.0 255.255.255.0 Ethernet 0 permanent

ip route 10.26.7.0 255.255.255.0 Serial 1 permanent

ip route 10.166.53.0 255.255.255.0 10.166.53.101

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 7 105D0015131200

login

!

line vty 0 4

password 7 105D0015131200

login

!

! The following commands are not recognized by Cisco ConfigMaker

! and are therefore appended here.

!

no service single-slot-reload-enable

ip default-gateway 10.166.53.101

!

end

I think you need to either use static routes *or* RIP, not both. The static routes you have are causing you problems I think.

Note, when you have both RIP routes and static routes to the same network, the static routes are used, not the RIP ones. Also EIGRP is a better protocol to use than RIP if you are going to use one.

In the scenario you have I suggest not using RIP or EIGRP at all, you only have 2 routers and thus a routing protocol is overkill for your needs.

To fix the configs to use only static routes do this:

On router #1 from above, get to # prompt (enable mode) and paste this in:

conf t

no router rip

no ip route 0.0.0.0 0.0.0.0 Ethernet 0

no ip default-gateway 10.166.53.101

ip route 10.26.7.0 255.255.255.0 10.10.10.2

ip route 0.0.0.0 0.0.0.0 10.166.53.101

On router #2 from above, get to # prompt (enable mode) and paste this in:

conf t

no router rip

no ip route 10.26.7.0 255.255.255.0 Ethernet 0 permanent

no ip route 10.26.7.0 255.255.255.0 Serial 1 permanent

no ip route 10.166.53.0 255.255.255.0 10.166.53.101

ip route 0.0.0.0 0.0.0.0 10.10.10.1

-HTH

still won't let me ping past the routers themselves.

New configs

RouterA

!

version 12.1

no service single-slot-reload-enable

service timestamps debug uptime

service timestamps log uptime

service password-encryption

!

hostname Cisco1601

!

enable password 7 14041B071A0138

!

!

!

!

!

ip subnet-zero

no ip domain-lookup

!

!

!

!

interface Ethernet0

description connected to EthernetLAN

ip address 10.166.53.251 255.255.255.0

!

interface Serial0

no ip address

shutdown

!

interface Serial1

description connected to Hickey

ip address 10.10.10.1 255.255.255.252

service-module t1 remote-alarm-enable

!

ip classless

ip route 0.0.0.0 0.0.0.0 10.166.53.101

ip route 0.0.0.0 0.0.0.0 10.26.7.251

ip route 10.26.7.0 255.255.255.0 10.10.10.2

no ip http server

!

snmp-server community public RO

!

line con 0

exec-timeout 0 0

password 7 071C2840580C0B

login

line vty 0 4

password 7 071C2840580C0B

login

!

end

RouterB

!

version 12.1

no service single-slot-reload-enable

service timestamps debug uptime

service timestamps log uptime

service password-encryption

!

hostname Hickey

!

enable password 7 095F47050F0005

!

!

!

!

!

ip subnet-zero

no ip domain-lookup

!

!

!

!

interface Ethernet0

description connected to EthernetLAN_1

ip address 10.26.7.251 255.255.255.0

!

interface Serial0

no ip address

shutdown

!

interface Serial1

description connected to Cisco1601

ip address 10.10.10.2 255.255.255.252

service-module t1 remote-alarm-enable

!

ip default-gateway 10.166.53.101

ip classless

ip route 0.0.0.0 0.0.0.0 10.166.53.101

ip route 0.0.0.0 0.0.0.0 10.166.53.251

ip route 0.0.0.0 0.0.0.0 10.10.10.1

no ip http server

!

snmp-server community public RO

!

line con 0

exec-timeout 0 0

password 7 105D0015131200

login

line vty 0 4

password 7 105D0015131200

login

!

end

You still have too many routes on the routers.

On Router A you need to remove:

ip route 0.0.0.0 0.0.0.0 10.26.7.251

On Router B you need to remove:

ip default-gateway 10.166.53.101

ip route 0.0.0.0 0.0.0.0 10.166.53.101

ip route 0.0.0.0 0.0.0.0 10.166.53.251

I'm assuming your Internet connection is on router A ethernet 0.

Here's what your configs should look like:

RouterA

!

version 12.1

no service single-slot-reload-enable

service timestamps debug uptime

service timestamps log uptime

service password-encryption

!

hostname Cisco1601

!

enable password xxxxx

!

!

!

!

!

ip subnet-zero

no ip domain-lookup

!

!

!

!

interface Ethernet0

description connected to EthernetLAN

ip address 10.166.53.251 255.255.255.0

!

interface Serial0

no ip address

shutdown

!

interface Serial1

description connected to Hickey

ip address 10.10.10.1 255.255.255.252

service-module t1 remote-alarm-enable

!

ip classless

ip route 0.0.0.0 0.0.0.0 10.166.53.101

ip route 10.26.7.0 255.255.255.0 10.10.10.2

no ip http server

!

snmp-server community public RO

!

line con 0

exec-timeout 0 0

password xxxx

login

line vty 0 4

password xxxx

login

!

end

RouterB

!

version 12.1

no service single-slot-reload-enable

service timestamps debug uptime

service timestamps log uptime

service password-encryption

!

hostname Hickey

!

enable password xxxx

!

!

!

!

!

ip subnet-zero

no ip domain-lookup

!

!

!

!

interface Ethernet0

description connected to EthernetLAN_1

ip address 10.26.7.251 255.255.255.0

!

interface Serial0

no ip address

shutdown

!

interface Serial1

description connected to Cisco1601

ip address 10.10.10.2 255.255.255.252

service-module t1 remote-alarm-enable

!

ip classless

ip route 0.0.0.0 0.0.0.0 10.10.10.1

no ip http server

!

snmp-server community public RO

!

line con 0

exec-timeout 0 0

password xxxxx

login

line vty 0 4

password xxxxx

login

!

end

Also it depends on where you are initiating pings and what you are pinging. If you are trying to ping from the Router A ethernet segment to the Router B ethernet segment, make sure you PC default gateway is Router A ethernet 0's IP-10.166.53.251 and it's mask is 255.255.255.0 and your PC has an IP in the 10.166.53.x range. Same thing on the Router B ethernet segment. All machines on the Router B ethernet segment should have an IP in the 10.26.7.x range and have a default gateway of 10.26.7.251 and a subnet mask of 255.255.255.0.

Also make sure you test from the routers themselves. From Router A make sure you can ping 10.10.10.2 and 10.26.7.251.

HTH

Copied the configs and still no luck. I can telnet into routerA or B and ping both of the interfaces of the opposite router. But when I try to ping from routerA to a client on the other side of B no response. When I then do a traceroute to that client it stops at B's serial interface and goes no further.

From a PC on Router A's ethernet segment, can you ping Router B's ethernet IP address (10.26.7.251)?

From a PC on Router B's ethernet segment, can you ping Router B's ethernet IP address (10.26.7.251)?

From a PC on Router B's ethernet segment, can you ping Router B's serial IP of 10.10.10.2?

From a PC on Router B's ethernet segment, can you ping Router A's serial IP of 10.10.10.1?

From a PC on Router B's ethernet segment, can you ping Router A's ethernet IP of 10.166.53.251?

Sounds like the default gateway/mask is incorrect on the hosts on the ethernet segment of Router B.

HTH

I agreed with the last post and I think there is a problem with the default gateway on the hosts. Ping uses ICMP echo reply and because of the incorrect configuration of the default gateway the ping does not know how to get back where the ping came from. Please check if the default gateway of the hosts is the ethernet interface of the router on that same segment.

amj