首页 > 其他分享 >实验3:OpenFlow协议分析实践

实验3:OpenFlow协议分析实践

时间:2022-09-28 00:34:50浏览次数:54  
标签:struct OpenFlow 实践 uint32 header ofp uint16 实验 port

一、实验目的

能够运用 wireshark 对 OpenFlow 协议数据交互过程进行抓包;
能够借助包解析工具,分析与解释 OpenFlow协议的数据包交互过程与机制。

二、实验环境

Ubuntu 20.04 Desktop amd64

二、Wireshark抓包结果

1、hello 控制台6633端口→交换机59020端口

hello 交换机59020端口→控制台6633端口

2 Features Request 控制台6633端口→交换机59020端口

3、Set Config 控制台6633端口→交换机59020端口

4、Port_Status 当交换机端口发生变化时 告知控制器相应的端口状态

5、Features Reply 交换机59020端口→控制台6633端口

6、Packet_In

7、Packet_Out

8、Flow_Mod

三、交互图

四、交换机与控制器建立通信时是使用TCP协议还是UDP协议?
答案:TCP协议

进阶要求

Openflow数据报头部

/* 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. */ }; OFP_ASSERT(sizeof(struct ofp_header) == 8);

OFTP_HELLO

`
/* OFPT_HELLO. This message has an empty body, but implementations must

  • ignore any data included in the body, to allow for future extensions. */
    struct ofp_hello {
    struct ofp_header header;
    };`

OFPT_PORT_STATUS

/* 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. */ }; OFP_ASSERT(sizeof(struct ofp_switch_config) == 12);

OFPT_PORT_STATUS

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; }; OFP_ASSERT(sizeof(struct ofp_port_status) == 64);

OFPT_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. */

};`

OFPT_PACKET_IN

/* Packet received on port (datapath -> controller). */ 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. */ }; OFP_ASSERT(sizeof(struct ofp_packet_in) == 20);

OFPT_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.) */ }; OFP_ASSERT(sizeof(struct ofp_packet_out) == 16);

OFPT_FLOW_MOD

`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. */

};
OFP_ASSERT(sizeof(struct ofp_flow_mod) == 72);`

个人总结

标签:struct,OpenFlow,实践,uint32,header,ofp,uint16,实验,port
From: https://www.cnblogs.com/epiphanyone/p/16736554.html

相关文章

  • 实验3:OpenFlow协议分析实践
    基本要求1、拓扑文件代码(/home/k/032002225/lab3/):frommininet.netimportMininetfrommininet.nodeimportController,RemoteController,OVSControllerfrommini......
  • 实验3:OpenFlow协议分析实践
    基础要求提交导入到/home/用户名/学号/lab3/目录下的拓扑文件wireshark抓包的结果截图和对应的文字说明Hello控制器6633端口(我最高能支持OpenFlow1.0)--->交换机45......
  • 实验3:OpenFlow协议分析实践
    一、基本要求(一)拓补文件(二)抓包截图1.hello2.FeaturesRequest3.SetConig4.Port_Status5.FeaturesReply6.Packet_in7.Flow_mod8.Packet_out(三)交互图......
  • sv实验3
      验证结构    随机约束实验3相比实验2引入了随机约束,主要体现在chnl_trans类中。实验2中的数据内容由generator的get_trans函数产生,而实验3在chnl_trans类......
  • Python第四章实验报告
    一.实验项目名称:《零基础学Python》第四章的14道实例和4道实战二.实验环境:IDLE(Python3.964-bit)三.实验目的和要求:熟练掌握Python序列的应用四.实验过程:实例01输出......
  • 实验3:OpenFlow协议分析实践
    基础要求一、拓扑文件#!/usr/bin/envpythonfrommininet.netimportMininetfrommininet.nodeimportController,RemoteController,OVSControllerfrommininet.......
  • 实验3:OpenFlow协议分析实践
    实验3:OpenFlow协议分析实践一、实验目的1.能够运用wireshark对OpenFlow协议数据交互过程进行抓包;2.能够借助包解析工具,分析与解释OpenFlow协议的数据包交互过程与......
  • 实验3 OpenFlow协议分时实践
    基础实验抓包分析step1:搭建拓扑并配置相应IPstep2:Pingall并抓包step3:分析(1)hello包表示含义:控制器6633端口发送“我最高能支持OpenFlow1.0”信息给交换机43826端......
  • 实验3:OpenFlow协议分析实践
    一、实验目的1.能够运用wireshark对OpenFlow协议数据交互过程进行抓包;2.能够借助包解析工具,分析与解释OpenFlow协议的数据包交互过程与机制。二、实验环境Ubuntu......
  • 实验3:OpenFlow协议分析实践
    实验3:OpenFlow协议分析实践一、实验要求1.基本要求(1)拓扑文件#!/usr/bin/envpythonfrommininet.netimportMininetfrommininet.nodeimportController,RemoteC......