Summary
The controller's state, readable in a sentence.
Reading flow tables and datapath status normally means a terminal and a memory for POX's module names. Having the memo resource alongside the tools is the part worth noticing: what you work out about a topology stays attached to it instead of scrolling away.
What it is
An MCP server that drives the POX SDN controller — listing OpenFlow datapaths, reading flow statistics and writing flow tables — aimed at teaching, prototyping and SDN research.
What you get
- Every connected OpenFlow datapath listed, with connection status and capabilities
- Detailed switch information for a given datapath identifier
- Flow statistics with packet counts, filterable by match structure, table id and output port
- Flow tables configured on a switch
- Findings appended to a network configuration memo that persists between sessions
- Live state exposed as resources: pox://topology for datapaths, hosts and links, pox://network-config for components and rules
- Prompts for POX network management, a simple L2 hub and a learning switch, each taking a datapath identifier
Requirements
A running POX controller the server can reach. No account or key — this talks to your controller, not to a service.
Setup effort
Build from source — clone the repository and build it, then point your client at the binary