Connecting managed and unmanaged switches

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

Connecting managed and unmanaged switches

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Connecting managed and unmanaged switches
Connecting managed and unmanaged switches
2019-07-07 08:05:41
Hardware Version: V3
Firmware Version:

Hi,

 

I have a t1600g-28ps switch having vlan 192.168.252.*/24.

I have a router on 192.168.253.1 and a unmanaged switch for newtwork192.168.253.*/24.

I wouldlike to connect 192.168.252.* to the router for internet access... but I have no firewall and no gateway.

Is it possible to create a vlan 192.168.253.* on the t1600g-28ps and to put a cable from vlan 192.168.252.* to 192.168.253.*on t1600g-28ps, and to define a gateway from 192.168.252.1 to 192.168.253.*? How?

 

Thank you.

  0      
  0      
#1
Options
10 Reply
Re: Connecting managed and unmanaged switches
2019-07-07 09:43:28 - last edited 2019-07-07 10:05:59

alainb wrote

Is it possible to create a vlan 192.168.253.* on the t1600g-28ps and to put a cable from vlan 192.168.252.* to 192.168.253.*on t1600g-28ps, and to define a gateway from 192.168.252.1 to 192.168.253.*?

 

Yes and no. Yes, because Inter-VLAN Routing is possible with T1600G, but no, because this alone does not help to connect the subnet to the Internet through an Internet router. You would have to set up a static network route on your router, too, and configure the firewall to separate the subnets again.

 

How?

 

 

To use the router as an Internet gateway for a second subnet 192.168.253.0/24 you could define this subnet as an additional network on your Internet router. This solution is much simpler to set up and requires no special routing on the T1600G and the router.

 

Just connect the second network directly to the router and assign the router two IPs, one for the 192.168.252.0/24 subnet and one for the 192.168.253.0/24 subnet. What switch you use for which subnet doesn't matter in this case. Be sure to create a different firewall zone for the second subnet on the router if you want client isolation between the two subnetworks.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#2
Options
Re:Re: Connecting managed and unmanaged switches
2019-07-07 12:41:50

My router will be a tp-link TL-ER6020.

If I go to network/lan on the router I can only enter one IP for the LAN. Where can I specify settings for a 2nd interface?

  0  
  0  
#3
Options
Re:Re:Re: Connecting managed and unmanaged switches
2019-07-08 02:56:39

Hi alainb

 

ER6020 doesn't support to set up multiple IP address for LAN.

I think you can disable DHCP server on ER6020. Enable DHCP server and set up L3 interface on T1600.

 

L3 Interface

 

DHCP server

 

Your situation is similar to a case of TP-LINK FAQ. Maybe you can refer to it. You still need to set up multi-nets on ER6020, and set up default routing on T1600. Because the L3 interface is using VLAN interface, you still need to set up 802.1Q VLAN.

https://www.tp-link.com/en/support/faq/887/

  0  
  0  
#4
Options
Re:Connecting managed and unmanaged switches
2019-07-08 09:19:54

TL-ER6020 doesn't support VLAN multiple IP Interfaces, but it support Multi-Net NAT, so it will know about several subnets on LAN side. Just configure routing on switch, as it was said above and add multi-net nat

  0  
  0  
#5
Options
Re:Re:Connecting managed and unmanaged switches
2019-07-08 10:15:15 - last edited 2019-07-08 10:20:44

Yes, Multi-Nets-NAT is TP-Link's terminology to describe an additional subnet and network interface on their routers. Multi-Nets-NAT will create another subnet and uses routing to reach those subnets in VLANs defined on the switch. If you ask me, it's much easier to set up such a scheme with a VLAN-aware router.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#6
Options
Re: Connecting managed and unmanaged switches
2019-07-08 10:29:13

Andone wrote

 

I think you can disable DHCP server on ER6020. Enable DHCP server and set up L3 interface on T1600.

 

Hello Andone,

 

T1600G switches do not offer a DHCP server, at least mine does not (HW V1, SW 2.0.0).

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#7
Options
Re:Re: Connecting managed and unmanaged switches
2019-07-08 10:46:09

R1D2 wrote

Andone wrote

 

I think you can disable DHCP server on ER6020. Enable DHCP server and set up L3 interface on T1600.

 

Hello Andone,

 

T1600G switches do not offer a DHCP server, at least mine does not (HW V1, SW 2.0.0).

 

T1600G series support DHCP Server. Just checked with my T1600G-52TS, firmware from hardware version 1 doesn't support, updated it to v3 -> support.

  0  
  0  
#8
Options
Re: Connecting managed and unmanaged switches
2019-07-08 11:16:50 - last edited 2019-07-08 11:21:10

Mitya wrote  

 

T1600G series support DHCP Server. Just checked with my T1600G-52TS, firmware from hardware version 1 doesn't support, updated it to v3 -> support.

 

Interesting. Mine doesn't. Yes, I tried to update to V3 firmware already, not possible with T1600G-28TS V1,that's why I asked for V2 firmware. The HW version listed below in the screenshot is wrong - it's a V1 device. I think it is the usual hardware/firmware version chaos with TP-Link devices.

 

 

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#9
Options
Re:Re: Connecting managed and unmanaged switches
2019-07-09 01:22:49

As I know, T1600G-52TS/52PS can upgrade the firmware from V1 to V2/V3. T1600G-28TS/28PS can upgarde the firmware from V1 to V2, cannot upgrade to V3. 

 

And only version 3.0 of T1600G series support DHCP server.

  0  
  0  
#10
Options
Re: Connecting managed and unmanaged switches
2019-07-09 10:55:44 - last edited 2019-07-09 10:56:49

Andone wrote

As I know, T1600G-52TS/52PS can upgrade the firmware from V1 to V2/V3.

 

Thanks for the info, I wasn't aware of this. Knowing this now, I could imagine that in case of T1600G-28 it probably could be just an (unintentional) bug that it can't be upgraded to V3 if its brother T1600G-52 allows this upgrade.

 

Anyway, this firmware upgrade policy from TP-Link sucks - I told them many times. It's the same with Omada EAP and Pharos products. We still have V1 devices on stock (from all products: switches, APs, wireless broadband), which lack upgrade support to the latest firmware, albeit they are still not EOL.

 

This is the reason why we won't hold newer devices on stock anymore.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#11
Options