我心永恒 | 25 Feb 10:50 2015
Picon

Questions of Mininet/Openflow-tutorial

Dear instructor, I'm a new student in the mininet/openflow-tutorial. I want to seek for solutions for two problems I encountered.

First one, In the section of "Learn Development Tools", when I set-up the switch by adding new flows using the cmd "ovs-ofctl add-flow s1 in_port=1,actions=output:2" and "ovs-ofctl add-flow s1 in_port=2,actions=output:1", the two entries seem never expire in the switch, but according to the tutorial, they owe to disappear after the default duration (60 s), so I really cannot understand this.

Second one, in the subsection named "View Openflow Messages For Ping", I can get the Hello/Features req/reply messages, but I cannot get the packet-in, packet-out, flow-mod messages at all, they seem never appear in the Wireshark window, I doubt the effect of the "controller ptcp:" command, can it really trigger packet-in message upon a table miss? Or maybe this is due to another problem still unknown to me, could you give me some hints?

ps: my OS is ubuntu 14.04 LTS, Memory 15.5 GiB, Disk 705 GB, processor Intel® Core™ i7-4800MQ CPU <at> 2.70GHz × 8. Virtualization software is VirtualBox, version: 4.3.10_Ubuntur93012, X11 version: X.Org X Server 1.15.1. VM image is mn-2.2.0-trusty64server-141209-14-11-49. 

Expect your reply and gratitude in advance!

  Best Regards
  Zhang Tianzhu
<div><div dir="ltr">
<span>Dear instructor, I'm a new student in the mininet/openflow-tutorial. I want to seek for solutions for two problems I encountered.</span><div><br></div>
<div>First one, In the section of "Learn Development Tools", when I set-up the switch by adding new flows using the cmd "<span>ovs-ofctl add-flow s1 in_port=1,actions=output:2</span>" and "<span>ovs-ofctl add-flow s1 in_port=2,actions=output:1</span>", the two entries seem never expire in the switch, but according to the tutorial, they owe to disappear after the default duration (60 s), so I really cannot understand this.</div>
<div>
<div><br></div>
<div>Second one, in the subsection named "View Openflow Messages For Ping", I can get the Hello/Features req/reply messages, but I cannot get the packet-in, packet-out, flow-mod messages at all, they seem never appear in the Wireshark window, I doubt the effect of the "controller ptcp:" command, can it really trigger packet-in message upon a table miss? Or maybe this is due to another problem still unknown to me, could you give me some hints?</div>
</div>
<div><br></div>
<div>ps: my OS is ubuntu 14.04 LTS, Memory 15.5 GiB, Disk 705 GB, processor&nbsp;Intel&reg; Core&trade; i7-4800MQ CPU  <at>  2.70GHz &times; 8. Virtualization software is VirtualBox, version: 4.3.10_Ubuntur93012, X11 version: X.Org X Server 1.15.1. VM image is&nbsp;mn-2.2.0-trusty64server-141209-14-11-49.&nbsp;</div>
<div><br></div>
<div>Expect your reply and gratitude in advance!</div>
<div><br></div>
<div>&nbsp; Best Regards</div>
<div>&nbsp; Zhang Tianzhu</div>
</div></div>
Mehrdad Moradi | 24 Feb 22:08 2015
Picon

Packet Tags

Hi All,

I'm dealing with a problem that requires to match the 
traffic on two labels at a given time without pushing 
or popping any of them. For example, 

match (vlan_id = 10, dscp = 20): drop packet or 
match (mpls_label = 20, dscp = 30): drop packets

given the above, is such operation possible in the 
latest openflow? 

-----
Mehrdad Moradi


<div><div dir="ltr">Hi All,<div><br></div>
<div>I'm dealing with a problem that requires to match the&nbsp;</div>
<div>traffic on two labels at a given time without pushing&nbsp;</div>
<div>or popping any of them. For example,&nbsp;</div>
<div><br></div>
<div>match (vlan_id = 10, dscp = 20): drop packet or&nbsp;</div>
<div>match (mpls_label = 20, dscp = 30): drop packets</div>
<div><br></div>
<div>given the above, is such operation possible in the&nbsp;</div>
<div>latest openflow?&nbsp;</div>
<div><br></div>
<div><div>
<div class="gmail_signature">
<span>-----<br></span><span>Mehrdad Moradi</span><br><span><br><div><br></div>
<div></div></span>
</div>
</div></div>
</div></div>
Clément Rault | 17 Feb 15:33 2015
Picon

