cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1202
Views
5
Helpful
4
Replies

Intervlan not working

HenryGorsten
Level 1
Level 1

Hi everyone,

 

Firstly, please go easy, I'm new to networking (started yesterday) and my brain is absolutely fried today, so I may just be making a very simple mistake that someone might be kind enough to point out.

 

Basically, I created a network earlier that I was happy with, got most things working except my VLANS were not talking to each other. To try and troubleshoot this issue I've created a new network to replicate this issue with a very simple network (1 router, 1 switch, 2 pcs, 2 vlans) and I still cannot ping across vlans, I'm probably missing something very simple so would really appreciate someone pointing it out. I can't seem to attach PKT file so here is an image of my network:

 

test network.JPG

 

Router config:

!
version 12.2
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname Router
!
!
!
!
!
!
!
!
ip cef
no ipv6 cef
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
interface FastEthernet0/0
 no ip address
 duplex auto
 speed auto
!
interface FastEthernet0/0.10
 encapsulation dot1Q 10
 ip address 192.168.10.1 255.255.255.0
!
interface FastEthernet0/0.20
 encapsulation dot1Q 20
 ip address 192.168.20.1 255.255.255.0
!
interface FastEthernet1/0
 no ip address
 duplex auto
 speed auto
 shutdown
!
interface Serial2/0
 no ip address
 clock rate 2000000
 shutdown
!
interface Serial3/0
 no ip address
 clock rate 2000000
 shutdown
!
interface FastEthernet4/0
 no ip address
 shutdown
!
interface FastEthernet5/0
 no ip address
 shutdown
!
ip classless
!
ip flow-export version 9
!
!
!
!
!
!
!
line con 0
!
line aux 0
!
line vty 0 4
 login
!
!
!
end

Switch Config:

!
version 12.1
no service timestamps log datetime msec
no service timestamps debug datetime msec
no service password-encryption
!
hostname Switch
!
!
!
!
!
spanning-tree mode pvst
spanning-tree extend system-id
!
interface FastEthernet0/1
 switchport mode trunk
!
interface FastEthernet1/1
 switchport access vlan 10
 switchport mode access
!
interface FastEthernet2/1
 switchport access vlan 20
 switchport mode access
!
interface FastEthernet3/1
!
interface FastEthernet4/1
!
interface FastEthernet5/1
!
interface Vlan1
 no ip address
 shutdown
!
interface Vlan10
 mac-address 0003.e429.e901
 ip address 192.168.10.1 255.255.255.0
!
interface Vlan20
 mac-address 0003.e429.e902
 ip address 192.168.20.1 255.255.255.0
!
!
!
!
line con 0
!
line vty 0 4
 login
line vty 5 15
 login
!
!
!
end

Assigned static IP's to both machines to keep simple, pc6 ip = 192.168.10.3, gateway = 192.168.10.1 & pc5 ip = 192.168.20.3, gateway 192.168.20.1. These machines cannot ping each other, please help.

 

As I say, please ignore my very, very simple network it's just for replication purposes :)

1 Accepted Solution

Accepted Solutions

Hello,

 

remove the VLAN interfaces from your switch:

 

no interface Vlan10
mac-address 0003.e429.e901
ip address 192.168.10.1 255.255.255.0
!
no interface Vlan20
mac-address 0003.e429.e902
ip address 192.168.20.1 255.255.255.0

View solution in original post

4 Replies 4

HenryGorsten
Level 1
Level 1

Ignore link lights - they are green, it's just I started up the file and took picture before the link lights turned to green :)

Hello,

 

remove the VLAN interfaces from your switch:

 

no interface Vlan10
mac-address 0003.e429.e901
ip address 192.168.10.1 255.255.255.0
!
no interface Vlan20
mac-address 0003.e429.e902
ip address 192.168.20.1 255.255.255.0

Problem solved! Thanks so much!

 

It was the same issue on my more complex network, can't believe I've been spending time banging my head trying to figure it out when it's so simple. 

 

Really appreciate your help!

Hello,

 

with your router-on-a-stick configuration (that's what it is called when you use a trunk between a router and a switch, and subinterfaces on the router), all routing is indeed done on the router. The VLAN interfaces on the switch are not necessary, and in your case actually prevent the inter-VLAN routing.