- Apr 15, 2024
-
-
Robert Schmidt authored
-
- Apr 13, 2024
-
-
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.
-
- Jan 25, 2024
-
-
- improved description of F1 and E1 operation on a local setup
-
- Dec 21, 2023
-
-
Robert Schmidt authored
-
- Nov 30, 2023
-
-
Robert Schmidt authored
-
- Nov 10, 2023
-
-
Robert Schmidt authored
-
- May 03, 2023
-
-
Robert Schmidt authored
-
- Sep 16, 2021
-
-
Thomas Laurent authored
-
- Jul 19, 2021
-
-
Thomas Laurent authored
-
- Jul 14, 2021
-
-
Thomas Laurent authored
-
- Jul 13, 2021
-
-
Thomas Laurent authored
-