Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

IPv6 support?
MatthewSteeples
#1 Posted : Friday, July 17, 2020 6:06:21 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 130
Location: United Kingdom

Thanks: 7 times
Was thanked: 18 time(s) in 16 post(s)
We're looking at disabling IPv4 on our VPN tunnels, but NCrunch doesn't appear to want to connect over IPv6. Looking at Resource Monitor the Grid Nodes appear to be listening on v6 addresses, but the client in Visual Studio won't accept IPv6 addresses in the config, or resolve them if the DNS entries only have DNS records. Are there plans to fix this?
Remco
#2 Posted : Saturday, July 18, 2020 12:07:23 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 930 times
Was thanked: 1257 time(s) in 1170 post(s)
Hi, thanks for sharing this issue.

The network code in place was originally built on components that do support IPv6, although it's been a long time since we tested it. It wouldn't surprise me if there is a hole in our compatibility somewhere. I'm marked this for investigation.

Do you have the option to work around this issue using a hostname or DNS alias?
MatthewSteeples
#3 Posted : Monday, July 20, 2020 3:02:51 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 130
Location: United Kingdom

Thanks: 7 times
Was thanked: 18 time(s) in 16 post(s)
For now we're OK to continue with IPv4, but I wanted to bring it to your attention. The main reason we noticed it is that we run a split-tunnel VPN, with DNS queries carried out by the user's ISP. In this instance our user's ISP (in what I assume is an effort to increase security) doesn't resolve addresses to private IP addresses, so we either need to update their host file, hardocde IPv4 addresses or use IPv6. We've gone with the 1st option for now.
Remco
#4 Posted : Monday, July 20, 2020 11:56:56 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 930 times
Was thanked: 1257 time(s) in 1170 post(s)
Thanks, we'll check it out.
MatthewSteeples
#5 Posted : Tuesday, March 5, 2024 1:30:28 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 130
Location: United Kingdom

Thanks: 7 times
Was thanked: 18 time(s) in 16 post(s)
This issue has changed slightly with the release of v5. DNS entries resolve, but VS fails to connect to the Gridnode's IPv6 address with the following error:

Code:
Connection Failure: None of the discovered or specified addresses match the socket address family.
Parameter name: context
Remco
#6 Posted : Tuesday, March 5, 2024 3:09:38 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 930 times
Was thanked: 1257 time(s) in 1170 post(s)
Thanks for reporting this. We've had IPv6 for a while, and none of this code has changed for several years. Is there any chance of the connection being blocked on your network? The blocking actions of firewalls and routers can sometimes kick in unexpectedly.
MatthewSteeples
#7 Posted : Tuesday, March 5, 2024 1:24:15 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 10/28/2014(UTC)
Posts: 130
Location: United Kingdom

Thanks: 7 times
Was thanked: 18 time(s) in 16 post(s)
Not as far as I can tell. I can connect to the same device over IPv4, and I can RDP into it over IPv6. Looking at TCPView (from Sysinternals) it doesn't look like a v6 connection is even being attempted, which ties in with the error being shown. I've restarted Windows and checked there's no rules in the firewall for it (only use the built in Windows one).

Separately, although possibly related, it's not possible to specify an IPv6 address in the server box, only DNS entries that resolve to v6 addresses
Remco
#8 Posted : Wednesday, March 6, 2024 12:45:17 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,976

Thanks: 930 times
Was thanked: 1257 time(s) in 1170 post(s)
MatthewSteeples;17077 wrote:

Separately, although possibly related, it's not possible to specify an IPv6 address in the server box, only DNS entries that resolve to v6 addresses


Thanks, we'll check it out.
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.042 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download