Robot radio blocking ports

Technical Control System
1

We’re having trouble with the robot radios blocking ports they shouldn’t be- specifically ports 22, 1180, 5800, 5801, and 5802 (as far as I recall.) This occurs on the OM5P-AC with 2017 firmware, OM5P-AN with 2017 firmware, and OM5P-AN with 2016 firmware.

On all radios, supposedly team-use ports 1180 and 5800+ were blocked. On the OM5P-AN w/ 2016 firmware, port 22 was also inaccessible. Team-use ports were tested by running a custom HTTP dashboard program listening on these ports. While little testing was done with port 22, it was inaccessible to the robotpy deploy tool. I have heard from another team that had the same problem with the Java deploy tool.

I haven’t run nmap or similar yet. I’m fairly sure that the radio is the problem, because the HTTP dashboard worked while USB-tethered.

Thanks for any input you may have.

2

When using the programing tool, make sure the firewall checkbox is disabled.

3

In our experience on many radios (both last year’s and this year’s) that checkbox is ignored and the firewall rules are established unconditionally. As a result, programming the robot over Wi-Fi is not possible since port 22 is blocked.

4

We are perfectly able to program over wifi using both last years and this years radio.

5

What firmware version are you using? Have you ever checked the Firewall box in any of your firmware loads or reconfiguration runs? What programming environment do you use? Could you possibly send me the output from a code deployment (assuming you use Eclipse)?

We have tried both 17.0 and 17.2 and use Java via Eclipse and the latest FRC Plugins.

6

Can you post the output from one of your code deployments? I think this is not a firewall issue but rather a mDNS issue.

7

I don’t have access to a robot at present, but the key message was “connection refused” when attempting to connect to port 22 of the RoboRIO.

We’ve already proven that our radios are blocking port 22 (ssh) by connecting a test laptop running Linux via WiFi to the radio which is in turn connected via Ethernet cable to the RoboRIO. When we remove the radio from the mix and go direct we can get into port 22 of the RoboRIO just fine. We are addressing the RoboRIO by its assigned IP address in both cases.

In the meantime, we’ve had to program the robot via USB cable. Note that we can bring up the webdashboard and operate the robot via WiFi just fine (since port 22 is not used in those cases).

Thanks guys for offering assistance/insights.

8

Make sure your PC firewall is disabled.