Gabriele Gerbino | 23 Oct 20:01 2014
Picon

Bandwidth isolation using FlowVisor

I'm looking for some material on this field and I've found discordant responses about bandwidth isolation...older posts say it was possible, others say it isn't, but I've found no recent information about that.

So, is it possible?

Regards
Gabriele
<div><div dir="ltr">I'm looking for some material on this field and I've found discordant responses about bandwidth isolation...older posts say it was possible, others say it isn't, but I've found no recent information about that.<div><br></div>
<div>So, is it possible?</div>
<div><br></div>
<div>Regards</div>
<div>Gabriele</div>
</div></div>
Lei Wang | 17 Oct 03:07 2014
Picon

[SPAM:#]


Sree Vidya S D | 16 Oct 14:27 2014
Picon

Source Routing in openflow

Iam trying to implement source routing in openflow with Floodlight controller and mininet.

I came across this mailthread regarding the same

I think I have proceeded as mentioned in this mailthread and embedded the port numbers in the ethernet protocol fieldof the action types. Precisely I have edited the mac headers with the sequence of port numbers through which the packet should pass.

I have created a linear topology with 4 nodes in mininet


h1---(1)S1(2)----(2)S2(3)---------(2)S3(3)--------(2)S4(1)----h4

and try pinging from h1 to h4

In the controller it edits the mac headers when an icmp packet is received..so I create a packet out message with mac headers edited for the packetin message corresponding to the icmp request.(the macheaders now contain 2 3 3 1 wrt this topology)

Can you please guide me what is the next step Iam supposed to do ?

From my understanding Iam supposed to sent this packet back to the switch.
can anybody please explain how will the switches on the route handle this packet further ??

--
--

<div><div dir="ltr">Iam trying to implement source routing in openflow with Floodlight controller and mininet.<div><br></div>
<div>I came across this mailthread regarding the same</div>
<div><a href="https://mailman.stanford.edu/pipermail/openflow-discuss/2011-April/002075.html">https://mailman.stanford.edu/pipermail/openflow-discuss/2011-April/002075.html</a></div>
<div><br></div>
<div>I think I have proceeded as mentioned in this mailthread and embedded the port numbers in the ethernet protocol fieldof the action types. Precisely I have edited the mac headers with the sequence of port numbers through which the packet should pass.</div>
<div><br></div>
<div>I have created a linear topology with 4 nodes in mininet</div>
<div><br></div>
<div><br></div>
<div>h1---(1)S1(2)----(2)S2(3)---------(2)S3(3)--------(2)S4(1)----h4</div>
<div><br></div>
<div>and try pinging from h1 to h4</div>
<div><br></div>
<div>In the controller it edits the mac headers when an icmp packet is received..so I create a packet out message with mac headers edited for the packetin message corresponding to the icmp request.(the macheaders now contain 2 3 3 1 wrt this topology)</div>
<div><br></div>
<div>Can you please guide me what is the next step Iam supposed to do ?</div>
<div><br></div>
<div>From my understanding Iam supposed to sent this packet back to the switch.<br>can anybody please explain how will the switches on the route handle this packet further ??<br clear="all"><div><br></div>-- <br>-- <br><br>
</div>
</div></div>
tech_kals Kals | 16 Oct 08:48 2014
Picon

Group Type - ALL

Hi Experts,

when i go through openflow spec 1.3.1, i am not able to understand the following lines from 5.6.1. Group Types.

In Group Type ALL, it is mentioned that, " if a bucket directs a packet explicitly out the ingress port, this packet clone is dropped". Why do we need to drop the clone when the packet is sent to ingress port again? Can someone clarify me please.

thanks,
kals.
<div><div dir="ltr">Hi Experts,<div><br></div>
<div>when i go through openflow spec 1.3.1, i am not able to understand the following lines from 5.6.1. Group Types.</div>
<div><br></div>
<div>In Group Type ALL, it is mentioned that, " if a bucket directs a packet explicitly out the ingress port, this packet clone is dropped". Why do we need to drop the clone when the packet is sent to ingress port again? Can someone clarify me please.</div>
<div><br></div>
<div>thanks,</div>
<div>kals.</div>
</div></div>
Caarveth | 15 Oct 21:35 2014
Picon

Suorce routing in Mininet

Hello,

Is it possible to simulate source routing in an SDN using Mininet
? Any ideas how it can be done? I would greatly appreciate any help...

Regards,
Marc
<div><div dir="ltr">
<div><span>Hello,</span></div>
<span><div><span><br></span></div>Is it possible to simulate source routing in an SDN using Mininet</span><span>? Any ideas how it can be done?&nbsp;</span><span>I would greatly appreciate any help...</span><div><br></div>
<div>Regards,</div>
<div>Marc</div>
</div></div>
Lefteris Mourikis | 14 Oct 12:52 2014
Picon

Topology separation using FlowVisor

Hello,


I use Flowvisor 1.4, mininet and OpenDaylight controller. I have two mininet topologies in two different mininet instanes, let's say Topo1 and Topo2. Topo1 has a single switch with static DPID ::AA . Topo2 has a lot of switches, with random DPIDs.


I also have two different OpenFlow controllers (OpenDaylight) with different IP addresses, let's say Controller1 and Controller2.


I need the switch at Topo1 to get connected only to Controller1 and any switches at Topo2 to get connected only to Controller2. To better understand what I am trying to do, take a look at the diagram here: http://bit.ly/ZpwerZ


I tried to create two slices and two flowspaces, as follows:


fvctl --user=fvadmin --passwd-file=/etc/flowvisor/flowvisor.passwd add-slice --recv-lldp Slice1 tcp:controller1ip:6633 me <at> of

fvctl --user=fvadmin --passwd-file=/etc/flowvisor/flowvisor.passwd add-slice --recv-lldp Slice2 tcp:controller2ip:6633 me <at> of


fvctl --user=fvadmin --passwd-file=/etc/flowvisor/flowvisor.passwd add-flowspace FS1 00:00:00:00:00:00:00:AA 100 any "Slice1=6"

fvctl --user=fvadmin --passwd-file=/etc/flowvisor/flowvisor.passwd add-flowspace FS2 all 10 any "Slice2=6"


However, using the above setup I end up having Topo2 connected only to Controller2 (this is OK) and Topo1 connected to both Controller1 and Controller2 (this is _not_ OK).


Is there any way to add a Flowspace rule, so that I can prevent DPID ::AA from connecting to Controller2?


Thank you in advance for any answers


Lefteris Mourikis

<div>
<p>Hello,</p>
<p><br></p>
<p>I use Flowvisor 1.4, mininet and OpenDaylight controller. I have two mininet topologies in two different mininet instanes, let's say Topo1 and Topo2. Topo1 has a single switch with static DPID ::AA . Topo2 has a lot of switches, with random DPIDs.</p>
<p><br></p>
<p>I also have two different OpenFlow controllers (OpenDaylight) with different IP addresses, let's say Controller1 and Controller2.</p>
<p><br></p>
<p>I need the switch at Topo1 to get connected only to Controller1 and any switches at Topo2 to get connected only to Controller2. To better understand what I am trying to do, take a look at the diagram here:
<a href="http://bit.ly/ZpwerZ">http://bit.ly/ZpwerZ</a><br></p>
<p><br></p>
<p>I tried to create two slices and two flowspaces, as follows:</p>
<p><br></p>
<p lang="en-US">fvctl --user=fvadmin --passwd-file=/etc/flowvisor/flowvisor.passwd add-slice --recv-lldp Slice1 tcp:controller1ip:6633 me <at> of</p>
<p lang="en-US">fvctl --user=fvadmin --passwd-file=/etc/flowvisor/flowvisor.passwd add-slice --recv-lldp Slice2 tcp:controller2ip:6633 me <at> of</p>
<p><br></p>
<p lang="en-US">fvctl --user=fvadmin --passwd-file=/etc/flowvisor/flowvisor.passwd add-flowspace FS1 00:00:00:00:00:00:00:AA 100 any "Slice1=6"</p>
<p lang="en-US">fvctl --user=fvadmin --passwd-file=/etc/flowvisor/flowvisor.passwd add-flowspace FS2 all 10 any "Slice2=6"</p>
<p lang="en-US"><br></p>
<p lang="en-US">However, using the above setup I end up having Topo2 connected only to Controller2 (this is OK) and Topo1 connected to both Controller1 and Controller2 (this is _not_ OK).</p>
<p lang="en-US"><br></p>
<p lang="en-US">Is there any way to add a Flowspace rule, so that I can prevent DPID ::AA from connecting to Controller2?</p>
<p lang="en-US"><br></p>
<p lang="en-US">Thank you in advance for any answers</p>
<p><br></p>
<div>
<div name="divtagdefaultwrapper">
<div>
<p class="MsoNormal"></p>
<div><span lang="EN-GB">
<p class="MsoNormal"><span>Lefteris Mourikis</span><span><a tabindex="0" href="http://blog.ctlab.gr/" target="_blank"><span lang="EN-US"></span></a></span></p>
</span></div>
</div>
</div>
</div>
</div>
G Vengada Prasad | 14 Oct 12:16 2014
Picon

Re: Using the setDlDst construct in a flowprogrammer API

Hello,
   I am trying to add a static flow using the flowProgrammer Northbound service. I am unable to modify the Destination MAC using setDlDst construct (please find the screen capture attached). I am able to set the output port though. Please let me know what am I missing here?


Regards,
Prasad.


<div><div>Hello, <br><div>
<div>
<div class="y_msg_container">
<span class="yiv8817233187"></span><div><div><div>
<div class="yiv8817233187">&nbsp;&nbsp; I am trying to add a static flow using the flowProgrammer Northbound service. I 
 am unable to modify the Destination MAC using setDlDst construct (please find the screen capture attached). I am able to set the output port though. Please let me know
 what am I missing here?<br class="yiv8817233187"><br class="yiv8817233187"><br class="yiv8817233187">
</div>
<div class="yiv8817233187">Regards,<br class="yiv8817233187">Prasad.</div>
</div></div></div>
<br><br>
</div> </div> </div>  </div></div>
Curtis Taylor | 13 Oct 16:34 2014

OpenWRT and OpenFlow with DHCP/NAT

Hello,

This is a continuation of questions from 2011 here: https://mailman.stanford.edu/pipermail/openflow-discuss/2011-July/002432.html

Is there any better documentation getting DHCP/NAT setup with OpenFlow? I’ve created the virtual
interfaces, configured veth1 with a static IP and added veth0 to the OpenFlow configuration.

I don’t quite understand what needs to happen for the “wiring” of the two virtual interfaces. Having
not used virtual interfaces before (only aliases), I’m a little unsure on what the network looks like
with these new interfaces and whether or not veth0 needs to be placed on a new VLAN in the
/etc/config/network file.

If a work configuration was available, I’m betting that would be sufficient. 

Thanks!

—Curtis

Gabriele Gerbino | 11 Oct 08:45 2014
Picon

FlowVisor - Controllers communication

Hi there,

this is the first message I send to this mailing list and I hope I'm doing it right :)

Here is my question: I want the FlowVisor to periodically send a request message for some data to all controllers, who will then reply back to him with some informations. How can I build such communication? Which classess should I exploit?

Thanks in advance
Gabriele
<div><div dir="ltr">
<span>Hi there,</span><div><br></div>
<div>this is the first message I send to this mailing list and I hope I'm doing it right :)</div>
<div><br></div>
<div>Here is my question: I want the FlowVisor to periodically send a request message for some data to all controllers, who will then reply back to him with some informations. How can I build such communication? Which classess should I exploit?</div>
<div><br></div>
<div>Thanks in advance</div>
<div>Gabriele</div>
</div></div>
Aravindhan Dhanasekaran | 11 Oct 06:50 2014
Picon

Using queues in OpenFlow soft switch 13

[I believe this to be more of a ofsoftswitch specific question, but I'm posting
it here as ofsoftswitch folks follow this list. Apologies for the wide
distribution.]

Hello,

I'm trying to use queues in ofsoftswitch13 for a small traffic shaping/limiting
experiment as discussed at http://archive.openflow.org/wk/index.php/Slicing

I'm using top-of-trunk versions of Mininet and ofsoftswitch13 in my testbed and
have two streams of TCP and UDP traffic.

My topology:
h1 [eth1] <-----> [s1-eth1] s1 [s1-eth2] <-----> [eth1] h2

My flow tables:
$ sudo dpctl unix:/tmp/s1 stats-flow
	{table="0", match="oxm{eth_type="0x800", ip_proto="6"}", dur_s="3740",
dur_ns="249000", prio="32768", idle_to="0", hard_to="0", cookie="0x0",
pkt_cnt="4000521", byte_cnt="4093372606", insts=[meta{meta="0x6",
mask="0xffffffffffffffff"}, goto{table="3"}]},
	{table="0", match="oxm{eth_type="0x800", ip_proto="17"}", dur_s="2622",
dur_ns="608000", prio="32768", idle_to="0", hard_to="0", cookie="0x0",
pkt_cnt="65574", byte_cnt="99147888", insts=[meta{meta="0x11",
mask="0xffffffffffffffff"}, goto{table="4"}]},
	{table="3", match="oxm{in_port="1", metadata="0x6"}", dur_s="3728",
dur_ns="131000", prio="32768", idle_to="0", hard_to="0", cookie="0x0",
pkt_cnt="1355622", byte_cnt="90368912", insts=[apply{acts=[out{port="2"}]}]},
	{table="3", match="oxm{in_port="2", metadata="0x6"}", dur_s="3728",
dur_ns="114000", prio="32768", idle_to="0", hard_to="0", cookie="0x0",
pkt_cnt="2644899", byte_cnt="4003003694", insts=[apply{acts=[out{port="1"}]}]},
	{table="4", match="oxm{in_port="1", metadata="0x17"}", dur_s="2670",
dur_ns="800000", prio="32768", idle_to="0", hard_to="0", cookie="0x0",
pkt_cnt="3", byte_cnt="4536", insts=[apply{acts=[out{port="2"}]}]},
	{table="4", match="oxm{in_port="2", metadata="0x17"}", dur_s="1951",
dur_ns="392000", prio="32768", idle_to="0", hard_to="0", cookie="0x0",
pkt_cnt="1968", byte_cnt="2975616", insts=[apply{acts=[out{port="1"}]}]}]}

