Replies: 1 comment
-
i didn't look at this too much but perhaps the any interface is causing issues w/ReceiveMessageFromAsync re-writing your recvfrom using BeginReceiveFrom (taken from https://gist.github.com/darkguy2008/413a6fea3a5b4e67e5e0d96f750088a9) gives me an address:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Intro
While trying to test/package https://github.com/TechnitiumSoftware/DnsServer encountered some issues in some places.
https://github.com/TechnitiumSoftware/DnsServer/blob/3a7636ac3b1c221521f4031bb185277bbc85f068/DnsServerCore/Dns/DnsServer.cs#L429 - being one of them causing
upon investigation it turned out that on Nanos - https://learn.microsoft.com/en-us/dotnet/api/system.net.sockets.ippacketinformation?view=net-8.0 looks like is not available.
Program.cs
- code to reproduce the "issue":.Net build instructions
dotnet --version 8.0.408
ops nanos
config_dnstest.json
ops run
test it
dig example.com @127.0.0.1
- you will getNo valid PacketInformation.Address available.
on ops logsWhile on linux, from the same binary, you get the proper receiver interface address.
Beta Was this translation helpful? Give feedback.
All reactions