Mutexes were not being initialized. In multiple
places they were not being unlocked. In fill rach
it was not being locked or unlocked.

Same logic as previous commit, same caveats.

There was a problem with several UEs in the wireshark log. It seems that
wireshark needs the UE id otherwise it gets confused and sees retransmissions
where it's just another UE connecting and doing the same as a previous
UE.

Let's put kind of a UE id. Each RNTI seen by macpdu2wireshark gets an UE id
assigned the first time it's seen in a trace.

This is a bit hackish but seems to be fine.

We could have added UE_id in all the traces, that is change the T() calls
in the softmodem. It was less work to do it as it is, ie. only touch
macpdu2wireshark.c.

The RAR uses the same UE id all the time, may be a problem. To be refined
if needed.

You need a recent version of wireshark for this to work properly.
Successfully tested with 3.3.2.

Deokseong Kim authored 4 years ago and Michael Cook committed 4 years ago

Adding ue id parameter to pdcp_init
Updating tun interface functions for proxy

The clean up includes removing white space changes, adding logs,
adding comments to make various changes more obvious, etc.

Melissa authored 4 years ago and Michael Cook committed 4 years ago

Fixed multiple UE EPC integration by resetting user->ueid=0;. Lots of logs in this commit, will remove later

(cherry picked from commit 04c5431468c9102dd625a73d9e5219b40b638fe3)
(cherry picked from commit 17880778c848406e562f98c20f7b7a6428502279)
(cherry picked from commit a26f44c197e854dd4261267a3695932392f09265)

And CPU affinity.
Also, use mlockall to keep our memory from being swapped out.

Add rrc_gNB_send_NGAP_PDUSESSION_SETUP_RESP
Fix some problems about pdu session setup

The T tracer macpdu2wireshark has been modified to handle the new traces.
The usage is the same as for LTE.

In NR the RACH is logged as an LTE RACH. Maybe we'll change that in the
future. Looking at the source code of wireshark, I could not find any
way to report NR RACH. Maybe they forgot it. Or I did not search correctly...

This change is to enable use of gprof which requires the process
call `exit` to write out the collected data.

The UE (lte-uesoftmodem) exits cleanly, but the eNB
(lte-softmodem) crashes as it tries to shut down...

Found by valgrind.

Add UEContextReleaseCommand Message
Modify NGSetup Message Encode failed

    also correction for Circular Dependency Protection on header files
    also correction on the banner check

Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>

Add UEContextReleaseCommand Message
Modify NGSetup Message Encode failed