21 Jul
2017
21 Jul
'17
6:14 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 created
at 74aa667511b83cbad8cb5159e97000961799d0ce (commit)
- Log -----------------------------------------------------------------
http://cgit.osmocom.org/osmo-pcap/commit/?id=74aa667511b83cbad8cb5159e97000…
commit 74aa667511b83cbad8cb5159e97000961799d0ce
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=41123e0540a541be34d5ee23492a61…
commit 41123e0540a541be34d5ee23492a61bec99adc6a
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=5494de5c0853dfebb1aac07126f68a…
commit 5494de5c0853dfebb1aac07126f68abaf6a7f284
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
http://cgit.osmocom.org/osmo-pcap/commit/?id=2fe9cb937d2e7aba621ee48a289278…
commit 2fe9cb937d2e7aba621ee48a2892782e5f1cbbbc
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Fri Jul 21 11:45:38 2017 +0200
Rename osmo_pcap_{client_server} executables to osmo-pcap-{client,server}
This naming is more in line with what all the other osmocom programs are
doing (e.g. osmo-pcu, osmo-bts-sysmo, osmo-bsc, ...). We don't
generally use osmo_ anywhere else, so I suggest to change it for more
uniformity.
Change-Id: If1e3ce76f93266e0f01c801204769432b571fdb1
http://cgit.osmocom.org/osmo-pcap/commit/?id=2aea8704f391675a704d0431497cf0…
commit 2aea8704f391675a704d0431497cf0100ca76b9a
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Fri Jul 21 11:55:04 2017 +0200
Use TCP port numbers for VTY that don't overlap with other Osmocom Software
osmo-pcap for historical reasons uses the same port numbers as
OsmoPCU and OsmoBTS. This leads to problems when wanting to run related
software together on one system. Let's break the historical assumptions
and start with non-overlapping port numbers that are allocated/assigned
from https://osmocom.org/projects/cellular-infrastructure/wiki/Port_Numbers
Change-Id: I638ac0534517931d0987ce9f72f5db4f5b6c16b7
http://cgit.osmocom.org/osmo-pcap/commit/?id=604e0711596e7e06600a2d7aea3394…
commit 604e0711596e7e06600a2d7aea3394d36e5d3bda
Author: Harald Welte <laforge(a)gnumonks.org>
Date: Fri Jul 21 13:06:15 2017 +0200
sock_src_init(): Don't freeaddrinfo() undefined src_result
src_result is only valid "if (src)", so we cannot unconditionally
free it:
(gdb) bt
host=0x52 <error: Cannot access memory at address 0x52>, src=0x0)
at
/usr/src/debug/osmo-pcap/0.0.6+gitrAUTOINC+4776b2972e-r1d/git/src/osmo_client_network.c:165
Change-Id: I3b6778d9110583ecb1daec59ef2c86465d5818b9
-----------------------------------------------------------------------
hooks/post-receive
--
Tools to centralize packet capture and storing