Why does ROS need a Hostname?
Currently I have two computers, one running a service 'TIME_SPAM' which endlessly sends UNIX timestamps to any subscribers. On a client PC, using the command 'ROS_MASTER_URI="hxxp://10.230.82.244:11311/" rostopic echo TIMEPAM' (Note: Changed from a http link as my karma is insufficient to post links) only works if I have added a hostname entry which resolves to that PC in /etc/hosts (currently it's '10.230.82.244 linaro-ubuntu-desktop'), if I comment the line out, the command no longer works, despite the fact that I'm passing it a direct IP address.
There are many obvious advantages to using Hostnames for lookups, but this becomes problematic if you do not own or control the network and are unable to setup static IP's and/or a DNS server..
Is there a reason for this, if not, where do I submit a bug report/feature request?
EDIT: The more I think about this problem, the more I consider it to be a bug - Consider this scenario:
I have a server with the IP 10.1.1.1 and the hostname 'server', on the server I execute this script: http://paste2.org/p/2599990.
On a client, if I attempt to execute the command 'ROS_MASTER_URI="http://10.1.1.1:11311/" rostopic echo TIMESPAM' it connects to the server, but does not display any data (this is different from an invalid host address, as it complains with 'could not connect to host').
Then, on the client, if I add an entry into /etc/hosts such that the hostname 'server' is bound to 10.1.1.1, a fresh execution of the command 'ROS_MASTER_URI="http://10.1.1.1:11311/" rostopic echo TIMESPAM' will immediately work correctly.
This appears to be an issue with the client needing to know the hostname of the server, despite the fact I'm passing the IP address as the URI - and the behavior of the issue may lead somebody to assume that the problem is elsewhere in the system.