IP ToS Field Tagging in Openflow

Question

IP ToS Field Tagging in Openflow

Navigation

#1 by (1 votes)
#2 by (1 votes)

21

I'm a beginner at this, so I have a question.

Considering a video application called DASH IF (dash.js) that runs (emulated) on a mesh network with SDN (Software Defined Network).

I want the ToS (Type of Service) field to be marked in the package so that the switch openflow on the network knows that it is a special package and should be sent to the controller.

How can I make this markup? Or would it be the implementation of this? Is it the switch that does or should it be implemented in the application?

Thank you all right away!

sdn ipv4

asked by anonymous 27.11.2015 / 00:01

2 answers

Is it possible to add scroll-only overflow behavior in a table's tbody? Constraint on table change with subquery

score 1 · Answer 1

Hello! I have little knowledge in the field, but for all I know, it's the controller that defines all the intelligence of the switch. So if you have any package checks before it is routed, this will be defined in the implementation of that switch on the controller that is developed in Python.

Marking a packet in the ToS field causes each packet to be parsed before being routed. I think it would be better to indicate the source of the package, or port, or ip or etc so that it would be more effective and from there send it somewhere.

I hope I have helped

score 1 · Answer 2

I have little knowledge in the area, but for all I know, it's the controller that defines all the switch intelligence. So if you have any package checks before it is routed, this will be defined in the implementation of that switch on the controller that is developed in Python.

In this case, in my view and complementing what colleague Lstonon mentioned, the marking should be performed by the first switch that receives these packages. This would require a rule that identifies the source of the package and modifies that field. For this rule to make such a modification, it should receive the action = set . The only problem is that this ToS change is only available in the OpenFlow version 1.0 .

So from what I researched, it would be something like this:

add-flow s1(nome do switch) tcp,nw_src=ip.do.servidor,tp_src=porta_origem,actions=set,tos=dash

As I no longer have an SDN environment, I could not validate whether the rule is complete or not. I believe you will need adjustments. But I hope it helps.