Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I6ecbce6aab11e1382ff9f71d901e1c6ac145f835
|
|
Change-Id: Iba106dcc18e3d429b4b9808610a44ac29b798172
|
|
Change-Id: I10ce4a9414768cdcf850feeca4088296e339919f
|
|
Change-Id: Id4e337cdc82c26922b7ca7f0fe8af523e9a0945c
|
|
Change-Id: I1bcbe047d233684647d6ffe9febb14a12c579696
|
|
This is an option enabled by default and not existent as cmdline param
since asn1c 0.9.26.
For some reason, when dropping it, asn1c generates different description
comment section on related files. In any case, this makes hnbap look
like other libraries which already got this param removed and hence also
generateds code looks the same.
Change-Id: Iccf81539a5045416185e619d24c3d542204437e6
|
|
Other libraries already use ASN1C_PREFIX except the HNBAP one. Let's use
it here to avoid collisions.
All new include/osmocom/hnbap/HNBAP_*.h and src/hnbap/HNBAP_*.c are
generated using the updated src/hnbap/Makefile.am.
Files such as src/*.c, test/* and include/osmocom/hnbap/hnbap_common.h
are modified manually to update structs/enums to new prefix.
Related: SYS#5516
Change-Id: I6c062f631527ae42811bfec134933671c05ecba6
|
|
Change-Id: Ib7a03973d43828f47ff59b561d9ddce43186f8af
|
|
Change-Id: I5666a6dc1ec9e56fe133642fb0054e913265c081
|
|
Change-Id: I203a25a8059218bb9fd6d10cbc028a296d347382
|
|
Warning observed compiling with gcc 11.1.0.
Change-Id: I6ca53dd57572338f15971633441da895843a164d
|
|
Change-Id: Icc8b90866a8edce9d10c87f4ced7137edf1c46f0
|
|
Change-Id: I9e21b504e4fac072d8481d0a699bc58d1b94a12d
|
|
It is needed by the new osmo-hnodeb project.
Related: SYS#5516
Change-Id: I8b800baacbfe3a3c424c51b418b5ac2e2848b3ba
|
|
It is needed by the new osmo-hnodeb project.
Related: SYS#5516
Change-Id: I0d0862e9d59d3b206f3f7dfae4b39ae4032bb762
|
|
Change-Id: Ie22df146cfaf6aaf9c7cef884a964e6a3dfcc8ad
|
|
It was no longer needed since .la was used.
Change-Id: I3f196d5c2bb35826709bfc32d10e6b3683b552ee
|
|
Change-Id: I934b7be7ca1fac05410df6640428ee8e9c70c3e7
|
|
Change-Id: Id33e2e8caa37dc359d564188747cd4c1b8bc4064
|
|
This allows the SGSN always having feedback on the resolution of the
release, hence being able to stay in PMM CONNECTED state until the
resolution is received, then moving to PMM IDLE.
Related: SYS#5389
Change-Id: Iac822c74e56750dc40e94573eae0e20853ff68c0
|
|
Change-Id: I2233df2b09ae46f28dd99d7540d71fee8e47b6ff
|
|
We don't want to print usage information after the VTY reference XML.
Change-Id: Ia729134a8f18d53274bbc063aa39508c7dcc1f72
|
|
Change-Id: I3b592c39646a77681efde5debb5ac2a844208949
|
|
For some unknown reason, using size=0 instead of 1 makes LeakSanitizer
report a leak when calling osmo-hnbgw --vty-ref-xml:
"""
==19857==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 96 byte(s) in 1 object(s) allocated from:
#0 0x7f083b4d0d28 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xc1d28)
#1 0x7f083a8e5661 in talloc_named_const (/usr/lib/x86_64-linux-gnu/libtalloc.so.2+0x6661)
"""
It seems iu_client.c is already using size=1.
Change-Id: I383653c981e68a053babd33dee1f0df8731752b0
|
|
This global variable is already defined in iu_client.c provided by
libosmo-ranap (and used by libasn1c).
Fixes ASan warning at starutp.
Change-Id: I7dbae83ce0dc4ac25dc10879e223280414f7b561
|
|
Change-Id: If07b00e928fbecc596a7f75fc55e811bd9199b72
Depends: Ie2022a7f9e167e5ceacf15350c037dd43768ff40
Relates: OS#5041
|
|
Change-Id: Ic53a0a9afb8038759bb3ab1d4c5970f23632e84e
|
|
Let's disable category here since we don't care about its formatting here.
In any case, every test relying on logging output validation should
always explicitly state the config to avoid issues in the future if
default values change.
Change-Id: Ia633cae0a26f294e276b431a82256abb1b57ebba
Related: OS#5034
|
|
The related compiler warnings were overlooked as due to the
asn1c-generated code there always are tons of warnings printed compiling
this project :(
Change-Id: I40b1265ba696501cc72e674f3ef4146c47aacf1b
|
|
Change-Id: I6d2d033b0427bdc84fee61e0f3cb7b29935214bf
Closes: OS#4143
|
|
So far we don't really have any way of matching a given log message
to a specific hNB. Let's use the newly-introduced LOGHNB() macro.
Change-Id: Ia16eed4ca5e9ef231259e94c65105f7586f366bc
|
|
Change-Id: I17f20cea8aa63ed79168653292b99c90b8c03caf
|
|
Change-Id: Ic92e60dda41a9e4d139294b1e851fff5c4f26143
|
|
Change-Id: I320ad86b83b0308b43489e8d95f63d6ed55821b5
|
|
Change-Id: I168e4f7cd48cbaa387e6b05868107250795a0f0c
|
|
Change-Id: If8b799777598377048512c338f6384560b445ba3
|
|
Change-Id: I04b1c0446124d66dae1e8fb99d9b82782d12bde7
|
|
gcc warns about set but not used variable otherwise.
Change-Id: Ia49b7e88a66a4a744c2b14db6331cc0de431f60b
|
|
Change-Id: I3b0a6218ac6242d03642972d5b244815ce9d97a0
|
|
Change-Id: I12870a1cf2462b7cc2868a54f58416e03a856084
|
|
osmo_hexdump expect it to be a const unsigned char*, and gcc warns about
incorrect signedness.
Change-Id: I7e0622f502a4442d700340b0f1c2f8cd01e90ecd
|
|
So far we don't really have any way of matching a given log message
to a specific hNB. Let's introduce a new log macro, together with
a configuration directive to select whether the hNB-ID or the
UMTS CellID shall be used.
Change-Id: I6113925216c6f88add2c6d27bdf47ccbb017f293
|
|
Change-Id: I4c539168597187408c31b906fd57844e0f165c9b
|
|
We don't want messages to be sent being delayed.
Related: OS#4499
Change-Id: I333e7f868e426f7d7ebb328ea2a441d769ea8ebd
|
|
See https://lists.osmocom.org/pipermail/openbsc/2020-October/013278.html.
Change-Id: I5c0a1efc21a5cc085b701be24dbcca1aaae15ee6
Depends: I8baf31ace93c536421893c2aa4e3d9d298dcbcc6
Related: SYS#4937
|
|
"127.0.0.1" is changed to "localhost" to let local NSS decide whether to
use IPv4 or IPv6. In newish systems, IPv6 ::1 will be selected since
IPv6 takes precedence over IPv4.
Similarly, the default source addr needs to be changed from NULL to "localhost"
since for some yet unknwon reason, getaddrinfo(AF_UNSPEC, NULL) returns
first IPv4 "0.0.0.0" and later "::", which is inconsistent with
getaddrinfo("localhost") result, resulting in src=IPv4(0.0.0.0) and
dst=IPv6(::1), which is incompatible and will fail. In any case, since
the default remote address is a local one and it's the client side,
there's no real logical change since the kernel would anyway should have
taken a local address anyway.
Change-Id: I3c07e6aa0c87b752c9ea22eb4936f6993de6571f
|
|
Let's add the type name whose encoding failed to give us some kind
of a clue what's happening in those situations.
Change-Id: I802677ba7164a4d3382d4bc00f5e1c7ab7067d89
|
|
With new gcc 10.1.0, tests failed at runtime when built with ASAN
enabled, since some global variables where defined multiple times.
See OS#4556 for a sample Asan error.
Fixes: OS#4556
Change-Id: I12a667ea8a9f16404c13c9218b246d2e3acfe3e8
|
|
Change-Id: I3ef7a3f1c3247615619a0d01c92d8f80572b0dfe
|
|
/usr/bin/ld: test_common.o:(.bss+0x0): multiple definition of `talloc_asn1_ctx'; test-helpers.o:(.bss+0x0): first defined here
See also https://alioth-lists.debian.net/pipermail/debian-mobcom-maintainers/Week-of-Mon-20200413/000652.html
Change-Id: I4ce41158bb27e6b9242613106f226fc86995c53c
|