Raspberry Pi MJPG Streamer -port 8080 okay?

[beijing_strbow]

Those restrictions are for ports on the rio, because the field uses certain ports to communicate with the robot. What port you use to stream off of the raspberry pi doesn't matter.

[billbo911]

Originally Posted by beijing_strbow

Those restrictions are for ports on the rio, because the field uses certain ports to communicate with the robot. What port you use to stream off of the raspberry pi doesn't matter.

Hang on, this is incorrect.

Data between an on board RPi and the RoboRio will not cross the WiFi, that is corrrect. It still should NOT use a port that conflicts with control packets. Data between the RPi and the DS is carried over the WiFi and is thus subject to the port restrictions.
mjpg_streamer does just that and therefore is subject to the restrictions.

[scca229]

If the traffic is going between the radio on the robot and the driver station ethernet port, it is subject to those restrictions via R65, policed by the FMS.

Anything completely internal to the robot (even through the radio's switch) or completely internal to the DS (Operator Console and attached devices) is unaffected by those restrictions.

[billbo911]

Originally Posted by scca229

If the traffic is going between the radio on the robot and the driver station ethernet port, it is subject to those restrictions via R65, policed by the FMS.

Anything completely internal to the robot (even through the radio's switch) or completely internal to the DS (Operator Console and attached devices) is unaffected by those restrictions.

Nate,
You are 100% correct.

Originally Posted by billbo911

..It still should NOT use a port that conflicts with control packets. ..

My comment above was aimed at making certain that there is no interference with command packets. If you follow the port restrictions, there is no chance of doing that. Now, flooding your network on the robot with TCP packets is another issue altogether! Trust me on that, we found out the hard way.

[rtrahms]

Thanks all for the quick replies!

We were able to add the -p 80 option to our mjpg_streamer call, but are now encountering a different problem: bind(80) failed on the Raspberry Pi.

I think the HTTP server is used to port 8080 by default, and I need to figure out how to open/enable port 80 on the RPi instead.

Suggestions?

[rtrahms]

Found the issue - it was a permission denied problem.
Executing same call with 'sudo mjpg_streamer...' worked.
We're up and running now, streaming video from the Raspberry Pi port 80!

Thanks for the help.