From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Or Gerlitz <gerlitz.or@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Andreas Schultz <aschultz@tpip.net>,
Tom Herbert <tom@herbertland.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
Jamal Hadi Salim <jhs@mojatatu.com>,
laforge <laforge@gnumonks.org>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] net/gtp: Add udp source port generation according to flow hash
Date: Wed, 15 Mar 2017 17:25:41 +0100 [thread overview]
Message-ID: <20170315162541.GA29639@salvia> (raw)
In-Reply-To: <CAJ3xEMiF_T_JxTik+yxvYoBQCiG=kKzukSsORApKB9nhTSvqeQ@mail.gmail.com>
On Wed, Mar 15, 2017 at 06:14:02PM +0200, Or Gerlitz wrote:
> On Thu, Feb 23, 2017 at 7:54 PM, David Miller <davem@davemloft.net> wrote:
> > From: Andreas Schultz <aschultz@tpip.net>
> > Date: Thu, 23 Feb 2017 18:19:16 +0100 (CET)
> >
> >> When we are talking about the xmit path, then currently none of the
> >> receivers we are talking to is going to be Linux and we have no
> >> idea how they will behave nor do we have any influence on them. Do
> >> we really need to make assumptions about other vendors implementations?
> >>
> >> Traces on live GRX networks show that about 90% of the SGSN/S-GW
> >> that would talk to us always use the default GTP-U port as source
> >> port. Some multi chassis GSN's seem to assign source port ranges to
> >> chassis, but that has nothing todo with DDOS protection.
> >
> > This is exactly what other UDP tunnel implementations did before
> > flow separation was prevelant.
> >
> > I don't see the point of any of this discussion discouraging the
> > enablement of proper flow separation.
>
> Hi Dave,
>
> So where do we go from here? should I resubmit the patch?
IIRC this patch didn't get into the merge window in time, so it's
reasonable to resubmit I think.
You may want to add this to the patch:
Acked-by: Pablo Neira Ayuso <pablo@netfilter.org>
Thanks Or.
next prev parent reply other threads:[~2017-03-15 16:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-16 14:59 [PATCH net-next] net/gtp: Add udp source port generation according to flow hash Or Gerlitz
2017-02-16 21:58 ` Andreas Schultz
2017-02-22 21:29 ` Or Gerlitz
2017-02-22 21:47 ` Tom Herbert
2017-02-23 9:35 ` Andreas Schultz
2017-02-23 14:00 ` Pablo Neira Ayuso
2017-02-23 16:35 ` Tom Herbert
2017-02-23 16:50 ` Harald Welte
2017-02-23 17:01 ` David Miller
2017-02-23 13:49 ` Pablo Neira Ayuso
2017-02-23 13:58 ` Or Gerlitz
2017-02-23 14:21 ` Andreas Schultz
2017-02-23 16:42 ` Pablo Neira Ayuso
2017-02-23 17:19 ` Andreas Schultz
2017-02-23 17:54 ` David Miller
2017-03-15 16:14 ` Or Gerlitz
2017-03-15 16:25 ` Pablo Neira Ayuso [this message]
2017-02-23 16:42 ` Tom Herbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170315162541.GA29639@salvia \
--to=pablo@netfilter.org \
--cc=aschultz@tpip.net \
--cc=davem@davemloft.net \
--cc=gerlitz.or@gmail.com \
--cc=jhs@mojatatu.com \
--cc=laforge@gnumonks.org \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=tom@herbertland.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).