The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
I would just like to know: What is this UDP port for?
Afaik each ROS node will also open a UDP port to facilitate subscribers that would like to exchange messages over UDPROS. Subscribers can negotiate that by adding the unreliable hint to their TransportHints.
I would like to ignore it, because I can't (for many reasons) route UDP through the firewall.
As long as your subscribers do not request subscriptions over the unreliable transport (ie: use UDPROS), firewalling those UDP ports should be fine.
There may even be fallback behaviour built-in, but I'm not sure of this: if the unreliable transport doesn't work, the reliable one (ie: TCPROS) gets used automatically.
| | 2 | No.2 Revision |
I would just like to know: What is this UDP port for?
Afaik each ROS node will also open a UDP port to facilitate subscribers that would like to exchange messages over UDPROS. Subscribers can negotiate that by adding the unreliable hint to their TransportHints.
I would like to ignore it, because I can't (for many reasons) route UDP through the firewall.
As long as your subscribers do not request subscriptions over the unreliable transport (ie: use UDPROS), firewalling those UDP ports should be fine.
There may even be fallback behaviour built-in, but I'm not sure of this: if the unreliable transport doesn't work, the reliable one (ie: TCPROS) gets used automatically.
NOTE: if you notice the .exe extension and such, yes...this is a ROS installation (kinetic) on windows. I have ported the ROS client libraries and the python infrastructure (roscore, etc.) and they work very well with very little modification.
You're referring to codenotes/ros_cygwin here, correct?
| | 3 | No.3 Revision |
I would just like to know: What is this UDP port for?
Afaik each ROS node will also open a UDP port to facilitate subscribers that would like to exchange messages over UDPROS. Subscribers can negotiate that by adding the unreliable hint to their TransportHints.
See also: wiki/roscpp/Overview - Publishers and Subscribers - Subscribing to a Topic - Transport Hints.
I would like to ignore it, because I can't (for many reasons) route UDP through the firewall.
As long as your subscribers do not request subscriptions over the unreliable transport (ie: use UDPROS), firewalling those UDP ports should be fine.
There may even be fallback behaviour built-in, but I'm not sure of this: if the unreliable transport doesn't work, the reliable one (ie: TCPROS) gets used automatically.
NOTE: if you notice the .exe extension and such, yes...this is a ROS installation (kinetic) on windows. I have ported the ROS client libraries and the python infrastructure (roscore, etc.) and they work very well with very little modification.
You're referring to codenotes/ros_cygwin here, correct?
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
