/etc/ros/robot.launch now includes /etc/ros/hrl.launch . Probably it's a good idea to put this file into a package in gt-ros-pkg, add to svn and symlink it, but this is a to do.

(not true anymore as this conflicts with 2d_nav package) by default we're launching teleop_joystick.launch (via an insertion into /etc/ros/robot.launch) so that the joystick will always be available to move the robot.

Nodes that need to launch by default by "sudo robot start" should be declared in /etc/ros/hrl.launch

Network

Plugging the PR2 to any HSI port will cause it to use the wired network, and it's currently wirelessly connected to robot1. Even though robot1 is a 192.* NATed network, there is a little bit of network magic through VPN tunnels that allows you to still connect with the above host names.

The client wireless router configuration on the robot is using the default HRL username and password.