VLAN and Routing with T2600G-52TS

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
12

VLAN and Routing with T2600G-52TS

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
VLAN and Routing with T2600G-52TS
VLAN and Routing with T2600G-52TS
2019-01-03 06:55:48

Hi, we have TPLINK T2600G-52TS Managed Switch, we want to make 3 VLAN within it, vlan 1, 2 and 3,

Vlan 1 will contain port 1 to port 2, vlan 2 will contain port 3 to 14, and vlan 3 will contain port 15 to 48,

so, here're the promblems we are facing:

 

1. We have created vlan 1, 2 and 3 and assigned the desired ports to each vlan (we also removed the ports that vlan 2 and use from vlan 1), but it doesnot look like working. 

we have created a network for each vlan, with several computers connected for each vlan, we have set the IP for each computer depending on the vlan where the computer is located. but the problem is, only vlan 1 functions and can communicate with other computers that are in vlan 1, while computers that are in vlan 2 and vlan 3 cannot communicate with other computers in the same vlan. we don't know why this happened. The networks we used are 192.168.0.0 (vlan 1), 129.168.1.0 (vlan 2), 192.168.2.0 (vlan 3). We also have attached an IP virtual Interface for each vlan, but again, only vlan 1 works. Please tell us why this happened.

 

2. This is actually a optional problem, in case we can solve problem number 1, is there any way to use static routing in T2600G-52TS to route 2 different vlan? for example we want to route vlan 2 to vlan 3.

 

Thank you, we hope you guys can guide us

  0      
  0      
#1
Options
11 Reply
Re: VLAN and Routing with T2600G-52TS
2019-01-03 22:33:05 - last edited 2019-01-03 22:34:08

rayendra wrote

1. We have created vlan 1, 2 and 3 and assigned the desired ports to each vlan (we also removed the ports that vlan 2 and use from vlan 1), but it doesnot look like working. 

 

Without seeing your actual config, nobody can tell why it doesn't work. Probably you forgot to set up the PVIDs for VLANs 2 or 3, but that's just a guess. Post setup of port/VLAN memberships and PVID assignments.

 

2. This is actually a optional problem, in case we can solve problem number 1, is there any way to use static routing in T2600G-52TS to route 2 different vlan? for example we want to route vlan 2 to vlan 3.

 

This is called Inter-VLAN routing. Just create virtual interfaces in both VLANs and add static routes from one VLAN/subnet to the other.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  1  
  1  
#2
Options
Re:Re: VLAN and Routing with T2600G-52TS
2019-01-04 00:55:03
We're using T2600G-52TS v3, can you please point us to any articles or tutorials that can lead us to solve our problem, because actually we followed tutorials from this page https://www.tp-link.com/us/download/T2600G-52TS.html#Related-Documents, we think we did exactly the same
  0  
  0  
#3
Options
Re:Re:Re: VLAN and Routing with T2600G-52TS
2019-01-04 09:01:26

rayendra wrote

We're using T2600G-52TS v3, can you please point us to any articles or tutorials that can lead us to solve our problem, because actually we followed tutorials from this page https://www.tp-link.com/us/download/T2600G-52TS.html#Related-Documents, we think we did exactly the same

 

Hi  Rayendra:

     

    I aggre with R1D2 also. In my opinion. there are something wroing with PVID.

   Maybe this FAQ can help you, please check the link as below:

   https://www.tp-link.com/en/faq-2149.html

 

  0  
  0  
#4
Options
Re:Re:Re:Re: VLAN and Routing with T2600G-52TS
2019-01-06 04:41:48

TPTHZ wrote

rayendra wrote

We're using T2600G-52TS v3, can you please point us to any articles or tutorials that can lead us to solve our problem, because actually we followed tutorials from this page https://www.tp-link.com/us/download/T2600G-52TS.html#Related-Documents, we think we did exactly the same

 

Hi  Rayendra:

     

    I aggre with R1D2 also. In my opinion. there are something wroing with PVID.

   Maybe this FAQ can help you, please check the link as below:

   https://www.tp-link.com/en/faq-2149.html

 

 

if the ports are directly connected to PCs, should we label the ports as tagged or untagged in order to have each PC connected (each PC can ping other PCs)?

for information, we have set PVID for each ports to desired vlan

  0  
  0  
#6
Options
Re:Re: VLAN and Routing with T2600G-52TS
2019-01-06 04:48:33

R1D2 wrote

rayendra wrote

