From: Harald Welte <laforge@netfilter•org>
To: Jonas Bonn <jonas@norrbonn•se>
Cc: netdev@vger•kernel.org, pablo@netfilter•org
Subject: Re: [PATCH net-next v2 10/12] gtp: add IPv6 support
Date: Sat, 12 Dec 2020 12:22:53 +0100 [thread overview]
Message-ID: <X9SoDToVmUdhgP0D@nataraja> (raw)
In-Reply-To: <20201211122612.869225-11-jonas@norrbonn.se>
Hi Jonas,
thanks again for your patches, they are very much appreciated.
However, I don't think that it is "that easy".
PDP contexts (at least) in GPRS/EDGE and UMTS come in three flavors:
* IPv4 only
* IPv6 only
* IPv4v6 (i.e. both an IPv4 and an IPv6 address within the same tunnel)
See for example osmo-ggsn at https://git.osmocom.org/osmo-ggsn
for an userspace implementation that covers all three cases,
as well as a related automatic test suite containing cases
for all three flavors at
https://git.osmocom.org/osmo-ttcn3-hacks/tree/ggsn_tests
If I read your patch correctly
On Fri, Dec 11, 2020 at 01:26:10PM +0100, Jonas Bonn wrote:
> - struct in_addr ms_addr_ip4;
> - struct in_addr peer_addr_ip4;
> + struct in6_addr ms_addr;
> + struct in6_addr peer_addr;
this simply replaces the (inner) IPv4 "MS addr" with an IPv6 "MS addr".
Sure, it is an improvement over v4-only. But IMHO any follow-up
change to introduce v4v6 PDP contexts would require significant changes,
basically re-introducing the ms_add_ip4 member which you are removing here.
Therefore, I argue very much in favor of intrducing proper IPv6 support
(including v4v6) in one go.
Regards,
Harald
--
- 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:[~2020-12-12 11:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 12:26 [PATCH net-next v2 00/12] gtp: IPv6 support Jonas Bonn
2020-12-11 12:26 ` [PATCH net-next v2 01/12] gtp: set initial MTU Jonas Bonn
2020-12-12 9:38 ` Harald Welte
2020-12-11 12:26 ` [PATCH net-next v2 02/12] gtp: include role in link info Jonas Bonn
2020-12-12 9:40 ` Harald Welte
2020-12-11 12:26 ` [PATCH net-next v2 03/12] gtp: really check namespaces before xmit Jonas Bonn
2020-12-12 9:41 ` Harald Welte
2020-12-11 12:26 ` [PATCH net-next v2 04/12] gtp: drop unnecessary call to skb_dst_drop Jonas Bonn
2020-12-12 9:50 ` Harald Welte
2020-12-12 11:38 ` Jonas Bonn
2020-12-11 12:26 ` [PATCH net-next v2 05/12] gtp: set device type Jonas Bonn
2020-12-12 9:51 ` Harald Welte
2020-12-11 12:26 ` [PATCH net-next v2 06/12] gtp: rework IPv4 functionality Jonas Bonn
2020-12-11 12:26 ` [PATCH net-next v2 07/12] gtp: use ephemeral source port Jonas Bonn
2020-12-12 5:35 ` Pravin Shelar
2020-12-12 7:49 ` Jonas Bonn
2020-12-12 10:07 ` Harald Welte
2020-12-12 13:40 ` Jonas Bonn
2020-12-11 12:26 ` [PATCH net-next v2 08/12] gtp: set dev features to enable GSO Jonas Bonn
2020-12-12 5:31 ` Pravin Shelar
2020-12-12 7:50 ` Jonas Bonn
2020-12-13 18:25 ` Pravin Shelar
2020-12-11 12:26 ` [PATCH net-next v2 09/12] gtp: support GRO Jonas Bonn
2020-12-11 15:43 ` kernel test robot
2020-12-11 12:26 ` [PATCH net-next v2 10/12] gtp: add IPv6 support Jonas Bonn
2020-12-12 5:51 ` Pravin Shelar
2020-12-12 7:05 ` Jonas Bonn
2020-12-12 11:05 ` Harald Welte
2020-12-12 11:22 ` Harald Welte [this message]
2020-12-12 13:59 ` Jonas Bonn
2020-12-11 12:26 ` [PATCH net-next v2 11/12] gtp: netlink update for ipv6 Jonas Bonn
2020-12-12 11:25 ` Harald Welte
2020-12-11 12:26 ` [PATCH net-next v2 12/12] gtp: add dst_cache to tunnels Jonas Bonn
2020-12-11 17:25 ` kernel test robot
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=X9SoDToVmUdhgP0D@nataraja \
--to=laforge@netfilter$(echo .)org \
--cc=jonas@norrbonn$(echo .)se \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pablo@netfilter$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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