TL-SG105E vlan/pvid issue ?
Hello everyone,
I just got two of these switches and planned to use their VLAN feature as follows:
* Ports 1, 2, 3 and 4 would be access ports to different VLANs
* Port 5 trunk for all VLANs
The switch itself should get an IP via DHCP on VLAN 100, how can I achieve this?
As is, the switch is getting an IP from any of the VLAN, randomly, via port 5 (I rebooted couple of times, and saw leases in all VLANS....).
What could be wrong?
Thank you
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @dynek
Thanks for posting in our business forum.
The switch is supposed to be in VLAN 1. Which looks like you have removed it from VLAN 1. And there is a PVID 1 for it. This is wrong.
- Copy Link
- Report Inappropriate Content
Hello @Clive_A,
What do you mean with "the switch is supposed to be in VLAN 1" ?
If I get it, you consider the management vlan / DHCP to be on VLAN 1, untagged ?
Not the case for me the device should get an IP on VLAN 100 through port 5.
However currently it fetches an IP in any of the VLAN, which is wrong.
Thank you
- Copy Link
- Report Inappropriate Content
Hi @dynek
Thanks for posting in our business forum.
dynek wrote
Hello @Clive_A,
What do you mean with "the switch is supposed to be in VLAN 1" ?
If I get it, you consider the management vlan / DHCP to be on VLAN 1, untagged ?
Not the case for me the device should get an IP on VLAN 100 through port 5.
However currently it fetches an IP in any of the VLAN, which is wrong.
Thank you
You want it to stay in VLAN 100 or VLAN 1? Usually, it is in 1.
If you need it to be on the VLAN 100, you gotta set the port 5 as untagged, PVID 100. And check again.
About the fetching IP in every VLAN, I think you might consider a different switch. This seems to be the switch not capable of the Management VLAN. In the Omada SG2000 series, you have the option to set a management VLAN.
How to Configure Management VLAN on TP-Link Smart and Managed Switches Using the New GUI
How to configure Management VLANs for Omada Switches and APs (for Business scenario)
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hi @dynek
Thanks for posting in our business forum.
dynek wrote
Port 5 is the trunk with all VLANs, and I can't set VLAN100 as both tagged and untagged. What surprises me about that device, is that currently with DHCP enabled the device is fetching an IP in any of the tagged VLAN, how is that possible ?
See the edited reply above. This might not be supported for this switch so it behaves strangely.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I am just another user and not from Tp-Link. After reading your post, I got curious about what you are trying to do. I have a spare SG105E and so decided to do some testing.
After my tests, it appears the switch must get its IP address from an untagged VLAN when configured for DHCP. I connected a trunk port from my router that has 5 VLANs, one untagged and four tagged (with IDs of 30, 40, 50, and 1733) to switch port 5. I then configured switch port 5 as a non-member of the switch's default VLAN 1. You must remember that the switch only uses VLAN ID 1 internally.
In the test setup and using the Easy Smart Configuration utility, I found the switch had an IP address of 192.168.0.1 with no default gateway. The switch's User Guide states "If the switch cannot receive an IP address from a DHCP server, it uses the static IP address of 192.168.0.1, with a subnet mask of 255.255.255.0.". This meant that the switch did not recognize any of the tagged VLANs, all of which have their own DHCP server.
One additional comment... I don't understand why you configured your IoT and Guest VLANs in the switch as you are not using the switch for those VLANs nor are you passing the trunk port through the switch to another trunk port. I would delete them to keep things simple.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 66
Replies: 7
Voters 0
No one has voted for it yet.