Yes, connection tracking (ct) is part of OVS 2.5.  NAT is built on top of 
connection tracking, but did not make it in 2.5.  The connection track in OVS 
2.5 is primarily used for building stateful firewalls.

Joe, Jarno, and I have all told you the same thing.  Between the three of us, 
we wrote the connection tracking and NAT code as well as the release notes, so 
you're not going to get a different answer about what's in 2.5.

--Justin


> On May 4, 2016, at 12:49 AM, Sheroo Pratap <[email protected]> 
> wrote:
> 
> Hi Justin,
> 
>   Thanks for you quick response.
>   
>   If you see in the link
>   http://openvswitch.org/releases/NEWS-2.5.0
>  
>   below section is added in OVS 2.5.0, published on 26 Feb 2016
> 
> ******************************************************************
>   - Add support for connection tracking through the new "ct" action and 
> "ct_state"/"ct_zone"/"ct_mark"/"ct_label" match fields.  
>     Only available on Linux kernels with the connection tracking module 
> loaded.
> ******************************************************************  
> it is clearly mentioned, that why i am suspecting NAT is supported in OVS 
> 2.5.0
>  Thanks and Regards
> 
>     Sheroo Pratap
> 
> On Wed, May 4, 2016 at 12:22 PM, Justin Pettit <[email protected]> wrote:
> 
> > On May 3, 2016, at 10:39 PM, Sheroo Pratap <[email protected]> 
> > wrote:
> >
> > Hi Joe,
> >
> >    I found below link for NAT support in OVS 2.5.0 release, looks like NAT 
> > is supported in latest release.
> >
> >     http://openvswitch.org/pipermail/announce/2016-February/000081.html
> >
> >    if you see in below link it is mentioned here that ct is supported in 
> > OVS 2.5.0 release
> >
> >    http://openvswitch.org/releases/NEWS-2.5.0
> 
> Yes, connection tracking is part of 2.5.  However, the release states: "This 
> feature makes it possible to implement stateful firewalls and will be the 
> basis for future stateful features such as NAT and load-balancing."  Notice 
> that it's referring to future features, which means they're not in that 
> release.  The NAT code was accepted by the upstream Linux kernel and is 
> currently being backported to earlier kernels, so I expect that they'll be in 
> the next OVS release.
> 
> --Justin
> 
> 
> 

_______________________________________________
discuss mailing list
[email protected]
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to