TP-LINK Smart Switches anyone?
-
I had severe issues with Zyxel and pfSense connecting to each other using VLAN-tagged connections. The symptom was: after changing any VLAN-interface-related config in pfSense, communication would completely stop between the Zyxel GS1910-24 switch and the pfSense box on that VLAN. The only solution was to unplug and re-plug the cable (!) into the very same port of the switch.
Never had anything even similar with any TP-Link or other switch. -
the usual big one vendors didn´t offer any device.
There are many other switches out, but not really in the same price range.
Cisco SG200-xx
Cisco SG300-xx
Cisco SG500-xx
D-Link DGS-1510-xx -
…the usual big one vendors didn't offer any device.
I doubt that.
Cisco SG300-28; HP 1810-24G, …Cisco SG300-28
Well, I consider this Linksys, not Cisco ;)
HP 1810-24G
clearly no IGMPv3 snooping capabilities
D-Link DGS-1510-xx
I bought those GS1910-24 ~ 2 years ago. There was no DGS-1510…
Well, I wouldn´t buy those Zyxel anymore...
-
Cisco SG300-28
Well, I consider this Linksys, not Cisco ;)
I hear you. Happily sold a couple SRW-2008/16/24 some time ago and don't look back.
These new SG-series devices are a whole lot different and there's a reason why Linksys is now a brand of Belkin. -
I have two VLANs defined on my Tplink TL-SG108E. The switch is on its own IP (192.168.0.1) which doesnt match with any of my local network. How can i put the switch ip on a separate vlan.
-
Ask TP-Link.
-
I have two VLANs defined on my Tplink TL-SG108E. The switch is on its own IP (192.168.0.1) which doesnt match with any of my local network. How can i put the switch ip on a separate vlan.
Is there a "Management VLAN" option anywhere in the menus?
If not, unfortunately this very basic "Easy Smart" model may not support this. This means the swicth's management interface is tied to VLAN 1.However, you can trick the whole thing by leaving it as it is in VLAN 1, and in pfSense configure the interface connecting to the switch also as untagged in 192.168.0.X/24. By simply putting all the other ports of the switch in different VLANs, you'll keep VLAN 1 as your management VLAN for the switch only.
-
I had severe issues with Zyxel and pfSense connecting to each other using VLAN-tagged connections. The symptom was: after changing any VLAN-interface-related config in pfSense, communication would completely stop between the Zyxel GS1910-24 switch and the pfSense box on that VLAN. The only solution was to unplug and re-plug the cable (!) into the very same port of the switch.
Never had anything even similar with any TP-Link or other switch.@work we have >50 zyxel switches some 22xx series / some 19xx series. Never had issue's and only very few hardware failures. some of those are connected to pfSense and i've never experienced anything like you are saying.
The last 5 years we've gotten 1x 2200 & 2x 1900 that were send back in warranty. even after 5 years of service they swapped them for free, no questions asked.in any case, over here in belgium, when you send your switch back to zyxel through the official RMA procedure…. the replacement arrives in 2-3 days (after they've received your defective device). If you got a good supplier he could/should give you are replacement immediately and handle the RMA himself.
return you broken sample :)Anyways, i love these zyxel switches:
-Dirt cheap (gs-1920-24 = around $130 | is actually 28ports, has 4 sfp)
-Good warranty
-Does everything i expect them todo
-Little failuressure, there are cheapo 24p cisco(linksys)/hp/dlink switches for <$150. they are either worse in what they do and/or they have less features then the zyxels.
i'm not saying other vendors are all selling crap:
zyxel can/will not compete with top-end device from cisco/juniper/allied telesis/brocade. so if you need a $5k switch (for whatever reason) you'll end up with the big guns. -
-
Is there a "Management VLAN" option anywhere in the menus?
If not, unfortunately this very basic "Easy Smart" model may not support this. This means the swicth's management interface is tied to VLAN 1.However, you can trick the whole thing by leaving it as it is in VLAN 1, and in pfSense configure the interface connecting to the switch also as untagged in 192.168.0.X/24. By simply putting all the other ports of the switch in different VLANs, you'll keep VLAN 1 as your management VLAN for the switch only.
No there is no "Management VLAN" anywhere in the menus. At the moment I have defined 3 vlans, VLAN 100/VLAN 200/VLAN 300 on pfsense box for the igb1 interface (which is connected to the switch). Are you suggesting one of the following?
a. Define "192.168.0.X/24" on the parent interface of these vlans
b. Create an additional VLAN 1 on pfsense box and define it as "192.168.0.X/24"Thanks
-
At least something like a "default" VLAN?
OK, just had a look at the manual. Well, you don't even configure this device directly but through an "Easy Smart Configuration Utility".
Just try putting all ports on one VLAN (like your V100) and see if you can still reach the device through the utility program.
Otherwise, the reset button is right next to the RJ45 ports… -
Are you suggesting one of the following?
a. Define "192.168.0.X/24" on the parent interface of these vlans
That's exactly what I'm suggesting.
And don't forget to set the proper gateway address in the System IP address of the switch. -
As far as the Zyxels are concerned in our environment, the management just decided to replace them all with TP-Links so the whole VLAN-divided network will be homogeneous.
They will be used as simple dumb Layer II swhicthes at special events only, where quick deployment of tens of ports is needed for a few days only - no VLANs used at their level anymore.Zyxels performed well in our environment as long as they didn't need to handle VLANs connected to non-zyxel equipment. So - as dumb switches, or as members of a VLANned network where only Zyxels are exchanging tagged packets with each other - they are fine. Looking at the swith solely it's not possible to RMA it, because it's not defective. It just simply has interoperability problems with other manufacturers equipment, and that seems to be by design.
-
Zyxels performed well in our environment as long as they didn't need to handle VLANs connected to non-zyxel equipment.
ZyXEL has been making switches a long time. I can't believe they can't handle dot1q.
-
I want to use port 8 as a trunk port and want to connect a freenas box to it. The freenas box will have multiple vlan setup. Before going down the Freenas route i wanted to check if indeed port 8 was being set as a trunk port. I hooked up my linux laptop to the port 8 after defining a vlan100 for its nic. Unfortunately, the linux laptop was unable to get the ip address from VLAN100 (LAN).
Is this the right way to define port 8 as a tunk port (images attached)?
-
untagging multiple vlans on the same port is seldom a good idea.
vlan trunks generally use tagging…..
-
Ok. This is how i got this working. Had to change Port 8 to tagged. And now the laptop is able to get the ip address.
-
When you have multiple VLANs on one port they all should be tagged, making it a trunk.
If you need a VLAN untagged then it should be the only VLAN on that port (and PVID). -
Hi all,
I have this setup:1 x.x.x.x/24 public pool (I get to the internet through a ethernet port on the rack that is connected to the switch)
1 tp-link TL-SL2428 switch
7 pcs (this machines change the ip from time to time)
2 servers (mail, web, ssh, etc)all using the referred x.x.x.x/24 public pool
All this runs ok, I just plug the ethernet wires to the switch and have no problem
Now they are asking me to add a new /24 pool to use with the same hardware (or add more machines) so lets call the new
range y.y.y.y/24 which It would be provided through a different ethernet portMy idea is:
Plug a wire from a free port of the switch to the new rack's port that it provides the new y.y.y.y/24 public range
Let the wire for the x.x.x.x/24 as it is (plugged)So with this setup when I configure a machine's ip, gateway, etc according to range y.y.y.y/24 it should get out to the internet
in the same way it does x.x.x.x/24.Am I right?
I think I do not even need vlans right?
If I am and that works I have a few more doubts I'd like to ask.
Thank you. -
Don't do that.
x.x.x.x/24 and y.y.y.y/24 are different networks, they must never be on the same layer II segment.Those switches are inexpensive. Just buy another one if you don't want to mess with VLANs and have free space in the rack.
If not, make 3 VLANs:- VLAN1 (this is factory default, keep it for management of the switch), and assign it to one single dedicated management port (say port 24) just for managing the switch now and in the future. Remove all the other ports from VLAN1!
- VLAN10 for x.x.x.x/24, assign ports, for example, from 1 to 8 to this, connect old ISP wire to port 1
- VLAN20 for y.y.y.y/24, assign ports, for example, from 9 to 16 to this, connect new ISP wire to port 9
Connect the pcs and servers according to their correct pools to the ports above.
Maybe you could label the ports visually on the switch or rack, to remember easily which ports belong to which pool.
