Hi all,

I have a RB951Ui-2HnD router with me, I am using it for a personal lab, not for internet access.
I have setup vlan1 on ether2 and ether3, vlan2 on ether4 and vlan3 has no assigned port. ether1 is the port I connected my laptop to in order to configure. I have an ESXi server on ether2. I am trying to get the router to forward my ICMP packets from my laptop to the ESXi server, and to be able to ping from vlan1 to vlan2. I can ping my gateways from the different VLANs but the router not being able to always ping my devices on the different VLANs.

Thank you, and I'm sorry this is the best way I was able to explain the issue.

My (first) reply:

- don't use vlan id = 1
- use a single bridge and add vlan filtering
- upgrade to latest LTS: 6.49.8
- read this : viewtopic.php?t=143620 (great explenation and examples)

Hi, thank you for the reply.

I know it's recommended to not use vlan-id=1, but this is a lab not a real setup in which the instructions said to do so.

When you say use a single bridge, what do you mean? What to link with the bridge?

Thank you for the advices and for the documentation, will go read it now <3

I know it's recommended to not use vlan-id=1, but this is a lab not a real setup in which the instructions said to do so.

The recommendation is not so much about production environment, it's about sink holes planted inside ROS if one wants to use VID 1 ... I'm not saying it's not possible, but one has to find all those sink holes to avoid the problems. So it's easier just to avoid VID=1 and be done with it.

When you say use a single bridge, what do you mean? What to link with the bridge?

The thing created under /interface bridge ... you've got 3 of them.

I lump all the interfaces inside 1 bridge and configure vlan filtering?

I lump all the interfaces inside 1 bridge and configure vlan filtering?

I guess you really should read the article @erlinden linked in reply #2 above.

I know it's recommended to not use vlan-id=1, but this is a lab not a real setup in which the instructions said to do so.

The recommendation is not so much about production environment, it's about sink holes planted inside ROS if one wants to use VID 1 ... I'm not saying it's not possible, but one has to find all those sink holes to avoid the problems. So it's easier just to avoid VID=1 and be done with it.

It's not just ROS. Lots of devices in the real world will treat VLAN 1 as "special" and do interesting and unpredictable things (if you are not familiar with that particular device) with traffic on VLAN 1. For example, you may hook up a switch and find that is does something unexpected with VLAN 1 - and then tear your hair out trying to figure out what some devices can't communicate as expected.

Simple solution - don't use VLAN 1 unless you specifically have to (and I DO have some devices that MUST use VLAN 1). Actually that last part is no longer the case as the firmware for those devices now allow assigning some other VLAN - but it used to require VLAN 1.

Okay thanks guys <3