-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lang/Mono - Error on every app depending on Mono (DNS) #200
Comments
patches accepted if you find one that solves the issue. |
I managed to build mono 5.10.0.160, and after some fireworks :) i realized the final result is the same... Feel free to close this issue. |
meaning you didn't attempt to "make patch" and search to code? solution might have been obvious if you're looking in the right file. |
oh well, i don't like to give up easily so... let's grep some code. |
I made some progress... So it appears to me (i don't remember much of c#) that mono "thinks" there's no socket support for ipv4 and ipv6.
Now, running this system reports:
And the DNS Lookup fails:
If i uncoment the part of the code i set those variables to True, compile and run, magic happens :)
Now, i've no ideia how mono sets this variables to start... i've already looked at make configure output but haven't found anything. I'm going to open an issue on Mono github in the hope they can point me in the right direction. |
Do your machine support IPv6? |
Yes, i think it supports IPv6. According to Mono devs:
So, i need to figure out why mono is initialized with both Socket.SupportsIPvx and Socket.OSSupportsIPvx to false. |
There's no way IPv6 should work when using value of 23. |
the question is whether it's IPv4 is failing everywhere or just your machine. As far as I can tell, it should work. |
That's a good question :) One i also would like to know the answer. |
I just checked and it seems it's still the case:
|
- Since we're already using 'USES= alias', an additional patch to identify us as FreeBSD internally in mono helped solving DragonFlyBSD/DPorts#200
- Since we're already using 'USES= alias', an additional patch to identify us as FreeBSD internally in mono helped solving DragonFlyBSD/DPorts#200
With commit, at least IPv4 is fixed: DragonFlyBSD/DeltaPorts@531ba20
That's good enough for us for now, we don't have a lot of time. If anybody can investigate the IPv6, please open a new issue. Thanks! |
Every app i tried which depends on Mono (emby, sonarr, radarr, ...) i get the error bellow. Because of that apps are unable to do name resolution and consequent "internet" requests fail.
I've tried building Mono from Dport source and i've made it, but needed to deal with some errors. Anyways the result is the same.
`18-4-5 02:01:13.3|Debug|Api|[PUT] /api/config/host: 202.Accepted (88 ms)
18-4-5 02:01:13.3|Error|TaskExtensions|Task Error
[v2.0.0.5153] System.Net.WebException: DNS Name Resolution Failure: 'services.sonarr.tv'
at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieCon
tainer cookies) [0x0015e] in <7e93f23c2fc54b74802f7126f4e364f7>:0
at NzbDrone.Common.Http.Dispatchers.FallbackHttpDispatcher.GetResponse (NzbDrone.Common.Http.HttpRequest request, System.Net.CookieCo
ntainer cookies) [0x000b5] in <7e93f23c2fc54b74802f7126f4e364f7>:0
at NzbDrone.Common.Http.HttpClient.ExecuteRequest (NzbDrone.Common.Http.HttpRequest request) [0x0007e] in <7e93f23c2fc54b74802f7126f4
e364f7>:0
at NzbDrone.Common.Http.HttpClient.Execute (NzbDrone.Common.Http.HttpRequest request) [0x00000] in <7e93f23c2fc54b74802f7126f4e364f7>
:0
at NzbDrone.Common.Http.HttpClient.Get (NzbDrone.Common.Http.HttpRequest request) [0x00007] in <7e93f23c2fc54b74802f7126f4e364f7>:0
at NzbDrone.Common.Http.HttpClient.Get[T] (NzbDrone.Common.Http.HttpRequest request) [0x00000] in <7e93f23c2fc54b74802f7126f4e364f7>:
0`
I'm also trying to build the last stable version from Mono, but until now i was unable to do it.
On Freebsd the current version of Mono is working with the apps referred above.
The text was updated successfully, but these errors were encountered: