Set priority inside mangle output does not work

RouterOS General
1

I tried to set a priority inside an output mangle rule without success.


When i watch packets (Wireshark) outgoing from the Routerboard interface, priority stay at “0” value inside the 802.1q tag.


Paquets are generated from the RouterOS Ping tools.



Does anyone got succesfull results with Vlan priority marking inside Mangle rules ?

2

I have just tested RB450G with v5.0beta1 - all is working, I can see VLAN priority by Wireshark

I can check v4.* if you want… =)

3

Same version here.

Are you watching packets from the ping tool ?

I will retry today. Quite strange. I ask myself if the priority value would not have been deleted by the Intel driver on my laptop.
I’m using the Intel advanced Proset driver registry trick to allow vlan monitoring with wireshark (MonitoringModeEnabled=1), and i can see vlan tags inside wireshark, but priority stay at “0” value.

I will wireshark my switch to see if i can really see priority tags.

4

yes, I added VLAN interface, IP address, static ARP entry and was pinging that entry. then added a rule to change priority - and I saw in Wireshark that it was changed

my PC is connected directly to the RB

5

Interesting.

From where did you sent pings ? from the PC or from RB ? Can you try to send ping requests from RB Ping tool and see if packets do arrive to the PC with a priority tag ?

6

of course I was pinging from the RB =)

7

You are right it is working.

I think that there was a problem in my setup.

I’ve found that it is not possible to wireshark VLAN Tags on a PC if the destination IP address is the Vlan IP address of this PC.

In other words we cannot use a PC to monitor Vlan Tags and at the same time connect to the network (except if using a an Ethernet analyzer card addon with a TAP bridge, or a triple card setup with a software bridge on two of them + a hardware tap).

The problem is that when we switch the Intel Ethernet card to “MonitorModeEnabled”, so that Vlan Tags are not filtered and can target wireshark, slave Vlan Interfaces do not connect anymore on the Vlans.

Seems like the only way to monitor effectively Vlans tags, is to put the PC on a mirror port on RB or on a switch, and use other machines to generate trafic.