cellular-infrastructure
/
osmo-ggsn
mirror of https://gerrit.osmocom.org/osmo-ggsn
9
0
Fork 0
Code Issues Releases Wiki Activity
677 Commits 25 Branches 19 Tags 5.7 MiB
Commit Graph

7 Commits

Author SHA1 Message Date
Pau Espin 00ef1b0d6e tests: Explicitly drop category from log 
Let's disable category here since we don't care about its formatting here.

In any case, every test relying on logging output validation should
always explicitly state the config to avoid issues in the future if
default values change.

Change-Id: Icce09882ef3ed07328679594ff84902383d16c72
Related: OS#5034
 2021-02-19 13:22:28 +01:00
Pau Espin 042a445cf3 use osmo_init_logging2 
Change-Id: Ic38fff17cc985238b91999c8acdd92d22fd28c72
 2018-04-17 14:31:42 +02:00
Pau Espin 9c0f4f49e9 tests: Split ipv6 specific tests into a new test group 
This way they can be easily disabled later on when IPv6 support is made
optional.

Change-Id: I3906dbf55ccf1650083398e08ac870add0bbdcef
 2017-12-04 13:25:02 +01:00
Neels Hofmeyr dabb8b4860 fix compiler warnings: return 0 in main(), in 3 tests 
Change-Id: I9e49ceba6b0a8dffd331e5707667d9bb007f3ec7
 2017-10-31 01:02:00 +01:00
Pau Espin 859f9b0752 ippool: Implement and use blacklist instead of blindly using IPPOOL_NOGATEWAY 
Commit dda21ed7d4 modified previous calls
to ippool_new() removing the pass of flags to avoid allocating certain
problematic IPs from the pool to MS, such as the network, gateway and
broadcast IPs.

Today I did some unsucessful tests with osmo-ggsn with a pool "ip prefix
dynamic 176.16.222.0/24", and thus IP 176.16.222.0 was being assigned to
the MS. De-capsulated DNS packets were received in the tun interface,
but the Linux system in there was unable to correctly forward the
packets to the gateway interface connected to the Internet. However,
adding a second MS which got 176.16.222.1 had its packets forwarded
correctly.

However, previous implementation relies on flag IPPOOL_NOGATEWAY flag to
blindly blacklist first IP after the network ip (ie, .0 and .1 are
removed), which limits the IP reserved for the tun device to be .1. If a
different IP in the range is assigned, it may cause issues. As a result,
a blacklist is introduced in this commit to dynamically fetch the tun IP
address and exlucde it from the pool of available IPs.

Change-Id: I8e91f7280d60490c858a769dd578c1c8e54e9243
 2017-10-17 19:10:24 +02:00
Pau Espin 361cb9e910 lib/ippool: Fix listsize calculated 1 elem too small 
Take the chance this commit is changing test output to also remove use
of IPPOOL_NOGATEWAY which is going to be removed soon, and instead test
IPPOOL_NOBROADCAST.

Change-Id: I95c24bc690490155bec9e3933d678e4668d7745f
 2017-10-16 11:59:43 +02:00
Harald Welte 1d8ffc6b23 Add ippool unit-test for 'make check' runs 
This test creates a variety of v4 (and one v6) pool and performs
allocations until the pool is full, then frees a random number of
randomly distributed addresses, re-allocates them and again checks that
they're all available and finally once the pool is full allocations
fail.

Change-Id: Ibf4588e8f3ae71684e5262c0caaa2689aee73a94
 2017-10-13 16:28:01 +02:00