-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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: cannot send multicast using ListenPacket("udp4", "") on Windows 10 (1909) #37998
Comments
Added screenshot. On today morning, same code fails. |
@filimonic sorry I am not network person, so I do not know why your program does not work reliably. I also don't have Wireshark program installed on my computer, so I cannot even try to reproduce your problem. But I noticed there are some tests in net package (in
All tests in net are obviously succeed on everyone's Windows computers. Maybe you can use net test code and adjust it to make it do what you need? Alex |
@alexbrainman The listed tests are skipped for Windows because the function used @filimonic There are several posts about conflicts between RDP and UDP on 1909. It might be the cause of what is identified. |
Here are the relevant tests for UDP on Windows. All successful on 1909.
|
Fair enough. Thank you for explaining. Alex |
I had the same problem, has the problem been solved? |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes, with 1.14 and 1.14.1 ( never tested earlier )
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Single file in directory: mctest_test.go :
udp port 1982
.What did you expect to see?
Expected 2 packets with source = "ip-of-my-ethernet", target "mulicast address", one using Ethernet interface and one using loopback interface
What did you see instead?
Sometimes everything is right ( I see everything as expected ). And sometimes I see
1 packet with source = "127.0.0.1", target "mulicast address", using loopback interface.
I can not determine, what happens with my envinronment to "switch" this behaviour. After system reboot I can see it working and some time after it stops, ot vice-versa.
SCREENSHOTS
Wireshark setup
Wireshark shows OK
Wireshark shows NOT OK
Sorry I have no screenshot now. It happens periodically each few days. I try add later

Update: Added Screenshot
The text was updated successfully, but these errors were encountered: