Hi Andreas,
On Fri, Feb 17, 2017 at 04:02:59PM +0100, Andreas Schultz wrote:
The test suite is proprietary, so we can only share the results but not the test setup itself.
it would be great to have some CI setup where both current stable as well as a development branch of the code is tested, and reports published regularly. Not sure how realistic that is.
We more or less removed static GTP tunnels. The tools in libgtpnl only work when an application is keeping the GTP socket alive.
Well, then those tools need to be adapted accordingly. That's what I also indicated in other mails: Changes in the kernel GTP code should always be followed-up with correspondign changes in libgtpnl and associated tools. I mean, the tool could just open the socket and then continue to run until terminated explicitly...
I think there's a lot of value in some very low-level tools for testing and experimentation, without the complexity of configuring + running an Erlang GGSN/P-GW with all its dependencies.