Multiple core using 127.* address can't run

[ghost]

Ros should not handle 127.0.0.0/255.0.0.0 as a unique ip: 127.0.0.1. It makes sence on specific environment to bind on 127.1.2.3 and not on 127.0.0.1 like in openshift gears.

It looks like this might be because adress starting with 127. are converted to 127.0.0.1

[simonlopez]

+1
One bad hack is located here:

ros_comm/tools/rosgraph/src/rosgraph/network.py

Line 253 in d6b62d3

if address and (address == 'localhost' or address.startswith('127.') or address == '::1' ):

[dirk-thomas]

I only found the problematic usage @simonlopez pointed to. That one is addressed in #316.

@Steffel Can you please try that branch and provide feedback if that works for your use case?

[ghost]

I've tried using #316 but but it still using ip 0.0.0.0

roscore -p 8091
netstat -antu | grep -i 8091
tcp        0      0 0.0.0.0:8091            0.0.0.0:*               LISTEN 

[dirk-thomas]

Can you please provide some more information in order to be able to reproduce your steps?

[ghost]

I'm using multiple roscore on Ubuntu 12.04 but i want each roscore to bind different adress using 127 adress (but same port). I'm using hydro version of ros installed using apt-get

[dirk-thomas]

Please provide the exact command sequence you use. Are you setting a different ROS_MASTER_URL / ROS_IP / ROS_HOSTNAME / __ip / __hostname? Have you checked out the 127_addresses branch of ros_comm, build it and used the environment of that?

[ghost]

export ROS_MASTER_URL = 127.2.4.23:10041
roscore -p 10041

I've not tried to use ROS_IP and ROS_HOSTNAME I will try and give my feedback.

[dirk-thomas]

roscore will not use the ROS_MASTER_URL to determine which ip and port to bind to. It will use the ROS_IP / ROS_HOSTNAME if set in the environment and the port number specified via the command line argument -p.

After setting ROS_IP=127.1.2.3 and using ros_comm (which requires a checkout of roscpp_core for Hydro) from the specific branch it worked for me: roscore bound to 127.1.2.3.