Help needed understanding VLANs, Subnets and Management VLAN

Help needed understanding VLANs, Subnets and Management VLAN

Help needed understanding VLANs, Subnets and Management VLAN
Help needed understanding VLANs, Subnets and Management VLAN
a week ago - last edited a week ago
Model: TL-SG2008   EAP245   ER605 (TL-R605)  
Hardware Version:
Firmware Version:

Hi all,

 

Please bear with me, I'm still learning!

 

I am running a setup connecting multiple rooms with different APs who have their own SSIDs, own Subnet (as in: one uses 192.168.30.X, another 192.168.40.X) and, when setting up the IP address range, also set one VLAN for each EAP, named according to the IP range ("30", "40" etc.). The goal is that devices on different wifis cannot communicate/disturb one another, and it's working well.

 

The router/modem are in one room, run to a TL-SG2008 v3.0 smart switch in the basement, to which the EAP245s are connected.

 

The issue I'm facing now is that if I want to use a wired ethernet connection in one of the other rooms, the plugged in device will receive an IP in the default range (192.168.0.X), which also the EAPs, Switch and router use. I'd much rather they received an IP in the same range of the subnet/VLAN associated with the AP.

 

If I assign a VLAN to the specific port of the switch, to make sure everything that happens behind it gets an IP in, for example, the range of VLAN 30 (192.168.30.X), the respective EAP245 also receives such an IP and I lose access to it from the OC200 cloud controller. I want to stay in control/connected to the EAPs, but have other ethernet clients receive a different IP. Hope that makes sense!

 

I hope I was able to explain my challenge/what I'm trying to achieve well enough, and would be grateful for any input on how to solve this!

 

Thanks a lot in advance,

D

  0      
  0      
#1
Options
2 Accepted Solutions
Re:Help needed understanding VLANs, Subnets and Management VLAN-Solution
a week ago - last edited a week ago

  @crinkles 

 

In your scenario, All vlans should live everywhere

Setup all hardware (switches, etc) on one vlan you nominate as the management vlan

Setup multilpe WiFi SSID, linked to a particular network / vlan tag, and you can select which AP broadcasts them either one or all of them.

Control inter-vlan communication with switch or gateway ACLs to isolate them

Having different vlans for a room is fine, but having the actual AP, Switch etc is completely not-fine.  You will have no way to manage the devices, and you will expose the AP, switch etc to users on that network.

Recommended Solution
  1  
  1  
#2
Options
Re:Help needed understanding VLANs, Subnets and Management VLAN-Solution
a week ago - last edited a week ago

Hi @crinkles 

Thanks for posting in our business forum.

Some guides:

Common Questions About 802.1Q VLAN

How to Configure VLAN on TP-Link Switch

 

You can also use this link to filter the related guides and articles:

https://community.tp-link.com/en/business/forum/3?tagId=626&labelIds=8744,8738

 

The official website has tons of guides regarding the management of VLAN and how VLAN works. You may also utilize them to equip yourself with VLAN knowledge.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
Recommended Solution
  1  
  1  
#3
Options
3 Reply
Re:Help needed understanding VLANs, Subnets and Management VLAN-Solution
a week ago - last edited a week ago

  @crinkles 

 

In your scenario, All vlans should live everywhere

Setup all hardware (switches, etc) on one vlan you nominate as the management vlan

Setup multilpe WiFi SSID, linked to a particular network / vlan tag, and you can select which AP broadcasts them either one or all of them.

Control inter-vlan communication with switch or gateway ACLs to isolate them

Having different vlans for a room is fine, but having the actual AP, Switch etc is completely not-fine.  You will have no way to manage the devices, and you will expose the AP, switch etc to users on that network.

Recommended Solution
  1  
  1  
#2
Options
Re:Help needed understanding VLANs, Subnets and Management VLAN-Solution
a week ago - last edited a week ago

Hi @crinkles 

Thanks for posting in our business forum.

Some guides:

Common Questions About 802.1Q VLAN

How to Configure VLAN on TP-Link Switch

 

You can also use this link to filter the related guides and articles:

https://community.tp-link.com/en/business/forum/3?tagId=626&labelIds=8744,8738

 

The official website has tons of guides regarding the management of VLAN and how VLAN works. You may also utilize them to equip yourself with VLAN knowledge.

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced.
Recommended Solution
  1  
  1  
#3
Options
Re:Help needed understanding VLANs, Subnets and Management VLAN
a week ago

GRL wrote

  @crinkles 

Setup all hardware (switches, etc) on one vlan you nominate as the management vlan

Setup multilpe WiFi SSID, linked to a particular network / vlan tag, and you can select which AP broadcasts them either one or all of them.

Control inter-vlan communication with switch or gateway ACLs to isolate them

Having different vlans for a room is fine, but having the actual AP, Switch etc is completely not-fine.  You will have no way to manage the devices, and you will expose the AP, switch etc to users on that network.

  @GRL 

Thanks a lot for the quick reply! Will look at management VLAN. Right now, the hardware lives in the default network, all wifi clients live in different ones, as you described.

 

As it is right now though, if I'm in one of the rooms and want to use an Ethernet connection, I'll also land in that default VLAN, wich is undesirable, or as you described it "completely not-fine" :)

 

If I isolate ethernet through the respective ports on the switch in the basement for every room, I lose control of the APs - Is there another way to isolate ethernet clients without losing control of the APs?

 

Just googled ACLs, looks like I will have to read up on them to understand how they work in my context.

 

Thanks again!

  0  
  0  
#4
Options