BOINC may not be working fully with IPv6 addresses


Advanced search

Questions and Answers : Windows : BOINC may not be working fully with IPv6 addresses
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile CElliott
Volunteer tester

Send message
Joined: 19 Jul 99
Posts: 178
Credit: 79,285,961
RAC: 0
United States
Message 1572656 - Posted: 16 Sep 2014, 13:45:10 UTC

Just in case, I put my link-local IPv6 address in remote_hosts.cfg. However, Boinc complains: "Can't resolve hostname in remote_hosts.cfg: fe80::852a:756b:462d:e79c". So I tried that address with boinccmd with the following command: boinccmd --host fe80:0:0:0:852a:756b:462d:e79c --get_host_info. The response was "can't connect to fe80". Boinccmd will work with 127.0.0.1 address, and both ping and tracert respond correctly using ip address fe80:0:0:0:852a:756b:462d:e79c. Note fe80::852a:756b:462d:e79c = fe80:0:0:0:852a:756b:462d:e79c, and both work with ping and tracert, but not with boinccmd.
ID: 1572656 · Report as offensive
Profile Jord
Volunteer tester
Avatar

Send message
Joined: 9 Jun 99
Posts: 15184
Credit: 4,362,181
RAC: 3
Netherlands
Message 1572660 - Posted: 16 Sep 2014, 13:56:47 UTC - in response to Message 1572656.  

Forwarded to BOINC development.
ID: 1572660 · Report as offensive
Profile David Anderson
Volunteer moderator
Project administrator
Project developer
Project scientist
Avatar

Send message
Joined: 13 Feb 99
Posts: 173
Credit: 502,653
RAC: 0
Message 1572756 - Posted: 16 Sep 2014, 19:34:03 UTC

I changed boinccmd so that it will work with IPv6 addresses. This doesn't address the original problem, but it may help you investigate it.
-- David
ID: 1572756 · Report as offensive

Questions and Answers : Windows : BOINC may not be working fully with IPv6 addresses


 
©2024 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.