Use of multiple group entries on a single packet

Hi all,


I am currently trying to implement an algorithm allowing an alternative path to be found without the need to contact the controller. And for that I need to use group entries of the fast failover type. In my algorithm, I'm using action buckets of multiple group entries on a single packet and I'm wondering if it's possible in practice (with OpenFlow) as group entries actions are processed almost right at the end and it might not be possible to go back to flow tables after that.


For example I have the following (simple) scenario:

Table 0:
Apply Gr 0 actions, Goto Table 1

Gr 0:
If port 1 is up then forward the packet there, put metadata to 1

Table 1:
If metadata is at 0 then Apply Gr 1 actions

Gr 1:
If port 2 is up then forward the packet there


I tried it (with mininet and ryu) but it didn't work and I'm worried that it's because it's not possible to apply the actions of multiple group entries. And probably because group entries actions are processed after going through all the flow tables.


I would really appreciate, if anyone can kindly help me to understand, if the following scenario is not working because of a design "issue" of Openflow or because it's an implementation issue (with ryu in my case).


Thanks in advance,

Best,
Clément
<div><div dir="ltr">Hi all,<br><br><br>I am currently trying to implement an algorithm allowing an alternative path to be found without the need to contact the controller. And for that I need to use group entries of the fast failover type. In my algorithm, I'm using action buckets of multiple group entries on a single packet and I'm wondering if it's possible in practice (with OpenFlow) as group entries actions are processed almost right at the end and it might not be possible to go back to flow tables after that.<br><br><br>For example I have the following (simple) scenario:<br><br>Table 0:<br>Apply Gr 0 actions, Goto Table 1<br><br>Gr 0:<br>If port 1 is up then forward the packet there, put metadata to 1<br><br>Table 1:<br>If metadata is at 0 then Apply Gr 1 actions<br><br>Gr 1:<br>If port 2 is up then forward the packet there<br><br><br>I tried it (with mininet and ryu) but it didn't work and I'm worried that it's because it's not possible to apply the actions of multiple group entries. And probably because group entries actions are processed after going through all the flow tables.<br><br><br>I would really appreciate, if anyone can kindly help me to understand, if the following scenario is not working because of a design "issue" of Openflow or because it's an implementation issue (with ryu in my case).<br><br><br>Thanks in advance,<br><br>Best,<br>Cl&eacute;ment</div></div>
Chengchen Hu | 16 Feb 22:47 2015
Picon

An open source hardware for SDN innovation

Dear colleagues, 

 

This email is to inform you a new open source hardware for SDN innovation called ONetSwitch. It is an all-programmable networking platform combining ARM and FPGA in a 17cm*13cm area (notebook size) for testing and verifying research idea related to networking. Different from previous FPGA develop board like NetFPGA/Xilinx PCIe board, host PC is not required any more for ONetSwitch, and it is smaller, cheaper, and more power efficient. and more flexible.

 

Last Monday, we have launched the ONetSwitch project on Kickstarter.com (a very famous crowd funding web). You can get an abstract from the short cool video (not take you long to get our idea :-) ): 

https://www.kickstarter.com/projects/onetswitch/onetswitch-open-source-hardware-for-networking

 

 

