osmo-ggsn.git branch pespin/fix-iproute updated. 1.0.0-32-gab5e160

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/osmocom-commitlog@lists.osmocom.org/.

gitosis at osmocom.org gitosis at osmocom.org
Wed Oct 11 17:49:11 UTC 2017


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "The OpenGGSN project".

The branch, pespin/fix-iproute has been updated
  discards  3c71d6d1b560b4d7213d63f38b01c81e4bf56951 (commit)
       via  ab5e1609373dcaa44d4e972920b9bbb4ab371727 (commit)

This update added new revisions after undoing existing revisions.  That is
to say, the old revision is not a strict subset of the new revision.  This
situation occurs when you --force push a change and generate a repository
containing something like this:

 * -- * -- B -- O -- O -- O (3c71d6d1b560b4d7213d63f38b01c81e4bf56951)
            \
             N -- N -- N (ab5e1609373dcaa44d4e972920b9bbb4ab371727)

When this happens we assume that you've already had alert emails for all
of the O revisions, and so we here report only the revisions in the N
branch from the common base, B.

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-ggsn/commit/?id=ab5e1609373dcaa44d4e972920b9bbb4ab371727

commit ab5e1609373dcaa44d4e972920b9bbb4ab371727
Author: Pau Espin Pedrol <pespin at sysmocom.de>
Date:   Wed Oct 11 18:56:08 2017 +0200

    apnt_start(): Pass ippool flags to avoid certain IPs
    
    Commit dda21ed7d4a897c9284c69175d0da598598eae40 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.
    
    Change-Id: I72ae59ad5929ca0dc9ee69937c50e57a5f49ca76

-----------------------------------------------------------------------

Summary of changes:


hooks/post-receive
-- 
The OpenGGSN project



More information about the osmocom-commitlog mailing list