On Tue, Jun 24, 2014 at 05:19:02PM -0700, Ben Pfaff wrote:
> > Maybe we also need a log message lower down in the stack showing what
> > is actually being sent to the kernel in these cases?
>
> I agree, I'm thinking about that too.
I sent out a short series:
http://openvswitch.org/piperma
On Wed, Jun 25, 2014 at 11:05:56AM +0200, Thomas Graf wrote:
> On 06/24/14 at 04:40pm, Ben Pfaff wrote:
> > Open vSwitch userspace is able to implement some actions that the kernel
> > doesn't support, such as modifying ARP fields. When it does this for a
> > tunneled packet, it needs to supply th
On 06/24/14 at 04:40pm, Ben Pfaff wrote:
> Open vSwitch userspace is able to implement some actions that the kernel
> doesn't support, such as modifying ARP fields. When it does this for a
> tunneled packet, it needs to supply the tunnel information with a "set"
> action, because the Linux kernel
On Tue, Jun 24, 2014 at 05:08:18PM -0700, Jesse Gross wrote:
> On Tue, Jun 24, 2014 at 4:40 PM, Ben Pfaff wrote:
> > Open vSwitch userspace is able to implement some actions that the kernel
> > doesn't support, such as modifying ARP fields. When it does this for a
> > tunneled packet, it needs to
On Tue, Jun 24, 2014 at 4:40 PM, Ben Pfaff wrote:
> Open vSwitch userspace is able to implement some actions that the kernel
> doesn't support, such as modifying ARP fields. When it does this for a
> tunneled packet, it needs to supply the tunnel information with a "set"
> action, because the Lin
Open vSwitch userspace is able to implement some actions that the kernel
doesn't support, such as modifying ARP fields. When it does this for a
tunneled packet, it needs to supply the tunnel information with a "set"
action, because the Linux kernel datapath throws away tunnel information
supplied
