TPLINK T1600G-28TS VLAN routing

TPLINK T1600G-28TS VLAN routing
TPLINK T1600G-28TS VLAN routing
2021-07-20 04:11:35
Hardware Version: V3
Firmware Version: 3.0.5 Build 20200109 Rel.39834(s)

Thank you in advance for the help. I'm trying to run, at least right now, two VLANs and have them talk to each other  through the Router. I'm running PSENSE and the TPLINK T1600G-28TS. I've setup my VLAN in PSENSE (see screenshots) with firewall rules to allow those interface to route anywhere. 

 

On the switch in "VLAN CONFIG" all ports set to VLAN1 except 22, and on VLAN50 Port22 is set at PVID 50 and Port2=Router is set as tagged.

 

On the switch I have one computer(192.168.1.100) plugged into Port1(VLAN1) and the other computer(192.168.50.10) into Port22(VLAN50). I cant ping either one though. Shouldn't a ping leave the computerB(192.168.50.10) untagged, then get tagged by Port22 as VLAN50(S_VLAN) and travel to Router(VLAN aware) on PORT2(set as tagged VLAN50 port) which should send it to the S_VLAN interface with firewall rules that pass all traffic and end up at at computerA(192.168.1.100)?

 

I'm just trying to figure out this piece of the puzzle before I make something for complex.

 

 

 

 

 

0
0
#1
Options
2 Reply
Re:TPLINK T1600G-28TS VLAN routing
2021-07-21 07:09:01

@JLAN_10 

To make PCA and PCB have different subnet and can communicate with each other, it probably depends on how the router creates the multi-subnet.

 

For the switch, port2 set up VLAN1 and 50, tagged; port 1 set up VLAN1, PVID1, untagged; port 22 set up VLAN 50, PVID 50, untagged.

The VLAN for the switch is based on 802.1Q VLAN, which means two different VLAN can not access to each other. 

 

If the router base on the VLAN interface to create mulit-subnet, then the device on the port 1 and port 22 can access each other by default.

 

0
0
#2
Options
Re:TPLINK T1600G-28TS VLAN routing
2021-07-22 02:38:18

@John1234 What you said makes sense but as soon as you change Port2=gateway to a Tagged port on VLAN1 I lose connection to the gateway.  So far i'm not a fan of the way TPLINK does their interface config. Why in every VLAN config window are their the same ports for tagged? If I list a port as tagged in one VLAN then have to list it in every other VLAN as tagged as well for that VLAN? Seem redundant, other than I'm telling the switch all the acceptable VLANs that should be on that trunk.

0
0
#3
Options