Support for kernel-based forwarder

[BenAgai]

I Hope I post the issue on the correct section.

I'm working on a project involving the usage of network service mesh.
In the project I want to use a kernel-based forwarder instead of the VPP-forwarder.

In the below link I found an example for VPP-forwarder:
https://github.com/networkservicemesh/cmd-forwarder-vpp/blob/main/main.go

I searched for a kernel-based forwarder but found an outdated version in the below link:
https://github.com/networkservicemesh/networkservicemesh/tree/v0.2.0/forwarder/kernel-forwarder

Is there any example or implementation of a kernel-based forwarder that I can use?
If not, do you have recommendations on getting/implementing one?

Thanks,
Ben Agai Meherabanan

[denis-tingaikin]

I super like this direction.

@edwarnicke Can we schedule this for some release?

[frank7y]

Are there any updates on this? I'm just approaching NSM and I guess using classic linux kernel forwarding may ease the learning curve of NSM internals, since I can leave VPP mechanisms aside, and I am more familiar with Linux virtual networking mechanics (veth/namespaces/netlink libs).

I was also looking into the most recent implementation of the NSM kernel forwarder here:
https://github.com/networkservicemesh/networkservicemesh/tree/master/forwarder/kernel-forwarder
but it'd be useful to know if some incompatibilities had been introduced in the meantime between 0.2.0 and 1.5.0 of NSM, making it deprecate, and in that case if there's a particular reason for it being deprecated/abandoned.

Thanks