You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently when you start a node with goroslib it registers itself and topics it creates under an IP address as seen here:
this is even the case when setting the Host variable within the NodeConf structure.
when using the basic rospy talker listener, we see here that it will use the hostname:
this unfortunately makes it so nodes running on another computer over the network cannot see the rostopics if ROS_IP or ROS_HOSTNAME are set properly on the remote.
i've looked through the code and it does seem like a larger change due to the fact that there is already ipv6 support built in,
i have a branch where i've made it work, but had to remove support for ipv6.
The text was updated successfully, but these errors were encountered:
currently when you start a node with goroslib it registers itself and topics it creates under an IP address as seen here:
this is even the case when setting the Host variable within the NodeConf structure.
when using the basic rospy talker listener, we see here that it will use the hostname:
this unfortunately makes it so nodes running on another computer over the network cannot see the rostopics if
ROS_IP
orROS_HOSTNAME
are set properly on the remote.i've looked through the code and it does seem like a larger change due to the fact that there is already ipv6 support built in,
i have a branch where i've made it work, but had to remove support for ipv6.
The text was updated successfully, but these errors were encountered: