Thanks again for the help Chris...see my notes below: 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 <address>' in the config. There's a chance this might work.
- Unfortunately this didn't work, I entered the following: local 10.137.5.3 I was also able to find the IP in the Qubes Manager as an FYI, however I also ran the command in a terminal. 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). - It doesn't look like my VPN changed their TLS cert, downloaded a new config file and tried again fresh. 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. - I built a new VPN template with a new AppVM, I get the notification pop up but no connection. 3. Unlikely: Interference from malware, possibly residing in sys-net. - I built a new sys-net (by creating a new Qube, provide network access, attached my Network controller/wireless....not sure more is needed to setup a sys-net) but this didn't fix it. Whats strange is that the connection is showing up as allowed in my firewall log, which makes me think everything is working with the Tasket solution. I did notice a strange connection to port 137 (NetBIOS) in my firewall which could be related or the cause. I also recently saw an ssh attempt from within Qubes. 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? Thanks again Chris and Qubes for what you are doing... -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/40c4f041-5a78-41ae-b1f2-3b2e29714343%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
