From: Harald Welte <laforge@gnumonks.org>
To: Tom Herbert <tom@herbertland.com>
Cc: netdev <netdev@vger.kernel.org>,
osmocom-net-gprs <osmocom-net-gprs@lists.osmocom.org>,
timo lindhorst <timo.lindhorst@travelping.com>,
Andreas Schultz <aschultz@tpip.net>, pablo <pablo@netfilter.org>
Subject: Re: [PATCH net-next v4 4/7] gtp: consolidate gtp socket rx path
Date: Thu, 23 Feb 2017 22:17:35 +0100 [thread overview]
Message-ID: <20170223211735.c47ms7yobt2omhgr@nataraja> (raw)
In-Reply-To: <CALx6S36XJfzYS7q2EjgUykAVWb-1aaT4kP2QxYmPdZBSpZaGCg@mail.gmail.com>
Hi Tom,
On Thu, Feb 23, 2017 at 10:07:03AM -0800, Tom Herbert wrote:
> I'm looking at the GTP encapsulation, it's not particularly complex.
> Is there any real reason why we can't just implement a netdev
> interface with static tunnels and configuration to do performance
> testing and development? For instance, if we want to add GSO/GRO
> support to GTP that's all we really need, the control plane should be
> inconsequential in that case.
As outlined several times in this thread, GTP tunneling is not
symmetric. The current mainline code can only act as one of the two
roles (GGSN/G-GW), not as the other one. The rationale is that in 3GPP
networks, that is the only point in the network that takes native IP
data (e.g.from the internet) and puts it into GTP. At all other places
in the network, you don't have this combination. By the time the inner
IP data arrives at the mobile phone, it is no longer encapsulated in
GTP, as the lower layers have been adapted one or multiple times to
other protocols by other network elements.
There's a patch that has recently been submitted which adds the
capability for the SGSN/S-GW side of a GTP-U tunnel, but that patch has
so far not been merged (due to concersn about its netlink interface),
and the patch *only* exists for testing, it has no real-world
application in 3GPP networks.
So as of now, it is not possible to run both endpoints of a tunnel in
Linux.
> > For performance testing, you would need a SGSN-side implementation of
> > I'll try to cook up some instructions extending
> > https://osmocom.org/projects/openggsn/wiki/OpenGGSN to cover also
> > sgsnemu for a basic use case of establishing one single tunnel. That's
> > of course like a manual "HOWTO" and not yet anything that can be tested
> > automatically.
> >
> That would be good. Thanks!
I've spent some hours earlier today on this, I expect the document to be
ready at some point over the weekend.
--
- Harald Welte <laforge@gnumonks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
next prev parent reply other threads:[~2017-02-24 7:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 10:18 [PATCH net-next v4 0/7] gtp: misc improvements Andreas Schultz
2017-02-21 10:18 ` [PATCH net-next v4 1/7] gtp: switch from struct socket to struct sock for the GTP sockets Andreas Schultz
2017-02-21 10:18 ` [PATCH net-next v4 2/7] gtp: make GTP sockets in gtp_newlink optional Andreas Schultz
2017-02-21 10:18 ` [PATCH net-next v4 3/7] gtp: merge gtp_get_net and gtp_genl_find_dev Andreas Schultz
2017-02-21 10:18 ` [PATCH net-next v4 4/7] gtp: consolidate gtp socket rx path Andreas Schultz
2017-02-22 17:41 ` Tom Herbert
2017-02-23 9:19 ` Andreas Schultz
2017-02-23 16:28 ` Tom Herbert
2017-02-23 16:46 ` Harald Welte
2017-02-23 18:07 ` Tom Herbert
2017-02-23 21:17 ` Harald Welte [this message]
2017-02-21 10:18 ` [PATCH net-next v4 5/7] gtp: unify genl_find_pdp and prepare for per socket lookup Andreas Schultz
2017-02-21 10:18 ` [PATCH net-next v4 6/7] gtp: consolidate pdp context destruction into helper Andreas Schultz
2017-02-21 10:18 ` [PATCH net-next v4 7/7] gtp: add socket to pdp context Andreas Schultz
2017-02-21 11:13 ` [PATCH net-next v4 0/7] gtp: misc improvements Andreas Schultz
2017-02-21 18:15 ` David Miller
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=20170223211735.c47ms7yobt2omhgr@nataraja \
--to=laforge@gnumonks.org \
--cc=aschultz@tpip.net \
--cc=netdev@vger.kernel.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--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