Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
# Steps to reproduce
Try to add a build host using it's IPv6 address (I am using 2001:470:e8e1::1:67bc)
# Expected behavior
Build host connects and functions
# Actual behavior
Build host connects fine, prompting for a user name and password. However, a strange IPv4-style address (0.0.7.209 for my example) is listed in brackets. Starting a debug session actually works fine! Unfortunately trying to actually build the project generates dozens of messages like this:
a socket operation was attempted to an unreachable network 0.0.7.209:22
# Supplemental info (logs, images, videos)
I'm trying to do development remotely using a DirectAccess connection, which is an IPv6 technology.
# Test environment (full version information)
Windows 10 Enterprise 64-bit, Visual Studio 2015, Xamarin 188.8.131.529, OSX 10.11.1, XCode 7.1.1
Just for a tiny bit of cross-referencing, a corresponding forum thread is here:
From the "still doesn't work" in the title of the forum thread I believe this is technically an enhancement request to add support for IPv6 addresses (since it sounds like the old build host didn't support them either). So if necessary for bookkeeping, I think it would be technically accurate to change the severity to "enhancement."
As per comment#1 and comment#2, changing the status to CONFIRMED for enhancement