We had a paper at ONS 2014 presenting the preliminary design of ONetSwitch (https://www.usenix.org/system/files/conference/ons2014/ons2014-paper-hu_chengchen.pdf) and a demo at SIGCOMM'14 setting a data center testbed on only desktop using ONetSwitch (http://nskeylab.xjtu.edu.cn/people/huc/Pub/DesktopDC_2014.pdf). In the new version now at kickstarter, we add further physical support on 802.11 AC, mSATA, which suits for more scenarios. Also, we have open source ref. design and supporting wiki available at github (https://github.com/MeshSr/wiki/wiki/REF-OpenFlowSwitch-HWFT).  The processing logic can be modified in both software (ARM) and hardware (FPGA) to fit your own needs. Although it is currently highlighted mainly on SDN and DCN, we aim to provide the research community a way to set their testbed for any networking innovations easily. 

 

I send the info. about ONetSwitch to this mail list since I think it may be useful to guys in this community. Please do us a favor and back us to get your own programmable testbed. We believe ONetSwitch would give much help to your research and development work. Also, can you help distribute it to friends and colleagues who will be interested with this? Even the guys, who do not need ONetSwitch but think it is good, we greatly appreciate you to back us with $1 for encouraging. 

 

Regards,

 

Chengchen Hu

 

=======================================================================
Dr. Chengchen Hu, 

 

Associate Professor (Sabbatical leave till Oct., 2015)
Xi'an Jiaotong University

 

ERCIM Fellow
Norwegian University of Science and Technology (NTNU)

 

http://nskeylab.xjtu.edu.cn/people/cchu
=======================================================================

 

<div><div dir="ltr">
<p class="MsoNormal" align="left"><span lang="EN-US">Dear colleagues,&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">This email is to inform you&nbsp;a new&nbsp;open</span><span lang="EN-US">&nbsp;</span><span lang="EN-US">source hardware&nbsp;for SDN innovation called ONetSwitch.&nbsp;It is an all-programmable networking platform combining ARM and FPGA in a 17cm*13cm area (notebook size) for testing and verifying research idea related to networking. Different&nbsp;from&nbsp;previous FPGA develop&nbsp;board&nbsp;like NetFPGA/Xilinx PCIe board, host PC is not required any more for ONetSwitch,&nbsp;and it&nbsp;is smaller, cheaper, and more power efficient.&nbsp;and more flexible.</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">Last Monday, we have&nbsp;launched&nbsp;the&nbsp;ONetSwitch project on Kickstarter.com&nbsp;(a very famous crowd funding web). You can get&nbsp;an&nbsp;abstract from the short cool video (not take you&nbsp;long to get our idea :-) ):&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US"><a href="https://www.kickstarter.com/projects/onetswitch/onetswitch-open-source-hardware-for-networking" target="_blank"><span>https://www.kickstarter.com/projects/onetswitch/onetswitch-open-source-hardware-for-networking</span></a>.&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">We&nbsp;had&nbsp;a paper&nbsp;at ONS 2014 presenting&nbsp;the preliminary design of ONetSwitch (<a href="https://www.usenix.org/system/files/conference/ons2014/ons2014-paper-hu_chengchen.pdf" target="_blank"><span>https://www.usenix.org/system/files/conference/ons2014/ons2014-paper-hu_chengchen.pdf</span></a>) and a demo at&nbsp;SIGCOMM'14&nbsp;setting a data center testbed on only desktop using ONetSwitch (<a href="http://nskeylab.xjtu.edu.cn/people/huc/Pub/DesktopDC_2014.pdf" target="_blank"><span>http://nskeylab.xjtu.edu.cn/people/huc/Pub/DesktopDC_2014.pdf</span></a>).&nbsp;In the new version now at&nbsp;kickstarter, we add&nbsp;further&nbsp;physical support on 802.11 AC, mSATA, which suits for more scenarios.&nbsp;Also, we have open source ref. design and supporting wiki available at github (<a href="https://github.com/MeshSr/wiki/wiki/REF-OpenFlowSwitch-HWFT" target="_blank"><span>https://github.com/MeshSr/wiki/wiki/REF-OpenFlowSwitch-HWFT</span></a>).&nbsp;&nbsp;The processing logic can be modified in both software (ARM) and hardware (FPGA) to fit your own needs. Although it is currently highlighted mainly&nbsp;on SDN and DCN, we aim to provide the research community a way to set their testbed for any networking innovations easily.&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">I send the info. about ONetSwitch to this mail list since I think&nbsp;it may be useful to guys in this community. Please do us a favor and back us to get your own programmable testbed. We believe ONetSwitch&nbsp;would&nbsp;give much help to your research and development work. Also, can you help distribute it to friends and colleagues who will&nbsp;be interested with this? Even the guys, who do not need ONetSwitch but think it is good, we greatly appreciate you to back us with $1 for encouraging.&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">Regards,</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">Chengchen Hu</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">=======================================================================<br>Dr. Chengchen Hu,&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">Associate Professor (Sabbatical leave till Oct., 2015)<br>Xi'an Jiaotong University</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">ERCIM Fellow<br>Norwegian University of Science and Technology (NTNU)</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">&nbsp;</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US"><a href="http://nskeylab.xjtu.edu.cn/people/cchu" target="_blank"><span>http://nskeylab.xjtu.edu.cn/people/cchu</span></a><br>=======================================================================</span></p>
<p class="MsoNormal" align="left"><span lang="EN-US">&nbsp;</span></p>
</div></div>
Ruchika Verma | 30 Jan 06:38 2015
Picon

