Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Hostname resolution fails using zeroconf #99
Using the zeroconf discovery, SyncThread on local host
The parameters for the zeroconf node are default; the zeroconf nodes discover each other perfectly.
Manual hostname resolution fails with:
Manual hostname resolution works with:
I'm not sure, it might be a better idea to use
The output from
While the hostname is correcty set to hostbar.local, the values master_uri and rpcuri in the txt array are propably not.
This might be a problem with the ROS Master API (http://wiki.ros.org/ROS/Master_API).
The discovery node calls
I'm not sure whether this is intended behavior; if it is, the discovery node might have to do a workaround for this.
Thank you very much!
Well, the discovery works fine now, but since the nodes itself do not use the FQDN, I have to set
Since I'm bound to an IPv6-only network, there were still a few things missing:
For better IPv6 compatibility it would be nice if the MasterMonitor was initialized in IPv6 mode
I've got a setung running now with:
Well, it's not that undocumented: http://www.ros.org/news/2012/06/ipv6-support-for-ros-nodes.html