Skip to content
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

net: multicast test fails when missing multicast route #1649

Closed
gopherbot opened this issue Mar 29, 2011 · 5 comments
Closed

net: multicast test fails when missing multicast route #1649

gopherbot opened this issue Mar 29, 2011 · 5 comments

Comments

@gopherbot
Copy link

by jtunney:

When building Go I noticed that TestMulticastJoinAndLeave
(src/pkg/net/multicast_test.go) failed with:

--- FAIL: net.TestMulticastJoinAndLeave (0.00 seconds)
    leavegroup udp 224.0.0.254: setsockopt: cannot assign requested address

I discovered this was because my system does not have a default multicast route (maybe
an Ubuntu quirk?)  The solution was to run the command:

sudo ip route add 224.0.0.0/3 dev eth0

I hope this information helps and that this potential hold-up in the build system
doesn't prevent others from being able to use Go.
@rsc
Copy link
Contributor

rsc commented Mar 29, 2011

Comment 1:

We should probably disable the multicast tests by default,
like we do with the ipv6 tests.

@davecheney
Copy link
Contributor

Comment 2:

Agreed, too many systems are misconfigured. 
FWIW, to the best of my understanding, every system has a multicast route if it has a
default route.

@rsc
Copy link
Contributor

rsc commented Apr 5, 2011

Comment 3:

Feel free to send a CL.

@davecheney
Copy link
Contributor

Comment 4:

Sure thing, http://golang.org/cl/4343056

@adg
Copy link
Contributor

adg commented Apr 11, 2011

Comment 5:

This issue was closed by revision 8b8b54a.

Status changed to Fixed.

@mikioh mikioh changed the title multicast test fails when missing multicast route net: multicast test fails when missing multicast route Jan 23, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants