21 Jul
2017
21 Jul
'17
6:25 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 "Tools to centralize packet capture and storing".
The branch, laforge/ipip has been updated
discards 74aa667511b83cbad8cb5159e97000961799d0ce (commit)
discards 41123e0540a541be34d5ee23492a61bec99adc6a (commit)
discards 5494de5c0853dfebb1aac07126f68abaf6a7f284 (commit)
via b147795a3ed4b42c3beb7539d52c84af5caba558 (commit)
via 5f071cd2c6af6c840d5ecac8e8474067fdc5738c (commit)
via f266924bac7c720485bee8fb4d27a35062643577 (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 (74aa667511b83cbad8cb5159e97000961799d0ce)
\
N -- N -- N (b147795a3ed4b42c3beb7539d52c84af5caba558)
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-pcap/commit/?id=b147795a3ed4b42c3beb7539d52c84…
commit b147795a3ed4b42c3beb7539d52c84af5caba558
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Fri Jul 21 18:12:01 2017 +0200
Add support for generating IPIP to osmo-pcap-client
This allows the user to change the configuration between either using
a) the classic OsmoPCAP protocol (over TCP with or without TLS)
which is used when you want to talk to an osmo-pcap-server
b) the (new) IPIP encapsulation, which will simply take the IP
packet (without Ethernet or pcap header) and transmit it inside IPIP
to the specified server IP address. This is useful for gettin
real-time streaming into wireshark.
Change-Id: I8056fc163ac2f15adcb964d867dd5e51df4e4710
http://cgit.osmocom.org/osmo-pcap/commit/?id=5f071cd2c6af6c840d5ecac8e84740…
commit 5f071cd2c6af6c840d5ecac8e8474067fdc5738c
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Fri Jul 21 16:57:12 2017 +0200
client: Move to osmo_sock_init2_ofd()
We can simplify the code even further by using the osmo_fd version
of osmo_sock_init2() called osmo_sock_init2_ofd(), which takes care
of filling the osmo_fd.fd member and registering the socket in the
select loop.
Change-Id: Ibf1480e7dee287db77a19bb9f0254edddf7706ab
http://cgit.osmocom.org/osmo-pcap/commit/?id=f266924bac7c720485bee8fb4d27a3…
commit f266924bac7c720485bee8fb4d27a35062643577
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Fri Jul 21 16:55:19 2017 +0200
Use libosmocore osmo_sock_init2() instead of local implementation
A related function for "create a socket, bind it locally and connect
remotely" has meanwhile been introduced in libosmocore, so the local
implementation can go.
Change-Id: Ieda77ad8b3f7b89faa09882c0037562ce4d0fc89
-----------------------------------------------------------------------
Summary of changes:
src/osmo_client_network.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
Tools to centralize packet capture and storing