From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Tom Herbert <tom@herbertland.com>
Cc: David Miller <davem@davemloft.net>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
laforge@gnumonks.org, aschultz@tpip.net,
openbsc@lists.osmocom.org
Subject: Re: [PATCH nf-next,v2] gtp: add initial driver for datapath of GPRS Tunneling Protocol (GTP-U)
Date: Tue, 10 May 2016 19:31:28 +0200 [thread overview]
Message-ID: <20160510173128.GA32285@salvia> (raw)
In-Reply-To: <CALx6S34cHSNmC-QLO8QrbktTwvJMpjkOnsQLEq3W4FLBannBRg@mail.gmail.com>
On Tue, May 10, 2016 at 10:16:33AM -0700, Tom Herbert wrote:
> On Tue, May 10, 2016 at 9:27 AM, David Miller <davem@davemloft.net> wrote:
> > From: Pablo Neira Ayuso <pablo@netfilter.org>
> > Date: Mon, 9 May 2016 00:55:48 +0200
> >
> >> This is an initial implementation of a netdev driver for GTP datapath
> >> (GTP-U) v0 and v1, according to the GSM TS 09.60 and 3GPP TS 29.060
> >> standards. This tunneling protocol is used to prevent subscribers from
> >> accessing mobile carrier core network infrastructure.
> >>
> >> This implementation requires a GGSN userspace daemon that implements the
> >> signaling protocol (GTP-C), such as OpenGGSN [1]. This userspace daemon
> >> updates the PDP context database that represents active subscriber
> >> sessions through a genetlink interface.
> >>
> >> For more context on this tunneling protocol, you can check the slides
> >> that were presented during the NetDev 1.1 [2].
> >>
> >> Only IPv4 is supported at this time.
> >>
>
> Is there a timeline for adding IPv6 support?
There is a preliminary kernel patch to add IPv6 that seems to be
untested yet, I can share it with you or anyone else want to have a
look. Specifically, there are missing bits on the netlink side of the
PDP context database to support SGSN and MS IPv6 address, but that
shouldn't be much of a problem.
On the userspace side, the userspace daemon OpenGGSN still doesn't
support IPv6. Adding IPv6 support to this daemon is a bit of a PITA,
several people using it in production told me that the daemon runs
stable for production, but from a developer perspective the current
codebase look not easy to extend (quite many stuff very IPv4 specific,
I already spend time trying to refactor it two years ago to prepare
this support). Meanwhile, this triggered a new daemon daemon
implementation osmo-ggsn to replace it, I posted a proof-of-concept on
the openbsc mailing list, but nobody jumped on this to support this
development effort so far.
next prev parent reply other threads:[~2016-05-10 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 22:55 [PATCH nf-next,v2] gtp: add initial driver for datapath of GPRS Tunneling Protocol (GTP-U) Pablo Neira Ayuso
2016-05-10 16:27 ` David Miller
2016-05-10 17:16 ` Tom Herbert
2016-05-10 17:31 ` Pablo Neira Ayuso [this message]
2016-05-10 18:54 ` Eric Dumazet
2016-05-11 5:24 ` Cong Wang
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=20160510173128.GA32285@salvia \
--to=pablo@netfilter.org \
--cc=aschultz@tpip.net \
--cc=davem@davemloft.net \
--cc=laforge@gnumonks.org \
--cc=netdev@vger.kernel.org \
--cc=openbsc@lists.osmocom.org \
--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).