- 22 May, 2024 40 commits
-
-
Robert Schmidt authored
Also, the check for clang is done in CMakeLists.txt; sleep is useless
-
Robert Schmidt authored
-
Robert Schmidt authored
Reset all the circular buffer to zero; this ensures that we cannot read uninitialized data. Since this is RFsimulator, performance is not a problem here either (and zeroing out happens only once).
-
Robert Schmidt authored
Memsan complains that uninitialized reads originate because of these warnings. Most of the corresponding variables are actually read into through by libconfig; nevertheless, initializing them should not have a bad side-effect (because the initialized value is overwritten).
-
Robert Schmidt authored
Fix clang warning warning: use of GNU old-style field designator extension [-Wgnu-designator]
-
Robert Schmidt authored
We access G_N at indexes that are not necessarily 32-byte aligned, leading to segfaults. Use simde_mm256_loadu_si256() to load from memory at an unaligned memory address to avoid the segfault. Discovered using clang; it is unclear why gcc did not encounter the same segfault.
-
Robert Schmidt authored
-rdynamic is necessary for clang as well to properly link shared executables. Add furthermore an option to ignore unused command line arguments, to suppress warning clang: warning: argument unused during compilation: '-rdynamic' [-Wunused-command-line-argument] This is likely because -rdynamic is only relevant for the linker, but the corresponding option add_link_options() is only available starting cmake 3.13, while we are still at 3.12 (for Ubuntu 18, to my understanding).
-
Laurent THOMAS authored
-
Jaroslava Fiedlerova authored
After the recent update of matix, collected logs contain color codes and we did not find the way to switch them completely off. Replacement of "docker compose logs" by "docker logs" resolves this issue. This commit includes changes related to "docker logs" usage.
-
Jaroslava Fiedlerova authored
-
sagar arora authored
- Update the configuration for benetel 650 and 550 for new firmware version - Remove the old firmware configuration file and description in the document - Add a new RU configuration section - Add How to get support from the OAI Community to clarify the support procedure.
-
sagar arora authored
Include "best practices" on how to ask questions.
-
francescomani authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Raghavendra Dinavahi authored
- RX/TX Phy processing accg to 38.211, 38.212 Rel16 - PSBCH simulator used to validate TX/RX phy processing - PSBCH SLSS Search procedures - PSBCH SIM also tests SLSS SEARCH
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
Unlike the previous commit, in noS1, we cannot use Attach(), as noS1 automatically brings up an interface, no matter whether the connection succeeded or not. Therefore, consistently wait a bit longer to increase the chance that the radio is really up.
-
Robert Schmidt authored
For various reasons, the UE might take longer to connect to the eNB. A simple sleep might not be enough; instead, use Attach() to actively wait that the UE gets an IP address. The added bonus of this function is that it will also stop&restart a UE if it did not attach, i.e., it will try multiple times to attach the UE.
-
Robert Schmidt authored
The code (author) confused MCE_PARAMS_DESC and MCE_NETPARAMS_DESC and tried to read the MCE name from MCE_NETPARAMS_DESC when in reality it should come from MCE_PARAMS_DESC. This commit fixes to use the right array.
-
Robert Schmidt authored
Same reasoning as in previous commit.
-
Robert Schmidt authored
Same reasoning as in the previous commit.
-
Robert Schmidt authored
Some reasoning as in previous commit.
-
Robert Schmidt authored
Same reasoning as in the previous commit. Remove filling of broadcast_plmn, which does not exist in the configuration.
-
Robert Schmidt authored
In a previous commit, the functionality of handling IPv6 (and DNS names) as part of the IPv4 was introduced (in IPv4 field for backwards compatibility). This commit now removes superfluous configuration fields: - IPv6: handled by IPv4 field - active: users can just remove an entry - preference: not needed
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
Rewrite sctp_create_new_listener() to use getaddrinfo() to look up IPv4/IPv6 addresses via a common interface. This allows to use e.g. DNS, and enables the SCTP library to listen on IPv6 ports. To support the above, the corresponding message is changed to not take an IPv4 address on 4 bytes (and separate IPv6), but a single name that will be resolved via getaddrinfo() The previous init message used to allow multiple IPv4/IPv6 addresses; since this is not used anywhere, remove the corresponding functionality. Modify all uses of this ITTI message to copy te SCTP init bind addr into ITTI message.
-
Robert Schmidt authored
Use getaddrinfo() to look up IP (v4/v6) addresses. The old interface of separately specifying IPv4 and IPv6 addresses is preserved, but both fields allow to specify types of addresses, and we will remove one field in the future.
-
Robert Schmidt authored
After the last commit, it is not possible to bind on separate interfaces for F1-C and F1-U. In other words, it is for instance not possible to have the F1-C on one subnet on one physical interface, and F1-U on another subnet on another physical interface. This commit introduces a second option MACRLCs.[0].local_n_address_f1u to allow to bind F1-U on an alternative address; if it is not specified, the interface of F1-C is reused. The above only works for the DU; no corresponding option exists for the CU. For the CU, use separate CU-CP and CU-UP. Use it in the CI.
-
Robert Schmidt authored
This reverts commit 28411652. The problem is that (1) we don't really support multi-homing, but (2) on some system, if the other IP addresses that the operating system considers part of the multi-homed connection are HEARTBEAT'ed (e.g., docker), they answer with SCTP ABORT, which breaks the entire connection. In other words, force single-homing by binding. For F1-U uses, another option will be introduced that allows to bind to a separate interface for F1-U (separate from F1-C), if necessary. Closes #727
-
Robert Schmidt authored
-
Guido Casati authored
-