OpenVSwitch Supports SSL

hello,

I am new to SDN and OVSwitch.

I have a basic query - does OpenVSwitch supports SSL?

If yes(which as per my current understanding is true), how do i make OVS SSL capable? Also, in which property will the switch communicate the SSL properties to controller?

I am able to create the keys and certificates using below command. 

sudo ovs-pki req+sign ctl controller sudo ovs-pki req+sign sc switch sudo ovs-vsctl set-ssl \ /etc/openvswitch/sc-privkey.pem \ /etc/openvswitch/sc-cert.pem \ /var/lib/openvswitch/pki/controllerca/cacert.pem

But i am not able to make the switch communicate the same to controller it seems, because when i check it through -

sudo ovs-vsctl showit shows tcpip connection instead of SSL.

Can you please guide.


Thanks
Ruchika
<div><div dir="ltr">
<div class="gmail_default">hello,</div>
<div class="gmail_default"><br></div>
<div class="gmail_default">I am new to SDN and OVSwitch.</div>
<div class="gmail_default"><br></div>
<div class="gmail_default">I have a basic query - does OpenVSwitch supports SSL?</div>
<div class="gmail_default"><br></div>
<div class="gmail_default">If yes(which as per my current understanding is true), how do i make OVS SSL capable? Also, in which property will the switch communicate the SSL properties to controller?</div>
<div class="gmail_default"><br></div>
<div class="gmail_default">I am able to create the keys and certificates using below command.&nbsp;</div>
<div class="gmail_default"><br></div>
<div class="gmail_default">sudo ovs-pki req+sign ctl controller
sudo ovs-pki req+sign sc switch
sudo ovs-vsctl set-ssl \
    /etc/openvswitch/≤span class="">sc-privkey.pem</span> \
    /etc/openvswitch/≤span class="">sc-cert.pem</span> \
    /var/lib/openvswitch/pki/controllerca/≤span class="">cacert.pem</span>
</div>
<div class="gmail_default"><br></div>
<div class="gmail_default">But i am not able to make the switch communicate the same to controller it seems, because when i check it through -</div>
<div class="gmail_default"><br></div>
<div class="gmail_default">sudo ovs-vsctl show<span>it shows tcpip connection instead of SSL.</span><br>
</div>
<div class="gmail_default"><br></div>
<div class="gmail_default">Can you please guide.</div>
<div class="gmail_default"><br></div>
<div class="gmail_default"><br></div>
<div class="gmail_default">Thanks</div>
<div class="gmail_default">Ruchika</div>
</div></div>
Sheena Goyal | 22 Jan 09:44 2015

Regarding permission for usage of OpenVSwitch reference.

Hi Team,

I am writing a whitepaper and wanted your permission to use the reference of  Openflow Switch Specification Version 1.4.0 in our whitepaper.
Is this the right place to seek permission or please direct me where to send the mail for the same ?


Thanks & Regards
Sheena Goyal

