Steve
Steve
> Are you experiencing a specific error with NativeAOT, or is this just an optimization? I encountered unresolved symbols error from the linker (because some Windows-specific P/Invoke doesn't get trimmed...
> In Ubuntu the so name is `libpcap.so.0.8` instead of `libpcap.so`, depending on what apt package you install. I think the package manager will create a symbolic link `libpcap.so` which...
> What symbols did you get an error for? The error message pointed to `pcap_open`, `pcap_setbuff` and `pcap_setmintocopy` explicitly.
You can try to build https://github.com/hez2010/SysuSurf using `dotnet publish -c Release -r linux-x64 /p:PublishAot=true`, or `dotnet publish -c Release -r linux-musl-x64 /p:PublishAot=true` with **.NET 8 preview 1** to verify whether...
Will try to figure out a way to use wpcap on Windows and pcap on Linux to fix the ci.
> the idea itself is ok, but the pr breaks CI, especially remote pcap. Is RPCAP a Windows-only feature?
> Any reason you have to use `` ? if removed, the code should still work without any changes to sharppcap. Only with `DirectPInvoke` can we statically linked the library...
After passing `--enable-remote --disable-universal` to `./configure`, I'm able to build it with `pcap_open` without issue now, so I revert the change to `pcap_open`.
Not sure why CI is still failing, seems like some unrelated timeout issue?
> Why do you want to statically link it in the first place? I want to run it on my router, which is hard to have all dependencies installed. So...