Some deliveries may take a little longer than usual due to regional shipping conditions.
DOWNLOAD THE APP
Customer Services
Copyright © 2025 Desertcart Holdings Limited
DOWNLOAD THE APP
RJ45 x 8, 10/100/1000 Mbps, MDI/MDIX, Jumbo Frame Review: VLAN) and a Draytek Vigor 2860 Router to play nicely with each other in terms of VLANs and tagged/untagged traffic. The Vigor seems to have a few issues with tagged and untagged traffic on the same port, including some embarrasing routing leaks that are being looked at by their support team. This switch does the job perfectly and I now have the general WiFi going to a standard hub and internal VMs on an ESXi host. Guest Wifi is routed direct to internet, and test WiFi going to test VMs via the Vigor and a second NIC on the ESXi host. The switch can work as normal without any VLAN config just fine, or can be configured for one of three different VLAN modes. After initial check out in port mode with ports 1-4 in one VLAN and 5-8 in another I dived in to the wonderful world of tagged VLANs which I thought I understood. I do now... With hindsight it's actually easy to configure. Give an ID and friendly name to a VLAN, select which ports will connect to it and if they should leave tags in place or not for outbound traffic, save and repeat for next VLAN. Each port can have multiple tagged VLANs connected. Easy. I had three issues. Sorry, I mean learning experiences: The management functions of the WiFi router are only accessible via VLAN 1 (undocumented) which is nothing to do with this switch of course, but it means you need to have VLAN 1 defined between the router, switch and tagging set up so you can still reach it from a management PC. At least 1 port on the switch must also be assigned to VLAN 1. I'm thinking this is a TP-Link thing and kinda makes sense. At least its mentioned in switch documentation, and since I need VLAN 1 for the Wifi it's no big deal. There's 4094 other IDs to chose from after all. For untagged traffic entering the switch from a normal PC or hub, you need to configure the default VLAN for that port *on a separate config screen" if you want the traffic to go on a VLAN. Really obvious in hindsight, but took me a little while to figure out what was going on. Maybe the lesson is not to try doing this late in the evening after a long day, nice dinner and couple of glasses of wine. Although it's only been in use for a couple of weeks it's doing the job very nicely. I'm using this for a home office & lab but I'd have no issues using in a "proper" commercial environment either. Review: Desde que lo compre lo puse a trabajar 24x365 y no presenta fallo alguno. Excelente hardware y muy rápido con sus puertos 1Gb. Es administrable por lo que puedo formar Vlans.
| ASIN | B00K4DS5KU |
| Amazon Bestseller | #474,739 in Computers ( See Top 100 in Computers ) #2,193 in Computer Networking Switches |
| Batteries Included | No |
| Batteries Required | No |
| Customer Reviews | 4.7 4.7 out of 5 stars (6,173) |
| Date First Available | May 1, 2014 |
| Global Trade Identification Number | 06935364021863 |
| Item Model Number | TL-SG108E |
| Item model number | TL-SG108E |
| Manufacturer | Graduationmall |
| Model Year | 2014 |
| Product Dimensions | 15.75 x 10.16 x 2.54 cm; 508.02 g |
| UPC | 840460604086 845973021856 |
| Wireless Comm Standard | 802.11a, 802.11b |
R**D
VLAN) and a Draytek Vigor 2860 Router to play nicely with each other in terms of VLANs and tagged/untagged traffic. The Vigor seems to have a few issues with tagged and untagged traffic on the same port, including some embarrasing routing leaks that are being looked at by their support team. This switch does the job perfectly and I now have the general WiFi going to a standard hub and internal VMs on an ESXi host. Guest Wifi is routed direct to internet, and test WiFi going to test VMs via the Vigor and a second NIC on the ESXi host. The switch can work as normal without any VLAN config just fine, or can be configured for one of three different VLAN modes. After initial check out in port mode with ports 1-4 in one VLAN and 5-8 in another I dived in to the wonderful world of tagged VLANs which I thought I understood. I do now... With hindsight it's actually easy to configure. Give an ID and friendly name to a VLAN, select which ports will connect to it and if they should leave tags in place or not for outbound traffic, save and repeat for next VLAN. Each port can have multiple tagged VLANs connected. Easy. I had three issues. Sorry, I mean learning experiences: The management functions of the WiFi router are only accessible via VLAN 1 (undocumented) which is nothing to do with this switch of course, but it means you need to have VLAN 1 defined between the router, switch and tagging set up so you can still reach it from a management PC. At least 1 port on the switch must also be assigned to VLAN 1. I'm thinking this is a TP-Link thing and kinda makes sense. At least its mentioned in switch documentation, and since I need VLAN 1 for the Wifi it's no big deal. There's 4094 other IDs to chose from after all. For untagged traffic entering the switch from a normal PC or hub, you need to configure the default VLAN for that port *on a separate config screen" if you want the traffic to go on a VLAN. Really obvious in hindsight, but took me a little while to figure out what was going on. Maybe the lesson is not to try doing this late in the evening after a long day, nice dinner and couple of glasses of wine. Although it's only been in use for a couple of weeks it's doing the job very nicely. I'm using this for a home office & lab but I'd have no issues using in a "proper" commercial environment either.
J**R
Desde que lo compre lo puse a trabajar 24x365 y no presenta fallo alguno. Excelente hardware y muy rápido con sus puertos 1Gb. Es administrable por lo que puedo formar Vlans.
A**R
حل مشكلة منافذ الروتر لدي، ويعمل بكفائه والسرعة المطلوبة على الرغم من توصيل اكثر من جهاز به، ليس له صوت وسهل الاستخدام
J**A
Es reducido y de calidad
S**S
Muito bom
Trustpilot
2 weeks ago
1 week ago