Test setup:
    1. Initially, I've both TCP and UDP traffic, originating at h2 and destined
to h1, to use the same egress interface (s1-eth1) whose bandwidth has been
limited to 10kbps. UDP takes over all the bandwidth as expected.
    2. I then created two queues on the egress interface with min guaranteed
rate as 7 and 3 kbps to be used for TCP and UDP respectively.

$ sudo dpctl unix:/tmp/s1 queue-mod 1 1 7
$ sudo dpctl unix:/tmp/s1 queue-mod 1 1 3
$ sudo dpctl unix:/tmp/s1 stats-queue
SENDING (xid=0xF0FF00F0):
stat_req{type="queue", flags="0x0", port="any", q="all"}

RECEIVED (xid=0xF0FF00F0):
stat_repl{type="queue", flags="0x0", stats=[{port="1", q="1", tx_bytes="0",
tx_pkt="0", tx_err="0"}, {port="1", q="2", tx_bytes="0", tx_pkt="0", tx_err="0"}]}

    3. I modified my flows to use the queue instead of directly sending it out
of the port. After tj
$ sudo dpctl unix:/tmp/s1 flow-mod cmd=add,table=3 meta=0x6,in_port=2 apply:queue1
$ sudo dpctl unix:/tmp/s1 flow-mod cmd=add,table=4 meta=0x11,in_port=2 apply:queue2
$ sudo dpctl unix:/tmp/s1 stats-flow | grep "q="
	{table="3", match="oxm{in_port="2", metadata="0x6"}", dur_s="31",
dur_ns="516000", prio="32768", idle_to="0", hard_to="0", cookie="0x0",
pkt_cnt="62", byte_cnt="93868", insts=[apply{acts=[queue{q="1"}]}]},
	{table="4", match="oxm{in_port="2", metadata="0x17"}", dur_s="21",
dur_ns="535000", prio="32768", idle_to="0", hard_to="0", cookie="0x0",
pkt_cnt="0", byte_cnt="0", insts=[apply{acts=[queue{q="2"}]}]}]}

    4. After step 3, my traffic (both TCP and UDP) seems to be dropped at
