Flole
Flole
@chkuendig I haven't had time to play with this again, however the source should never be a multicast address, so this is probably the destination that ends up in there?...
It should not be getting the local IP but the remote IP though when a packet is received.... Let me first fix the issues that prevent this from compiling.....
Okay this should be working, but I likely introduced some security issues. I will have to look at it again and fix those.
We should allow longer lines, the current settings add many line breaks, also in the existing codebase
The failing builds are due to the include re-ordering. I'll need to read on how to do it properly so that clang-format doesn't break everything.
IIRC I saw these (or similar) issues when initially setting up GH actions, so I went with the older version. It needs to be addressed at some point though.
If it's the `name` field, then yes, we have a huge deb and a not so huge rpm zip artifact. That should probably be improved/changed.
> IIRC I saw these (or similar) issues when initially setting up GH actions, so I went with the older version. It needs to be addressed at some point though....
I'd guess all that's needed is adding a variable to the name for the architecture. Just a guess though and the docs should clear that up. No need to rush...
You'll probably need to add the architecture to it somehow, otherwise i386 and x64 are conflicting again.