Hi Sergio,
On 2015年12月08日 14:42, Sergio Andrés Rivera Polanco wrote:
> It does. Thank you for your reply. I will do it that way. However, I think
> that hard-coding the port value is a bit odd, wouldn't it be better something
> like the following instead?
>
> $ curl -X POST -d '{
> "dpid":
It does. Thank you for your reply. I will do it that way. However, I think
that hard-coding the port value is a bit odd, wouldn't it be better
something like the following instead?
$ curl -X POST -d '{
"dpid": 1,
"match":{
"in_port": 1
},
"actions":[
{
"
Hi,
On 2015年12月08日 13:57, nitish nagesh wrote:
> Hello,
>
>I am trying to modify the existing example script to generate a packet out
> for every packet-in. My requirement is to send a packet out message to the
> switch with the Packet-Out payload containing a 802.1Q VLAN tag of the
> cont
Hi Sergio,
On 2015年12月08日 12:11, Sergio Andrés Rivera Polanco wrote:
> Hi, I am trying out Ryu's REST API following the online documentation found
> at http://ryu-zhdoc.readthedocs.org/en/latest/app/ofctl_rest.html
>
> Even though the type of actions and match fields is properly described, I
>
Hello,
I am trying to modify the existing example script to generate a packet
out for every packet-in. My requirement is to send a packet out message to
the switch with the Packet-Out payload containing a 802.1Q VLAN tag of the
controller VID. In other words, irrespective of what packet was sen
Hi, I am trying out Ryu's REST API following the online documentation found
at http://ryu-zhdoc.readthedocs.org/en/latest/app/ofctl_rest.html
Even though the type of actions and match fields is properly described, I
didn't find the format for actions like "Send to Controller", "Flood",
"Local", "I
