Re: [ros-users] Current best practice for multiple interface…

Top Page
Attachments:
Message as email
+ (text/plain)
+ signature.asc (application/pgp-signature)
Delete this message
Reply to this message
Author: User discussions
Date:  
To: ros-users
Subject: Re: [ros-users] Current best practice for multiple interfaces
On 16/01/13 06:57, Bil Morris wrote:
> I am not sure why the XML RPC server does not support binding to
> INADDR_ANY instead of a specific ip address.


Yeah, this would be great from a systems perspective! Why doesn't it do
that already?

> If the server could be modified to connect to all interfaces and rebind
> the sockets when the xmlrpc server receives
> a SIGHUP, then I think you could take something like our upstart scripts
> [1] and modify them to start ROS on boot and
> and send SIGHUP to ROS whenever the WiFi interface bounces.


IIRC if you listen on any socket, you don't need to re-bind as
interfaces come and go, so I don't think even sending a signal would
even be necessary.

For people that want a robot to "just work" as soon as you switch it on,
this would make life much easier.

//Mike

--
Michael Gratton <http://www.cse.unsw.edu.au/~mikeg/>
UNSW School of Computer Science and Engineering.