On Wed, Dec 12, 2012 at 11:08 PM, Jarno Rajahalme
wrote:
> On Dec 13, 2012, at 8:22 , ext Rich Lane wrote:
> On Mon, Dec 10, 2012 at 6:42 PM, Jesse Gross wrote:
>> On Mon, Dec 10, 2012 at 5:16 PM, Rich Lane
>> wrote:
>> Another issue is that this doesn't help on the receive side,
>> particularly
On Dec 13, 2012, at 8:22 , ext Rich Lane wrote:
> On Mon, Dec 10, 2012 at 6:42 PM, Jesse Gross wrote:
> On Mon, Dec 10, 2012 at 5:16 PM, Rich Lane wrote:
> > This action allows the controller to change the destination IP of the
> > encapsulating packet. It just exposes the existing Linux datapath
On Mon, Dec 10, 2012 at 6:42 PM, Jesse Gross wrote:
> On Mon, Dec 10, 2012 at 5:16 PM, Rich Lane
> wrote:
> > This action allows the controller to change the destination IP of the
> > encapsulating packet. It just exposes the existing Linux datapath
> > functionality.
> >
> > Tested by installin
On Tue, Dec 11, 2012 at 10:17:31AM +0200, Jarno Rajahalme wrote:
> To allow them to be applied the OXMs I defined should probably be changed to
> NXMs instead. Either way they would be usable on both OF 1.2+ and OF 1.0 (via
> NXT_FLOW_MOD).
At first I was going to suggest that they should use a No
On Dec 11, 2012, at 6:53 , ext Ben Pfaff wrote:
> On Mon, Dec 10, 2012 at 05:16:39PM -0800, Rich Lane wrote:
>> I would have liked to put this in under the BSN vendor ID but there isn't any
>> existing support for actions from other vendors. Let me know if you'd like me
>> to add that.
>
> Jesse m
On Mon, Dec 10, 2012 at 05:16:39PM -0800, Rich Lane wrote:
> I would have liked to put this in under the BSN vendor ID but there isn't any
> existing support for actions from other vendors. Let me know if you'd like me
> to add that.
Jesse made some comments on the rest, here's some on this bit.
On Mon, Dec 10, 2012 at 5:16 PM, Rich Lane wrote:
> This action allows the controller to change the destination IP of the
> encapsulating packet. It just exposes the existing Linux datapath
> functionality.
>
> Tested by installing a flow with the new action and an output action to a GRE
> tunnel
onday, December 10, 2012 5:16:39 PM
> Subject: [ovs-dev] [PATCH] support NXAST_SET_TUNNEL_DST action
>
> This action allows the controller to change the destination IP of the
> encapsulating packet. It just exposes the existing Linux datapath
> functionality.
>
> Tested b
This action allows the controller to change the destination IP of the
encapsulating packet. It just exposes the existing Linux datapath
functionality.
Tested by installing a flow with the new action and an output action to a GRE
tunnel port. The resulting packet had the correct destination IP.
Si