=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain
confidential or privileged information. If you are
not the intended recipient, any dissemination, use,
review, distribution, printing or copying of the
information contained in this e-mail message
and/or attachments to it are strictly prohibited. If
you have received this communication in error,
please notify us by reply e-mail or telephone and
immediately and permanently delete the message
and any attachments. Thank you

<div>Hi Team,
<br><br>I am writing a whitepaper and wanted
your permission to use the reference of &nbsp;Openflow
Switch Specification Version 1.4.0
in our whitepaper.<br>
Is this the right place to seek permission or please direct me where to
send the mail for the same ?
<br><br><br>
Thanks &amp; Regards<br>
Sheena Goyal<p>=====-----=====-----=====<br>
Notice: The information contained in this e-mail<br>
message and/or attachments to it may contain <br>
confidential or privileged information. If you are <br>
not the intended recipient, any dissemination, use, <br>
review, distribution, printing or copying of the <br>
information contained in this e-mail message <br>
and/or attachments to it are strictly prohibited. If <br>
you have received this communication in error, <br>
please notify us by reply e-mail or telephone and <br>
immediately and permanently delete the message <br>
and any attachments. Thank you</p>

<p></p>
</div>
Azouni Abdelhadi | 21 Jan 18:32 2015

Controller reaction to ARP requests

Hello all,

From an OpenFlow view, how should a controller reply to a message-in containing an ARP request (that the of-switch didn't know how to handle) ? in both cases: 
1. the controller has the info about the requested IP
2. the controller has not the info 

Thank you 
<div><div dir="ltr">
<span>Hello all,</span><div><br></div>
<div>From an OpenFlow view, how should a controller reply to a message-in containing an ARP request (that the of-switch didn't know how to handle) ? in both cases:&nbsp;</div>
<div>1. the controller has the info about the requested IP</div>
<div>2. the controller has not the info&nbsp;</div>
<div><br></div>
<div>Thank you&nbsp;</div>
</div></div>
tech_kals Kals | 20 Jan 17:58 2015
Picon

Connecting openflow switch to the controller

Hi Experts,

I am very new to openflow protocol. have started to go through the openflow specification. I have few doubts. I see, there are some reserved ports supported by the switch.
Those reserved ports have been given below. 

1) Are they a logical port or physical port?

2) Reserved port types are ALL/ CONTROLLER/ TABLE/ IN_PORT/ ANY/ LOCAL/ NORMAL/ FLOOD. 
     will we mention these types anywhere in the port configuration? I am really getting confused. where this ALL port type would be mentioned? can someone clarify ?

3) If you have config in your hand, could you please share ? I just want to take a look at it.

4) CONTROLLER: The physical port which is connected to the controller would be configured as "controller port"? what will happen, if i dont configure a port as controller port even though it has been connected to the controller?



---------------
Required: ALL: Represents all ports the switch can use for forwarding a specic packet. Can
be used only as an output port. In that case a copy of the packet is sent to all standard ports,
excluding the packet ingress port and ports that are congured OFPPC_NO_FWD.

ˆ Required: CONTROLLER: Represents the control channel with the OpenFlow controller. Can
be used as an ingress port or as an output port. When used as an output port, encapsulate the
packet in a packet-in message and send it using the OpenFlow protocol (see A.4.1). When used
as an ingress port, this identies a packet originating from the controller.

ˆ Required: TABLE: Represents the start of the OpenFlow pipeline. This port is only valid in an
output action in the action list of a packet-out message, and submits the packet to the flowow table 
so that the packet can be processed through the regular OpenFlow pipeline.

ˆ Required: IN PORT: Represents the packet ingress port. Can be used only as an output port,
send the packet out through its ingress port.

ˆ Required: ANY: Special value used in some OpenFlow commands when no port is specied (i.e.
port is wildcarded). Can neither be used as an ingress port nor as an output port.

ˆ Optional: LOCAL: Represents the switch's local networking stack and its management stack.
Can be used as an ingress port or as an output port. The local port enables remote entities to
interact with the switch and its network services via the OpenFlow network, rather than via a
separate control network. With a suitable set of default 
ow entries it can be used to implement
an in-band controller connection.

