| | 1 | = OpenFlow Miscellany = |
| | 2 | |
| | 3 | This page documents various odds-and-ends regarding !OpenFlow and related platforms, tools, and whatnot. |
| | 4 | |
| | 5 | * Using xterm with mininet hosts. You can background then by doing: |
| | 6 | {{{ |
| | 7 | mininet> h1 xterm & |
| | 8 | }}} |
| | 9 | this allows you to spawn a terminal for a switch, from which you can, say, sniff packets using wireshark. |
| | 10 | |
| | 11 | * A good way to track packets and transactions between datapath and controller is via buffer Id for switch-initiated conversations, and by XID for controller-initiated transactions. A caveat is that the buffer ID is only applicable to a subset of messages e.g. !PacketIns and !PacketOuts. A -1 buffer ID indicates a controller-generated packet (e.g. by a flow pushing tool or via a REST API for static flows). |