s1-eth1. I verified this using tcpdump on the ingress interface (s1-eth2) and I
could see my traffic there.

Can anyone please explain me what's wrong with my setup?

Also, how would the switch know which queue of which port should be used for
egress if we just specify the queue ID alone as done in step 3? Or should queue
IDs be globally (across all datapath ports) unique?

Thanks,
/Aravind
Farzaneh Pakzad | 9 Oct 03:57 2014
Picon
Picon

OFPBRC_BUFFER_UNKNOWN in OFELIA testbed

Hello everybody, I don't know if it is a relevant question to ask here: I am trying to do OpenFlow topology discovery (with pox) in real testbed called OFELIA. I've chosen some switches form one of the island to run the test.
After I did all the settings, the controller started to work and detect the switches and links between them.
However, in the meantime there are some openflow error messages and warnings as well. These errors are as follow:

"""
ERROR:openflow.of_01:[00-00-00-00-00-02|512 2] OpenFlow Error:
[00-00-00-00-00-02|512 2] Error: header:
[00-00-00-00-00-02|512 2] Error: version: 1
[00-00-00-00-00-02|512 2] Error: type: 1 (OFPT_ERROR)
[00-00-00-00-00-02|512 2] Error: length: 28
[00-00-00-00-00-02|512 2] Error: xid: 0
[00-00-00-00-00-02|512 2] Error: type: OFPET_BAD_REQUEST (1)
[00-00-00-00-00-02|512 2] Error: code: OFPBRC_BUFFER_UNKNOWN (8)
[00-00-00-00-00-02|512 2] Error: datalen: 16
[00-00-00-00-00-02|512 2] Error: 0000: 01 0d 00 10 00 00 00 18 9e 11 2d 2c 00 06 00 00 |..........-,....|
"""

