[ros-users] Current best practice for multiple interfaces
Bil Morris
bill at iheartengineering.com
Thu Jan 17 01:01:49 UTC 2013
On 01/16/2013 06:20 PM, Benjamin Johnston wrote:
> I'm just speculating here, and I'm sorry if I've misunderstood the discussion, but my understanding of the ROS XMLRPC interfaces is that this could be a little more complex than just binding to INADDR_ANY...
>
> I don't believe there's anything that would prevent a ROS master itself from binding to any address. However, when nodes register themselves with the master, they need to give a 'return' address so that other nodes can find them. The problem is that pubs or subs from the local machine need to be registered with the master using a public address so that other external nodes can locate it. Even though the master could use INADDR_ANY, whenever the public IP address changes (e.g., new wifi connection), then any topics that have a pub or sub from the local machine would need to be reregistered with the master (or the master would need to "cleverly" adjust any such pubs/subs from the local machine).
One option would be use Dynamic DNS and/or for nodes to offer a hostname
that returns multiple A records, then the node could be located locally
or remotely by trying to connect to a series of ip addresses.
More information about the ros-users
mailing list