pavel_odintsov

It was more about way to fix some very broken tool. ssh was just an example. It may be proprietary app without source code available.

Thank you very much for approving my idea!

In home network single $70 USD device with 2 daemons running may be clearly too much but for corporate or even office network it's just one more box in addition to dozens of network devices.

Author is here.

Thank you for sharing! Yes, macOS has such logic and it works just fine. The main issue from clatd that it's pretty tricky to setup and it emulates presence of IPv4 on machine which is not very desirable as it tends to hide issues with other tools.

My plan was to explicitly disable IPv4 connectivity for machine and hide it from other app but keep it active for subset of well known broken tools and then fix them one by one and switch to IPv6 only setup.

eBPF requires way more tooling which I find excessive for such easy task.

More complicated load balancing protocols may need more complicated balancing microcode and eBPF will be helpful in this case.

One of the main differences between BPF and eBPF is number of allowed instructions and it's very big for eBPF.

I think you can do XDP based DHCP server in theory and keep state in eBPF map. Not sure that it does make any sense but clearly doable.

Thank you for your great feedback