ˆ Optional: NORMAL: Represents the traditional non-OpenFlow pipeline of the switch (see 5.1).
Can be used only as an output port and processes the packet using the normal pipeline. If the
switch cannot forward packets from the OpenFlow pipeline to the normal pipeline, it must indicate
that it does not support this action.

ˆ Optional: FLOOD: Represents 
ooding using the normal pipeline of the switch (see 5.1). Can
be used only as an output port, in general will send the packet out all standard ports, but not to
the ingress port, nor ports that are in OFPPS_BLOCKED state. The switch may also use the packet
VLAN ID to select which ports to food.

--------------
<div><div dir="ltr">Hi Experts,<div><br></div>
<div>I am very new to openflow protocol. have started to go through the openflow specification. I have few doubts. I see, there are some reserved ports supported by the switch.</div>
<div>Those reserved ports have been given below.&nbsp;</div>
<div><br></div>
<div>1) Are they a logical port or physical port?</div>
<div><br></div>
<div>2) Reserved port types are ALL/ CONTROLLER/ TABLE/ IN_PORT/ ANY/ LOCAL/ NORMAL/ FLOOD.&nbsp;</div>
<div>&nbsp; &nbsp; &nbsp;will we mention these types anywhere in the port configuration? I am really getting confused. where this ALL port type would be mentioned? can someone clarify ?</div>
<div><br></div>
<div>3) If you have config in your hand, could you please share ? I just want to take a look at it.</div>
<div><br></div>
<div>4) CONTROLLER: The physical port which is connected to the controller would be configured as "controller port"? what will happen, if i dont configure a port as controller port even though it has been connected to the controller?</div>
<div><br></div>
<div>
<br><div><br></div>
<div>---------------</div>
<div>
<div>Required: ALL: Represents all ports the switch can use for forwarding a specic packet. Can</div>
<div>be used only as an output port. In that case a copy of the packet is sent to all standard ports,</div>
<div>excluding the packet ingress port and ports that are congured OFPPC_NO_FWD.</div>
<div><br></div>
<div>&#136; Required: CONTROLLER: Represents the control channel with the OpenFlow controller. Can</div>
<div>be used as an ingress port or as an output port. When used as an output port, encapsulate the</div>
<div>packet in a packet-in message and send it using the OpenFlow protocol (see A.4.1). When used</div>
<div>as an ingress port, this identies a packet originating from the controller.</div>
<div><br></div>
<div>&#136; Required: TABLE: Represents the start of the OpenFlow pipeline. This port is only valid in an</div>
<div>output action in the action list of a packet-out message, and submits the packet to the flowow table&nbsp;</div>
<div>so that the packet can be processed through the regular OpenFlow pipeline.</div>
<div><br></div>
<div>&#136; Required: IN PORT: Represents the packet ingress port. Can be used only as an output port,</div>
<div>send the packet out through its ingress port.</div>
<div><br></div>
<div>&#136; Required: ANY: Special value used in some OpenFlow commands when no port is specied (i.e.</div>
<div>port is wildcarded). Can neither be used as an ingress port nor as an output port.</div>
<div><br></div>
<div>&#136; Optional: LOCAL: Represents the switch's local networking stack and its management stack.</div>
<div>Can be used as an ingress port or as an output port. The local port enables remote entities to</div>
<div>interact with the switch and its network services via the OpenFlow network, rather than via a</div>
<div>separate control network. With a suitable set of default&nbsp;</div>
<div>ow entries it can be used to implement</div>
<div>an in-band controller connection.</div>
<div><br></div>
<div>&#136; Optional: NORMAL: Represents the traditional non-OpenFlow pipeline of the switch (see 5.1).</div>
<div>Can be used only as an output port and processes the packet using the normal pipeline. If the</div>
<div>switch cannot forward packets from the OpenFlow pipeline to the normal pipeline, it must indicate</div>
<div>that it does not support this action.</div>
<div><br></div>
<div>&#136; Optional: FLOOD: Represents&nbsp;</div>
<div>ooding using the normal pipeline of the switch (see 5.1). Can</div>
<div>be used only as an output port, in general will send the packet out all standard ports, but not to</div>
<div>the ingress port, nor ports that are in OFPPS_BLOCKED state. The switch may also use the packet</div>
<div>VLAN ID to select which ports to food.</div>
</div>
</div>
<div><br></div>
<div>--------------</div>
</div></div>
Steve Uhlig | 17 Jan 17:56 2015
Picon

