-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ros-teleop can not work in VM(NAT mode) #19
Comments
This is a general ROS problem; it's not specific to teleop_twist_keyboard. |
Thanks a lot, I realize that it is the mechanism of ROS and NAT that cause it. It is impossible to make it by topic, but I want to find a way to make it work(not bridge). I think service maybe work, so I make some attempts: |
I am using teleop in VM to control the robotic car, but it doesn't work. The specific situation is as follows:
Teleop is installed on Ubuntu of the VM and VM is in NAT mode. The Teleop could work, but the robot could not pick up the instructions from it.
If the VM is switched to Bridge mode, Teleop can control and the instructions can be received by robot. This has been bothering me for a long time. I want to ask if you have any suggestions
I test the talker and listener example in NAT mode and it can work, it really make me confused.
The text was updated successfully, but these errors were encountered: