rakotomandimby wrote

I have a bunch of TL-SG2210P & TL-SG2424 (T1600G-28TS 2.0) and I would like to administer them from my desk without having to physically plug on each.

Assign each switch a different IP in the System (Default) VLAN. For example, my five switches have IPs 192.168.1.250, .251, .252. .253 and .254. I have no idea why you think that you would have to physically connect to the switch to reach its web UI. Of course the web UI can be accessed from any device which is also connected to the subnet the switch is in.

If you use a management VLAN different from the System VLAN, make sure to set the management VLAN on the switches requiring it. As for the T1600G you set the management IP(s) in menu "Routing" (where you did create the IPs for VLANs). Just enable or disable Admin status according to your needs.

See also http://www.tp-link.com/no/faq-956.html

Sure it does work. I do this all the day. A switch is not a router and you can use any IP to go to the switch independent of your network addressing scheme.

But I wonder why you don't just assign free static IPs from your network to the switches? What exactly is the problem in doing so?

I still don't get your problem.

In recent switches you assign an IP to the switch's interface of a VLAN. So, if you use VLAN 6 you assign the first switch's IP to the first interface on the first switch, the second switch's IP to the second interface on the second switch and so on.

For example, I use 192.168.1.250 for the first switch on VLAN 1, which is spread to all other switches. The second switch has 192.168.1.251 on its own interface for VLAN 1, the third switch has 192.168.1.252 on its interface for VLAN 1 and so on. I can easily address each switch from any member of VLAN 1.

Maybe, confusion did arise because you think that the VLAN has an IP. A VLAN never has an IP. It's the switch - more precisely: the switch's interface - which has an IP. You need this IP only for routing into a VLAN (if you use Inter-VLAN routing at all) or for accessing a particular switch over this VLAN.

Just imagine that the VLAN is a separate subnet, then it should become very clear that two interfaces on the same subnet never can share the same IP.

Again: you are not assigning IPs to a VLAN. You cannot assign IPs to a VLAN, that's impossible.

You assign IPs to an interface into a VLAN. A switch's interface is not the VLAN, it's an interface, albeit this interface can be a "door" into a VLAN.

The solution is simply to assign different IPs (192.168.0.1, 192.168.0.2, 192.168.0.3 etc.) to different switch interfaces to be able to reach them.
Of course, if you assign the same IP to different switch interfaces, this cannot work. How should a switch know which one you want to reach?

See your picture in post #1: it's a list of interfaces, it is not a list of VLANs. The VLAN ID, Mode, IP and so on belong to the interface. Maybe it helps if you give those interfaces a distinct name such as "switch1", "switch2", "switch3" etc. on the different switches to realize the difference.

Also, 192,168,0,1 isn't a valid IP: change commas into dots to make it an IP.

rakotomandimby wrote

I am sorry but you definitely may assign an IP to a VLAN.
This is something very often in complex environments.
For example, on the Cisco world, you can do like this: http://www.bhcblog.com/howto-create-vlans-on-a-cisco-switch/ (see step 2)

No, it does not assign an IP to the VLAN, but it (quote) "assigns IPs to the gateway for this VLAN" (end quote). A gateway is an interface, which needs to have a unique IP to be useful. The VLAN doesn't have nor does it need an IP. Of course, assigning an IP to a gateway of a given VLAN will assign (quote from the blog post you linked) "an address range to a VLAN" (end quote), which is the same as "assigning an IP range to a subnet". A VLAN is a (virtual) subnet and a subnet can have an IP range, but never a single IP address. If you still disagree, I wish you much fun in implementing TCP/IP for a subnet with only one IP address.

You can also see the 192.168.0.0/24 as the IP range for your VLAN, sure. But you cannot assign the IP 192.168.0.0 to a switch's interface (gateway) and you cannot assign an IP such as 192.168.0.1 to more than one device in the same subnet, except if you want such "very complex" setups, where you have to physically connect to a switch to play kind of a roulette in logically connecting to "the right switch" for managing it.

Especially in our case, the TP Link Official FAQ clearly states the assignment is to the Vlan ( http://www.tp-link.com/no/faq-956.html), so you are free to strongly argue this is not assigned to the Vlan but I do assert this is Vlan assignation

Definitely no.

Quote from the TP-Link FAQ: "If you want to change the default management IP address, you will have to go to “Routing”-” Interface ”,click on “Edit” for VLAN 1,and change the IP address and Subnet Mask." [of the interface]. In this menu you are assigning an IP to an interface and you are assigning an interface to a VLAN, that's why the menu reads " Interface list", not " VLAN list" and this interface is a property of the switch's routing policy. But the interface is local to the switch, while the VLAN can span more switches. The interface must have a single IP, the VLAN is used to carry traffic to all interfaces falling into a certain IP range.

If you don't believe me that a VLAN cannot have an IP assigned to it, maybe you believe other senior network admins (see the answers):

https://serverfault.com/questions/118449/why-does-a-vlan-have-an-ip-address

https://supportforums.cisco.com/t5/lan-switching-and-routing/does-native-vlan-need-ip-address/td-p/1886227


We can discuss this endlessly as long as you refuse to get the terminology right, therefore sorry, but I'm out of this discussion.