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

实验3:OpenFlow协议分析实践

时间:2022-09-26 23:13:18浏览次数:45  
标签:struct OpenFlow 端口 实践 header ofp uint16 实验 port

(一)基本要求

  1. 拓扑文件
  2. wireshark抓包
  • Hello
    控制器6633端口(我最高能支持OpenFlow 1.0) ---> 交换机55626端口



    交换机55626端口(我最高能支持OpenFlow 1.5) ---> 控制器6633端口



    于是双方建立连接,并使用OpenFlow 1.0

  • Features Request
    控制器6633端口(我需要你的特征信息) ---> 交换机55626端口

  • Set Conig
    控制器6633端口(请按照我给你的flag和max bytes of packet进行配置) ---> 交换机55626端口

  • Port Status
    当交换机端口发生变化时,告知控制器相应的端口状态。

  • Features Reply
    交换机55626端口(这是我的特征信息,请查收) ---> 控制器6633端口

  • Packet_in
    交换机55626端口(有数据包进来,请指示)--- 控制器6633端口

  • Flow_mod
    分析抓取的flow_mod数据包,控制器通过6633端口向交换机55626端口下发流表项,指导数据的转发处理



  • Packet_out
    控制器6633端口(请按照我给你的action进行处理) ---> 交换机55626端口

  1. 交互图

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

(二)进阶要求
将抓包基础要求第2步的抓包结果对照OpenFlow源码。

  • Hello
/* 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);

/* 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;
};



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

/* 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;
};

  • Set Conig
/* 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);

  • Port Staus
  1. 交换机查找流表,发现没有匹配条目,但是这种包没有抓到过
/* Why is this packet being sent to the controller? */
enum ofp_packet_in_reason {
    OFPR_NO_MATCH,          /* No matching flow. */
    OFPR_ACTION             /* Action explicitly output to controller. */
};
  1. 有匹配条目,对应的action是OUTPUT=CONTROLLER,固定收到向控制器发送包
/* 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;
};
OFP_ASSERT(sizeof(struct ofp_port_status) == 64);

  • Features Reply
/* 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. */
};
OFP_ASSERT(sizeof(struct ofp_phy_port) == 48);

/* Switch features. */
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. */
};
OFP_ASSERT(sizeof(struct ofp_switch_features) == 32);

  • 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);

  • 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. */
};
OFP_ASSERT(sizeof(struct ofp_flow_mod) == 72);



  • 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);

个人总结

  • 抓包时未发现Hello数据包
    先开启抓包再构建拓扑
  • 在观察交换机55626端口与控制器6633端口之间的Hello时,过滤出 openflow_v1 中并没看到需要的信息。
    过滤器改成openflow_v6就能看到交互情况。
  • 没找到Features Request的源码
    查阅资料后发现它与Hello的格式是一致的。
  • 通过本次实验,学会了如何运用 wireshark 对 OpenFlow 协议数据交互过程进行抓包;以及借助包解析工具,分析与解释 OpenFlow协议的数据包交互过程与机制。 本次实验的总体难度不大,主要是抓包和找源码的时候很费眼睛。

标签:struct,OpenFlow,端口,实践,header,ofp,uint16,实验,port
From: https://www.cnblogs.com/Debbie-/p/16732653.html

相关文章

  • 实验3:OpenFlow协议分析实践
    一、基本要求1、拓扑文件#!/usr/bin/envpythonfrommininet.netimportMininetfrommininet.nodeimportController,RemoteController,OVSControllerfrommini......
  • 实验3:OpenFlow协议分析实践
    1.基础要求a)/home/用户名/学号/lab3/目录下的拓扑文件b)wireshark抓包的结果截图和对应的文字说明Hello控制器6633端口(我最高能支持OpenFlow1.0)--->交换机4063......
  • 实验3:OpenFlow协议分析实践
    目录实验3:OpenFlow协议分析实践基本要求1.搭建拓扑,完成相关IP配置2-1.查看抓包结果HelloFeatures_RequestSet_ConigPort_StatusFeatures_ReplyPacket_InPacket_OutFlow_M......
  • 实验3:OpenFlow协议分析实践
    实验3:OpenFlow协议分析实践一、实验目的能够运用wireshark对OpenFlow协议数据交互过程进行抓包;能够借助包解析工具,分析与解释OpenFlow协议的数据包交互过程与机......
  • 实验3:OpenFlow协议分析实践
    实验3:OpenFlow协议分析实践一、实验目的1.能够运用wireshark对OpenFlow协议数据交互过程进行抓包;2.能够借助包解析工具,分析与解释OpenFlow协议的数据包交互过程与......
  • 实验3:OpenFlow协议分析实践
    实验3:OpenFlow协议分析实践一、实验目的能够运用wireshark对OpenFlow协议数据交互过程进行抓包;能够借助包解析工具,分析与解释OpenFlow协议的数据包交互过程与机制......
  • Pest24实验部分细节总结
    1.整体实验部分实验应用了四种最先进的深度学习方法,即。两个两阶段检测器,FasterRCNN(Ren等人,2015)和CascadeRCNN,Cai和Vasconcelos,2018),以及两个一阶段检测器,SSD(Liu等人,2015......
  • 实验3:OpenFlow协议分析实践
    (一)基本要求1.搭建下图所示拓扑,完成相关IP配置,并实现主机与主机之间的IP通信。用抓包软件获取控制器与交换机之间的通信数据包。2.查看抓包结果,分析OpenFlow协议中交换机......
  • sdn实验(1)——mininet安装及可视化工具miniedit的使用
    一、实验目的安装mininet及使用miniedit二、实验要求安装虚拟机,逐步配置好环境,并初步使用miniedit完成可视化工具的编辑三、具体步骤1.安装Ubuntu虚拟机,......
  • 实验3:OpenFlow协议分析实践
    一、基本要求(1)拓扑文件(2)wireshark抓包结果1.hello控制器6633端口--->交换机33896端口交换机33896端口--->控制器6633端口2.FeaturesRequest控制器6633端......