From: Neels Hofmeyr <nhofmeyr@sysmocom.de>
To: Andreas Schultz <aschultz@tpip.net>
Cc: laforge <laforge@gnumonks.org>, Jonas Bonn <jonas@southpole.se>,
netdev <netdev@vger.kernel.org>,
osmocom-net-gprs <osmocom-net-gprs@lists.osmocom.org>,
Lionel Gauthier <Lionel.Gauthier@eurecom.fr>,
pablo <pablo@netfilter.org>
Subject: Re: [PATCH net-next v3 1/8] gtp: add documentation
Date: Tue, 21 Feb 2017 02:12:45 +0100 [thread overview]
Message-ID: <20170221011245.GB1961@my.box> (raw)
In-Reply-To: <1839823227.173727.1487611687205.JavaMail.zimbra@tpip.net>
[-- Attachment #1: Type: text/plain, Size: 670 bytes --]
On Mon, Feb 20, 2017 at 06:28:07PM +0100, Andreas Schultz wrote:
> >> +A specific tunnel is only defined by the destination entity. Since the
> >> +destination port is constant, only the destination IP and TEID define
> >> +a tunnel. The source IP and Port have no meaning for the tunnel.
> >
> > Are you absolutely sure about this?
>
> Yes. It took me a while to realize this. The crux is this statement in TS 29.060,
> Section 7.3.1:
Also sounds right to me. When the tunnel is established, each side of a GTP
tunnel stores the other side's IP and TEID; port number is constant
(unfortunately, which is one of the ideas/reasons behind gtphub).
~N
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-02-21 1:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 15:36 [PATCH net-next v3 0/8] gtp: misc improvements Andreas Schultz
2017-02-13 15:36 ` [PATCH net-next v3 1/8] gtp: add documentation Andreas Schultz
2017-02-20 16:15 ` Harald Welte
2017-02-20 17:28 ` Andreas Schultz
2017-02-21 1:12 ` Neels Hofmeyr [this message]
2017-02-22 8:36 ` Harald Welte
2017-02-22 11:30 ` Andreas Schultz
2017-02-13 15:36 ` [PATCH net-next v3 2/8] gtp: switch from struct socket to struct sock for the GTP sockets Andreas Schultz
2017-02-14 17:48 ` David Miller
2017-02-15 7:04 ` Andreas Schultz
2017-02-15 16:07 ` David Miller
2017-02-13 15:36 ` [PATCH net-next v3 3/8] gtp: make GTP sockets in gtp_newlink optional Andreas Schultz
2017-02-13 15:36 ` [PATCH net-next v3 4/8] gtp: merge gtp_get_net and gtp_genl_find_dev Andreas Schultz
2017-02-13 15:36 ` [PATCH net-next v3 5/8] gtp: consolidate gtp socket rx path Andreas Schultz
2017-02-13 15:36 ` [PATCH net-next v3 6/8] gtp: unify genl_find_pdp and prepare for per socket lookup Andreas Schultz
2017-02-13 15:36 ` [PATCH net-next v3 7/8] gtp: consolidate pdp context destruction into helper Andreas Schultz
2017-02-13 15:36 ` [PATCH net-next v3 8/8] gtp: add socket to pdp context Andreas Schultz
2017-02-16 21:38 ` [PATCH net-next v3 0/8] gtp: misc improvements Andreas Schultz
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=20170221011245.GB1961@my.box \
--to=nhofmeyr@sysmocom.de \
--cc=Lionel.Gauthier@eurecom.fr \
--cc=aschultz@tpip.net \
--cc=jonas@southpole.se \
--cc=laforge@gnumonks.org \
--cc=netdev@vger.kernel.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pablo@netfilter.org \
/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).