Bug 30197

Summary: Add Support for Steam Remote Play
Product: Mageia Reporter: John <johnms>
Component: RPM PackagesAssignee: Nicolas Lécureuil <mageia>
Status: RESOLVED INVALID QA Contact:
Severity: enhancement    
Priority: Normal CC: davidwhodgins, paul.blackburn
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: drakx-net CVE:
Status comment:
Attachments: Add Steam Remote Play
MCC-Security-Personal Firewall dialogues

Description John 2022-03-23 16:50:32 CET
Adds the ports to open when you wish to enable Steam Remote Play. See https://help.steampowered.com/en/faqs/view/0689-74B8-92AC-10F2#networkports for details on the ports.
Comment 1 John 2022-03-23 16:52:30 CET
Created attachment 13189 [details]
Add Steam Remote Play

Adds the ability to open the ports for drakfirewall and drakfirewall6.
Comment 2 sturmvogel 2022-03-23 18:50:13 CET
Listening on this port as this is required by steam is already possible?! The Firewall only blocks ingoing traffic.

But some experts may correct me at this point.
Comment 3 sturmvogel 2022-03-23 19:31:26 CET
I'm sorry to say this, but: your burreport is INVALID.

Steam remote play works out of the box without any need to open ports. 

Testet this with a supportet Steam title (Brawlhalla). 

Enable remote play on your streaming machine.
Install Steam Link on your tablet/smartphone/tv/controller.
Install steam game which is enabled for remote play on streaming machine.
Couple streaming machine with Stream Link device
Have fun and play.

Closing INVALID.

Status: NEW => RESOLVED
Resolution: (none) => INVALID

Comment 4 John 2022-03-23 19:38:19 CET
I re-opened this as I was asked to open the bug report to submit this patch as an enhancement.

Resolution: INVALID => (none)
Status: RESOLVED => REOPENED

Comment 5 sturmvogel 2022-03-23 19:45:33 CET
 Who asked you to do this? This is absolutely not needed?
Comment 6 John 2022-03-23 20:34:36 CET
It was on the IRC channel. I don't remember the user-name at the moment.
Comment 7 sturmvogel 2022-03-23 20:36:12 CET
Can you at least tell which channel? Because we need to kno why we should open ports that are not needed to open?
Comment 8 Lewis Smith 2022-03-23 20:52:13 CET
Created attachment 13190 [details]
MCC-Security-Personal Firewall dialogues

Yes John.
> I was asked to open the bug report to submit this patch as an enhancement
This would be valid if it is *necessary* to do whatever is needed.
Perhaps you need to explain more fully why the user you represent cannot do what is necessary with MCC-Security-Personal Firewall.

I wonder whether what prompted this request is that the standard list presented shows many standard services, which do not include remote Steam; and that he wanted this in the displayed list.
But I suspect what he should do instead is use the ADVANCED dialogue to add whatever ports he wants.
Both 'standard' & 'advanced' dialogues are shown in this attached image (excuse the Welsh, you will make sense of it).

There are many applications which require their special ports to be opened in the firewall, which is why we cannot extend the standard list ad infinitum.

CC: (none) => lewyssmith

Comment 9 Dave Hodgins 2022-03-23 21:04:22 CET
In #mageia ...
[Wednesday, 23 March 2022] [10.20.45 EDT] <neoclust>    more seriously, when done, please open a bugreport
[Wednesday, 23 March 2022] [10.20.55 EDT] <JohnMS_WORK> Will do.
[Wednesday, 23 March 2022] [10.21.05 EDT] <neoclust>    we are working on migrating this part on our future gitlab instance
[Wednesday, 23 March 2022] [10.21.39 EDT] <JohnMS_WORK> Should I do a git clone or just download the file and use patch directly?
[Wednesday, 23 March 2022] [10.22.59 EDT] <neoclust>    JohnMS_WORK: do a git clone, work on it, git commit ( locally ), git format-patch and add the patch(es) in the bugreport

Adding neoclust to the cc list.

CC: (none) => davidwhodgins, mageia

Comment 10 Paul Blackburn 2022-03-23 21:53:56 CET
FAO: sturmvogel

Observed today (Wednesday 23rd March 2022 at about 1323 GMT) on #mageia on the libera IRC chat network.

screenshot from hexchat: https://i.imgur.com/0dRo2Cg.png


I think it is a bit of "overkill" adding a specific firewall rule just for steam.
There always has been the facility to add a specific port and protocol to drakfirewall configuration.

Sensibly (IMHO) drakfirewall has a short list of the key services which might be needed.

In general, it is not good security practice to open inbound ports through the shorewall firewall because by doing so it makes another route for an attacker to try to compromise the system.

How many people actually need a rule specifying steam in drakfirewall?

If we are going to add steam to the list then why not add all the others in /etc/services? [Actually this would not be a good thing to do because it could encourage users to weaken their security.]

I think I prefer that while it is possible to add new rules, it is under the label "Advanced" which will possibly discourage novice users from messing around with this and ending up with more vulnerable systems.

CC: (none) => paul.blackburn

Comment 11 sturmvogel 2022-03-23 22:04:50 CET
Thanks Paul. 

As i already wrote, it is not even neccessary to open any additional ports for steam remote play. Steam remote play uses the same ports as steam itself. And there is no single port blocked or closed which used by steam. Im playing steam games under Mageia since years and there was never a need to open any additional ports for it.

So my conclusion stays the same: INVALID
Comment 12 sturmvogel 2022-03-23 22:23:44 CET
In addition i did also some other tests to confirm that there is absolutely no need to change anything at the firewall if you want to use steam remote play even between different OS and devices.


Desktop MGA8 <-> Laptop MGA8  works out of the box
Desktop MGA8 <-> Android 10 Smartphone works out of the box
Desktop Opensuse Tumbleweed <-> Laptop MGA8 works out of the box
...
Comment 13 Lewis Smith 2022-03-25 08:58:32 CET
Comment 8 & comment 10 coincide in spirit, and all sturmvogel's evidence indicates that this specific request is superflous.

Comment 9 (illustrated in Paul's link) indicates that neoclust thinks the request is OK, so assigning the bug to him. Do note comment 10, though.

Assignee: bugsquad => mageia
CC: lewyssmith, mageia => (none)

Comment 14 Nicolas Lécureuil 2022-03-25 22:59:01 CET
it indicates NOTHING.

I have just been asked how to propose a bug/feature. I just explained.
Comment 15 Dave Hodgins 2022-03-25 23:25:32 CET
Re-closing based on above comments.

Resolution: (none) => INVALID
Status: REOPENED => RESOLVED