From: David Miller <davem@davemloft.net>
To: laforge@gnumonks.org
Cc: tom@herbertland.com, pablo@netfilter.org, aschultz@tpip.net,
gerlitz.or@gmail.com, ogerlitz@mellanox.com, jhs@mojatatu.com,
netdev@vger.kernel.org, timo.lindhorst@travelping.com
Subject: Re: [PATCH net-next] net/gtp: Add udp source port generation according to flow hash
Date: Thu, 23 Feb 2017 12:01:24 -0500 (EST) [thread overview]
Message-ID: <20170223.120124.846549814513489060.davem@davemloft.net> (raw)
In-Reply-To: <20170223165051.c3jlvht4mhsuoxmq@nataraja>
From: Harald Welte <laforge@gnumonks.org>
Date: Thu, 23 Feb 2017 17:50:51 +0100
> I understand and support the motivation to design robust systsems even
> in the presence of broken/ignorant specs, but I think this is one of the
> situations where it is useless (and IMHO impossible) to do anything
> about it.
I think avoiding trying to do something reasonable about this and just
saying "this is how cellular networks are" is not acceptable.
We know how to properly strengthen tunnelling implementations in the
kernel against DDoS attachs, GTP can be treated similarly.
next prev parent reply other threads:[~2017-02-23 17:37 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 [this message]
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
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=20170223.120124.846549814513489060.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aschultz@tpip.net \
--cc=gerlitz.or@gmail.com \
--cc=jhs@mojatatu.com \
--cc=laforge@gnumonks.org \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=pablo@netfilter.org \
--cc=timo.lindhorst@travelping.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).