Quantcast
Channel: Software Defined Networking topics
Viewing all articles
Browse latest Browse all 611

Unable to match on the updated DSCP mark given by meter

$
0
0

Hi,

I am facing yet another problem in the DSCP remark meters. 

consider this scenario: I have two tables and one meter. 

Table 0 directs packets into meter 1, and then into table 1. 

Meter 1 changes the DSCP mark of packets that are over the meter's rate from DSCP X to DSCP Y.

Table 1 has a flow entry that matches on DSCP Y.

Although packets are correctly remarked to DSCP Y as shown in the receiver's Wireshark capture, the flow entry in table 1 does not match any packets. If I originally send packets with DSCP Y with no metering, the flow entry is correctly matched.

It seems it is related somehow to the bug I have previously reported. The old DSCP mark is taken into account when performing the matching in the following tables instead of the new DSCP mark given by the meter.

At what point is the DSCP mark changed in the switch processing flow? It seems to me that the mark is changed after (or right before) the packet is queued and not inside the OpenFlow pipeline?

Note: I am only trying to match on the new meter DSCP mark as a workaround for the previous problem of incorrect queue selection, however, this also does not work :(  

Thanks,

Enas

 


Viewing all articles
Browse latest Browse all 611

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>