Capture E2AP Packets in RIC

[Kazi Samin Mubasshir]

Dear Powder Community,

I am running an ORAN RIC using the ORAN profile and connecting my RAN profile over the E2TERM using shvlan. I am trying to capture the E2AP packets in the RIC following the srsRAN instructions (https://docs.srsran.com/projects/project/en/latest/tutorials/source/near-rt-ric/source/index.html#e2ap-packet-analyzer). However, I cannot see any E2AP packets. Please let me know the recommended way to capture the E2AP packets.

RIC link: https://www.powderwireless.net/status.php?uuid=a7745b5f-aaab-11f0-bc80-e4434b2381fc

RAN link: https://www.powderwireless.net/status.php?uuid=4e55fbe9-aaac-11f0-bc80-e4434b2381fc

Best Regards

Kazi

------------------------

Kazi Samin Mubasshir

[David M Johnson]

On 10/16/25 12:22, Kazi Samin Mubasshir wrote:
> Dear Powder Community,
> I am running an ORAN RIC using the ORAN profile and connecting my RAN
> profile over the E2TERM using shvlan. I am trying to capture the E2AP
> packets in the RIC following the srsRAN instructions (https://
> docs.srsran.com/projects/project/en/latest/tutorials/source/near-rt-ric/

> source/index.html#e2ap-packet-analyzer <https://docs.srsran.com/
> projects/project/en/latest/tutorials/source/near-rt-ric/source/
> index.html#e2ap-packet-analyzer>). However, I cannot see any E2AP

> packets. Please let me know the recommended way to capture the E2AP packets.

Hi Kazi. The issue here is that you are using the `master` branch of
the O-RAN profile, which deploys the POWDER E2-enabled fork of srsLTE --
and the instructions you cite apply only to newer versions of
srsRAN_Project. (srslte-ric does not contain the helpful pcap dump
feature that srsRAN_Project has, that can leave pcap traces for various
subsystems in files.) The O-RAN profile deploys srsRAN_Project only if
you choose the `u24-update` branch. You can capture E2 packets by
tcpdump'ing on the srslte-ric SCTP port, or by deploying a debug k8s
container (with tcpdump) in the same network namespace as the e2term
service, and tcpdump'ing on the e2term SCTP port.

(Aside, it has been on my list for quite some time to merge the
`u24-update` branch to `master`, after first preserving current master
as `legacy`. I will notify here once I've done this, hopefully next week.)

> *RIC link: *https://www.powderwireless.net/status.php?uuid=a7745b5f-
> aaab-11f0-bc80-e4434b2381fc <https://www.powderwireless.net/status.php?
> uuid=a7745b5f-aaab-11f0-bc80-e4434b2381fc>
> *RAN link:* https://www.powderwireless.net/status.php?uuid=4e55fbe9-
> aaac-11f0-bc80-e4434b2381fc <https://www.powderwireless.net/status.php?
> uuid=4e55fbe9-aaac-11f0-bc80-e4434b2381fc>
>
> Best Regards
> Kazi

David