Revision history [back]

Is this a ROS-problem

No.

or simply a network setting in ubuntu?

yes.

Try enabling the "Use this connection only for resources on its network" setting for the NIC connected to Baxter.

![https://i.imgur.com/kXPOm7s.jpg]

From the commandline: How to toggle NetworkManager's “Use this connection only for resources on its network” option via command line.

Is this a ROS-problem

No.

or simply a network setting in ubuntu?

yes.

Try enabling the "Use this connection only for resources on its network" setting for the NIC connected to Baxter.

![https://i.imgur.com/kXPOm7s.jpg]

From the commandline: How to toggle NetworkManager's “Use this connection only for resources on its network” option via command line.

Is this a ROS-problem

No.

or simply a network setting in ubuntu?

yes.

Try enabling the "Use this connection only for resources on its network" setting for the NIC connected to Baxter.

From Using the commandline: command line (from How to toggle NetworkManager's “Use this connection only for resources on its network” option via command line.):

nmcli connection modify enp3s0 ipv4.never-default true

Is this a ROS-problem

No.

or simply a network setting in ubuntu?

yes.

Try enabling the "Use this connection only for resources on its network" setting for the NIC connected to Baxter.

Using the command line (from How to toggle NetworkManager's “Use this connection only for resources on its network” option via command line):

nmcli connection modify enp3s0 ipv4.never-default true

Is this a ROS-problem

No.

or simply a network setting in ubuntu?

yes.

Try enabling the "Use this connection only for resources on its network" setting for the NIC connected to Baxter.

This setting (image from here):

Using the command line (from How to toggle NetworkManager's “Use this connection only for resources on its network” option via command line):

nmcli connection modify enp3s0 ipv4.never-default true

make sure to use the correct name for the connection of course.