From: Harald Welte <laforge@gnumonks.org>
To: Jiannan Ouyang <ouyangj@fb.com>
Cc: osmocom-net-gprs@lists.osmocom.org, netdev@vger.kernel.org,
dev@openvswitch.org, pablo@netfilter.org, pshelar@nicira.com,
wieger.ijntema.tno@gmail.com, yi.y.yang@intel.com, joe@ovn.org,
amarpadmanabhan@fb.com
Subject: Re: [PATCH net-next v1 0/3] Flow Based GTP Tunneling
Date: Thu, 13 Jul 2017 09:12:49 +0200 [thread overview]
Message-ID: <20170713071249.lk7dph6bpzgn622d@nataraja> (raw)
In-Reply-To: <20170713004455.3946570-1-ouyangj@fb.com>
hi Jiannan,
net-next si closed, as it has been pointed out already by Joe.
On Wed, Jul 12, 2017 at 05:44:52PM -0700, Jiannan Ouyang wrote:
> ovs-ofctl add-flow br0
> "in_port=2,tun_src=192.168.60.141,tun_id=123, \
> actions=set_field:02:00:00:00:00:00->eth_src, \
> set_field:ff:ff:ff:ff:ff:ff->eth_dst,LOCAL"
I'm not familiar with the details here, but does this imply that you
are matching on the outer (transport layer) source IP address? If so,
please note this is in violation of the 3GPP specifications for GTP,
which require explicitly that the TEID is the *only* criteria for
matching an encapsulated packet to the tunnel. Basically anyone can
send you an encapsulated packet from any random source IP, just as long
as the TEID matches a tunnel, it will be decapsulated.
This is [presumably] in order to take care of mobility, as the
subscribers' phone moves around different MME/S-GW/SGSN, each having
different source IP addresses.
--
- 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-07-13 7:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 0:44 [PATCH net-next v1 0/3] Flow Based GTP Tunneling Jiannan Ouyang
[not found] ` <20170713004455.3946570-1-ouyangj-b10kYP2dOMg@public.gmane.org>
2017-07-13 0:44 ` [PATCH net-next v1 1/3] gtp: refactor to support flow-based gtp encap and decap Jiannan Ouyang
2017-07-13 7:26 ` Harald Welte
2017-07-14 0:55 ` Jiannan Ouyang
[not found] ` <3729E0DA-08AB-4C5C-B9EC-C76DAAA60E10-b10kYP2dOMg@public.gmane.org>
2017-07-14 8:03 ` Harald Welte
2017-07-31 7:21 ` Andreas Schultz
2017-08-02 12:52 ` Pablo Neira Ayuso
2017-07-13 0:44 ` [PATCH net-next v1 2/3] gtp: Support creating flow-based gtp net_device Jiannan Ouyang
[not found] ` <20170713004455.3946570-3-ouyangj-b10kYP2dOMg@public.gmane.org>
2017-07-13 7:35 ` Harald Welte
2017-07-14 1:01 ` Jiannan Ouyang
2017-07-14 8:12 ` Harald Welte
2017-07-13 18:01 ` Joe Stringer
2017-07-13 1:28 ` [PATCH net-next v1 0/3] Flow Based GTP Tunneling Joe Stringer
2017-07-13 0:44 ` [PATCH net-next v1 3/3] openvswitch: Add GPRS Tunnel Protocol (GTP) vport support Jiannan Ouyang
2017-07-13 7:12 ` Harald Welte [this message]
2017-07-13 18:14 ` [PATCH net-next v1 0/3] Flow Based GTP Tunneling Joe Stringer
2017-07-13 22:54 ` Jiannan Ouyang
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=20170713071249.lk7dph6bpzgn622d@nataraja \
--to=laforge@gnumonks.org \
--cc=amarpadmanabhan@fb.com \
--cc=dev@openvswitch.org \
--cc=joe@ovn.org \
--cc=netdev@vger.kernel.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=ouyangj@fb.com \
--cc=pablo@netfilter.org \
--cc=pshelar@nicira.com \
--cc=wieger.ijntema.tno@gmail.com \
--cc=yi.y.yang@intel.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