newbie needs basic routing help

[uthorns]

I'm new at this and would appreciate any help.
I can't get traffic to pass through the ethernet interfaces, can someone look at the config below and let me know what I'm doing wrong. Thanks.

Current configuration:
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname bbcs_router
!
enable secret 5 $1$Wjx0$hUl/BIj5jbMbWA5doB1vl0
!
memory-size iomem 20
ip subnet-zero
!
!
!
!
!
interface FastEthernet0/0
ip address 192.168.100.100 255.255.255.0
no ip directed-broadcast
!
interface Serial0/0
no ip address
no ip directed-broadcast
no ip mroute-cache
shutdown
!
interface FastEthernet0/1
ip address 192.168.102.1 255.255.255.0
no ip directed-broadcast
!
ip classless
ip route 0.0.0.0 0.0.0.0 FastEthernet0/0
ip route 192.168.100.0 255.255.255.0 FastEthernet0/0
no ip http server
!
!
!
line con 0
password 7 13071601185D55787B
transport input none
line aux 0
line vty 0 4
password 7 104C080A164643595C
login
line vty 5 133
password 7 104C080A164643595C
login
!
no scheduler allocate
end


bbcs_router#sh ip route

Gateway of last resort is 0.0.0.0 to network 0.0.0.0

C 192.168.102.0/24 is directly connected, FastEthernet0/1
C 192.168.100.0/24 is directly connected, FastEthernet0/0
S* 0.0.0.0/0 is directly connected, FastEthernet0/0

 

[lgarner]

Looks OK. What's happening? Do devices on either side have their default gateways set to their respective router interface addresses?

 

[vipergg]

I would point the default route to the ip address that is on the other end of interface F0/0 instead of pointing to the interface . Other than that it looks ok.

 

[uthorns]

I have the default gateway set to 192.168.102.1 for the pc on that side.

viper, I have f0/0 just plugged into one of our hub ports on the .100 network, so I'm not sure how I can do that?
Would this do...ip route 0.0.0.0 0.0.0.0 192.168.100.0?


I can ping the .100 interface from a pc on the .102 side, but I can't ping anything on the other side of .100, e.g. 192.168.100.4.

 

[lgarner]

If you don't need a default route, take it out.

What are the PCs on the .100 side using for a default route? It should be 192.168.100.100. If it's not, then you probably need to visit that gateway and add a route to 192.168.102.0/24 via 192.168.100.100. Normally that will redirect your clients to your new router to get to the .102 network.

Also, if the PCs on the .100 network have a different default gateway, that's most likely what you want for this router's default as well.

 

[KiscoKid]

If the goal here is simply to enable effective routing between PCs on the 192.168.100.0 and 192.168.102.0 networks, then you don't need either of the static routing statements you have defined, namely:


ip route 0.0.0.0 0.0.0.0 FastEthernet0/0
ip route 192.168.100.0 255.255.255.0 FastEthernet0/0


You may need a default route if perhaps you have an internet gateway, e.g. ip route 0.0.0.0 0.0.0.0 a.b.c.d
where a.b.c.d is the IP address of the internet gateway.

As the other posters have alluded to, check the default gateway and subnet mask setting on the PCs on each network.

For the 192.168.100.0 network, PCs need a subnet mask of 255.255.255.0 and default gateway of 192.168.100.100.

On the 192.168.102.0 network, PCs need the subnet mask of 255.255.255.0 and default gateway of 192.168.102.1.