1. We have created vlan 1, 2 and 3 and assigned the desired ports to each vlan (we also removed the ports that vlan 2 and use from vlan 1), but it doesnot look like working. 

 

Without seeing your actual config, nobody can tell why it doesn't work. Probably you forgot to set up the PVIDs for VLANs 2 or 3, but that's just a guess. Post setup of port/VLAN memberships and PVID assignments.

 

2. This is actually a optional problem, in case we can solve problem number 1, is there any way to use static routing in T2600G-52TS to route 2 different vlan? for example we want to route vlan 2 to vlan 3.

 

This is called Inter-VLAN routing. Just create virtual interfaces in both VLANs and add static routes from one VLAN/subnet to the other.

 

here is the config file:

 

 

!T2600G-52TS
#
vlan 10
 name "PublicNetwork"
#
vlan 20
 name "LocalNetwork"
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
#
serial_port baud_rate 38400
#
#
system-time ntp UTC+08:00 133.100.9.2 139.78.100.163 12
no system-time dst
#
#
#
user name aderayendra privilege admin secret 5 $1$N2L3B4@>A1A7F7J1F0J0L0A6N/J:H<L='()}%
user name admin privilege admin secret 5 $1$N2L3B4@>A1A7F7J1F0J0L0A6N/J:H<L='()}%
#
#
#
#
#
service dhcp server
ip dhcp server pool "LocDHCP"
network 192.168.0.0 255.255.255.0
default-gateway 192.168.0.1
#
#
ip dhcp server pool "LocDHCP"
address 192.168.0.199 hardware-address 4c:ed:fb:6c:5e:55 hardware-type ethernet
#
#
#
#
#
#
ip route 192.168.0.0 255.255.255.0 192.168.1.30
ip route 192.168.1.0 255.255.255.0 192.168.0.1
#
#

#
#
service dhcp relay
#
#
#
#
#
#
interface vlan 1
  ip address 192.168.100.1 255.255.255.0
  description "ConfigGateway"
  ipv6 enable
#
interface vlan 10
  ip address 192.168.1.30 255.255.255.0
  description "PublicGateway"
  no ipv6 enable
  ip helper-address 192.168.1.1
#
interface vlan 20
  ip address 192.168.0.1 255.255.255.0
  description "LocalGateway"
  no ipv6 enable
#
interface gigabitEthernet 1/0/1
  
#
interface gigabitEthernet 1/0/2
  
#
interface gigabitEthernet 1/0/3
  switchport general allowed vlan 10 untagged
  switchport pvid 10
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/4
  switchport general allowed vlan 10 untagged
  switchport pvid 10
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/5
  switchport general allowed vlan 10 untagged
  switchport pvid 10
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/6
  description "PublicGateway"
  switchport general allowed vlan 10 untagged
  switchport pvid 10
  no switchport general allowed vlan 1
  
  no ip igmp snooping
  no ipv6 mld snooping
#
interface gigabitEthernet 1/0/7
  switchport general allowed vlan 10 untagged
  switchport pvid 10
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/8
  switchport general allowed vlan 10 untagged
  switchport pvid 10
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/9
  switchport general allowed vlan 10 untagged
  switchport pvid 10
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/10
  switchport general allowed vlan 10 untagged
  switchport pvid 10
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/11
  switchport general allowed vlan 10 untagged
  switchport pvid 10
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/12
  switchport general allowed vlan 10 untagged
  switchport pvid 10
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/13
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/14
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/15
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/16
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/17
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/18
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/19
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/20
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/21
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/22
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/23
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/24
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/25
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/26
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/27
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/28
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/29
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/30
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/31
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/32
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/33
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/34
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/35
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/36
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/37
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/38
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/39
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/40
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/41
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/42
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/43
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/44
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/45
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/46
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/47
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/48
  switchport general allowed vlan 20 untagged
  switchport pvid 20
  no switchport general allowed vlan 1
  
#
interface gigabitEthernet 1/0/49
  
#
interface gigabitEthernet 1/0/50
  
#
interface gigabitEthernet 1/0/51
  
#
interface gigabitEthernet 1/0/52
  
#
end
 

  0  
  0  
#7
Options
Re:Re:Re:Re:Re: VLAN and Routing with T2600G-52TS
2019-01-07 03:38:32

rayendra wrote

TPTHZ wrote

rayendra wrote

We're using T2600G-52TS v3, can you please point us to any articles or tutorials that can lead us to solve our problem, because actually we followed tutorials from this page https://www.tp-link.com/us/download/T2600G-52TS.html#Related-Documents, we think we did exactly the same

 

