The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Hi,
I completely understand the original post. It's counterintuitive for ROS to publish to its loopback interface despite the routing tables correct determination of the network. I can recreate the error in my lab on Ubuntu 20.04.4 LTS running noetic.
The idea here would be that a self contained autonomous ROS implementation publish a topic over a network where a second self contained ROS implementation would subscribe to it.
The original post's idea of disabling the Loopback would have been to force it to publish over another (useful) interface. It seems perfectly logical, what am I missing?
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.
