Static Routing Question
bankintheroll
Member Posts: 121
in CCNA & CCENT
Here is a picture of my network:
I am having trouble setting up static routes with my subnets. I have only started with Router1 so far. I can ping both interfaces of Router2 and Router3 from Router1 so far, as well as all 3 switches, but I cannot ping the PCs on Networks 192.168.2.0 and 192.168.3.0.
So far, the only static routes I setup are the following (from the show ip route command):
S 192.168.2.0/24 [1/0] via 192.168.4.2
S 192.168.3.0/24 [1/0] via 192.168.5.2
All of the end devices are on subnets 192.168.20.0 and 192.168.30.0, so I think I have to do something with that, but I can't figure it out. Here is a full show ip route:
C 192.168.1.0/24 is directly connected, FastEthernet0/0
S 192.168.2.0/24 [1/0] via 192.168.4.2
S 192.168.3.0/24 [1/0] via 192.168.5.2
C 192.168.4.0/24 is directly connected, Serial2/0
C 192.168.5.0/24 is directly connected, Serial3/0
C 192.168.20.0/24 is directly connected, FastEthernet0/0.20
C 192.168.30.0/24 is directly connected, FastEthernet0/0.30
I am having trouble setting up static routes with my subnets. I have only started with Router1 so far. I can ping both interfaces of Router2 and Router3 from Router1 so far, as well as all 3 switches, but I cannot ping the PCs on Networks 192.168.2.0 and 192.168.3.0.
So far, the only static routes I setup are the following (from the show ip route command):
S 192.168.2.0/24 [1/0] via 192.168.4.2
S 192.168.3.0/24 [1/0] via 192.168.5.2
All of the end devices are on subnets 192.168.20.0 and 192.168.30.0, so I think I have to do something with that, but I can't figure it out. Here is a full show ip route:
C 192.168.1.0/24 is directly connected, FastEthernet0/0
S 192.168.2.0/24 [1/0] via 192.168.4.2
S 192.168.3.0/24 [1/0] via 192.168.5.2
C 192.168.4.0/24 is directly connected, Serial2/0
C 192.168.5.0/24 is directly connected, Serial3/0
C 192.168.20.0/24 is directly connected, FastEthernet0/0.20
C 192.168.30.0/24 is directly connected, FastEthernet0/0.30
Comments
-
EdTheLad Member Posts: 2,111 ■■■■□□□□□□Default gateways set on PCs?Networking, sometimes i love it, mostly i hate it.Its all about the $$$$
-
bankintheroll Member Posts: 121Default gateways set on PCs?
Yes. The default gateways on the 192.168.1.0 network are set to 192.168.20.1 and 192.168.30.1 The default gateways on the 192.168.2.0 network are set to 192.168.20.2 and 192.168.30.2. The default gateways on the 192.168.3.0 network are set to 192.168.20.3 and 192.168.30.3.
These are the subinterface IPs on the routers. The interfaces themselves have the IPs of 192.168.1.1, 192.168.2.1, and 192.168.3.1 on R1, R2, and R3.
I can ping every device with one another in the same subset. I can even ping every router and switch to each other. I just can't ping the routers to PCs, or vise versa, to each other in different subnets. -
bankintheroll Member Posts: 121Here is the show running-config output in case that helps (from Router1):
Router1(config)#do show run
Building configuration...
Current configuration : 1745 bytes
!
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname Router1
!
!
!
enable secret 5 $1$mERr$hx5rVt7rPNoS4wqbXKX7m0
!
!
!
!
!
!
username brad secret 5 $1$mERr$hx5rVt7rPNoS4wqbXKX7m0
!
!
!
!
!
ip ssh version 2
ip domain-name brad.com
!
!
!
!
!
!
interface FastEthernet0/0
ip address 192.168.1.1 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/0.20
encapsulation dot1Q 20
ip address 192.168.20.1 255.255.255.0
!
interface FastEthernet0/0.30
encapsulation dot1Q 30
ip address 192.168.30.1 255.255.255.0
!
interface FastEthernet1/0
no ip address
duplex auto
speed auto
shutdown
!
interface Serial2/0
ip address 192.168.4.1 255.255.255.0
!
interface Serial3/0
ip address 192.168.5.1 255.255.255.0
!
interface FastEthernet4/0
no ip address
shutdown
!
interface FastEthernet5/0
no ip address
shutdown
!
ip classless
ip route 192.168.2.0 255.255.255.0 192.168.4.2
ip route 192.168.3.0 255.255.255.0 192.168.5.2
ip route 192.168.20.0 255.255.255.0 192.168.5.2
ip route 192.168.30.0 255.255.255.0 192.168.5.2
ip route 192.168.30.0 255.255.255.0 192.168.4.2
ip route 192.168.20.0 255.255.255.0 192.168.4.2
ip route 192.168.20.0 255.255.255.0 192.168.2.1
ip route 192.168.30.0 255.255.255.0 192.168.2.1
ip route 192.168.20.0 255.255.255.0 192.168.20.2
!
!
!
banner motd ^C
************************************************
You are about to access Router 1
************************************************^C
!
!
!
!
line con 0
exec-timeout 0 0
logging synchronous
login local
!
line aux 0
!
line vty 0 4
exec-timeout 0 0
logging synchronous
login local
line vty 5 15
exec-timeout 0 0
logging synchronous
login local
!
!
!
end -
mikeybinec Member Posts: 484 ■■■□□□□□□□I see you are running inter vlan. Make sure your switches have a ip default-gateway <ip address> set on themCisco NetAcad Cuyamaca College
A.S. LAN Management 2010 Grossmont College
B.S. I.T. Management 2013 National University -
Adam B Member Posts: 108 ■■□□□□□□□□For Router 3 and Router 2, do you have the subinterfaces configured for the Vlan 20 and Vlan 30 on their fa0/0's? Check to make sure you did that and see if that helps any2015 Goals: CCNP SWITCH [] SEC+ [ ] CCNP ROUTE [ ] CCNP TSHOOT [ ]
-
bankintheroll Member Posts: 121I think I'm having problems because I am doing more than I've been taught so far studying CCENT. The examples of static routing and OSPF are not shown with VLANs and subnets already put in place.
Are inter VLANs common in organizations?
My switches have the following default-gateways:
Switch 1: 192.168.1.1
Switch 2: 192.168.2.1
Switch 3: 192.168.3.1
I'm pretty sure the problem of my static routing has something to do with the 192.168.20.0 and 192.168.30.0 subnets. I just don't know if the problem is in the switch, router, or both? Also, I don't know what exactly to look for. -
bankintheroll Member Posts: 121mikeybinec wrote: »I see you are running inter vlan. Make sure your switches have a ip default-gateway <ip address> set on them
Yes, here is the Router 2 and 3 show running-config:
Router2(config)#do show run
Building configuration...
Current configuration : 1484 bytes
!
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname Router2
!
!
!
enable secret 5 $1$mERr$hx5rVt7rPNoS4wqbXKX7m0
!
!
!
!
!
!
username brad secret 5 $1$mERr$hx5rVt7rPNoS4wqbXKX7m0
!
!
!
!
!
ip ssh version 2
ip domain-name brad.com
!
!
!
!
!
!
interface FastEthernet0/0
ip address 192.168.2.1 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/0.20
encapsulation dot1Q 20
ip address 192.168.20.2 255.255.255.0
!
interface FastEthernet0/0.30
encapsulation dot1Q 30
ip address 192.168.30.2 255.255.255.0
!
interface FastEthernet1/0
no ip address
duplex auto
speed auto
shutdown
!
interface Serial2/0
ip address 192.168.4.2 255.255.255.0
!
interface Serial3/0
no ip address
shutdown
!
interface FastEthernet4/0
no ip address
shutdown
!
interface FastEthernet5/0
no ip address
shutdown
!
ip classless
ip route 192.168.1.0 255.255.255.0 192.168.4.1
ip route 192.168.5.0 255.255.255.0 192.168.4.1
ip route 192.168.5.0 255.255.255.0 192.168.5.1
ip route 192.168.3.0 255.255.255.0 192.168.5.2
!
!
!
banner motd ^C
************************************************
You are about to access Router 2
************************************************^C
!
!
!
!
line con 0
exec-timeout 0 0
logging synchronous
login local
!
line aux 0
!
line vty 0 4
exec-timeout 0 0
logging synchronous
login local
line vty 5 15
exec-timeout 0 0
logging synchronous
login local
!
!
!
end
Router3(config)#do show run
Building configuration...
Current configuration : 1437 bytes
!
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname Router3
!
!
!
enable secret 5 $1$mERr$hx5rVt7rPNoS4wqbXKX7m0
!
!
!
!
!
!
username brad secret 5 $1$mERr$hx5rVt7rPNoS4wqbXKX7m0
!
!
!
!
!
ip ssh version 2
ip domain-name brad.com
!
!
!
!
!
!
interface FastEthernet0/0
ip address 192.168.3.1 255.255.255.0
duplex auto
speed auto
!
interface FastEthernet0/0.20
encapsulation dot1Q 20
ip address 192.168.20.3 255.255.255.0
!
interface FastEthernet0/0.30
encapsulation dot1Q 30
ip address 192.168.30.3 255.255.255.0
!
interface FastEthernet1/0
no ip address
duplex auto
speed auto
shutdown
!
interface Serial2/0
no ip address
shutdown
!
interface Serial3/0
ip address 192.168.5.2 255.255.255.0
!
interface FastEthernet4/0
no ip address
shutdown
!
interface FastEthernet5/0
no ip address
shutdown
!
ip classless
ip route 192.168.4.0 255.255.255.0 192.168.5.1
ip route 192.168.2.0 255.255.255.0 192.168.4.2
ip route 192.168.1.0 255.255.255.0 192.168.5.1
!
!
!
banner motd ^C
************************************************
You are about to access Router 3
************************************************
^C
!
!
!
!
line con 0
exec-timeout 0 0
logging synchronous
login local
!
line aux 0
!
line vty 0 4
exec-timeout 0 0
logging synchronous
login local
line vty 5 15
exec-timeout 0 0
logging synchronous
login local
!
!
!
end -
Adam B Member Posts: 108 ■■□□□□□□□□I believe the problem could be that you separated the same vlans into different networks, rather than onto multiple switches within the same network. Same subnet, so no point having it on a different network. Then again, I could be wrong, but from my understanding there would be no use in having vlan 10 on one network and then running vlan 10 on another network, when theyre in the same vlan. Just keep em in the same network under one router if that makes sense. Just trying my best to help2015 Goals: CCNP SWITCH [] SEC+ [ ] CCNP ROUTE [ ] CCNP TSHOOT [ ]
-
EdTheLad Member Posts: 2,111 ■■■■□□□□□□Looking at your topology, it seems you don't know what you're doing. PC1 & PC3, PC2 & PC4 share the same subnet but are on different router interfaces. Why are you using the physical interface addresses? you only need the subinterfaces, this is where you are getting confused between gateway addresses.
PC1 192.168.20.151
DG 192.168.20.1
Switchport connected to PC1 should be access vlan 20
Switchport connected to PC2 should be access vlan 30
switchport connected to R2 should be trunk allowing vlan 20 & 30
R2 remove 192.168.2.1 from f0/0
Now you should be able to ping between PC1 and PC2
Do the same thing on the second branch, but you will need to change the subnet from 20 and 30 to something else, otherwise R1 will see the same subnet coming from R2 and R3, how will it know which way to route?
I think you really need to go back and learn the theory basics before labbing.Networking, sometimes i love it, mostly i hate it.Its all about the $$$$ -
bankintheroll Member Posts: 121Looking at your topology, it seems you don't know what you're doing. PC1 & PC3, PC2 & PC4 share the same subnet but are on different router interfaces. Why are you using the physical interface addresses? you only need the subinterfaces, this is where you are getting confused between gateway addresses.
PC1 192.168.20.151
DG 192.168.20.1
Switchport connected to PC1 should be access vlan 20
Switchport connected to PC2 should be access vlan 30
switchport connected to R2 should be trunk allowing vlan 20 & 30
R2 remove 192.168.2.1 from f0/0
Now you should be able to ping between PC1 and PC2
Do the same thing on the second branch, but you will need to change the subnet from 20 and 30 to something else, otherwise R1 will see the same subnet coming from R2 and R3, how will it know which way to route?
I think you really need to go back and learn the theory basics before labbing.
Ed, like I said, I am only on chapter 19 of the CCENT official cert guide. I was trying to do some stuff outside of what I have learned already. (I also watch Jeremy's CBT Nugget videos, and the examples he shows do not include VLANs/subnets, so I got confused a bit). I actually find it helpful running into problems as I have to enter a ton of commands and ask questions here. I really appreciate your time helping me out!
Actually, all of this is already set up as you said to:
"PC1 192.168.20.151
DG 192.168.20.1
Switchport connected to PC1 should be access vlan 20
Switchport connected to PC2 should be access vlan 30
switchport connected to R2 should be trunk allowing vlan 20 & 30"
I do have the physical interface address still, but even then I'm still able to ping between PC1 and PC2. That was never the issue. I can't ping from server 1 & 2 to PC 1 & 2 or PC 3 & 4. Or vice versa. -
Abdul201288 Member Posts: 32 ■■□□□□□□□□For the PCs, make sure that the gateways are set to the the switches. For example, Accounting switch is 192.168.30.2. You add that to the gateway. And Vice versa.
-
Garo Member Posts: 20 ■□□□□□□□□□You have 2 different routers with the same subnet, how will they figure out the right way route it? and please remove the IPs from the router interfaces, makes no sense.