.

[zidj]

.

[blurymind]

I want a way to do it, which will not be undone by a steamos update

[davebrosnan]

+1

[zasha_m]

I honestly don't see any reason for Valve to do anything as it's Linux you can easily do it yourself as already highlighted by OP..

[CorruptComputer]

Oprindeligt skrevet af zasha_m:

I honestly don't see any reason for Valve to do anything as it's Linux you can easily do it yourself as already highlighted by OP..

If you disable read only mode to install this, next time SteamOS updates it will overwrite your changes and you'll need to do it again. Having it built in would make this a lot easier for everyone. Also having a menu in the SteamOS game mode would make it even easier than having to switch to desktop mode every time.

[DeathCow]

There is literally zero reason for Valve not to include OpenVPN support. Just none. Posting to keep this thread high up in the visibility.

[CorruptComputer]

I would want Wireguard support to be added as well, the protocol has lower overhead latency than OpenVPN so for gaming it would be ideal. Wireguard support was added in Kernel 5.6 and SteamOS is already using Kernel 5.13, so all they would need to do is add the `wireguard-tools` package to support it.

https://archlinux.org/packages/extra/x86_64/wireguard-tools

EDIT: Thought I should add since folks might not be familiar with it, Wireguard is a new open standard that is widely supported by VPN providers and they almost universally say that this is faster and more secure than OpenVPN connections. It was created as a replacement to OpenVPN to solve the issues that exist with it. More specifically that it uses more modern cryptography and has a smaller performance overhead due to the protocol itself being slimmer than OpenVPN.

For reference:
- Wireguard: https://www.wireguard.com
- ProtonVPN: https://protonvpn.com/support/what-is-wireguard
- Private Internet Access: https://www.privateinternetaccess.com/vpn-features/wireguard
- NordVPN: https://nordvpn.com/blog/nordlynx-protocol-wireguard
- Mullvad: https://mullvad.net/en/help/why-wireguard
- Surfshark: https://surfshark.com/blog/what-is-wireguard

[ben]

I really hope valve doesnt consider adding VPN simply because it would be considered bloatware to 99% of the users. And I know the people who want VPN will start to rage now because they think its the most important thing on earth. But the reality is: For the majority of users it simply doesnt bring any value at all. I am a regular openvpn user myself. I use it every single day on my phone and I dont want to miss it either but most people dont. Of course its true you have to reinstall any vpn Software after an OS update but considering you can install openvpn with one line in terminal and store your openvpn settings in a single ovpn file in your home directory I dont really think its a big deal for the users who actually WANT it.

I want valve to focus on the best gaming experience and best user experience there can be and not having to deal with 3rd party support people can do themselves.

[Boblin the Goblin]

Oprindeligt skrevet af ben:

I really hope valve doesnt consider adding VPN simply because it would be considered bloatware to 99% of the users. And I know the people who want VPN will start to rage now because they think its the most important thing on earth. But the reality is: For the majority of users it simply doesnt bring any value at all. I am a regular openvpn user myself. I use it every single day on my phone and I dont want to miss it either but most people dont. Of course its true you have to reinstall any vpn Software after an OS update but considering you can install openvpn with one line in terminal and store your openvpn settings in a single ovpn file in your home directory I dont really think its a big deal for the users who actually WANT it.

I want valve to focus on the best gaming experience and best user experience there can be and not having to deal with 3rd party support people can do themselves.

They aren't asking to add a VPN to the Deck. They are asking for easy VPN support.

Big difference.

[ben]

Oprindeligt skrevet af KittenGrindr:

They aren't asking to add a VPN to the Deck. They are asking for easy VPN support.Big difference.

There already is. You can do it yourself just as I did. And tbh I really do not think I am a linux professional in any way, especially not arch based distros.

[Boblin the Goblin]

Oprindeligt skrevet af ben:

Oprindeligt skrevet af KittenGrindr:

They aren't asking to add a VPN to the Deck. They are asking for easy VPN support.Big difference.

There already is. You can do it yourself just as I did. Nobody forces you to install every OS update. And even then its easy to do.

Having VPN support wouldn't be the same as adding a VPN. Nobody is forcing you to install a VPN just because support is added.

As you can see by OP, it doesn't support OpenVPN, only proxies to connect to you to the VPN. That's the issue.

[ben]

Oprindeligt skrevet af KittenGrindr:

Oprindeligt skrevet af ben:

There already is. You can do it yourself just as I did. Nobody forces you to install every OS update. And even then its easy to do.

Having VPN support wouldn't be the same as adding a VPN. Nobody is forcing you to install a VPN just because support is added.

As you can see by OP, it doesn't support OpenVPN, only proxies to connect to you to the VPN. That's the issue.

OP literally posted how to get openvpn working with three commands so I am not sure if "not supported" is the right term in this case. And even if its not supported its very simple to do. What would you consider valve should do to not give away too much of the OS and where should they draw the line? One users asks for openvpn, the next one asks for wireguard, the next one asks for sonicwall netextender because they use the deck at work. I am pretty sure valve had good reasons to make the OS readonly - thats not a decision you make just because you feel like it.

[Boblin the Goblin]

Oprindeligt skrevet af ben:

OP literally posted how to get openvpn working with three commands so I am not sure if "not supported" is the right term in this case.

Oprindeligt skrevet af rat:

The Deck by default does not support vpn connections, only proxies, even in desktop mode. Sometimes, I need a VPN to connect to Steam... I use Tunnelbear, which only supports OpenVPN on Linux. Until there is official OpenVPN support, Here is how I got openvpn connections to work...

Oprindeligt skrevet af ben:

And even if its not supported its very simple to do. What would you consider valve should do to not give away too much of the OS and where should they draw the line?

How would adding support be "giving away the OS"? Considering SteamOS is already being customized and distributed on GitHub.

Oprindeligt skrevet af ben:

One users asks for openvpn, the next one asks for wireguard, the next one asks for sonicwall netextender because they use the deck at work. I am pretty sure valve had good reasons to make the OS readonly - thats not a decision you make just because you feel like it.

Except it depends on what those VPNs use. As people have stated, a lot of common VPNs use OpenVPN for Linux, so they wouldn't have to make support for each individual company. This also has nothing to do with the OS being readonly considering with a simple command, you can turn that restriction off with a simple command line.

[ben]

Oprindeligt skrevet af KittenGrindr:

This also has nothing to do with the OS being readonly considering with a simple command, you can turn that restriction off with a simple command line.

I am not sure if I understand what you mean. Actually the whole discussion OP started is about just that and nothing more. What keeps you from putting OPs commands into a .sh and run it once after a OS update and be happy?

[Boblin the Goblin]

Oprindeligt skrevet af ben:

Oprindeligt skrevet af KittenGrindr:

This also has nothing to do with the OS being readonly considering with a simple command, you can turn that restriction off with a simple command line.

I am not sure if I understand what you mean. Actually the whole discussion OP started is about just that and nothing more. What keeps you from putting OPs commands into a .sh and run it once after a OS update and be happy?

The same thing that apparently keeps you from not having to do that if official support gets added.

[ben]

so it's a problem of inconvenience but not actually a real problem