T: macpdu2wireshark: dump to file instead of sending UDP packets
In NR with several layers, we may have MAC PDU of size bigger than 64KB, which does not fit into a UDP buffer, destroying macpdu2wireshark. Let's add an option to dump to a pcap file instead of using UDP packets. The DLT 252 magic is used (check wireshark documentation to understand). Run macpdu2wireshark with -h to see how to configure wireshark to read the produced files.
This commit is contained in:
@@ -3,7 +3,8 @@
|
||||
First, read the [basic usage](./basic.md) to compile things.
|
||||
|
||||
It is possible to use `wireshark` to analyse MAC PDUs for UEs,
|
||||
MIBs, SIBs, and random accesses seen by the eNodeB.
|
||||
MIBs, SIBs, and random accesses seen by the eNodeB. It also
|
||||
works for the gNB, as well as for the nrUE.
|
||||
|
||||
## Live usage
|
||||
|
||||
@@ -20,6 +21,14 @@ Then run:
|
||||
./macpdu2wireshark -d ../T_messages.txt -live
|
||||
```
|
||||
|
||||
Note: in some cases a MAC PDU may be bigger than the size of an UDP payload
|
||||
(slightly less than 64 KiB). This is particularily the case for large
|
||||
bandwidths in NR and MIMO. In this case macpdu2wireshark, sending UDP packets
|
||||
in its default mode of operations, will fail. By using the option `-to-file`
|
||||
a pcap file may be directly generated. You need to configure wireshark to
|
||||
process the generated files (run `macpdu2wireshark -h` to see how to
|
||||
configure wireshark for this case).
|
||||
|
||||
For other options of `macpdu2wireshark`, run:
|
||||
|
||||
```shell
|
||||
|
||||
Reference in New Issue
Block a user