Open linouxis9 opened 7 months ago
Hi @yoursunny;
Thank you for your suggestion!
For 1., point taken, thanks for the suggestion. In that case, automatic routes creation should probably also be disabled when VRF are disabled. Else, funny things may happen on the host :-)
For 2., the use case we were thinking was k8s with Multus attaching multiple host interfaces (or creating multiple MacVLAN interfaces) and attaching it to the PacketRusher's pod. But I agree that having to use several contiguous IPv4 addresses is not the best in any cases. The switch to eUPF's eBPF from gtp5g as the WIP PR available here https://github.com/HewlettPackard/PacketRusher/pull/47 should alleviate some of these issues but it's still WIP, and work only with a single UE for now. For PacketRusher on plain old Docker, I would recommend the usage of --net host, the usage of Docker's virtual interfaces may impact negatively the user plane performance of PacketRusher.
Thanks, Valentin
I tried PacketRusher with a Dockerfile like this:
It works with a mounted configuration file, but there are several complications:
--cap-add=NET_ADMIN --device /dev/net/tun:/dev/net/tun
. Applications who want to interact with the PDU session would need to explicitly bind to the netif that represents the PDU session.--dedicatedGnbs
flag expects the container to have several contiguous IPv4 addresses range. This may not be supported by Docker. I don't know of a clean solution to this.