Blocked Multicast IPs - TurtleBot3 and Remote PC
hi,
I'm new to ROS2 and currently setting up the TurtleBot 3 Burger like on the website link text advised. My PC is running with Ubuntu 18.04.4 LTS just as my TB3 Burger. Both are using the Debian Package of ROS2 Dashing the rest is just like in the e-manual recommended.
They are on the same wireless network and multicast is working too. But after i initialized the
ros2 launch turtlebot3_bringup robot.launch.py
on the e-manual via SSH i do not get any topics or nodes from the Turtlebot on my remote PC with
rqt
or
ros2 topic list
I don't even get an error to look into. The Simulations worked fine and without problems on my PC.
It would be helpful to understand how the two devices are communicating.
edit: ROS_DOMAIN_ID is the same on both and the firewall enables both IPs. I sourced multiple times too. Is there a possibility to install wrong?
The usual demo listener/talker nodes does work on the same machine but not to the other one. I even disabled the
ufw. Through Wireshark on the Remote PC I could see that no messages withros2 multicastwas send even when they are in the same Group. Network also allows multicasting because some devices (I think the Scanner/Printer) are using the IP range (239.255.0.251) of multicast.So i went deeper and found out that the packages that were send to the multicast port 17900 are not being used by ros2 but the "hint" that it is on the multicast channel were definitively there. I will try to set up another ros2 dashing (i had debian) and later on the eloquent to try things out
After completely wiping my PC and the TurtleBot3-Burger it still does not communicate with ros-dashing with the listerner/talker and the multicast. I even enabled the
ufwports like in the [Troubleshoot] (https://index.ros.org/doc/ros2/Troubl...) advised. I tried to minimize the installations and don't even have the TurtleBot Package on it because i think the listener/talker demo should be functioning first.