"""
INFO:packet:(lldp tlv parse) warning TLV data too short to parse (86)
INFO:packet:(lldp parse) error parsing TLV
"""
Would you please help me with that?

I would like to know if anyone had this problem before
and what makes this problem to happen and if I can solve it or not?

Thank you all.
Farzaneh
<div>
<div>
Hello everybody,

I don't know if it is a relevant question to ask here:
I am trying to do OpenFlow topology discovery (with pox) in real testbed called OFELIA.
I've chosen some switches form one of the island to run the test.<br>After I did all the settings, the controller started to work and detect the switches and links between them.<br>However, in the meantime there are some openflow error messages and warnings as well. These errors are as follow:<br><br>"""<br>ERROR:openflow.of_01:[00-00-00-00-00-02|512 2] OpenFlow Error:<br>[00-00-00-00-00-02|512 2] Error: header: <br>[00-00-00-00-00-02|512 2] Error:   version: 1<br>[00-00-00-00-00-02|512 2] Error:   type:    1 (OFPT_ERROR)<br>[00-00-00-00-00-02|512 2] Error:   length:  28<br>[00-00-00-00-00-02|512 2] Error:   xid:     0<br>[00-00-00-00-00-02|512 2] Error: type: OFPET_BAD_REQUEST (1)<br>[00-00-00-00-00-02|512 2] Error: code: OFPBRC_BUFFER_UNKNOWN (8)<br>[00-00-00-00-00-02|512 2] Error: datalen: 16<br>[00-00-00-00-00-02|512 2] Error: 0000: 01 0d 00 10 00 00 00 18  9e 11 2d 2c 00 06 00 00   |..........-,....|<br>"""<br><br>"""<br>INFO:packet:(lldp tlv parse) warning TLV data too short to parse (86)<br>INFO:packet:(lldp parse) error parsing TLV<br>"""<br>Would you please help me with that? <br><br>I would like to know if anyone had this problem before<br>and what makes this problem to happen and if I can solve it or not? <br><br>Thank you all.
<br>Farzaneh<br>
</div>
</div>

Gmane