Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 09/15/2018 05:07 AM, 22...@tutamail.com wrote: Thanks Chris...I understand now. I just tried it again and below are my logs, while I don't get the "Operation not permitted (code=1)" error I still get the TLS error Fri Sep 14 16:55:06 2018 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.08 Enter Auth Username: My username Enter Auth Password: ** Fri Sep 14 16:55:35 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]208.X.x.x ; port xx Fri Sep 14 16:55:35 2018 Socket Buffers: R=[212992->212992] S=[212992->212992] Fri Sep 14 16:55:35 2018 UDP link local: (not bound) Fri Sep 14 16:55:35 2018 UDP link remote: [AF_INET]208.x.x.x: port xx Fri Sep 14 16:56:36 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Fri Sep 14 16:56:36 2018 TLS Error: TLS handshake failed Fri Sep 14 16:56:36 2018 SIGUSR1[soft,tls-error] received, process restarting Fri Sep 14 16:56:36 2018 Restart pause, 5 second(s) Looks like the connection type is still set as UDP in your OpenVPN configuration file (.ovpn or .conf). Did you try to set it to TCP and according ports? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/aab36350-bd17-8322-a4ea-6a3f603df7a4%40rbox.co. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 09/14/2018 03:25 PM, 22...@tutamail.com wrote: Thank you Anac and Chris, appreciate your suggestions: You said that Tor was running. When combining Tor with VPN, the VPN's connection type should be TCP, not UDP. Did you check that? I did check this...opened the connection to Any/Any but this didn't seem to be the issue. I also eliminated TOR for testing and connected directly to the sys-net(to also eliminate any sys-firewall potential issues) Before you go through the trouble of a whole reinstall, you could try setting your VPN VM to use Fedora 28 instead to see if it works. You can also perform a reinstall of the Debian template. I tried with fedora-28 but also had the same TLS connection error. I ran the tests in step 3 as suggested and recieved the following errors with both the Debian and Fedora setup: Fri Sep 14 10:30:53 2018 OpenVPN 2.4.0 x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Jul 18 2017 Fri Sep 14 10:30:53 2018 library versions: OpenSSL 1.0.2l 25 May 2017, LZO 2.08 Enter Auth Username: My user name Enter Auth Password: ** Fri Sep 14 10:32:34 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]208.167.254.76:1198 Fri Sep 14 10:32:34 2018 Socket Buffers: R=[212992->212992] S=[212992->212992] Fri Sep 14 10:32:34 2018 UDP link local: (not bound) Fri Sep 14 10:32:34 2018 UDP link remote: [AF_INET]208.x.x.x:port xx Fri Sep 14 10:32:34 2018 write UDP: Operation not permitted (code=1) Fri Sep 14 10:32:36 2018 write UDP: Operation not permitted (code=1) Fri Sep 14 10:32:40 2018 write UDP: Operation not permitted (code=1) Fri Sep 14 10:32:48 2018 write UDP: Operation not permitted (code=1) Fri Sep 14 10:33:04 2018 write UDP: Operation not permitted (code=1) Fri Sep 14 10:33:34 2018 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) Fri Sep 14 10:33:34 2018 TLS Error: TLS handshake failed Fri Sep 14 10:33:34 2018 SIGUSR1[soft,tls-error] received, process restarting Fri Sep 14 10:33:34 2018 Restart pause, 5 second(s) Definitely strange considering it was working great for a few months...the good news is the kill switch functionality with this solution worked. Any insight with the errors I recieved? If not I think a reinstall is my best course... You would normally get operation not permitted if the internal firewall script is in effect, which is why this step comes before any scripts are added (i.e. its performed in a fresh VM). You can either disable the firewall script in /rw/config/qubes-firewall.d and reboot, or try the test in a new VM connected to sys-net. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a48bdd20-e74d-20ea-ac6d-003ce44a4957%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 09/13/2018 08:00 PM, Anac wrote: On 09/14/2018 12:13 AM, 22...@tutamail.com wrote: Unfortunately I have been under constant attack and a target and the only solution I see is a fresh rebuild or new computer unless you have another idea? https://github.com/tasket/qubes-doc/blob/tunnel/configuration/vpn.md#set-up-a-proxyvm-as-a-vpn-gateway-using-the-qubes-tunnel-service Step 3 of the revised doc is probably the most effective test you can perform... its basically starting fresh with (at that point) no scripts added. Its just openvpn + the config. If that doesn't work then you may be right that something in Qubes itself has become broken and maybe a reinstall is necessary. Before you go through the trouble of a whole reinstall, you could try setting your VPN VM to use Fedora 28 instead to see if it works. You can also perform a reinstall of the Debian template. You said that Tor was running. When combining Tor with VPN, the VPN's connection type should be TCP, not UDP. Did you check that? When connecting to VPN through TOR, TCP is required but depending on your provider's server config you may also have to change the port number. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f8ea83ca-9adc-add1-c376-a0791eac5062%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 09/14/2018 12:13 AM, 22...@tutamail.com wrote: Unfortunately I have been under constant attack and a target and the only solution I see is a fresh rebuild or new computer unless you have another idea? You said that Tor was running. When combining Tor with VPN, the VPN's connection type should be TCP, not UDP. Did you check that? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f9b9defd-b9b7-3484-19b2-84524feec988%40rbox.co. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 09/07/2018 11:10 AM, 22...@tutamail.com wrote: Thank you both for your responses...fair question John but I am the OP, lost access to my old tutamail. Yes my VPN was working fine for a few months however with a recent update it broke?? Its a little concerning because I did both a Debian and Dom0 update. When trying to update Dom0 I was not able to update it via Tor or VPN via Qubes?? I managed to confirm my VPN is spawning out in an attempt to connect but the TLS is still not working...I tried it on 3 different networks. I know you can modify the DNS resolver by adding the following to the OpenVPN configuration: setenv tunnel_dns '8.8.8.8' But what would I add to "Specifying 'local'" in the OpenVPN configuration? Thanks again for any help... IIRC you only need to specify the IP address of a regular system interface, which in this case is eth0. So do a 'sudo ip addr' and look up the eth0 'inet' address and put 'local ' in the config. There's a chance this might work. If it doesn't work, and you know of no custom firewall rules or net settings that you can check or remove, then I'd consider the following possibilities: 1. Your VPN provider has changed their TLS certificate or other connection parameters. In this case their special client software (e.g. installed on other devices?) would automatically refresh the config files while your Qubes config would remain stale and unable to complete TLS verification of the remote. Remedy for this is to download your provider's current openvpn configs and put them in /rw/config/qtunnel (making sure that qtunnel.conf points to a new config file). 2. Some residual network property of your VPN VM has triggered a bug that prevents it from working correctly. Simple remedy would be to create and setup a new proxyVM and use that instead. 3. Unlikely: Interference from malware, possibly residing in sys-net. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d6b0e16f-7b37-f078-689a-802336cca615%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 09/06/2018 10:22 AM, 22...@tutamail.com wrote: It appears as if I am getting a TLS error? Why would this suddenly start? Wed Sep 5 17:23:39 2018 TLS Error: TLS handshake failed Wed Sep 5 17:23:39 2018 SIGUSR1[soft,tls-error] received, process restarting Wed Sep 5 17:23:39 2018 Restart pause, 5 second(s) Wed Sep 5 17:23:44 2018 TCP/UDP: Preserving recently used remote address: [AF_INET]xxx.xxx.xxx.xx:port xxx I have restarted the computer, I am using Qubes 4.0 and leveraging a Debian 9 template. The other devices are using OpenVPN... Any ideas? When I search on the TLS error I get results like this: https://serverfault.com/questions/709860/fix-tls-error-tls-handshake-failed-on-openvpn-client#765205 Specifying 'local' may be worth a try. It sounds like something has gone wrong with the virtual devices or the Qubes firewall for that VM... perhaps triggered by the system update. I'm also using Debian 9 on Qubes 4. dom0 is updated with security-testing enabled. Check your kernel version, mine is 4.14.67-1. Testing basic connectivity for the VM can be done by first disabling the tunnel firewall rules... delete the link at /rw/config/qubes-firewall.d/90_tunnel-restrict. Then restart VM and use ping/traceroute. John, Not sure what " script in an appvm/qube instead of the "tunnel" version ?" is...I had tried to set up the "iptables and CLI scripts" https://www.qubes-os.org/doc/vpn/ but really struggled. I found the Tasket solution easier to set up for a relative novice in desperate need of VPN security. I am also able to setup a few configurations so I can use different destinations. Is this the version you are using? You can think of the vpn doc as a much older version of qubes-tunnel. I doubt switching to it would help. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1460cb9e-f9ff-12ed-0512-9c2d964a530f%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 09/05/2018 11:32 AM, 22...@tutamail.com wrote: Correctionmy TOR is working. Any ideas how to trouble shoot? Everything has been working fine, however recently my VPN tunnel is failing? I ran: sudo journalctl -u qubes-tunnel and I get: Sep 05 10:17:48 VPN-Mid qtunnel-setup[1138]: Wed Sep 5 10:17:48 2018 All connections have been connect-retry-max (7) times unsuccessful, e Sep 05 10:17:48 VPN-Mid qtunnel-setup[1138]: Wed Sep 5 10:17:48 2018 Exiting due to fatal error Sep 05 10:17:48 VPN-Mid systemd[1]: qubes-tunnel.service: Main process exited, code=exited, status=1/FAILURE Sep 05 10:17:48 VPN-Mid qtunnel-setup[1149]: STOP-ing network forwarding! Sep 05 10:17:48 VPN-Mid systemd[1]: qubes-tunnel.service: Unit entered failed state. Sep 05 10:17:48 VPN-Mid systemd[1]: qubes-tunnel.service: Failed with result 'exit-code'. Some additional notes: My connection works on other devices I am able to get Internet access via non-VPN connection I did update Dom0 and my templates but it worked shortly afterwards Did you reboot the computer after the updates? What kind of template is the VPN VM using? Perhaps your other devices use non-openvpn protocols, and the VPN service's openvpn server has gone offline? You can try to make the connection manually, like this: sudo systemctl stop qubes-tunnel sudo iptables -P OUTPUT ACCEPT cd /rw/config/qtunnel sudo openvpn --config qtunnel.conf --verb 3 This will show a lot of detail in the terminal. A successful connection will show "Initialization sequence completed" at the end. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/68267906-f16e-bef3-517d-b681e0dad062%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 05/12/2018 02:10 PM, get wrote: Hi. script not working more on debian-9/fedora-26. Please fix it. Tested vpn's : mullvad, privateinternetaccess, expressvpn and multiple random openvpn. Guides: https://github.com/tasket/Qubes-vpn-support https://github.com/tasket/qubes-doc/blob/tunnel/configuration/vpn.md#set-up-a-proxyvm-as-a-vpn-gateway-using-the-qubes-tunnel-service https://github.com/tasket/qubes-tunnel This thread is for qubes-tunnel not Qubes-vpn-support. Also I can't read minds... Can you describe a specific example with one VPN? -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2a5cc0aa-4b2e-2584-c0a5-37ce1bbcbde9%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 05/14/2018 09:09 AM, Chris Laprise wrote: On 05/12/2018 03:11 PM, JonHBit wrote: I've updating to 1.4beta4 and switched templates from debian-9 to fedora-28, but I'm getting the same error - also it seems like openvpn flag defaults changed, as it now returns an error for the up and down arguments Did you mean fedora-26? Specifically, it parses /usr/lib/qubes/qtunnel-connect up as 2 arguments instead of 1; putting the whole phrase in double quotes fixes this, which I see you did but for some reason the quotes seem to be removed when ExecStart runs, i.e. checking systemctl status qubes-tunnel shows the command without the quotes I'm a little unclear: Did you get the link working like this? I have two fedora 26 templates, one was last updated over 10 days ago and the other updated today. The VPN link won't come up with the latter one... I did some tests and there seems to be an intermittent problem with qubes-firewall on fedora only. This can prevent openvpn from connecting. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4c4fdb4a-c529-8cd2-7c68-8fd282a9efad%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 05/06/2018 05:24 PM, morlan.aus...@gmail.com wrote: Worked great for me with Qubes 4.0 and Fedora 26. I'm unclear on how to use sys-firewall now though. Should it be sys-net -> sys-firewall -> VPN -> App? Thanks. That arrangement is OK. But you can take sys-firewall out of the path (connect VPN directly to sys-net) because a VPN qube configured with qubes-tunnel still does the job of a regular proxy qube (like sys-firewall). -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/95d94842-6f3a-6022-dadb-c97bf040ebfb%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 05/12/2018 03:11 PM, JonHBit wrote: I've updating to 1.4beta4 and switched templates from debian-9 to fedora-28, but I'm getting the same error - also it seems like openvpn flag defaults changed, as it now returns an error for the up and down arguments Did you mean fedora-26? Specifically, it parses /usr/lib/qubes/qtunnel-connect up as 2 arguments instead of 1; putting the whole phrase in double quotes fixes this, which I see you did but for some reason the quotes seem to be removed when ExecStart runs, i.e. checking systemctl status qubes-tunnel shows the command without the quotes I'm a little unclear: Did you get the link working like this? I have two fedora 26 templates, one was last updated over 10 days ago and the other updated today. The VPN link won't come up with the latter one... -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d555adea-6f74-1ebb-36ed-d84a8f124bf6%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On Thursday, April 26, 2018 at 6:38:41 PM UTC-7, Chris Laprise wrote: > On 04/26/2018 05:29 PM, JonHBit wrote: > > On Wednesday, April 18, 2018 at 5:36:37 AM UTC-4, Chris Laprise wrote: > >> On 04/17/2018 11:42 PM, Chris Laprise wrote: > >>> On 04/17/2018 09:20 PM, JonHBit wrote: > >> > Worked well for me using a debian-9 template & commit 4e96ca8, only > trouble was that my VPN provider's configs used > /etc/update-resolv-conf and failed silently when it was missing - so > shipping it with qubes-tunnel and installing it by default may be > helpful. > >>> > >>> Thanks! > >>> > >>> This issue just became apparent to me when another user reported it. The > >>> underlying problem is a bug (or several bugs) in openvpn's option parsing: > >>> > >>> https://github.com/tasket/Qubes-vpn-support/issues/19 > >>> > >>> It only shows up when the config specifies its own scripts which is > >>> rare. I'm trying out a workaround now which involves: > >>> > >>> 1. Removing the paths in the up & down options in the .service file. > >>> > >>> 2. Moving the up & down options to the beginning just after the openvpn > >>> command. > >>> > >>> 3. Symlinking the up/down script from /usr/lib/qubes to the > >>> /rw/config/qtunnel dir. > >>> > >>> Hopefully this will override the config's up/down settings as intended. > >> > >> I had to use a different approach but it should be fixed now. Update it > >> by copying new version to template and running installer. Then you'll > >> need to remove the 'qubes-tunnel' Qubes service for the proxyVM and add > >> 'qubes-tunnel-openvpn' instead. > >> > >> > >> -- > >> > >> Chris Laprise, tas...@posteo.net > >> https://github.com/tasket > >> https://twitter.com/ttaskett > >> PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 > > > > Hi Chris, > > > > Good to see the update! > > > > However I think that's a separate issue; what I'm referencing is these > > lines in my .ovpn config: > > > > script-security 2 > > up /etc/openvpn/update-resolv-conf > > down /etc/openvpn/update-resolv-conf > > > > The VPN installer script will normally download this if it's missing - used > > to change the DNS server to the VPN-provided one. > > > > The script is here: > > https://raw.githubusercontent.com/ProtonVPN/scripts/master/update-resolv-conf.sh > > > > After adding it everything worked well. > > The update will replace those lines because they should be overridden > with the Qubes-specific DNS handling. If dnat isn't setup for DNS then > those packets could get mis-routed. > > You can check the dnat rules (which should have some address other than > 10.139.1.x after connecting) with this: > > sudo iptables -v -t nat -L PR-QBS > > My guess why it might work with incorrect dnat addresses is that your > VPN provider takes the step of re-assigning DNS destination addresses to > its own. But this is unorthodox so I wouldn't count on it. > > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 I've updating to 1.4beta4 and switched templates from debian-9 to fedora-28, but I'm getting the same error - also it seems like openvpn flag defaults changed, as it now returns an error for the up and down arguments Specifically, it parses /usr/lib/qubes/qtunnel-connect up as 2 arguments instead of 1; putting the whole phrase in double quotes fixes this, which I see you did but for some reason the quotes seem to be removed when ExecStart runs, i.e. checking systemctl status qubes-tunnel shows the command without the quotes -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/eeefbba3-565f-443b-b80f-04353cd975a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
Strangest thing, I did a fresh installation of Qubes and now I can't get this to work again? Sorry for the basic question but is there something I need to do to the fresh debian template after installation? I am trying to eliminate all possible issues but to install OpenVPN to the debian template: 1) I simply allow access to TOR or a network to get OpneVPN 2) Type : sudo apt-get install openvpn I am having the same issue with Fedora as well, could there be another reason for this not connecting? I get the "Waiting for connection" message but I don't get the "Link is up"... Thanks for any thoughts... V -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/43185fcd-09f6-470c-acab-23553d7af623%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
Sorry correction to my notes: Using qTunnel: For Debian proxy, add OpenVPN package to your VPN template: su apt-get update && apt-get install openvpn unzip Download and transfer file to template https://github.com/tasket/qubes-tunnel.git cd “Then drag downloaded file into terminal from tasket” sudo bash ./install Create proxy AppVM using VPN template: sys-VPN Colour: Green Provides Network Checked connect to sys-net Launch settings - Checked Settings: Add files and Terminal to Applications Add “qubes-tunnel-openvpn” to services Move VPN config files to new proxy AppVM Open proxy AppVM terminal: sudo mkdir /rw/config/qtunnel sudo /usr/lib/qubes/qtunnel-setup --config Enter VPN name and password sudo mv “Then highlight the .pem, .crt and config file (renamed to xx.ovpn)” /rw/config/qtunnel Optional - Change config DNS: setenv tunnel_dns '208.67.222.222 208.67.220.220' cd /rw/config/qtunnel sudo ln -s xx.ovpn qtunnel.conf (xx is the VPN client config) Restart AppVM...look for “Links is up” pop-up https://github.com/tasket/qubes-tunnel -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4bf9dd58-16af-48e7-b372-5c819946d402%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
Here are my notes/instructions I made based on yours, I drag and drop some files into terminal(vs purely command lines): Using qTunnel: For Debian proxy, add OpenVPN package to your VPN template: su apt-get update && apt-get install openvpn unzip Download and transfer file to template https://github.com/tasket/qubes-tunnel.git cd “Then drag downloaded file into terminal from tasket” sudo bash ./install Create proxy AppVM using VPN template: sys-VPN Colour: Green Provides Network Checked connect to sys-net Launch settings - Checked Settings: Add files and Terminal to Applications Add “qubes-tunnel-openvpn” to services Move VPN config files to new proxy AppVM Open proxy AppVM terminal: sudo mkdir /rw/config/qtunnel sudo /usr/lib/qubes/qtunnel-setup --config Enter VPN name and password sudo mv “Then highlight the .pem, .crt and config file (renamed to “openvpn-client.ovpn)” /rw/config/qtunnel Optional - Change config DNS: setenv tunnel_dns '208.67.222.222 208.67.220.220' cd /rw/config/qtunnel sudo ln -s xx.ovpn qtunnel.conf (xx is the VPN client config) Restart AppVM...look for “Links is up” pop-up https://github.com/tasket/qubes-tunnel -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/81279605-3256-4e42-a2c4-c62337fcfdf6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
Adding this to my config: setenv tunnel_dns '208.67.222.222 208.67.220.220' instead of: setenv vpn_dns '208.67.222.222 208.67.220.220' worked. Both http://welcome.opendns.com/ and https://www.dnsleaktest.com/ show that OpenDNS are being used. I am more then happy to help test, I was planning to make the shift but my DNS wasn't working...all good now. Thanks for the help... I'll move my sys-VPNs to this new project...I was just reluctant to make the move as my DNS was not showing correct. All good now! Thanks again...if anything comes up I'll report back. If you want me to try something more then happy to help... Thx -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3bba2bdb-0253-4283-9be4-d8ce097e261a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 04/29/2018 10:14 PM, vel...@tutamail.com wrote: I just tried this version in 4.0 in the template. Some notes feedback: 1) When I tried changing the DNS to OpenDNS in my config file: setenv vpn_dns '208.67.222.222 208.67.220.220' I then went to: http://welcome.opendns.com/ It failed and informed me I was not using OpenDNS. -- Using debian 9, link indicates "Link is up", I get internet connection, https://www.dnsleaktest.com/ indicates my VPNs IP(despite "setenv vpn_dns '208.67.222.222 208.67.220.220'" in my vpn configuration) when I use this configuration... Its working when I try it. On dnsleaktest.com, your VPN provider IP should always appear on the first page. Then when you click on a test button it should show "OpenDNS, LLC" in the ISP column. The OpenDNS addresses will also show up in the log alongside "Using DNS servers...". The problem is you're mixing instructions from the two different projects. This thread is for testing qubes-tunnel but you said you were using Qubes-vpn-support (...but said you were using qtunnel* commands which belong to qubes-tunnel and are not correct for Qubes-vpn-support). If using 'qubes-tunnel-openvpn' service for your VPN VM, your configs should reside in /rw/config/qtunnel and the setenv line that you add will be: setenv tunnel_dns '208.67.222.222 208.67.220.220' - It would be nice, however, if you made the switch to qubes-tunnel to give us some testing feedback. :) -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c5f727a8-f577-5a1e-0b64-9fc9df47202f%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
Using debian 9, link indicates "Link is up", I get internet connection, https://www.dnsleaktest.com/ indicates my VPNs IP(despite "setenv vpn_dns '208.67.222.222 208.67.220.220'" in my vpn configuration) when I use this configuration... V -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/71b39261-7ea0-4259-a639-05a007c1cfa0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
Chris/Tasket, I am currently using this version: https://github.com/tasket/Qubes-vpn-support "Master version" I have this running in a proxy AppVM (Not in a template) Using PIA VPN service OpenDNS checks out OK I just tried this version in 4.0 in the template. Some notes feedback: 1) When I tried changing the DNS to OpenDNS in my config file: setenv vpn_dns '208.67.222.222 208.67.220.220' I then went to: http://welcome.opendns.com/ It failed and informed me I was not using OpenDNS. 2) The step 3. in the abbreviated instructions say to run: /usr/lib/qubes/qtunnel-setup --config However I had to run: sudo /usr/lib/qubes/qtunnel-setup --config I was able to get to the internetI didn't do any further testing. If you want me to try some things more then happy to help... Thanks again for the work. V -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b86bb2c7-91db-4c6f-aa4d-a9de218eea88%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 04/26/2018 05:29 PM, JonHBit wrote: On Wednesday, April 18, 2018 at 5:36:37 AM UTC-4, Chris Laprise wrote: On 04/17/2018 11:42 PM, Chris Laprise wrote: On 04/17/2018 09:20 PM, JonHBit wrote: Worked well for me using a debian-9 template & commit 4e96ca8, only trouble was that my VPN provider's configs used /etc/update-resolv-conf and failed silently when it was missing - so shipping it with qubes-tunnel and installing it by default may be helpful. Thanks! This issue just became apparent to me when another user reported it. The underlying problem is a bug (or several bugs) in openvpn's option parsing: https://github.com/tasket/Qubes-vpn-support/issues/19 It only shows up when the config specifies its own scripts which is rare. I'm trying out a workaround now which involves: 1. Removing the paths in the up & down options in the .service file. 2. Moving the up & down options to the beginning just after the openvpn command. 3. Symlinking the up/down script from /usr/lib/qubes to the /rw/config/qtunnel dir. Hopefully this will override the config's up/down settings as intended. I had to use a different approach but it should be fixed now. Update it by copying new version to template and running installer. Then you'll need to remove the 'qubes-tunnel' Qubes service for the proxyVM and add 'qubes-tunnel-openvpn' instead. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 Hi Chris, Good to see the update! However I think that's a separate issue; what I'm referencing is these lines in my .ovpn config: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf The VPN installer script will normally download this if it's missing - used to change the DNS server to the VPN-provided one. The script is here: https://raw.githubusercontent.com/ProtonVPN/scripts/master/update-resolv-conf.sh After adding it everything worked well. The update will replace those lines because they should be overridden with the Qubes-specific DNS handling. If dnat isn't setup for DNS then those packets could get mis-routed. You can check the dnat rules (which should have some address other than 10.139.1.x after connecting) with this: sudo iptables -v -t nat -L PR-QBS My guess why it might work with incorrect dnat addresses is that your VPN provider takes the step of re-assigning DNS destination addresses to its own. But this is unorthodox so I wouldn't count on it. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4bc0ca96-848c-adf5-05e0-d5dcdb7eda68%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On Wednesday, April 18, 2018 at 5:36:37 AM UTC-4, Chris Laprise wrote: > On 04/17/2018 11:42 PM, Chris Laprise wrote: > > On 04/17/2018 09:20 PM, JonHBit wrote: > > >> Worked well for me using a debian-9 template & commit 4e96ca8, only > >> trouble was that my VPN provider's configs used > >> /etc/update-resolv-conf and failed silently when it was missing - so > >> shipping it with qubes-tunnel and installing it by default may be > >> helpful. > > > > Thanks! > > > > This issue just became apparent to me when another user reported it. The > > underlying problem is a bug (or several bugs) in openvpn's option parsing: > > > > https://github.com/tasket/Qubes-vpn-support/issues/19 > > > > It only shows up when the config specifies its own scripts which is > > rare. I'm trying out a workaround now which involves: > > > > 1. Removing the paths in the up & down options in the .service file. > > > > 2. Moving the up & down options to the beginning just after the openvpn > > command. > > > > 3. Symlinking the up/down script from /usr/lib/qubes to the > > /rw/config/qtunnel dir. > > > > Hopefully this will override the config's up/down settings as intended. > > I had to use a different approach but it should be fixed now. Update it > by copying new version to template and running installer. Then you'll > need to remove the 'qubes-tunnel' Qubes service for the proxyVM and add > 'qubes-tunnel-openvpn' instead. > > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 Hi Chris, Good to see the update! However I think that's a separate issue; what I'm referencing is these lines in my .ovpn config: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf The VPN installer script will normally download this if it's missing - used to change the DNS server to the VPN-provided one. The script is here: https://raw.githubusercontent.com/ProtonVPN/scripts/master/update-resolv-conf.sh After adding it everything worked well. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/08de9d8f-d104-4b46-b2e2-e7bc3abe976d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 04/20/2018 11:14 AM, cicero wrote: On 04/20/18 04:58, Chris Laprise wrote: Since there's no connection information in the template -- only the VPN scripts & the OS are there -- templates don't affect configuration issues like different locations. In any case, you have a proxyVM which contains configurations for the connections to various sites, but each proxyVM connects to only one VPN remote site at a time. So to have two AppVMs routed through two different VPN sites, you need two proxyVMs (one for each AppVM). hmm, so I guess by installing the script in the Template(cloned), it would save me from having to re-run the script in the AppProxyVMs, that's it ? You wouldn't have to install it into proxyVMs. But there is still one script-running step when configuring a proxyVM with qubes-tunnel. https://github.com/tasket/qubes-tunnel But, if I'm just cloning the Original AppProxyVMs , to make a 2nd geolocation, doesn't seem like saves me any work by not having to re-run the script, as it is already in the cloned AppProxyVM ? If you clone an already configured proxyVM, no further configuration is required for the clone to connect to the same site. To change the site, you will only need to change the qtunnel.conf link. Do I have this correct? But, sometime in the future, a possible newer version will only run in a Template, but then the rest is about the same on configuration, ( a separate AppProxyVM for each location wanted , unless one wanted to manually change the symlink to change locations ? That's the intention, to make qubes-tunnel (child of Qubes-vpn-support) already available for use in the templates. This simplifies the setup process for users. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/357250d3-c88a-cff5-7bc2-b0dd2f4c8c04%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 04/20/18 04:58, Chris Laprise wrote: Since there's no connection information in the template -- only the VPN scripts & the OS are there -- templates don't affect configuration issues like different locations. In any case, you have a proxyVM which contains configurations for the connections to various sites, but each proxyVM connects to only one VPN remote site at a time. So to have two AppVMs routed through two different VPN sites, you need two proxyVMs (one for each AppVM). hmm, so I guess by installing the script in the Template(cloned), it would save me from having to re-run the script in the AppProxyVMs, that's it ? But, if I'm just cloning the Original AppProxyVMs , to make a 2nd geolocation, doesn't seem like saves me any work by not having to re-run the script, as it is already in the cloned AppProxyVM ? Do I have this correct? But, sometime in the future, a possible newer version will only run in a Template, but then the rest is about the same on configuration, ( a separate AppProxyVM for each location wanted , unless one wanted to manually change the symlink to change locations ? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5ea799d9-7554-78dd-d3a9-3ba259aaad96%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 04/20/2018 10:04 AM, cicero wrote: On 04/20/18 03:12, Chris Laprise wrote: On 04/20/2018 02:03 AM, cicero wrote: On 04/19/18 14:04, Chris Laprise wrote: On 04/19/2018 07:26 PM, john wrote: I installed this in a App/proxy 4.0 VM, as I am familiar with the 3.2 CLI VPN creation. I don't really understand how installing it in a Template or The Template(not cloning it 1st) would allow me to swich between geolocations ... So, I used the AppVM, then I simply cloned the 1st one created with the script and went into the PIA config file area and did rm -f ln -s to the network manager thing. and then recreated the ln -s to a new config file, which works , and Even wakes up from suspend (where in 3.2 it never did) ; However, If the AppVM using one of the VPN-foo as a netvm, and it is started, and I want to switch to another VPN-foo1 it doesn't work on the fly, I have to go and qvm-shutdown the AppVM and open it again, which is a big pain. I am often running out of RAM, and so try to just use one App-proxy-vpnVM , however , is this the expected behavior no switching vpn appvms on the fly ? IIRC this is a bug in the versions of Linux kernel that Qubes 4.0 uses. There is an issue but I can't locate it at the moment. So, I guess I'll learn to live with it , and try not to change VPNs buy buying some more expensive RAM :) But, I'm curious , If I install the new script in the Template/s , how would I switch VPN locations? Or would every AppVM based on that Template be locked into whatever geolocation's config file was symlinked to ? Templates don't affect your ability to set a custom location script. This is because the link that points from qtunnel.conf to any particular config is stored in each proxyVM under /rw/config/qtunnel. You can of course do one proxyVM setup, then clone it and change the link in each clone. BTW, thanks for trying it out! Chris, what I'm trying to say is, if it is recommended to install it in the Template or a cloned Template ; how then do I change the geolocation to two different locations, one for each of , say, two AppVMs ? Since there's no connection information in the template -- only the VPN scripts & the OS are there -- templates don't affect configuration issues like different locations. In any case, you have a proxyVM which contains configurations for the connections to various sites, but each proxyVM connects to only one VPN remote site at a time. So to have two AppVMs routed through two different VPN sites, you need two proxyVMs (one for each AppVM). This is not an absolute rule BTW. Its just how our current tools are most logically and safely configured. Conceivably you could rig a single proxyVM to safely handle more than one VPN connection. I could create symlinks in /rw/config/qtunnel? in the AppVMs ? or I understand that if this is integrated later, then I probably need to learn to use it in the Template now, to avoid more issues down the road, I don't really like cloning the Template too much, as Qubes, is already a challenge in its complexity To clarify... Cloning the template is recommended because the VPN software is still being tested. Its just a way to backup in case something in the modified template gets damaged. Cloning a proxyVM is a quick way to make additional VPN VMs that can connect to different VPN sites. eg: my current dracut emergency shell situation PS: seems I had an old Q3.2 in an enclosure, I was going to reformat but hadn't yet, and during a reboot it was in the USB drive, and this seems to have caused Q4.0 in efi installation to dump it's init to boot ; so do I go make a fedora live usb drive and try to mount and save it ? and lose all the configuration and restoring of 3.2 VMs or just reinstall Q4.0? Boot issues aren't my strong suit, but this sounds serious enough to start a separate thread for it. I have read some folks on here , whom when trying to go back to Q3.2 are having big issues, I don't really understand how efi works, my UEFI still says Qubes 3.1 for some reason (I think there are some gymnastics to try to get the EFI to update it's names but fear I'll lose the windows 10 install on the 2nd HD, etc etc . Strangely windows 10 "just works", but I digress . -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d77cce73-dcd9-d9fc-8c11-b21589a5a6d9%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 04/20/18 03:12, Chris Laprise wrote: On 04/20/2018 02:03 AM, cicero wrote: On 04/19/18 14:04, Chris Laprise wrote: On 04/19/2018 07:26 PM, john wrote: I installed this in a App/proxy 4.0 VM, as I am familiar with the 3.2 CLI VPN creation. I don't really understand how installing it in a Template or The Template(not cloning it 1st) would allow me to swich between geolocations ... So, I used the AppVM, then I simply cloned the 1st one created with the script and went into the PIA config file area and did rm -f ln -s to the network manager thing. and then recreated the ln -s to a new config file, which works , and Even wakes up from suspend (where in 3.2 it never did) ; However, If the AppVM using one of the VPN-foo as a netvm, and it is started, and I want to switch to another VPN-foo1 it doesn't work on the fly, I have to go and qvm-shutdown the AppVM and open it again, which is a big pain. I am often running out of RAM, and so try to just use one App-proxy-vpnVM , however , is this the expected behavior no switching vpn appvms on the fly ? IIRC this is a bug in the versions of Linux kernel that Qubes 4.0 uses. There is an issue but I can't locate it at the moment. So, I guess I'll learn to live with it , and try not to change VPNs buy buying some more expensive RAM :) But, I'm curious , If I install the new script in the Template/s , how would I switch VPN locations? Or would every AppVM based on that Template be locked into whatever geolocation's config file was symlinked to ? Templates don't affect your ability to set a custom location script. This is because the link that points from qtunnel.conf to any particular config is stored in each proxyVM under /rw/config/qtunnel. You can of course do one proxyVM setup, then clone it and change the link in each clone. BTW, thanks for trying it out! Chris, what I'm trying to say is, if it is recommended to install it in the Template or a cloned Template ; how then do I change the geolocation to two different locations, one for each of , say, two AppVMs ? I could create symlinks in /rw/config/qtunnel? in the AppVMs ? or I understand that if this is integrated later, then I probably need to learn to use it in the Template now, to avoid more issues down the road, I don't really like cloning the Template too much, as Qubes, is already a challenge in its complexity eg: my current dracut emergency shell situation PS: seems I had an old Q3.2 in an enclosure, I was going to reformat but hadn't yet, and during a reboot it was in the USB drive, and this seems to have caused Q4.0 in efi installation to dump it's init to boot ; so do I go make a fedora live usb drive and try to mount and save it ? and lose all the configuration and restoring of 3.2 VMs or just reinstall Q4.0? I have read some folks on here , whom when trying to go back to Q3.2 are having big issues, I don't really understand how efi works, my UEFI still says Qubes 3.1 for some reason (I think there are some gymnastics to try to get the EFI to update it's names but fear I'll lose the windows 10 install on the 2nd HD, etc etc . Strangely windows 10 "just works", but I digress . -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/31ebb291-809a-6267-64af-1771e5f7aaa6%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 04/20/2018 02:03 AM, cicero wrote: On 04/19/18 14:04, Chris Laprise wrote: On 04/19/2018 07:26 PM, john wrote: I installed this in a App/proxy 4.0 VM, as I am familiar with the 3.2 CLI VPN creation. I don't really understand how installing it in a Template or The Template(not cloning it 1st) would allow me to swich between geolocations ... So, I used the AppVM, then I simply cloned the 1st one created with the script and went into the PIA config file area and did rm -f ln -s to the network manager thing. and then recreated the ln -s to a new config file, which works , and Even wakes up from suspend (where in 3.2 it never did) ; However, If the AppVM using one of the VPN-foo as a netvm, and it is started, and I want to switch to another VPN-foo1 it doesn't work on the fly, I have to go and qvm-shutdown the AppVM and open it again, which is a big pain. I am often running out of RAM, and so try to just use one App-proxy-vpnVM , however , is this the expected behavior no switching vpn appvms on the fly ? IIRC this is a bug in the versions of Linux kernel that Qubes 4.0 uses. There is an issue but I can't locate it at the moment. So, I guess I'll learn to live with it , and try not to change VPNs buy buying some more expensive RAM :) But, I'm curious , If I install the new script in the Template/s , how would I switch VPN locations? Or would every AppVM based on that Template be locked into whatever geolocation's config file was symlinked to ? Templates don't affect your ability to set a custom location script. This is because the link that points from qtunnel.conf to any particular config is stored in each proxyVM under /rw/config/qtunnel. You can of course do one proxyVM setup, then clone it and change the link in each clone. BTW, thanks for trying it out! -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/52bbd116-5ccd-78a7-3423-b6952b2007c6%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 04/19/18 14:04, Chris Laprise wrote: On 04/19/2018 07:26 PM, john wrote: I installed this in a App/proxy 4.0 VM, as I am familiar with the 3.2 CLI VPN creation. I don't really understand how installing it in a Template or The Template(not cloning it 1st) would allow me to swich between geolocations ... So, I used the AppVM, then I simply cloned the 1st one created with the script and went into the PIA config file area and did rm -f ln -s to the network manager thing. and then recreated the ln -s to a new config file, which works , and Even wakes up from suspend (where in 3.2 it never did) ; However, If the AppVM using one of the VPN-foo as a netvm, and it is started, and I want to switch to another VPN-foo1 it doesn't work on the fly, I have to go and qvm-shutdown the AppVM and open it again, which is a big pain. I am often running out of RAM, and so try to just use one App-proxy-vpnVM , however , is this the expected behavior no switching vpn appvms on the fly ? IIRC this is a bug in the versions of Linux kernel that Qubes 4.0 uses. There is an issue but I can't locate it at the moment. So, I guess I'll learn to live with it , and try not to change VPNs buy buying some more expensive RAM :) But, I'm curious , If I install the new script in the Template/s , how would I switch VPN locations? Or would every AppVM based on that Template be locked into whatever geolocation's config file was symlinked to ? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2571bdf5-8e73-71ea-0c9c-825b909889bc%40riseup.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 04/17/2018 11:42 PM, Chris Laprise wrote: On 04/17/2018 09:20 PM, JonHBit wrote: Worked well for me using a debian-9 template & commit 4e96ca8, only trouble was that my VPN provider's configs used /etc/update-resolv-conf and failed silently when it was missing - so shipping it with qubes-tunnel and installing it by default may be helpful. Thanks! This issue just became apparent to me when another user reported it. The underlying problem is a bug (or several bugs) in openvpn's option parsing: https://github.com/tasket/Qubes-vpn-support/issues/19 It only shows up when the config specifies its own scripts which is rare. I'm trying out a workaround now which involves: 1. Removing the paths in the up & down options in the .service file. 2. Moving the up & down options to the beginning just after the openvpn command. 3. Symlinking the up/down script from /usr/lib/qubes to the /rw/config/qtunnel dir. Hopefully this will override the config's up/down settings as intended. I had to use a different approach but it should be fixed now. Update it by copying new version to template and running installer. Then you'll need to remove the 'qubes-tunnel' Qubes service for the proxyVM and add 'qubes-tunnel-openvpn' instead. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4123b1ac-7eaf-95f3-cb69-e01c86221770%40posteo.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: ANN: Testing new VPN code for Qubes
On 04/17/2018 09:20 PM, JonHBit wrote: On Tuesday, April 17, 2018 at 2:13:29 PM UTC-7, Chris Laprise wrote: Hello fellow Qubes users: Per issue 3503 the Qubes project would like to incorporate VPN features from Qubes-vpn-support -- which a number of you are already using -- into the Qubes 4.1 release. I've set up a new project "qubes-tunnel" to act as a staging area for testing and eventual forking into Qubes. It is nearly the same as Qubes-vpn-support except some names & paths are different... and install to template is required for obvious reasons :) . Project Link... https://github.com/tasket/qubes-tunnel Everyone with an available VPN service is welcome to try this out and report here on your results! - PS - Some of you will wonder if installing qubes-tunnel into an existing template already used for Qubes-vpn-support will cause a conflict; They will not conflict as long as the two services aren't enabled for the same ProxyVM(s). -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 Worked well for me using a debian-9 template & commit 4e96ca8, only trouble was that my VPN provider's configs used /etc/update-resolv-conf and failed silently when it was missing - so shipping it with qubes-tunnel and installing it by default may be helpful. Thanks! This issue just became apparent to me when another user reported it. The underlying problem is a bug (or several bugs) in openvpn's option parsing: https://github.com/tasket/Qubes-vpn-support/issues/19 It only shows up when the config specifies its own scripts which is rare. I'm trying out a workaround now which involves: 1. Removing the paths in the up & down options in the .service file. 2. Moving the up & down options to the beginning just after the openvpn command. 3. Symlinking the up/down script from /usr/lib/qubes to the /rw/config/qtunnel dir. Hopefully this will override the config's up/down settings as intended. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/43b11e07-760e-7357-566d-b74a926f4889%40posteo.net. For more options, visit https://groups.google.com/d/optout.
