# ROS2 Default Behavior (Wifi)

**URL:** https://discourse.openrobotics.org/t/ros2-default-behavior-wifi/13460
**Category:** ROS General
**Tags:** ros2
**Created:** [March 31, 2020, 6:40pm UTC](https://discourse.openrobotics.org/t/ros2-default-behavior-wifi/13460 "2020-03-31T18:40:59Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![gavanderhoorn](https://sea2.discourse-cdn.com/flex022/user_avatar/discourse.openrobotics.org/gavanderhoorn/32/969_2.png) [@gavanderhoorn](https://discourse.openrobotics.org/u/gavanderhoorn)
#### Post date: [March 31, 2020, 7:18pm UTC](https://discourse.openrobotics.org/t/ros2-default-behavior-wifi/13460/2 "2020-03-31T19:18:32Z")

</div>

> [@smac](#):
>
> I venture to assume the industrial manipulator crowd may be less interested in this [..]

Actually, taking this a bit broader and as someone who has gotten the same questions many times, starting in 2012 with ROS 1 (“_This is crap, it doesn’t work, I cannot create a 10 kHz current-control loop distributed over a Windows machine, a Mac and your Linux. Isn’t that what this R-O-S is supposed to do?_”), I support this.

In the end, after explaining sufficiently, all engineers are willing to understand there are limits to technology and that things may not work out-of-the-box immediately.

But it does not look good when you have to get all apologetic about a technology stack. Especially not one which is geared towards use in production environments (ROS 2 == ROS-for-Products).

And, more often than not, there is no one around with sufficient in-depth knowledge to explain _why_ something isn’t working, and how to change it such that it will work. Finding a configuration which can improve the out-of-the-box experience on a set of use-cases which are common would be _tremendously_ valuable.

As in real-life, first impressions count.

If a single configuration isn’t feasible, perhaps a set of profiles could be introduced? “_Switch to the wifi/lossy-network profile if you’re not using a cabled network_”.

But that’s all assuming wifi actually needs special configuration, and it 's not something else which is affecting user experiences here.

> [@smac](#):
>
> Much of the limited documentation you find on this topic blames the router (which doesn’t induce confidence)

Are you referring to [ros2/rmw\_fastrtps#315](https://github.com/ros2/rmw_fastrtps/issues/315) among others? That wasn’t specifically blamed on the router I believe. It was more a combination of factors (but the router was among those). I believe the FastRTPS documentation was extended with some more info on use over wifi as a result of diagnosing those issues: [Typical Use-Cases: Fast-RTPS over WIFI](https://fast-rtps.docs.eprosima.com/en/latest/use-cases.html#fast-rtps-over-wifi). I could imagine other vendors have similar documentation.

---

_[View the full topic](https://discourse.openrobotics.org/t/ros2-default-behavior-wifi/13460)._