Proper setup of switches
-
Well you would really have something like this:
WAN (re1) – DHCP
LAN (re2) -- 192.168.4.1/24
OPT1 (re0.5) VLAN05 --> 192.168.5.1/24
OPT2 (re0.10) VLAN10 --> 192.168.10.1/24
OPT3 (re0.15) VLAN15 --> 192.168.15.1/24
OPT4 (re0.20) VLAN20 --> 192.168.20.1/24The switch port connected to re0 would have to have VLANs 5, 10, 15, and 20 TAGGED on that switch port.
-
Well you would really have something like this:
WAN (re1) – DHCP
LAN (re2) -- 192.168.4.1/24
OPT1 (re0.5) VLAN05 --> 192.168.5.1/24
OPT2 (re0.10) VLAN10 --> 192.168.10.1/24
OPT3 (re0.15) VLAN15 --> 192.168.15.1/24
OPT4 (re0.20) VLAN20 --> 192.168.20.1/24The switch port connected to re0 would have to have VLANs 5, 10, 15, and 20 TAGGED on that switch port.
I cleaned up my original posting. I have the trunk on port 2 with all of the VLANS as well as with port 3.
-
(although, I am actually using a Tl-Link SG108E)
Bad choice. TP-Link switches don't handle VLANs properly. There's another thread about problems with the similar SG105E.
-
(although, I am actually using a Tl-Link SG108E)
Bad choice. TP-Link switches don't handle VLANs properly. There's another thread about problems with the similar SG105E.
Well, I have Netgear GS108E v2 (which is why I was using the TL-Link because of being able to access via the web interface as opposed to the configuration program for the v2) or a Mikrotik Routerboard RB951Ui (which I really didn't want to mess with because of the learning curve). Would any of these work better?
-
Probably, but the TP-Links definitely have problems.
-
I have the netgear 108ev3 and can tell that it works with vlans - unlike the tp-link pos.. The hopeful news is there is suppose to be some new "beta" firmware from tplink to fix the vlan nonsense they currently have. You can hope that their new firmware when/if released fixes the problem.
The v3 has web gui if that is what your after. Or you could go with the dlink 1100 it has web gui and also handles vlans correctly.
-
Yeah sorry but between the re0 (realtek) and TP-Link, your gonna have a bad day. :P
Assuming you can pop in a PCIe card, you can ebay some new gear for less than 50 USD and have intel NICs and a Cisco gigabit 24 port switch ;) A bit more to learn but its not that bad. Cisco has amazing documentation.
-
Yeah sorry but between the re0 (realtek) and TP-Link, your gonna have a bad day. :P
Assuming you can pop in a PCIe card, you can ebay some new gear for less than 50 USD and have intel NICs and a Cisco gigabit 24 port switch ;) A bit more to learn but its not that bad. Cisco has amazing documentation.
Well, it is what I have to work with… I could switch to equipment at the home location. But the reality is that I am trying to be a miserly as possibly on power since I am using the my travel trailer that I use when I am working. So the need for the APU, a decent low powered switch and probably the Nanostation.
-
(although, I am actually using a Tl-Link SG108E)
Bad choice. TP-Link switches don't handle VLANs properly. There's another thread about problems with the similar SG105E.
Probably, but the TP-Links definitely have problems.
Not all of them. More correctly: some low-end models don't, but their majority do handle VLANs properly.
-
The re drivers and the APU work fine even with dot1q. They are workhorses.
Being miserly is fine but that switch is broken. Get a D-Link DGS-1100-08. They're about $30 and they actually work.
-
The re drivers and the APU work fine even with dot1q. They are workhorses.
Being miserly is fine but that switch is broken. Get a D-Link DGS-1100-08. They're about $30 and they actually work.
I will go replace with the DGS-1100. I am somewhat confused, since the result of what I was trying to achieve seems to be working. On the SG108, I have the LAN interface on port 1; I have the OPT interface in port 2, which has VLAN[5, 10, 15, 20] trunked; I have my TL-Link WA901ND AP with multiple SSID using VLAN[5, 10, 15, 20] tagged on port 3 on the switch.
When I connect to a particular SSID using DHCP, I am assigned the appropriate IP address from the correct VLAN. I don't normally hard connect to the untagged ports, but if I create a static address in any of the VLANs or the LAN, I have proper connection on the subnet, I am unclear on the purpose of a untagged port as well as the PVID, but everything seems to work as I think is should be doing. So what does it mean that the TP-Link has issues?
-
"So what does it mean that the TP-Link has issues?"
Ports can not be removed from vlan 1.. Any broadcast traffic on vlan 1 will be seen on ALL Ports not just vlan 1 ports.. So if you have broadcast traffic on vlan 1, all your other vlan will see this traffic..
-
"So what does it mean that the TP-Link has issues?"
Ports can not be removed from vlan 1.. Any broadcast traffic on vlan 1 will be seen on ALL Ports not just vlan 1 ports.. So if you have broadcast traffic on vlan 1, all your other vlan will see this traffic..
I have the same issue on a TP-Link access point. As a result, IPv6 router advertisements are appearing on the wrong SSID, causing devices to get an address on the wrong prefix. While other TP-Link switches may be OK, I think it's better to just stay away from any company that does things that are so incompetent.
