-
Notifications
You must be signed in to change notification settings - Fork 1k
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
ActorSelection can have IPV4/IPV6 mapping conflicts on Mono / POSIX #2254
Comments
I suppose it is connected with #2194 |
@kantora yep, I suspect you are correct. What I think is happening under the hood: I think despite explicitly specifying IPV4 in the configuration, Mono sockets are still using IPV6 as the address family are performing a mapping - this is not correct and not what Helios does on Windows when provided with an IPV4 address. I'll be working on getting Linux CI up and running for Helios shortly. Just got it working for NBench a few minutes ago. |
close akkadotnet#2254 close akkadotnet#2195 close akkadotnet#2194 close akkadotnet#1594 close akkadotnet#1110
close akkadotnet#2254 close akkadotnet#2195 close akkadotnet#2194 close akkadotnet#1594 close akkadotnet#1110
close akkadotnet#2254 close akkadotnet#2195 close akkadotnet#2194 close akkadotnet#1594 close akkadotnet#1110
close akkadotnet#2254 close akkadotnet#2195 close akkadotnet#2194 close akkadotnet#1594 close akkadotnet#1110
close akkadotnet#2254 close akkadotnet#2195 close akkadotnet#2194 close akkadotnet#1594 close akkadotnet#1110
http://stackoverflow.com/questions/38917902/akka-net-remote-between-linux-and-windows
Pretty sure this is the issue (repeating my SO answer):
The issue here appears to be that Mono is using an IPV6 address mapped to IPV4 in its bound address for some reason.
If you decode this URL that gets translated to
So I think what is happening here is that outbound address Helios is supposed to parse from that is getting screwed up on the Linux side, so it attempts to connect to a mal-formed address that isn't the same as the one Windows listens on. Something platform-specific in the actor selection URI parsing code is incorrect I suspect.
The text was updated successfully, but these errors were encountered: