Age | Commit message (Collapse) | Author | Files | Lines |
|
Related: OS#5223
Change-Id: I90c4723034a7fcd29421ef825b958dbdbb594dc2
|
|
Related: OS#5223
Change-Id: I5d085695d4bdd2aaac4105c129e423d27be63a3e
|
|
Change-Id: I0c6fe9d0c59110211f8cc2ac28ce93b885fd565d
|
|
Depends: I5021c64a787b63314e0f2f1cba0b8fc7bff4f09b
Change-Id: I0fc8142756040c98c1862ddb18a77a032f2a7143
|
|
Change-Id: I120f015183f05ec8477cdcd9b04379f43e20428d
|
|
osmo-ci utils
Previous script didn't clean workspace and git repositories were
allegedly not being updated, hiding build failures against newer deps.
Currently cellmgr-ng is not being maintained and fails to build against
recent libosmo-sccp. For that dep repo, tag "old_sua" is used since
after that tag, APIs changed considerably and it is known that
cellmgr-ng cannot build starting from there.
It's up to whoever wants to maintain it to make changes in cellmgr-ng to
support newer libosmo-sccp.
While building with new jenkins.sh script and "old_sua" tag, still there
are some build issues (mostly related to build system), like some
Makefile.am files missing some LDFLAGS. Some of them are fixed in
follow-up patches. Some other are left as an exercise for whover wants
to revive this repo.
Change-Id: Ic597664198547ec367d7926d4e401b9734c8cfa9
|
|
Change-Id: I32da63d05a45aff50c657fe8640fa997daa668e2
|
|
Currently the connect is blocking leading to one bad connection
(e.g. to a black hole) blocking all other connections leading to
bursty traffic.
Change-Id: Idfca8acbce09176055da3e577566386e07d7a348
|
|
This facilitate the use of "git review" command for gerrit submissions.
Change-Id: Ic2df30f053687b6d48232cf04ce22592e1e09a94
|
|
Change-Id: Id3c41595475dac06dcdf3a104570640349c8f8bf
|
|
It seems that the Ubuntu linker is quite picky in where it is looking
for symbols. Link libosmocore (and as such talloc) last of the Osmocom
libraries. This could fix:
gcc -Wall -I/usr/include/ -I/usr/include/ -I/usr/include/ -I/usr/include/ -DNO_UNIPORTE -g -O2 -fdebug-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-Bsymbolic-functions -Wl,-z,relro -o cellmgr_ng main.o mtp_layer3.o thread.o ipaccess.o pcap.o bss_patch.o bssap_sccp.o bsc_sccp.o bsc_ussd.o links.o msc_conn.o link_udp.o snmp_mtp.o debug.o isup.o mtp_link.o counter.o sccp_state.o bsc.o ss7_application.o vty_interface_legacy.o vty_interface_cmds.o mgcp_patch.o mgcp_callagent.o isup_filter.o -ltalloc -losmocore -ltalloc -losmogsm -losmocore -ltalloc -losmovty -losmocore -losmosccp -losmoxua -lpthread -lnetsnmp -lcrypto
[ 79s] /usr/lib/gcc/x86_64-linux-gnu/6/../../../x86_64-linux-gnu/libosmosccp.so: undefined reference to `talloc_free'
Change-Id: I94c87496ebffd41a6217d860b0ca4bed6ff2d24c
|
|
Change-Id: I51dccafb01c47a543f3223c3502f7b02819bd33f
|
|
Change-Id: Iec6ad62c01aaaa7300086d130cc5512683f6c565
|
|
Change-Id: Ib50b6df0d843b730418a98907666aba42d20dd1a
|
|
There seems to be issues with the write handling of the osmo-stp
and so far we did not enable vty tests here. Make it possible to
enable the tests, fix the VTY strings, change string to OsmoSTP.
Change-Id: I547fd4840d86ce16e8589fb63802dd7099781194
|
|
Provide a modern systemd service file for the osmo-stp. The sysvinit
file is quite basic and doesn't signal syntax errors nicely. Let us
embrace the future.
Change-Id: Ic0cc0f17d442aa0ad38de9f0cf8aeb14121938de
|
|
Change-Id: I4ed058aba15d9fdc22dde99d60df0aabd6585b75
|
|
mgcp/mgcp_protocol.c: In function ‘mgcp_handle_message’:
/home/ich/install/openbsc/include/osmocom/core/logging.h:59:4: warning: ‘save’ may be used uninitialized in this function [-Wmaybe-uninitialized]
logp2(ss, level, __BASE_FILE__, __LINE__, 0, fmt, ##args); \
^
mgcp/mgcp_protocol.c:368:15: note: ‘save’ was declared here
char *elem, *save;
Change-Id: I28152373b043c8a5b55a83ac09dd7bafce4d2d66
|
|
The return type changed from enum to int and it is time to catch
up with it.
vty_interface.c:108:2: warning: initialization from incompatible pointer type
.go_parent_cb = ss7_go_parent,
^
vty_interface.c:108:2: warning: (near initialization for ‘vty_info.go_parent_cb’)
mgcp_ss7_vty.c:36:2: warning: initialization from incompatible pointer type
.go_parent_cb = mgcp_go_parent,
^
mgcp_ss7_vty.c:36:2: warning: (near initialization for ‘vty_info.go_parent_cb’)
Change-Id: I8061df697daf79fa57b8313c15f6567ff152f4a5
|
|
echo 1.3.0.66-35f9 > ../../.version-t && mv ../../.version-t ../../.version
/bin/bash: ../../.version-t: Permission denied
Makefile:786: recipe for target '../../.version' failed
|
|
This can be used to replicate a build issue more easily.
|
|
The introduction of a 'if + do {} while' lead to not being able to
return the result of the logging anymore. Just return.
|
|
For M3UA we already skip the link-test handling and there is no
point in waiting for management messages to collect routing info.
We already know where to send things. At first I tried to overload
the skip handling but it is better to just set the timer to 0 and
then move on.
|
|
|
|
Make it possible to set it. 10s seems to be a very reasonable
timeout. It should not really take much longer than that.
|
|
For M3UA we should have one time-out for operation we want and
then re-transmit it. As this is too much work right now create
a single timer that waits that after a connect the ASPAC_ACK
state will be reached.
|
|
|
|
|
|
|
|
In case of back pressure we can not send messages quick enough
and will drop messages. Add a counter so we can count how often
this happened per link/linkset. The SCTP M2UA code is not changed
as we don't have a link in the hands and adding it is too risky
without tests (not all M2UA have a link index so some might not
have a link).
|
|
Try to make it clear that this is only for the IPA bridging
mode and not a general setting.
|
|
For the "bridging" to IPA mode we can force the SCTP/M3UA connection
down. This way the remote STP will do a proper link fail-over
procedure instead of the STP throwing data away.
This is not configurable yet.
|
|
This can be used to force one connection down while the other
is down. E.g. to force SCTP down when the IPA connection is
down as well.
|
|
Print the errno and RC to give some kind of idea about
the error.
|
|
|
|
|
|
|
|
* It is in sbin and not bin
* Daemonize is not supported, let start-stop-daemon do it
|
|
|
|
We don't have regression testing here but this could be
the correct fix.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
RFC4666:
The DATA message MUST NOT be sent on stream 0
|
|
|
|
Make the code work for both ISUP and SCCP and let the address
handling still be part of the linkset/mtp3 code.
|
|
the opc/dpc for ISUP is currently wrong. The send/recv path
for actual SCCP data is not tested.
|