omec-project/upf

UPF does not reply GTP-U Echo Request

lulloaX opened this issue · 3 comments

lulloaX commented

Describe the bug
UPF is not able to reply GTP-U Echo Request message sent by eNodeB. We already verified that GTP Echo Request message is process by BESS pipeline but it is discard on pdrLookup Block and sent to pdrLookupFail.
In past UPF version 0.3.20 we verified it worked but currently on version 0.5.1 is where we find this issue.

To Reproduce
Current setup include deployed UPF using omec-user-plane-0.5.1 version and access network (RAN) is emulated by Spirent Tool. We already verify that Core and RAN have properly connectivity.

Expected behavior
UPF/BESS pipeline should process GTP-U Echo request message and reply with a GTP-U Echo response message to eNodeB.
For this GTP-U Echo procedure, What is the correct path that package should follow on UPF/BESS pipeline?.
We have verified that the path that Echo Request message is following is:

  1. accessQ0FastPI
  2. accessFastBPF
  3. accessRxIPCksum
  4. accessRxUDPCksum
  5. pktParse
  6. pdrLookup
  7. pdrLookupFail

But after accessFastBPF block we see a gtpuEcho block on pipeline GUI.

image

Additional context

c.c. @krsna1729

krsna1729 commented

@pudelkoM can you translate those version numbers?

  • 👀1
lulloaX commented

@krsna1729 @pudelkoM if is useful, as I mentioned I used omec-user-plane-0.5.1 ONF helm chart to deploy UPF and this helm chart use the follow images tags:

  • bess: `registry.aetherproject.org/proxy/omecproject/upf-epc-bess:master-9a3fc9a`

  • pfcpiface: `registry.aetherproject.org/proxy/omecproject/upf-epc-pfcpiface:master-9a3fc9a`

  • tools: `registry.aetherproject.org/tools/busybox:stable`
lulloaX commented

@krsna1729 as we talked, attache the bess/upf gui consider total packets
UPF_BESS_pipeline_total_packet.zip