# Unconfigured DDS considered harmful to Networks

**URL:** <https://discourse.openrobotics.org/t/unconfigured-dds-considered-harmful-to-networks/25689>\
**Category:** ROS General\
**Tags:** ros2, dds, cyclonedds\
**Created:** [May 20, 2022, 7:14pm UTC](https://discourse.openrobotics.org/t/unconfigured-dds-considered-harmful-to-networks/25689 "2022-05-20T19:14:16Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![tylerweaver](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/tylerweaver/32/15495_2.png) [@tylerweaver](https://discourse.openrobotics.org/u/tylerweaver)\
**Post date:** [May 21, 2022, 4:24pm UTC](https://discourse.openrobotics.org/t/unconfigured-dds-considered-harmful-to-networks/25689/15 "2022-05-21T16:24:43Z")

</div>

Destructive was a bit of hyperbole. The network hardware does resume working after finding which machine is originating all the multicast traffic and unplugging it. Our current best theory why we are suffering from this is that unmanaged switches or something about our wifi networks might amplify the multicast traffic. None of us know enough about networking to have a clear answer to why this is happening. I only posted this because I figured our bad experience was probably not unique. We’ll continue to try to understand this because while in most cases we are not building multi-machine systems with ROS 2, it is something we do sometimes and it would be good if we could enable that feature without making our networks unusable.

---

_[View the full topic](https://discourse.openrobotics.org/t/unconfigured-dds-considered-harmful-to-networks/25689)._