Turtlebot3 and Remote PC connection problem (only topics present are /parameter_events and /rosout) about turtlebot3 HOT 2 CLOSED

@HuaYuXiao Thanks for your response! It was indeed a connection problem, but the '.bashrc' and '/etc/hosts' files were configured correctly.

After searching a little more on the Internet, I found the cause of the problem.
The Remote PC running in the Virtual Machine was using a network connection utilizing NAT. Because of that, the multicast packets sent by the TurtleBot weren't received, despite of the Remote PC and TurtleBot being on the same network.

To solve the issue, I should've switched the Virtual Machine network connection to Bridge, but from what I've seen, it doesn't work on Wi-Fi Adapters because of driver issues. So Bridge connection for the VM only works on Ethernet connections.

The solution is to use Ubuntu natively to make it work on Wi-Fi connections, but I didn't want to dual boot Ubuntu on my laptop. Instead, I installed and booted of a persistent Ubuntu live USB, on which I installed ROS2. This way I was able to communicate with my Turtlebot, using Wi-Fi on both the Remote PC and TurtleBot.

from turtlebot3.

I want to mention that both my Remote PC and Turtlebot3 are connected through Wi-Fi on the same Wi-Fi network.
Ubuntu 20.04 LTS on my remote PC is on a Virtual Machine (ping works with the IP of TurtleBot3 Burger)

from turtlebot3.