Age | Commit message (Collapse) | Author | Files | Lines |
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
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
|
|
Currently looking at a weird issue. Make it possible to install the
-dbg packages.
Change-Id: I7d6c8e491be459151c1531b86f28bb1dc2ee8bb4
|
|
Change-Id: Ibe86b761b494e0fb78bbbc78e3c1982e44185750
|
|
Modify the osmo_sock_init (code clone to be integrated upstream)
to allow binding to a specific source ip and source port. Allow
the source ip to be configured but allow the kernel to pick a
random port for us.
This is necessary for systems with multiple interfaces where the
default route is not necessarily the right one to connect to the
pcap server.
Change-Id: I84e728b0752213d28f970fcbbfd6565c441ccfeb
|
|
Change-Id: I85e210e6ed14aef085902a5af6407d51685aecba
|
|
When not running as root the opening might fail and then we would
crash when sending the link information. Do not crash. This could
have crashed before the re-factoring but due the async connect it
seems more likely we hit it now.
Change-Id: I26a10c401a9a8998acc50a4bd4432d2ac7fceaeb
|
|
With the VTY a user can write connect, connect, connect and this
would lead to leaking fds. Always close the connection.
Change-Id: Iab94dc2fd28496bf5fd8ceb5611f9e6505ccae1b
|
|
Change-Id: I2118723345caf6a68f03de74a4182506e7bf105c
|
|
Ignore the default connection if no srv_port and has been specified.
Change-Id: I6a3a9a0af73a9183a6b233937af3357d15a07f25
|
|
Allow to configure multiple servers and connect. Introduce a new VTY
node to allow multiple servers. Add an explicit connect. Do not put
the main connection into the same list but assume it exists.
Change-Id: I9448ad4a005dd7c7eb1c615d03e57d6cb058ae4d
|
|
If we want to have multiple servers we should not block when trying to
connect to one of them. Enable non blocking mode and handle the fd
specially until it is connected. E.g. on failed connect the read will
become readable but fail, otherwise it becomes writable.
Clear the write queue to make sure that the link data is sent first.
We might be able to introduce a osmo_wqueue_prepend.
Change-Id: Iae2bc264d15aa8598beefc194e3b8c4ebe87320a
|
|
There is no VTY code yet and no servers in the list but it looks
good client this.
Change-Id: Ic35748f1a95a880a9fa49dd18361592d8ac941ba
|
|
Change-Id: I3c7c499c921b03752cbbcdda3eac8ca360323a22
|
|
Take out various fields into a new connection class. We will have the
option to connect to multiple servers.
Change-Id: I820176d133fbdb0240a16eb4e1a6d505e5c080c6
|
|
Add TLS support to the client and server. What is known working is
support of anonymous mode with generated DH params. Mildly tested
by hand over localhost.
|
|
Change-Id: Iba0008e3e0da276cc65c7501145b65294233febb
|
|
Change-Id: Ifc042e6755c223339fafbc3af9106073341f9b45
|
|
Make the priority configurable, load DH params, allow to specify
certificates or anonymous operations.
Change-Id: I8ec3c0f8e1ee2089e1b7dacd9de842260930032f
|
|
Add simple vty command to enable tls per client or not. We still
need a lot more tls commands for the server.
Change-Id: I583b7d5c999ed01c135882895fb2a8f04739ad00
|
|
Using tls priority of NORMAL:+ANON-ECDH:+ANON-DH already allows a
client to connect to a server and protect the data using tls.
Generate the dh params on load (and do that for the client right
now as well) but that will go away soon.
Change-Id: Ifa2ad24c0a631573c259a3bf94b91a946ad9ec9d
|
|
In preparation of TLS let's not call close_connection from
within the dispatch but return an error and then close the
connection from the outside.
Change-Id: I607fed0191907cfbc8887d749c88f7f4ffb87166
|
|
Change-Id: I4295854c749d86ca8c34a979c877363d9f48e176
|
|
We are only reading from the socket and never write but the osmo_tls
code is integrated with it. We will never write and the queue size is
set to 0. Simplify the read_cb.
Change-Id: I32335b1f7b7ed06b92c6222516c185301ce13781
|
|
Change-Id: I8861acaaec5465de620637b7fdf3341517133c4f
|
|
Use GNUtls because it is GPL compatible and instead of mbedTLS seems
to have a working non-blocking I/O integration. GNUtls has various
issues that could not be resolved easily:
* Pick spdy as sub protocol
* gmt_time not randomized
* private key loaded to RAM (but not verified)
This is the beginning and not the end. Client support might need more
work with actual tls verification. Maybe more manual x509 cert
verification is needed and maybe client certs don't work at all. I try
to ignore renegotiation as I threw away the key.
Reload x509 creds and keys as they might have changed from one
connection to another.
Change-Id: I9128e14084da1fc2705f858393f98b8133996172
|
|
Change-Id: Ib4e17948ffa84e73c1c81734e6002a73251d744b
|
|
Change-Id: I63a8cea776e57dce747a357c40f9caa0a9e2d3b5
|
|
Change-Id: I1704e0d58a04770a3aac1f70f3e01ee9ac585dbf
|
|
Attempt to write code that detects the wrap and is doing the
right thing when it happens.
Change-Id: I501ebc49d3e86b0605ec1fbe2f62aee3f362aa36
|
|
Add the basics for getting a picture what a client and the server
is doing. We need to create unique descriptions as the code is
working with names and not numbers for clients.
Change-Id: I4a9be5bdd815d280cccf0199efc2ca79fc77d393
|
|
Add more counters and start counting them when reading from the
PCAP library and when trying to write to the socket.
Change-Id: I52d3064a265b402ac849d8578a14f718156c0805
|
|
Count certain events that can help to understand what is going on.
This includes OOM, failure to queues.
Change-Id: I4a2dad32afb577822c7181d2813ea5a7e693c704
|
|
Change-Id: Ibd14da3e7f62065f5d28d4a90d2b55eed609b64f
|
|
Change-Id: Ic628dd348f8fce978691aaa331b0e67ee13f10c6
|
|
Initialize the stats backend allowing key performance indicators
to be pushed out of the system.
Change-Id: Id652b60d230f705b927e49d81cd3731432156c7e
|
|
In file included from osmo_client_main.c:27:0:
/home/ich/install/openbsc/include/osmocom/core/process.h:1:2: warning: #warning "Update from osmocom/core/process.h to osmocom/core/application.h" [-Wcpp]
#warning "Update from osmocom/core/process.h to osmocom/core/application.h"
Change-Id: Id60cf90ebb7255d79f8e3bdb81f099f1362d538b
|
|
osmo_client_main.c:57:2: warning: initialization from incompatible pointer type
.go_parent_cb = osmopcap_go_parent,
^
osmo_client_main.c:57:2: warning: (near initialization for ‘vty_info.go_parent_cb’)
CCLD osmo_pcap_client
CC osmo_server_main.o
osmo_server_main.c:56:2: warning: initialization from incompatible pointer type
.go_parent_cb = osmopcap_go_parent,
^
osmo_server_main.c:56:2: warning: (near initialization for ‘vty_info.go_parent_cb’)
Change-Id: If73c85a64789ef4bff63dcfe008e918e650b428f
|
|
Change-Id: I002e72776c6916ee331b4387b6d645d0c48c388c
|
|
Change-Id: I97c23cbf2d5f42b12e2fc8426633401c4edc1a62
|
|
To allow easily extracting or streaming the data to an external
analysis system, zeromq can be configured (and reconfigured). The
system works as fire and forget and no loss detection is present.
A simple go based client application is provided to subscribe to
the publisher.
Change-Id: I4f3e6d675023a81b7d2ee19bf1f44a2be0ca003c
|
|
Change-Id: I383558bb9aad3cb149f35e13910a1d6aa79afc84
|
|
We might only want to centralize the data streams but handle the
data differently. This will be combined with an upcoming ZeroMQ
publisher feature to broadcast all events out.
Change-Id: I12c6bf16310820d882fa28c6930931650475e0bb
|
|
Change-Id: I26de644a9cf4c6d6fb366c8a8fd701570005b9a8
|
|
Change-Id: I5a6c473a97d04aecae8101a024edb734bbe24401
Reviewed-on: https://gerrit.osmocom.org/27
Tested-by: Jenkins Builder
Reviewed-by: Harald Welte <laforge@gnumonks.org>
|
|
Change-Id: I566d48fe9831f384b93c3fad72a7dae9dd61b2d2
|