Hi  Rayendra:

     

    I aggre with R1D2 also. In my opinion. there are something wroing with PVID.

   Maybe this FAQ can help you, please check the link as below:

   https://www.tp-link.com/en/faq-2149.html

 

 

if the ports are directly connected to PCs, should we label the ports as tagged or untagged in order to have each PC connected (each PC can ping other PCs)?

for information, we have set PVID for each ports to desired vlan

Hi Rayendra:

     Maye there are some misundertstanding about this case.

     From the configuration file that you copied, there are many difference with the description in your first email.

     Now, you have VLAN 10(port3-port12) and VLAN 20(port 13-port 48)

     In my opinion,  the computer connect to Port3 are able to communicate with the computer that connect to port4, is it right?

     Now, the computer are able to communicate with each other in same vlan, but cannot communicate with different vlan, this is your question now, is it right?

  0  
  0  
#8
Options
VLAN and Routing with T2600G-52TS
2019-01-07 04:54:08

TPTHZ wrote

rayendra wrote

TPTHZ wrote

rayendra wrote

We're using T2600G-52TS v3, can you please point us to any articles or tutorials that can lead us to solve our problem, because actually we followed tutorials from this page https://www.tp-link.com/us/download/T2600G-52TS.html#Related-Documents, we think we did exactly the same

 

Hi  Rayendra:

     

    I aggre with R1D2 also. In my opinion. there are something wroing with PVID.

   Maybe this FAQ can help you, please check the link as below:

   https://www.tp-link.com/en/faq-2149.html

 

 

if the ports are directly connected to PCs, should we label the ports as tagged or untagged in order to have each PC connected (each PC can ping other PCs)?

for information, we have set PVID for each ports to desired vlan

Hi Rayendra:

     Maye there are some misundertstanding about this case.

     From the configuration file that you copied, there are many difference with the description in your first email.

     Now, you have VLAN 10(port3-port12) and VLAN 20(port 13-port 48)

     In my opinion,  the computer connect to Port3 are able to communicate with the computer that connect to port4, is it right?

     Now, the computer are able to communicate with each other in same vlan, but cannot communicate with different vlan, this is your question now, is it right?

 

No, the computers can't connect to other computers in the same vlan, we don't why this happened 

  0  
  0  
#10
Options
Re:VLAN and Routing with T2600G-52TS
2019-01-08 09:51:26

rayendra wrote

TPTHZ wrote

rayendra wrote

TPTHZ wrote

rayendra wrote

We're using T2600G-52TS v3, can you please point us to any articles or tutorials that can lead us to solve our problem, because actually we followed tutorials from this page https://www.tp-link.com/us/download/T2600G-52TS.html#Related-Documents, we think we did exactly the same

 

Hi  Rayendra:

     

    I aggre with R1D2 also. In my opinion. there are something wroing with PVID.

   Maybe this FAQ can help you, please check the link as below:

   https://www.tp-link.com/en/faq-2149.html

 

 

if the ports are directly connected to PCs, should we label the ports as tagged or untagged in order to have each PC connected (each PC can ping other PCs)?

for information, we have set PVID for each ports to desired vlan

Hi Rayendra:

     Maye there are some misundertstanding about this case.

     From the configuration file that you copied, there are many difference with the description in your first email.

     Now, you have VLAN 10(port3-port12) and VLAN 20(port 13-port 48)

     In my opinion,  the computer connect to Port3 are able to communicate with the computer that connect to port4, is it right?

     Now, the computer are able to communicate with each other in same vlan, but cannot communicate with different vlan, this is your question now, is it right?

 

No, the computers can't connect to other computers in the same vlan, we don't why this happened 

Hi Rayendra:

     Port3 can not communicate port4? From the configuration file, Port 3 and port 4 should communicate with each other.

     How did you test it?  use the ping command?

     Do you check the status of firewall in these computers.

 

  1  
  1  
#11
Options
Re:Re:VLAN and Routing with T2600G-52TS
2019-01-09 02:38:11
no, I didnot check it, that might be the problem, thanks
  0  
  0  
#12
Options
Re:Re:VLAN and Routing with T2600G-52TS
2019-11-20 13:00:18

@rayendra 

I'm having the same problem. Did you solve the problem with the switch? It was really the firewall problem?

  0  
  0  
#13
Options

Information

Helpful: 0

Views: 5637

Replies: 11

Related Articles