[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170217180316.ujzsbnb2s2ee44iw@nataraja>
Date: Fri, 17 Feb 2017 19:03:16 +0100
From: Harald Welte <laforge@...monks.org>
To: Andreas Schultz <aschultz@...p.net>
Cc: Pablo Neira Ayuso <pablo@...monks.org>,
netdev <netdev@...r.kernel.org>,
osmocom-net-gprs <osmocom-net-gprs@...ts.osmocom.org>
Subject: Re: RFC: unit tests for kernel GTP module
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.
--
- Harald Welte <laforge@...monks.org> http://laforge.gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
Powered by blists - more mailing lists