2 open postdoc positions on SDN for IXPs within EU ENDEAVOUR project

The School of Electronic Engineering and Computer Science at Queen Mary, 
University of London is seeking to appoint two Research Assistants as part of
the project “Towards a flexible software-defined network ecosystem” (ENDEAVOUR), 
funded by the EU within the Horizon 2020 program.

The successful candidates will be responsible for investigating software-defined networking 
(SDN) aspects relevant for the next generation of Internet Exchange Points (IXP). This will 
involve: 
(1) analyzing large-scale network data, 
(2) the development and application of SDN software in the context of IXPs, and 
(3) the design of new distributed systems techniques for network management.

The closing date for applications is 15 February 2015 and interviews are expected to be held 
shortly afterwards.

For more details about the application process, please see:

Informal enquiries should be addressed to Prof Steve Uhlig at steve.uhlig <at> qmul.ac.uk.
<div>
<div class="">The School of Electronic Engineering and Computer Science at Queen Mary,&nbsp;</div>
<div class="">University of London is seeking to appoint two Research Assistants as part of</div>
<div class="">the project &ldquo;Towards a flexible software-defined network ecosystem&rdquo; (ENDEAVOUR),&nbsp;</div>
<div class="">funded by the EU within the Horizon 2020 program.<br class=""><br class="">
The successful candidates will be responsible for investigating software-defined networking&nbsp;</div>
<div class="">(SDN) aspects relevant for the next generation of Internet Exchange Points (IXP). This will&nbsp;</div>
<div class="">involve:&nbsp;</div>
<div class="">(1) analyzing large-scale network data,&nbsp;</div>
<div class="">(2) the development and application of SDN software in the context of IXPs, and&nbsp;</div>
<div class="">(3) the design of new distributed systems techniques for network management.</div>
<div class=""><br class=""></div>
<div class="">The closing date for applications is 15 February 2015 and interviews are expected to be held&nbsp;</div>
<div class="">shortly afterwards.</div>
<div class=""><br class=""></div>
<div class="">For more details about the application process, please see:</div>
<div class=""><a href="http://www.jobs.qmul.ac.uk/search/?s=QMUL5200" class="">http://www.jobs.qmul.ac.uk/search/?s=QMUL5200</a></div>
<div class=""><br class=""></div>
<div class="">Informal enquiries should be addressed to Prof Steve Uhlig at <a href="mailto:steve.uhlig <at> qmul.ac.uk" class="">
steve.uhlig <at> qmul.ac.uk</a>.</div>
</div>
shankar.pachari | 14 Jan 13:08 2015

sharing QoS for multiple hosts

Hi,

 

                I am trying to implement a QoS example using Floodlight (OF 1.0) and Mininet and came across this doubt.

 

Since queues are created by the admins in each switch manually and shared, what is the best practice  to follow when the same QoS needs to be enforced among multiple hosts?

 

If we route all traffic that belongs to a particular ToS to the same queue, will it not degrade the QoS for each individual hosts?

 

Thanks,

Shankar.

<div>
<div class="WordSection1">
<p class="MsoNormal">Hi,<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I am trying to implement a QoS example using Floodlight (OF 1.0) and Mininet and came across this doubt.
<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Since queues are created by the admins in each switch manually and shared, what is the best practice &nbsp;to follow when the same QoS needs to be enforced among multiple hosts?<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">If we route all traffic that belongs to a particular ToS to the same queue, will it not degrade the QoS for each individual hosts?<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Thanks,<p></p></p>
<p class="MsoNormal">Shankar.<p></p></p>
</div>
</div>
Picon

new member

Hi 

Rafid almahdi

<div>
<p>Hi&nbsp;</p>
<div>Rafid almahdi<br><br>
</div>
</div>

Gmane