Not connected, Your IP: 3.16.66.206
Online: 22331 users - 238988 Mbit/s total BWSearch the Community
Showing results for 'qubes'.
Found 13 results
-
I'm experimenting with Eddie in Standalone qubes VM. It's installed but when network lock is NOT enabled it's stuck at "Checking route IPv6" when connecting. I've tried setting it to use only IPv4 in Networking>Internet protocol used for connection but it still gets stuck at the same. When network lock is enabled the eddie client itself connects fine and internet is via the VPN in that cube, but then I can't make the other qubes connect through that cube even if I've enabled "Allow lan/private" in "Netowork Lock" and even whitelisted the specific cube internal IP address. So either way I can't make it usable in qubes. -
Hello, I was trying to run eddie in a proxy vm in qubes, something like "browser vm --> eddie vm --> net vm", but eddie seems to modify routing table so that proxy doesn't route traffic downstream from a "browser vm". How would I need to modify the routing table to make eddie route traffic from "browser vm" to airvpn gateway with network lock enabled? I attached the system report of my configuration, where 10.138.37.231 is a browser vm, 10.138.35.206 is a net vm. system report.txt
-
I cannot have eddie's netlock feature working in a qube in Qubes OS 4. When trying to enable it within eddie-ui, I get a pop-up "Exception: Unable to initialize iptable_filter module". The same with the cli: $ eddie-ui -cli -netlock (...) Activation of Network Lock - Linux iptables Exception: Unable to initialize iptable_filter module (...) This behavior was observed both in a Debian 10 qube and in a Fedora 32 qube. I don't get this error in a Debian 10 installed over bare metal. eddie ver. 2.18.9
-
I've managed to run Eddie client in it's own VM on qubes fine and route other qubes through it. They have ping to IPs but can't resolve domains. I've experiment with the DNS settings but haven't found a way to make other cubes resolve domains when using the VM with Eddie as networking. I don't know much about networking so I'm hoping someone will point me to something obvious I might have been missing.
-
Qubes OS is security focused OS. I was wondering if eddie can be ran on their network-vpn domain and if there are anything different or special when running it like that?
-
Qubes offers great protection of your privacy. First, since everything is compartmentalized. a compromised browser/PDF reader etc will not give the attacker access to the rest of your system and sensitive files. Secondly, the networking system and ProxyVM's make it very easy to route your(or part of your) traffic through VPN/Tor, and if the VM is compromised, it cannot obtain your real IP address since all its traffic is routed through the ProxyVM. Mullvad has already donated to Qubes OS. They have a decentralized bitcoin fund (https://www.qubes-os.org/news/2016/07/13/qubes-distributed-fund/) and are also on Open Collective(https://opencollective.com/qubes-os) which offers great transparency and pays the individual developers directly.
-
Hello. What do you think would produce the best balance between security and speed? 1. Running AirVPN's client 'Eddie' in sys-netVM. 2. Putting AirVPN's OpenVPN config into Turris Omnia 2 GB router. 3. Setting up a VPN gateway in Qubes as described in Qubes' docs. Hardware: Asus »Zenbook«, Intel i5-5200U, 2.20 GHz, 12 GB RAM. Any hints and ideas are very much appreciated. Best regards. PS: This also refers to the very interesting topic: https://airvpn.org/topic/22471-qubes-whonixtor-airvpn-world/?hl=qubes -
Is there any guide on how to use Eddie on qubes 4?
-
Hey all, new to AirVPN. I've been trying to get the above setup working (only a day left until I have to renew) and it's definitely been a challenging one. Essentially, I'd like to have Me -> Tor -> AirVPN within a highly secure Operating System, and at the moment Qubes/Whonix seem to fit that description best as actively developed OS'. I have been trying to follow this guide: https://www.qubes-os.org/doc/vpn/#set-up-a-proxyvm-as-a-vpn-gateway-using-iptables-and-cli-scripts , installing the AirVPN client on the ProxyVM. and using it as a bridge between whonix workstation and wonix gateway however AirVPN fails to connect to any servers. Using the browser inside the AirVPN VM does work however, showing the Tor address. An easy to follow guide from Air on how to set up something like this would be awesome. I read this as well: https://airvpn.org/tor/ but if I'm being honest I wasn't sure how to apply the concepts in that article to Qubes/Whonix. I'm also open to suggestions on an easier method of achieving my goal of secure OS + Tor/VPN, even if it means using a different OS. Thanks.
-
I'm a complete noob with Linux. I have absolutely no idea about any of the command line. I've tried using the Quebs documentation, but it's clearly written for people who know what they are doing, as it doesn't say how to do the things, just that they have to be done. For one, I have no idea how to get the Airvpn config file into the relevant folders and even if I could get them there, I don't know what to do with them because the documentation just says "Set up your VPN as described in the NetworkManager documentation linked above." Well, I don't see that documentation. I really have no idea what to do. Any help is appreciated.
-
Hello, i am trying to configure AirVPN as ProxyVM(debian 8) in Qubes. Therefore i run the AirVPN Eddie Client within my ProxyVM. The connection to the AirVPN Server works fine but when i try to use the browser to enter a webpage, it doesn't work. AppVms aren't able to connect through the airvpn proxyvm(netvm) to the internet neither Does anyone has experience regarding setting up AirVPN in Qubes? Thank you for your help
-
So i downloaded the config files from AirVPN, set it to Linux, tried both UDP and TCP, in the network connection i did import saved VPN configuration and i save that. Then i try to connect to it and nothing. "connection failed because VPN connection timed out" I tried this both in sys-net, AppVM, and in proxyVM based on fedora-23. not sure what i'm doing wrong? -
This is old news from Thu 04 August 2016, but I though users would find this Security Vulnerability interesting. http://blog.quarkslab.com/xen-exploitation-part-3-xsa-182-qubes-escape.html#id24
