[ovs-discuss] 答复: icmp packet
duankebo at huawei.com
Tue Mar 24 02:06:04 UTC 2015
Thank you Ben.
Yes, we can packetIn the ping request packet to Openflow controller, which packet out a response then.
But for every ping request packet, the controller have to packetIn/packetOut the packet, imaging large scale datacenter where there are many hosts
which may send ping request to virtual address(means address don't exist physically and need Controller/switch to process the icmp request),
the controller will become a choke point.
So we are looking for better ways that the ping request can be responsed by the vSwitch.
åä»¶äºº: Ben Pfaff [mailto:blp at nicira.com]
åéæ¶é´: 2015å¹´3æ24æ¥ 0:00
æ¶ä»¶äºº: Lilin (pineorange, IT)
æé: discuss at openvswitch.org; Duankebo (Frank); Liyi (David, ITPL)
ä¸»é¢: Re: [ovs-discuss] icmp packet
On Mon, Mar 23, 2015 at 03:54:48AM +0000, Lilin (pineorange, IT) wrote:
> Recently I had a problem when I tried to set NXM_OF_ICMP_TYPE and NXM_OF_ICMP_CODE items in ip packet by adding flow-entries on ovs bridge. As Follows:
> root at it_207:~# ovs-ofctl add-flow br-int -O OpenFlow10 "table=0,priority=44,icmp,ip_dst=192.168.1.16, actions=move:NXM_OF_ETH_SRC->NXM_OF_ETH_DST,mod_dl_src:fa:16:3e:6b:1e:60, load:0x08->NXM_OF_ICMP_TYPE,load:0x00->NXM_OF_ICMP_CODE, move:NXM_OF_IP_SRC->NXM_OF_IP_DST, load:0xc0a80110->NXM_OF_IP_SRC,IN_PORT"
> 2015-03-19T11:01:22Z|00001|meta_flow|WARN|destination field icmp_type is not writable
> ovs-ofctl: actions are invalid with specified match (OFPBAC_BAD_SET_ARGUMENT)
> My OVS version is 2.3.90:
> root at it_207:~# ovs-vsctl --version
> ovs-vsctl (Open vSwitch) 2.3.90
> Compiled Mar 5 2015 10:31:02
> DB Schema 7.7.0
> I want to know that, does OVS support modifing TYPE and CODE items in icmp packet? If not, is there any other methods that I can achieve my destination?
OVS doesn't yet support modifying the type or code in ICMP.
You could do this with an OpenFlow controller.
More information about the discuss