wireshark indicate that the switch route packet to the wrong Vlan
Hm, this means that besides the two VLANs you mentioned, there must be at least a third ("wrong") one (having a switch IP interface), because otherwise the only other (second) one besides the first one would always be the "proper" one - hence routing would work. Second, from what you say follows, that the switch _does_ routing between VLANs, it only selects a wrong VLAN for packet forwarding. Or in case that the "wrong" VLAN doesn't have a switch IP interface, would the packets then be erroneously bridged to that VLAN? Third, how can you see from wireshark running at a device other than the switch, how the switch indeed forwards (or bridges) IP packets? Or did you use Port Mirroring?
each equipment can ping all interface vlan on the switch (ex endpoint on vlan 1 can ping 192.168.1.250 and 192.168.0.250)
This is probably due to the so called "
weak host model" that any multihoming host (like your switch) might operate, even if it is not configured for (or able to do) routing.
Just for completeness: Can you tell the VLAN settings for the ports involved (untagged/tagged/no memberships, and also important: The PVID settings)?
Let's assume you try to ping from device 192.168.0.10 to 192.168.1.10. Before you start, you delete the ARP caches of both devices and the intermediate switch and start Wireshark on both devices.
Can you restrict the problem to one of the following steps that doesn't work (?):
- At 192.168.0.10: You should see an outgoing (broadcast) ARP request asking for the MAC address for 192.168.0.250.
- At 192.168.0.10: You should receive an incoming (unicast) ARP reply coming from the switch interface, which tells the requested MAC address for 192.168.0.250.
- At 192.168.0.10: You should see an outgoing IP packet (an echo request) sent from 192.168.0.10 to 192.168.1.10, encapsulated into an Ethernet frame from the local device's MAC address to the switch's MAC address corresponding to 192.168.0.250, that was resolved in steps 1 and 2.
- At 192.168.1.10: You should see an incoming (broadcast) ARP request coming from the switch's MAC address that belongs to 192.168.1.250, that asks for the MAC address for 192.168.1.10
- At 192.168.1.10: You should see an outgoing (unicast) ARP reply sent from the device's MAC address back to the switch's MAC address that corresponds to 192.168.1.250.
- At 192.168.1.10: You should see an incoming IP packet sent from 192.168.0.10 to 192.168.1.10, encapsulated into an Ethernet frame from the switch's MAC address corresponding to 192.168.1.250 to the MAC address of the local device.
- At 192.168.1.10: You should see an outgoing IP packet (an echo reply) sent from 192.168.1.10 to 192.168.0.10, encapsulated into an Ethernet frame from the local device's MAC address to the switch's MAC address corresponding to 192.168.1.250
- At 192.168.0.10: You should see an incoming IP packet sent from 192.168.1.10 to 192.168.0.10, encapsulated into an Ethernet frame from the switch's MAC address corresponding to 192.168.0.250 to the MAC address of the local device.
Up to which step can you proceed or rather which step will fail?
For example, if you can proceed to step 6 (inclusive) and step 7 fails (no echo reply sent), this might be due to a local host's firewall setting that refuses (drops) echo requests that stem from networks other than the local one (default behaviour of Windows).
Dlink support indicate to me that i have to take 1510 instead of 1210
Did they tell why? I mean: Routing between VLANs is an included/promised product feature, and if it doesn't work, you should return the switch to your dealer and get your money back.
