Re: [ovs-dev] [PATCH v2 2/2] ofproto: Honor mtu_request even for internal ports.

2016-09-02 Thread Daniele Di Proietto
On 02/09/2016 14:43, "Joe Stringer" wrote: >On 2 September 2016 at 14:02, Ben Pfaff wrote: >> On Fri, Sep 02, 2016 at 11:23:22AM -0700, Daniele Di Proietto wrote: >>> By default Open vSwitch tries to configure internal interfaces MTU to >>> match the bridge

Re: [ovs-dev] [PATCH v2 2/2] ofproto: Honor mtu_request even for internal ports.

2016-09-02 Thread Joe Stringer
On 2 September 2016 at 14:02, Ben Pfaff wrote: > On Fri, Sep 02, 2016 at 11:23:22AM -0700, Daniele Di Proietto wrote: >> By default Open vSwitch tries to configure internal interfaces MTU to >> match the bridge minimum, overriding any attempt by the user to >> configure it through

Re: [ovs-dev] [PATCH v2 2/2] ofproto: Honor mtu_request even for internal ports.

2016-09-02 Thread Ben Pfaff
On Fri, Sep 02, 2016 at 11:23:22AM -0700, Daniele Di Proietto wrote: > By default Open vSwitch tries to configure internal interfaces MTU to > match the bridge minimum, overriding any attempt by the user to > configure it through standard system tools, or the database. > > While this works in

[ovs-dev] [PATCH v2 2/2] ofproto: Honor mtu_request even for internal ports.

2016-09-02 Thread Daniele Di Proietto
By default Open vSwitch tries to configure internal interfaces MTU to match the bridge minimum, overriding any attempt by the user to configure it through standard system tools, or the database. While this works in many simple cases (there are probably many users that rely on this) it may create