eBPF on OpenWrt - Introduction to loxilb

Hello OpenWRT community,

We would like to introduce loxilb which can potentially benefit OpenWRT and vice-versa.

LoxiLB is an open-source service load-balancer for cloud-native workloads written from scratch using eBPF as its core-engine and based on Go Language. It is primarily designed to support on-premise and edge deployments.

LoxiLB is fully stateful in nature and provides full-stack kernel bypass networking. Its purpose-built eBPF engine gives it various advantages such as exceptional performance, scalability and the flexibility to support services ranging from simple (tcp/udp/http) to exotic ones (5g-gtp/sctp, nat66, nat64 etc). There are also tons of visibility and configuration options built-in.

Repo : https://github.com/loxilb-io/loxilb

If anyone is interested to integrate loxilb or help loxilb-dev team integrate loxilb based ebpf for OpenWRT use-cases, feel free to chime in or visit our github.

Loxilb Project


thanks for all i will check that

i'm very interested by the qos

Interesting to see LBO feature. Will try it out!

Sounds very interesting but isn't Go a no-go (pun intended) on space constrained devices OpenWrt mainly runs on?

Usually golang runtime takes 500MB which is not really an expensive space. Besides, there are few benefits which comes along with golang like memory protection, faster development cycle. IMO, these so called tradeoffs are worth exploring. And, I am also a C programmer advocating golang! :slight_smile:

Sure, but a typical OpenWrt device will have from 8 MiB to 256 MiB flash, so...

For most router type devices (embedded), about as out of place as mammary glands on a male bovine; but if you are on a x86....

Agreed but memory can be expanded. There are users who are exploring some new applications like MQTT after upgrading SD.

so, i have to ask, how do you envision this working with / for openwrt, explain the benefit if you mind?