Re: [ovs-discuss] OVN - MTU path discovery

2018-11-01 Thread Ben Pfaff
On Tue, Oct 30, 2018 at 04:07:42PM +0530, Numan Siddique wrote: > During the discussion, Ben proposed a new action instead which will check > the MTU of the outport for the given port. > something like check_mtu(router_port_xyzzy). This action would raise an > exception if the packet size is

Re: [ovs-discuss] OVN - MTU path discovery

2018-10-30 Thread Numan Siddique
Hi All, In the last week's OVN meeting we discussed about this issue. I want to summarize the discussion here and ask a few questions. Based on the suggestions I got from Ben few weeks earlier, I took the approach of checking the packet length using a new OVS action - chk_pkt_len_gt(length) ,

Re: [ovs-discuss] OVN - MTU path discovery

2018-09-24 Thread Daniel Alvarez Sanchez
Resending this email as I can't see it in [0] for some reason. [0] https://mail.openvswitch.org/pipermail/ovs-dev/2018-September/ On Fri, Sep 21, 2018 at 2:36 PM Daniel Alvarez Sanchez wrote: > Hi folks, > > After talking to Numan and reading log from IRC meeting yesterday, > looks like

Re: [ovs-discuss] OVN - MTU path discovery

2018-08-13 Thread Miguel Angel Ajo Pelayo
Yeah, later on we have found that it was, again, more important that we think. For example, there are still cases not covered by TCP MSS negotiation (or for UDP/other protocols): Imagine you have two clouds, both with an internal MTU (let’s imagine MTUb on cloud B, and MTUa on cloud A), and an

Re: [ovs-discuss] OVN - MTU path discovery

2018-08-03 Thread Miguel Angel Ajo Pelayo
We didn’t understand why a MTU missmatch in one direction worked (N/S), but in other direction (S/N) didn’t work… and we found that that it’s actually working (at least for TCP, via MSS negotiation), we had a missconfiguration In one of the physical interfaces. So, in the case of TCP we are fine.

Re: [ovs-discuss] OVN - MTU path discovery

2018-08-03 Thread Miguel Angel Ajo Pelayo
I’m going to capture some example traffic and try to figure out which RFCs talk about that behaviour so we can come up with a consistent solution. I can document it in the project. To be honest, when I looked at it, I was expecting that the router would fragment, and I ended up discovering that

Re: [ovs-discuss] OVN - MTU path discovery

2018-08-02 Thread Ben Pfaff
On Thu, Aug 02, 2018 at 01:19:57PM -0700, Ben Pfaff wrote: > On Wed, Aug 01, 2018 at 10:46:07AM -0400, Miguel Angel Ajo Pelayo wrote: > > Hi Ben, ICMP is used as a signal from the router to tell the sender > > “next hop has a lower mtu, please send smaller packets”, we would > > need at least

Re: [ovs-discuss] OVN - MTU path discovery

2018-08-02 Thread Ben Pfaff
On Wed, Aug 01, 2018 at 10:46:07AM -0400, Miguel Angel Ajo Pelayo wrote: > Hi Ben, ICMP is used as a signal from the router to tell the sender > “next hop has a lower mtu, please send smaller packets”, we would > need at least something in OVS to slow-path the “bigger than X” packets, > at that

Re: [ovs-discuss] OVN - MTU path discovery

2018-07-27 Thread Ben Pfaff
On Thu, Jul 12, 2018 at 04:03:33PM +0200, Miguel Angel Ajo Pelayo wrote: > Is there any way to match packet_size > X on a flow? > > How could we implement this? OVS doesn't currently have a way to do that. Adding such a feature would require kernel changes. You mentioned ICMP at one point. It

Re: [ovs-discuss] OVN - MTU path discovery

2018-07-27 Thread Han Zhou
On Fri, Jul 27, 2018 at 12:49 AM, Miguel Angel Ajo Pelayo < majop...@redhat.com> wrote: > > > > On 24 July 2018 at 17:43:51, Han Zhou (zhou...@gmail.com) wrote: > > > > On Tue, Jul 24, 2018 at 8:26 AM, Miguel Angel Ajo Pelayo < > majop...@redhat.com> wrote: > >> >> >> >> On 24 July 2018 at

Re: [ovs-discuss] OVN - MTU path discovery

2018-07-27 Thread Miguel Angel Ajo Pelayo
On 24 July 2018 at 17:43:51, Han Zhou (zhou...@gmail.com) wrote: On Tue, Jul 24, 2018 at 8:26 AM, Miguel Angel Ajo Pelayo < majop...@redhat.com> wrote: > > > > On 24 July 2018 at 17:20:59, Han Zhou (zhou...@gmail.com) wrote: > > > > On Thu, Jul 12, 2018 at 7:03 AM, Miguel Angel Ajo Pelayo < >

Re: [ovs-discuss] OVN - MTU path discovery

2018-07-24 Thread Han Zhou
On Tue, Jul 24, 2018 at 8:26 AM, Miguel Angel Ajo Pelayo < majop...@redhat.com> wrote: > > > > On 24 July 2018 at 17:20:59, Han Zhou (zhou...@gmail.com) wrote: > > > > On Thu, Jul 12, 2018 at 7:03 AM, Miguel Angel Ajo Pelayo < > majop...@redhat.com> wrote: > >> I believe we need to emit ICMP /

Re: [ovs-discuss] OVN - MTU path discovery

2018-07-24 Thread Miguel Angel Ajo Pelayo
On 24 July 2018 at 17:20:59, Han Zhou (zhou...@gmail.com) wrote: On Thu, Jul 12, 2018 at 7:03 AM, Miguel Angel Ajo Pelayo < majop...@redhat.com> wrote: > I believe we need to emit ICMP / need to frag messages to have proper > support > on different MTUs (on router sides), I wonder how does it

Re: [ovs-discuss] OVN - MTU path discovery

2018-07-24 Thread Han Zhou
On Thu, Jul 12, 2018 at 7:03 AM, Miguel Angel Ajo Pelayo < majop...@redhat.com> wrote: > I believe we need to emit ICMP / need to frag messages to have proper > support > on different MTUs (on router sides), I wonder how does it work the other > way > around (when external net is 1500, and

Re: [ovs-discuss] OVN - MTU path discovery

2018-07-12 Thread Miguel Angel Ajo Pelayo
I believe we need to emit ICMP / need to frag messages to have proper support on different MTUs (on router sides), I wonder how does it work the other way around (when external net is 1500, and internal net is 1500-geneve overhead). Is there any way to match packet_size > X on a flow? How could

Re: [ovs-discuss] OVN - MTU path discovery

2018-07-11 Thread Daniel Alvarez Sanchez
On Wed, Jul 11, 2018 at 12:55 PM Daniel Alvarez Sanchez wrote: > Hi all, > > Miguel Angel Ajo and I have been trying to setup Jumbo frames in OpenStack > using OVN as a backend. > > The external network has an MTU of 1900 while we have created two tenant > networks (Logical Switches) with an MTU