| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
| |
that represent various header fields. One place where OXMs are used is in
the sef_field action, which contains one OXM representing the header field
to set, followed by padding to align the action in the OpenFlow message to
64 bits. Currently, we assume that a set_field action can contain multiple
OXMs and that they do not need to be padded.
This matches the way we handle OpenFlow messages that contain set_field
actions so that we follow the specs.
OK ori claudio
|
| |
|
|
| |
openflow part tested by rzalamena@, ok deraadt@
|
| |
|
|
| |
ok reyk@
|
| |
|
|
|
|
| |
change the truncation message in hello with the standard one.
ok reyk@
|
| |
|
|
| |
OK rzalamena@
|
| | |
|
| |
|
|
| |
OpenFlow 1.3.5 it is a reserved field that is not being used.
|
| |
|
|
| |
Requested by rzalamena@
|
| |
|
|
|
|
| |
(manually synced). Also make the output a bit more like other printers.
OK rzalamena@
|
| |
|
|
|
|
|
|
| |
eg. tcpdump -y openflow -i switch0
Includes a minor bump for libpcap.
Feedback and OK rzalamena@
|
| | |
|
|
|
supports the following message types: hello, error, echo request/reply,
feature request/reply, set config, packet-in, packet-out, flow removed and
flow mod.
We currently only support printing this messages for OpenFlow 1.3.5, however
it is possible to reuse some functions and get other versions working too.
ok deraadt@
|