Thanks Murphy McCauley I will try this. :)
On Sun, Apr 14, 2013 at 4:28 AM, Murphy McCauley
wrote:
> Queue configuration is external to OpenFlow, so it seems to me that you
> can't expect the controller to magically know which queues to use for what
> on which switches.
>
> The first thing that s
Queue configuration is external to OpenFlow, so it seems to me that you can't
expect the controller to magically know which queues to use for what on which
switches.
The first thing that seems reasonable to me is to set the DPIDs for the
switches to known values when configuring them -- at the
Thanks for your reply. Is there anyway that dpid is taken automatically not
to be entered manually??
On Sun, Apr 14, 2013 at 4:00 AM, Murphy McCauley
wrote:
> The event object also has a .dpid attribute which you can use to
> distinguish between switches -- each switch has a different DPID.
>
> S
The event object also has a .dpid attribute which you can use to distinguish
between switches -- each switch has a different DPID.
So you'll want to do something along the lines of...
if event.dpid == :
if packet.find('tcp'):
action = of.ofp_action_enqueue(port = port, queue_id = 3)
...
First of all I created two queues i.e. queue-0 and queue-1 on PORT Eth-1 of
OVS. I use the code below on cotroller
if packet.find('tcp'):
queue=1
elif packet.find('arp'):
queue=0
else:
queue=1
msg = of.ofp_flow_mod()
msg.match = of.ofp_match.from_packet(p
I don't have time to get into this much until next Thursday. You can ping me
again then if you still want my input.
Besides what Peter suggested, you also may find that just increasing the link
timeout helps (e.g., --link-timeout=20) helps. If that doesn't, you could
adjust the way send_cycle
