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 derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

cisco routing help

Status
Not open for further replies.

hb12498

MIS
Joined
Apr 30, 2006
Messages
3
Location
US
I have a cisco routing config question. I am attempting two routers on the same physical lan. Router 1 is on an existing network with internet connectivity on Serial0/0. 192.168.100.XXX LAN connectivity is on FE0/0. I am putting up a different subnet 192.168.0.XXX on router 2. This has 2 ethernet ports. I have port a at 192.168.100.248 and port b at 192.168.0.238. I am running rip and have defined the 2 networks as 192.168.0.0 and 192.168.100.0. I can ping any ip off either subnet from the router but I can't ping anything on subnet 192.168.100.xxx from a computer on 192.168.0.XXX which can ping the port b interface but not the port a interface. IP route is on. Thanks for any aid.
 
hb12498,

Post your config (without passwords etc.)

It will be much easier to see what might be wrong!



E.A. Broda
CCNA, CCDA, CCAI, Network +
 
Make sure you have the right default gateways and subnet masks on the PCs on the 192.168.100.xxx LAN. It's possible that they just don't know how to get off of their own subnet.
 
hb,
..i have tried to draw out the topology as you have explaned it.

..but i'm not seeing the picture...

Are you saying on router "2" has two fe ports. one with sub 192.168.100.0 and the other 192.168.0.0

..and router 1 also has subnet 192.168.100.0

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

...i will say in my past lab experiences i have had routing issues dealing with 192.168.0.0 subnet..i think this is just my little hang up though.





CCNP,CCSP,MCSE,Sec+,Net+,A+...
 
check your RIP statement on the routers, has to be on both, and make sure you haven't got a 255.255.0.0 class B mask on hte statement, if the RIP config looks good, take off RIP and replace with static routing, if it still doesn't work it must be the addressing sceme on the pc's.
 
Here are the configs. Cisco 2600 first then Cisco 2610.

Current configuration : 793 bytes
!
version 12.3
service timestamps debug datetime msec
service timestamps log datetime msec
no service password-encryption
!
hostname Cisco-db
!
boot-start-marker
boot-end-marker
!
enable secret
enable password
!
no aaa new-model
ip subnet-zero
!
!
!
ip audit notify log
ip audit po max-events 100
!
!
!
!
interface Ethernet0/0
ip address 192.168.0.238 255.255.255.0
half-duplex
!
interface Ethernet0/1
ip address 192.168.100.248 255.255.255.0
half-duplex
!
router rip
network 192.168.0.0
network 192.168.100.0
!
no ip http server
no ip http secure-server
no ip classless
!
!
!
snmp-server community public RO
snmp-server enable traps tty
!
!
!
!
!
line con 0
line aux 0
line vty 0 4
password
login
!
!
!
end

Next Cisco 2610

Current configuration : 2451 bytes
!
version 13.3
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname Cisco2610
!
boot-start-marker
boot-end-marker
!
enable secret
enable password
!
no aaa new-model
ip subnet-zero
!
!
!
ip inspect name ethernet_0_0 ftp
ip inspect name Ethernet_0_0 smtp
ip inspect name Ethernet_0_0 udp
ip inspect name Ethernet_0_0 tcp
ip audit notify log
ip audit po max-events 100
!
!
!
!
interface Ethernet0/0
description Connected to Ethernet Lan
ip address 192.168.100.180 255.255.255.0
ip nat inside
no ip mroute-cache
full-duplex
no cdp enable
!
interface Serial0/0
description connected to Internet
ip address 13.134.198.158 255.255.255.252
ip access-group 101 in
ip nat outside
encapsulation ppp
no ip mroute-cache
service-module t1 remote-alarm-enable
!
interface Ethernet0/1
no ip address
shutdown
half-duplex
!
ip nat inside source list 2 interface Serial0/0 overload
ip nat inside source static 192.168.100.230 13.42.99.250
ip nat inside source static 192.168.100.216 13.42.99.249
ip nat inside source static 192.168.100.217 13.42.99.248
ip nat inside source static 192.168.100.218 13.42.99.247
ip nat inside source static 192.168.100.219 13.42.99.246
ip nat inside source static 192.168.100.220 13.42.99.245
ip nat inside source static 192.168.100.231 13.42.99.244
ip nat inside source static 192.168.100.215 13.42.99.243
ip nat inside source static 192.168.100.225 13.42.99.242
no ip http server
no ip http secure-server
ip classless
ip route 0.0.0.0 0.0.0.0 13.134.198.157
!
!
access-list 2 permit 192.168.100.0 0.0.0.255
access-list 101 permit tcp any host 13.134.197.158 eq telnet
access-list 101 permit icmp any any echo
access-list 101 permit icmp any any echo-reply
access-list 101 permit tcp any any established
access-list 101 permit tcp any any eq www
access-list 101 permit tcp any any eq smtp
access-list 101 permit tcp any any eq pop3
access-list 101 permit tcp any any eq ftp-data
access-list 101 permit tcp any any eq ftp
access-list 101 permit udp any eq domain any
access-list 101 permit tcp any gt 1023 any eq ftp-data
access-list 101 permit tcp any any gt 1023
access-list 101 permit tcp any host 192.168.100.216 eq 8080
!
snmp-server community imagewerks RW
snmp-server enable traps tty
!
!
!
!
!
line con 0
line aux 0
line vty 0 4
password
login
!
!
!
end
 
ok you don't have RIP running on the 2610, so you wont be broadcasting the networks, also you have the statement of "no ip classless" on the 2600 which will negate the RIP protocol running correctly.

take RIP off altogether and put static route statements in each router, you would need to put a statement in the 2610 pointing the 192.168.0.0 /24 network via the 192.168.100.248 interface.

and a default route on the 2600 pointing at the 192.168.100.180 interface.
 
What do you mean that "no ip classless" will negate RIP? RIP is a routing protocol, and as such, it influences which routes are installed into the routing table. The "[no] ip classless" command changes the search behavior of the router when doing routing lookups against routes that are already in the table.

Can you explain what you mean by your statement?

As an FYI to all, "ip classless" is the best way to go. Any other setting will eventually result in route lookup behavior that is less than intuitive.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top