| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
I asked this question on the ros discourses, but wanted to put it here as well.
https://discourse.ros.org/t/explicitl...
In raw dds, specifically for coredx, there is a way to give an interfaces list to the domain participant so that it will only talk on those network interfaces. Is there a way to use that through ros2?
The ROS 2 API doesn't contain a way to constrain the network interfaces at the moment. You might want to check the specific RMW implementation you want to use and use the vendor-specific configuration to do that (if available).
Thanks. Is there a specific way you would recommend for the rmw implementation to expose this type of thing?
In all cases, you'd probably have to use XML files to configure the underlying implementation or else modify our code.
For FastRTPS (our default implementation right now), you might be able to start here: https://eprosima-fast-rtps.readthedoc...
For Connext, see: https://community.rti.com/kb/how-do-i...
Has there been a support to this in the recent versions of ROS2? Something like Whitelist interfaces by eProsima? https://eprosima-fast-rtps.readthedoc...
This is already supported in ROS 2 using Fast DDS interface whitelisting https://fast-dds.docs.eprosima.com/en.... You can also check here how to configure ROS 2 with Fast DDS XML files https://fast-dds.docs.eprosima.com/en...
Asked: 2018-08-07 14:21:18 -0500
Seen: 1,793 times
Last updated: Aug 07 '18
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
