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

mdns storm #616

Open
ineiti opened this issue Oct 1, 2024 · 1 comment
Open

mdns storm #616

ineiti opened this issue Oct 1, 2024 · 1 comment

Comments

@ineiti
Copy link

ineiti commented Oct 1, 2024

I'm using the latest version of the webrtc crate to connect nodes between servers and webclients. Recently I had problems in my home network, and it turned out that my nodes running on my server using webrtc create mdns storms:

08:32:16.365924 fwpr100p0 Out IP fricklebox.fritz.box.mdns > mdns.mcast.net.mdns: 0 A (QM)? 53854a1e-1c02-4df1-932a-c3f8bad7784f.local. (60)
08:32:16.365924 fwpr100p0 Out IP fricklebox.fritz.box.mdns > mdns.mcast.net.mdns: 0 A (QM)? 53854a1e-1c02-4df1-932a-c3f8bad7784f.local. (60)
08:32:16.365926 eno4  Out IP fricklebox.fritz.box.mdns > mdns.mcast.net.mdns: 0 A (QM)? 53854a1e-1c02-4df1-932a-c3f8bad7784f.local. (60)
08:32:16.365928 eno1  Out IP fricklebox.fritz.box.mdns > mdns.mcast.net.mdns: 0 A (QM)? 53854a1e-1c02-4df1-932a-c3f8bad7784f.local. (60)
08:32:16.365928 eno4  Out IP fricklebox.fritz.box.mdns > mdns.mcast.net.mdns: 0 A (QM)? 53854a1e-1c02-4df1-932a-c3f8bad7784f.local. (60)

Lots and lots of them. If I correlated this correctly, it tries to find the mdns of a remote web-client, which will never be in the local network.

Is there something to do to calm down these mdns storms? I tried to look how to configure the mdns part in the documentation, but didn't find how to do that.

The nodes are running in a docker container - might this impact how mdns interacts with the network?

@ineiti
Copy link
Author

ineiti commented Oct 1, 2024

I added the following lines to the setup of the APIBuilder from the /examples directory. I'm not really sure what the consequences of it are with regard to running it on the local network. I guess it still will manage to find the nodes locally.

Also not sure if I should keep the issue open or not. Without turning off the mdns module, I still have the flood of messages.

        // There seems to be some trouble with mdns where it can flood the local network
        // with requests - so turn it off.
        let mut setting_engine = SettingEngine::default();
        setting_engine.set_ice_multicast_dns_mode(MulticastDnsMode::Disabled);

        // Create the API object with the MediaEngine
        let api = APIBuilder::new()
            .with_media_engine(m)
            .with_interceptor_registry(registry)
            .with_setting_engine(setting_engine)
            .build();

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant