Cannot connect to ROS master running on virtual machine

Question

caesar 2018-4-3

1
链接

此问题的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/392422-cannot-connect-to-ros-master-running-on-virtual-machine

评论： Adil Farooq 2023-1-11

Matlab cannot connect to ROS master on virtual machine. here are the complete setup :

I am using Matlab 2017B on my host machine, also have Ubuntu 16.04 LTS and ROS kinetic running on Virtual machine (Virtualbox).

the Ifconfig result is :

ethernet address: 10.0.2.15 (on Ubuntu)

on host machine :

ipconfig
130.209.140.237

on Ubuntu

 $ echo $ROS_MASTER_URI  
 http://10.0.2.15:11311
$ echo $ROS_HOSTNAME
 10.0.2.15

i had tried many ways to connect to ROS master on Matlab :

1-

rosinit ('10.0.2.15', 'NodeHost', '130.209.140.237')

2-

setenv('ROS_MASTER_URI','http://10.0.2.15:11311')
setenv('ROS_IP','130.209.140.237')
 rosinit

and same error message:

Cannot connect to ROS master at http://10.0.2.15:11311. Check the specified address or hostname.

also , i tried to ping the virtual machine but no reply :

ping 10.0.2.15 
request time out

one last thing , I have attached an image showing the 'Network' setting for my virtual machine . has anyone faced the same problem before?

thanks in advanced

2 个评论
显示无隐藏无

Sebastian Castro 2018-4-5

If you can't even ping the VM, this might be a firewall issue.

Make sure that both programs (MATLAB and VirtualBox) are allowed by the firewall, assuming you have one.

Ameer Hamza 2018-4-20

@caesar I can not find the image you attached to the question, but it appears that you might be using NAT network to interface guest VM with the host. The host cannot reach guest behind NAT network. You either need to use Bridged Network or Host-only Adapter to communicate between both machines.

请先登录，再进行评论。

请先登录，再回答此问题。

Answer 1

Stefano Dalla Gasperina 2019-2-7

1
链接

此回答的直接链接

https://ww2.mathworks.cn/matlabcentral/answers/392422-cannot-connect-to-ros-master-running-on-virtual-machine#answer_359992

在 MATLAB Online 中打开

@caesar, I got the same issue and I was able to solve by setting the "Bridged Adapter" mode in the VirtualBox Network Settings. Actually, by using the "Bridge" mode, your VM will get a ip address on the same subnet as your host, while in default "NAT" mode your host will act as a router (firewall) and your VM will be on a private subnet (e.g. ip 10.0.2.15).