Thanks everyone.
I realize that what I should actually be doing is modifying the existing
openflow protocols with additional fields, not defining new protocols.
Sorry for the confusion and thanks again for taking the time to help. I
will create a new thread if I run into new problems in that appr
Thank you for the response Iwase,
Originally my protocol did not reserve any tcp ports. However, in order to
test your solution, I added TCP ports with unique values to the protocol,
and implemented your changes.
Unfortunately, the result is the same (albeit with additional fields):
'\xad\x9c\xd
Hi,
Does your custom protocol reserve any TCP src/dst port?
If you can define it, please modify the following to return your protocol class.
https://github.com/osrg/ryu/blob/master/ryu/lib/packet/tcp.py#L135
e.g.)
$ git diff
diff --git a/ryu/lib/packet/tcp.py b/ryu/lib/packet/tcp.py
index 1771
Good afternoon everyone,
I am experimenting with handling custom protocols with Ryu, but am unable
to parse the new protocols at the switch or controller.
I have created a custom protocol with Scapy that simple holds 3 IntFields
(4 bytes each) and 2 ShortFields (2 bytes each). I create a packet w
