Restricting communication between robots

Yes, both are desirable. But I would believe intentional inter robot communication comes after safe single robot communication in a shared network.

Even developer machine isolation, how do companies with multiple developers on ROS2 work? OSRF uses DOMAIN_ID as far as I know, is it a standard practice for other companies?

The fact that someone doing their first ROS2 tutorials could be affecting someone else’s simulation or physical robot is a radical and potentially dangerous change from ROS1.

Just yesterday I was going crazy seeing nodes alive after I had killed them while working from home. After some head scratching I found out I was seeing some colleague’s nodes on their home pc through the shared company VPN.

@christian and @tomoyafujita have provided excellent ideas, as well as @spiderkeys here.

Maybe a first step would be to gather all of them somewhere with examples and detailing their limitations and costs, as well as add documentation that makes this behavior clear, or we provide some default settings that disable it (I’m testing export ROS_LOCALHOST_ONLY=1 now).

5 Likes