实验3：OpenFlow协议分析实践
一、实验目的
1.能够运用 wireshark 对 OpenFlow 协议数据交互过程进行抓包；
2.能够借助包解析工具，分析与解释 OpenFlow协议的数据包交互过程与机制。
二、实验环境
Ubuntu 20.04 Desktop amd64
三、实验要求
（一）基本要求
1.搭建下图所示拓扑，完成相关 IP 配置，并实现主机与主机之间的 IP 通信。用抓包软件获取控制器与交换机之间的通信数据。
2.查看抓包结果，分析OpenFlow协议中交换机与控制器的消息交互过程，画出相关交互图或流程图
hello
控制器6633端口->交换机49349端口
交换机49349端口->控制器6633端口
Feature Request
控制器6633端口（我需要你的特征信息） ---> 交换机49340端口
Set Config
控制器6633端口（请按照我给你的flag和max bytes of packet进行配置） ---> 交换机49340端口
Port_Status
当交换机端口发生变化时，告知控制器相应的端口状态。
Features Reply
交换机端口49340（这是我的特征信息，请查收） ---> 控制器6633端口
Packet_In
Flow_Mod
分析OpenFlow协议中交换机与控制器的消息交互过程，画出相关交互图或流程图
回答问题：交换机与控制器建立通信时是使用TCP协议还是UDP协议？
TCP
（二）进阶要求
将抓包基础要求第2步的抓包结果对照OpenFlow源码，了解OpenFlow主要消息类型对应的数据结构定义。
Hello
struct ofp_header {
uint8_t version; /* OFP_VERSION. */
uint8_t type; /* One of the OFPT_ constants. */
uint16_t length; /* Length including this ofp_header. */
uint32_t xid;
/* Transaction id associated with this packet.
Replies use the same id as was in the request to facilitate pairing.
*/};
struct ofp_hello {
struct ofp_header header;
};
Features Request
/* Header on all OpenFlow packets. */
struct ofp_header {
uint8_t version; /* OFP_VERSION. */
uint8_t type; /* One of the OFPT_ constants. */
uint16_t length; /* Length including this ofp_header. */
uint32_t xid; /* Transaction id associated with this packet.
Replies use the same id as was in the request
to facilitate pairing. */
};
//feature_request的结构和hello一样
Set Config
/* Switch configuration. */
struct ofp_switch_config {
struct ofp_header header;
uint16_t flags; /* OFPC_* flags. */
uint16_t miss_send_len; /* Max bytes of new flow that datapath should
send to the controller. */
};
//除了头部，还有端口类型，以及packet可携带的最大消息长度
Port_Status
/* A physical port has changed in the datapath */
struct ofp_port_status {
struct ofp_header header;
uint8_t reason; /* One of OFPPR_*. */
uint8_t pad[7]; /* Align to 64-bits. */
struct ofp_phy_port desc;
};
//添加、删除或修改物理端口时，需要发送Port-Status 消息来通知OpenFlow 控制器
Features Reply
struct ofp_switch_features {
struct ofp_header header;
uint64_t datapath_id; /* Datapath unique ID. The lower 48-bits are for
a MAC address, while the upper 16-bits are
implementer-defined. */
uint32_t n_buffers; /* Max packets buffered at once. */
uint8_t n_tables; /* Number of tables supported by datapath. */
uint8_t pad[3]; /* Align to 64-bits. */
/* Features. */
uint32_t capabilities; /* Bitmap of support "ofp_capabilities". */
uint32_t actions; /* Bitmap of supported "ofp_action_type"s. */
/* Port info.*/
struct ofp_phy_port ports[0]; /* Port definitions. The number of ports
is inferred from the length field in
the header. */
};
/* Description of a physical port */
struct ofp_phy_port {
uint16_t port_no;
uint8_t hw_addr[OFP_ETH_ALEN];
char name[OFP_MAX_PORT_NAME_LEN]; /* Null-terminated */
uint32_t config; /* Bitmap of OFPPC_* flags. */
uint32_t state; /* Bitmap of OFPPS_* flags. */
/* Bitmaps of OFPPF_* that describe features. All bits zeroed if
* unsupported or unavailable. */
uint32_t curr; /* Current features. */
uint32_t advertised; /* Features being advertised by the port. */
uint32_t supported; /* Features supported by the port. */
uint32_t peer; /* Features advertised by peer. */
};
packet_in
struct ofp_packet_in {
struct ofp_header header;
uint32_t buffer_id; /* ID assigned by datapath. */
uint16_t total_len; /* Full length of frame. */
uint16_t in_port; /* Port on which frame was received. */
uint8_t reason; /* Reason packet is being sent (one of OFPR_*) */
uint8_t pad;
uint8_t data[0]; /* Ethernet frame, halfway through 32-bit word,
so the IP header is 32-bit aligned. The
amount of data is inferred from the length
field in the header. Because of padding,
offsetof(struct ofp_packet_in, data) ==
sizeof(struct ofp_packet_in) - 2. */
};
flow_mod
/* Flow setup and teardown (controller -> datapath). */
struct ofp_flow_mod {
struct ofp_header header;
struct ofp_match match; /* Fields to match */
uint64_t cookie; /* Opaque controller-issued identifier. */
/* Flow actions. */
uint16_t command; /* One of OFPFC_*. */
uint16_t idle_timeout; /* Idle time before discarding (seconds). */
uint16_t hard_timeout; /* Max time before discarding (seconds). */
uint16_t priority; /* Priority level of flow entry. */
uint32_t buffer_id; /* Buffered packet to apply to (or -1).
Not meaningful for OFPFC_DELETE*. */
uint16_t out_port; /* For OFPFC_DELETE* commands, require
matching entries to include this as an
output port. A value of OFPP_NONE
indicates no restriction. */
uint16_t flags; /* One of OFPFF_*. */
struct ofp_action_header actions[0]; /* The action length is inferred
from the length field in the
header. */
};
//包括流表项标志符cookie，command代表五种操作，对应值分别为0-4，优先级等
Packet_out
/* Send packet (controller -> datapath). */
struct ofp_packet_out {
struct ofp_header header;
uint32_t buffer_id; /* ID assigned by datapath (-1 if none). */
uint16_t in_port; /* Packet's input port (OFPP_NONE if none). */
uint16_t actions_len; /* Size of action array in bytes. */
struct ofp_action_header actions[0]; /* Actions. */
/* uint8_t data[0]; */ /* Packet data. The length is inferred
from the length field in the header.
(Only meaningful if buffer_id == -1.) */
};
//包括动作列表、缓冲区ID等
个人总结
这次得实验操作比前几次都要简单许多，应该是因为在之前的实验做过类似的，所以这次的实验完成的还算顺利，但是也同样还是出现了几个问题
1.在进行抓包时候的顺序弄错了导致无法将所需要的截图全部抓包捕获到
2.在看进阶代码的时候废了好一阵的功夫，最后询问同学弄清楚
3.在抓包的时候因为拓扑没有保存，导致一开始每次抓包都需要重建拓扑
当然，这次的实验整体难度还算可以，所以解决问题的时间花的也相对较少，学习到了openflowswitch和controller的握手交互，同时也知道了之间采用的协议，同时通多和源码的对照，更简洁明了地清楚了其中的通信过程。