Skip to content

Commit 48fecc4

Browse files
committed
updated description
1 parent e4dba13 commit 48fecc4

1 file changed

Lines changed: 1 addition & 5 deletions

File tree

‎_posts/2023-05-23-home-security-networking.md‎

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -390,11 +390,7 @@ Then we will have the following config:
390390

391391
The table above is a generic configuration setup for TPLink switch. However, much of the information here can be applied to other switches.
392392

393-
Here we are setting the ports to be untagged since the devices that we are connecting are not VLAN aware. This means they do not know what to do if there's an additional parameter in the packet coming to them. In this case the VLAN ID is added to the packet. Typically, you would only want to tag the port in a few conditions:
394-
- connecting 2 switches together
395-
- connecting WAP's that are capable of VLAN's
396-
- connecting devices that are VLAN aware
397-
393+
Here we are setting the ports to be tagged since the devices that we are connecting are VLAN aware. Also, it specifies that the traffic coming over those ports should be going to specific VLANs. We also add Port 1 to the IoT VLAN so that the IoT VLAN can reach back to the main router/firewall/modem to get internet access.
398394

399395
Repeat the process for the other VLANS we configured
400396

0 commit comments

Comments
 (0)