24 Sep
2017
24 Sep
'17
4:50 p.m.
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, laforge/sgsnemu-v6 has been updated
discards e585641387af4730498a04168d8e90c403efff04 (commit)
discards a35a1f792b4ac73b463f9fcd4d48d40748d85a57 (commit)
discards 0d8dccb7e1911ccd5a93791379c4ecf7458ab3ce (commit)
discards 96a79de85f8ef14023d265970d6597f44eb5a0aa (commit)
discards ab763a4cda30e5b298eb25a73c84f3488fc39f42 (commit)
discards 6988e48b3f12eadef8cf817b0f85d63fe61834af (commit)
via a6196e932d74355b0761e9372ca7f5491ee4f439 (commit)
via edebd6794a20cc1ae1cec8efae53de949898534b (commit)
via 72137b146a089e92a546f0ffb330d7ca98853ff3 (commit)
via 808b4ced0bb64181e18ff47dfc952f30829e5de1 (commit)
via e21c3e4f5ebfeb33ef24d3af069063983ed5dd08 (commit)
via 01b25c7389e8000a2ac7b3c019374687552b6b6c (commit)
via ff438174aab40a07fe0597d3f1d2b12d88090a20 (commit)
via 3ca419a2ef00bea935fad17278810d48d780baf7 (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 (e585641387af4730498a04168d8e90c403efff04)
\
N -- N -- N (a6196e932d74355b0761e9372ca7f5491ee4f439)
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=a6196e932d74355b0761e9372ca7f5…
commit a6196e932d74355b0761e9372ca7f5491ee4f439
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Sun Sep 24 21:54:59 2017 +0800
sgsnemu: Add IPv6 support via tun device and "-t v6 --createif"
The idea is to only implement the GTP-C plane and configure the right
link-local source address on the tun-device and let the regular (Linux)
kernel take care of sending router solicitations and
accepting/processing the related router advertisement. This avoids a
lot of complexity in sgsnemu.
For this to work, you must have /proc/sys/net/conf/$tun/accept_ra set
to either 1 (works only if no IPv6 forwarding/routing configured on your
sgsnemu-running system) or 2 (works even if forwarding/routing is
configured).
Change-Id: I57e4c53ee648e1efecfba3eea592d1129849557c
Closes: OS#2518
http://cgit.osmocom.org/osmo-ggsn/commit/?id=edebd6794a20cc1ae1cec8efae53de…
commit edebd6794a20cc1ae1cec8efae53de949898534b
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Sun Sep 24 18:12:40 2017 +0800
sgsnemu: Allow specification of PDP (EUA) Type IPv4 or IPv6
This just adds the capability to sgsnemu to request a certain PDP
EUA type. It doesn't mean it actually handles anything beyond the
existing IPv4 yet.
Change-Id: I157f9157a7ff2ea56c37a4a902d4706de4c7d35d
http://cgit.osmocom.org/osmo-ggsn/commit/?id=72137b146a089e92a546f0ffb330d7…
commit 72137b146a089e92a546f0ffb330d7ca98853ff3
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Sun Sep 24 17:45:05 2017 +0800
Replace EUA magic numbers for IETF, IPv4 and IPv6 with #defines
Change-Id: I33f65e404217e717bd795e5229c8d9456a7b3739
-----------------------------------------------------------------------
Summary of changes:
ggsn/ggsn_vty.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
hooks/post-receive
--
The OpenGGSN project