On 5 April 2016 at 03:46, Aswin S <aswinsur...@gmail.com> wrote:
> Hi,
>
> I was exploring the NAT action support added in OVS. I compiled the master
> and installed the OVS(2.5.9). But when I add bridge I could see the info
> does not support ct_state_nat in the log
>
>
> 2016-04-05T20:16:08.625Z|00012|ofproto_dpif|INFO|system@ovs-system: Datapath
> supports ct_zone
> 2016-04-05T20:16:08.625Z|00013|ofproto_dpif|INFO|system@ovs-system: Datapath
> supports ct_mark
> 2016-04-05T20:16:08.625Z|00014|ofproto_dpif|INFO|system@ovs-system: Datapath
> supports ct_label
> 2016-04-05T20:16:08.625Z|00015|ofproto_dpif|INFO|system@ovs-system: Datapath
> does not support ct_state_nat
>
> Also when I try to add a flow with NAT action, it is throwing
> OFPBAC_BAD_TYPE error
>
> sudo ovs-ofctl add-flow br-int
> table=0,in_port=1,ip,action=ct"("commit,zone=1,nat"("src=10.1.1.240-10.1.1.255"))",2
> OFPT_ERROR (xid=0x4): OFPBAC_BAD_TYPE
> OFPT_FLOW_MOD (xid=0x4):
> (***truncated to 64 bytes from 128***)
>
> Am I missing anything? My kernel version is 3.13.
You'll need to use one of the latest net-next development kernels to
access this feature for the moment.
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
