----- Original Message -----
From: "Peter Robinson" <pbrobinson(a)gmail.com>
thanks for your feedback.
In the above page:
* Network configuration: I see NetworkManager in there but nothing
I used browser search in that page and 'systemd' (which is the name
of the source package that provides systemd-networkd) is listed.
* Other: firewalld including zones and other such configurations
The firewalld package is also mentioned.
> Most prominent subpages:
> * https://fedoraproject.org/wiki/QA/Networking/Test_environment
In this section I see "IPv6 node" but nothing that covers a IPv6 only
routed network with IPv6 to IPv4 gateway ie it runs v6 only internally
but uses 6 to 4 services for legacy services.
That is an interesting points. It sort of falls into the IPv6 only case
but has enough specifics to be mentioned, at the least.
> * https://fedoraproject.org/wiki/QA/Networking/Client_software
Again nothing about a native IPv6 only network with a gateway that
supports 6to4 for legacy services outside the network.
To be honest we are most interested in native connectivity. If anyone
needs to use tunneled connectivity as a workaround, he should probably
choose a mechanism that provides comparable results. On the other hand,
the biggest difference in 6to4 when using the `2002::/16` subprefixes
is that it is not preferred over IPv4 addresses by default according
to RFC 6724.
What about a iOS9 style preferring of IPv6 over IPv4 in the general
desktop. In the iOS9 case they do network measurements and favour IPv6
bydefault, and if it's going to be faster but fail back quickly if
it's not, how would we deal with this?
In my opinion this is out of scope of the networking QA project as
we see it.
> * https://fedoraproject.org/wiki/QA/Networking/Server_software
Nothing in here about:
* IPv6 services RA, dhcp6, 6 to 4 proxies, 4 to 6 proxies and other
such transition servers
That is correct. The page is about general networking server workflow,
for network configuration details see the respective document below.
* what about VPN services like a IPv6 only network connecting to a
dual stack VPN, or a IPv4 only VPN or a number of combinations there
of IE interfaces that are v6 only and ones that are v4 only. What
happens with routing then if there's other 6 to 4 services in play?
Like in the following bug report? Yes, that sounds useful to add
* Load balancers ie like facebook uses to bridge external dual stack
to IPv6 only internal services, or providing IPv6 externally to
present internal v4 services externally to v6
I don't think we (people currently involved in the project) have the
capacity to test Fedora based services with load balancers. Anyone
is free to submit bug reports, though.
There's also nothing I can see from a quick read about offload
engines. A lot of 10Gb+ network interfaces have offloads for generic
IP, TCP, other acceleration to enable to do line speed 10+gb on IPv4,
we obviously want acceleration because IPv6 headers are larger and
hence take up more memory.
It is not explicitly stated (and that should be fixed) that we
are focusing on userspace and configuration, not kernel networking
features. That doesn't prevent anyone from joining and extending the
project nor from filing kernel bug reports and feature requests.
There's toolkits like dpgk (
) for acceleration of packets across large bandwidth
interfaces but I don't see any mention of that or network IO
Facebook and others have been testing these sorts of things:
Along these lines also I see nothing about Open vSwitch and SND
encapsulation protocols testing such as vxlan, GRE, GENEVE etc
I think this is the same situation as above.
> During the first phase we are interested in getting feedback on
> testing methods and test cases. Any other ideas are of course
> welcome. Even contacts for future collaboration would be great.
A future development would be around 6LoWPAN and the routing protocols
etc for that so we can communicate with IoT devices.
The way I read a lot of the pages above is a "this is how we did it on
IPv4 lets test it on IPv6" rather than a review of how things are
going to change with IPv6, how would I get to a IPv4 site if I'm on a
IPv6 network, visa versa and the whole sets of new use cases that are
appearing as a result of it.
Let us now if there are specific cases that need to be covered to make
Fedora packages communicate well over the versions of the IP protocol.