On 2016-10-16 23:22, Marek Marczykowski-Górecki wrote:
On Sun, Oct 16, 2016 at 08:21:17PM +0200, Pawel Debski wrote:
Folks,
I'm planning R3.1 -> 3.2 upgrade and need explanation:
|sudo qubes-dom0-update --enablerepo=qubes*testing --releasever=3.2
qubes-release|
why do I need to enable
On Saturday, October 15, 2016 at 10:28:24 PM UTC-4, QubesOS User wrote:
> You mentioned some good points about QubesOS. One thing I definitely dislike
> about QubesOS (and that's no offense of course - it's simply unavoidable, and
> of course that's not the developers' fault - in contrast I
On Sunday, October 16, 2016 at 12:03:59 AM UTC-4, pleo...@gmail.com wrote:
> I dont know how to install it,im so stupid omg.Maybe like ProxyVM and route
> trafic by pFsense? but its no option to choice only fedora debian.WTF im so
> stupid.I dont know how to install it.
Its too complicated for
On Saturday, October 15, 2016 at 11:38:07 PM UTC-4, pleo...@gmail.com wrote:
> unikernel u mean this?
> http://roscidus.com/blog/blog/2016/01/01/a-unikernel-firewall-for-qubesos/
> i have installed it and work good.
ya thats what i was talking about, nice I'll have to try it out.
--
You
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, Oct 16, 2016 at 08:21:17PM +0200, Pawel Debski wrote:
> Folks,
>
> I'm planning R3.1 -> 3.2 upgrade and need explanation:
>
> |sudo qubes-dom0-update --enablerepo=qubes*testing --releasever=3.2
> qubes-release|
>
> why do I need to enable
Hello
Following the tutorial about anonymize MAC address, I have installed
debian 9, create a sys-net, assign a network controller but doesn't detect
no wifi.
How can I solve this issue?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To
Folks,
I'm planning R3.1 -> 3.2 upgrade and need explanation:
|sudo qubes-dom0-update --enablerepo=qubes*testing --releasever=3.2
qubes-release|
why do I need to enable testing repo? I thought that R3.2 has already
been released as stable.
Maybe I do not understand something. Please
You don't need to manually add the iptables rules. When enable the
'qubes-yum-proxy' on the VPNVM the rule to iptables is automatically added:
Chain PR-QBS-SERVICES (1 references)
pkts bytes target prot opt in out source destination
0 0 REDIRECT tcp
I basically need to add some static routes to access different parts of the
local network, otherwise the traffic destined to my internal network will be
tunneled through the VPN.
I've tried to add this via the NetworkManager which is what I intend, however
the routes, as soon as the VM is
