Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upVPN seems 'throttled' R4.0-rc1 #2980
Comments
andrewdavidwong
added
the
C: other
label
Aug 5, 2017
andrewdavidwong
added this to the Release 4.0 milestone
Aug 5, 2017
andrewdavidwong
added
the
bug
label
Nov 3, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
tasket
Nov 9, 2017
Not sure if this belongs logged as a bug; Qubes networking is not vanilla Linux and VPN provider custom scripts/clients AFAIK are not supported. This would be better addressed on qubes-users list.
@JPL1 My advice for now would be to use the Airvpn config generator then use that config with the Qubes VPN doc. The doc was written for Qubes 3.x, so when you create "qubes-firewall-user-script" save it as "qubes-ip-change-hook" instead. Of course, where it says "proxyVM" use an appVM that "provides network". This should get it running with Qubes-specific leak protection (which the Airvpn client probably doesn't provide, though I can't tell because its a compiled binary).
tasket
commented
Nov 9, 2017
|
Not sure if this belongs logged as a bug; Qubes networking is not vanilla Linux and VPN provider custom scripts/clients AFAIK are not supported. This would be better addressed on qubes-users list. @JPL1 My advice for now would be to use the Airvpn config generator then use that config with the Qubes VPN doc. The doc was written for Qubes 3.x, so when you create "qubes-firewall-user-script" save it as "qubes-ip-change-hook" instead. Of course, where it says "proxyVM" use an appVM that "provides network". This should get it running with Qubes-specific leak protection (which the Airvpn client probably doesn't provide, though I can't tell because its a compiled binary). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
andrewdavidwong
Nov 10, 2017
Member
Based on our issue reporting guidelines, this does not appear to be suitable for qubes-issues. We ask that you please send this to the qubes-users mailing list instead. If, after reading our issue reporting guidelines, you believe we are mistaken, please leave a brief comment explaining why. We'll be happy to take another look, and, if appropriate, reopen this issue. Thank you for your understanding.
|
Based on our issue reporting guidelines, this does not appear to be suitable for |
andrewdavidwong
closed this
Nov 10, 2017
andrewdavidwong
added
invalid
and removed
bug
labels
Nov 10, 2017
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
JPL1
commented
Nov 10, 2017
|
@tasket I will try that. Thanks for the tip. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
JPL1
Nov 12, 2017
I can report that the problems do not occur on 4.0rc2. AirVPN works 'out of the box'
JPL1
commented
Nov 12, 2017
|
I can report that the problems do not occur on 4.0rc2. AirVPN works 'out of the box' |
JPL1 commentedAug 5, 2017
Qubes OS version (e.g.,
R3.2):R4.0-rc1
Process
Created an AppVM based on fedora-25 with 'provides network' checked. Installed AirVPN client, selected sys-firewall as NetVM. Ran airvpn as sudo (wouldn't let me run as user). It connected to VPN server OK but very slow. Tried many alternative servers - same result.
Tried changing the netVM to sys-net - same problem.
Tried installing VPN in another AppVN - same problem.
Tried adding PCI devices such as network-manager in the VPN AppVM settings but that caused an error.
Added network-manager and meminfo-writer under services - no difference
The problem is definitely this installation and not Airvpn as everything works fine in R3.2 where I have the same setup.
Any ideas? Am I doing something wrong?