-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
mdns example panics on Windows in release mode, but not in debug mode #14
Comments
Hello there. This is an interesting issue. I also have the same setup on my
development machine, including the ZeroTier One adapter and WSL vEthernet.
Indeed, running on release mode panics the sample example. I'm curious if
this is an issue on the sample or an optimization triggering a bug in the
library.
I currently don't have much time on my hands to troubleshoot this, but I
can test any patches on my dev environment to validate changes.
Sorry for not having time to help at this moment.
Kind regards,
Em qui., 5 de mai. de 2022 às 20:07, Dudemanjude ***@***.***>
escreveu:
… First of all, thanks for making such a nice crate. After looking at the
source code, I realize what I would be getting into had I needed to
implement multicast on all interfaces myself for both Windows and Linux.
😄
But I am having a bit of a problem. Just like the title says, I can run
the mdns example in debug mode, and it works perfectly fine, but it panics
in release mode with this error:
thread 'main' panicked at 'could not broadcast message to ips being listened: Os { code: 10022, kind
: InvalidInput, message: "An invalid argument was supplied." }', examples\mdns.rs:25:10
I'm also running into this issue in my own project using this crate. It
can send out a multicast (checked with Wireshark) in debug mode, but in
release, it panics with the same error.
I have multiple different network adapters, WSL's vEthernet, VirtualBox's
Host-Only Network, my WiFi adapter, Ethernet (that I'm not using), and
ZeroTier One. I ended up on your crate due to my multicasts ending up on
WSL's interface, rather than my WiFi adapter's.
If I can provide any more system information, or do some more testing, I'd
be happy to help.
—
Reply to this email directly, view it on GitHub
<#14>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA2XIVVPTFPGKQELLPYVVTVIRIDVANCNFSM5VGQC3LA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Out of curiosity, and since |
mon
added a commit
to mon/multicast-socket
that referenced
this issue
Nov 28, 2023
control_buffer was going out of scope Closes bltavares#14
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
First of all, thanks for making such a nice crate. After looking at the source code, I realize what I would be getting into had I needed to implement multicast on all interfaces myself for both Windows and Linux. 😄
But I am having a bit of a problem. Just like the title says, I can run the mdns example in debug mode, and it works perfectly fine, but it panics in release mode with this error:
I'm also running into this issue in my own project using this crate. It can send out a multicast (checked with Wireshark) in debug mode, but in release, it panics with the same error.
I have multiple different network adapters, WSL's vEthernet, VirtualBox's Host-Only Network, my WiFi adapter, Ethernet (that I'm not using), and ZeroTier One. I ended up on your crate due to my multicasts ending up on WSL's interface, rather than my WiFi adapter's.
If I can provide any more system information, or do some more testing, I'd be happy to help.
The text was updated successfully, but these errors were encountered: