Re: [qubes-users] Possible to add second interface to sys-firewall?

2017-10-06 Thread Mike Keehan
On Fri, 6 Oct 2017 10:20:18 -0400 Ed wrote: > What I would like to do is add a second IP to both sys-firewall and > sys-net so that I can NAT traffic from one of my VM's in/out through > these IP's. So what I end up with is two IP's on sys-net, one > handling all the

[qubes-users] Re: Possible to add second interface to sys-firewall?

2017-10-06 Thread filtration
Assuming you mean a physical interface. -- 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

[qubes-users] Re: Possible to add second interface to sys-firewall?

2017-10-06 Thread Ed
On 10/06/2017 12:14 PM, filtration wrote: Can you create another sys-net chain with the second interface? You could keep things isolated without scripting. Assuming you are using Qubes 3.2, the interface could be assigned to sys-net-2 via VM Settings->Devices. Looks like you and both Mike

Re: [qubes-users] Re: Possible to get usable Win7 gui?

2017-10-06 Thread mathdegiovani
Hello, > I work around the issue by using Remmina (or other RDP client) in an > appVM, and allowing IP forwarding in the firewall vm. This solution does > not suffer from increasing lag, and should be usable for everything > except gaming. See instructions here: > Remmina indeed seems to make

[qubes-users] Re: Possible to add second interface to sys-firewall?

2017-10-06 Thread Ed
On 10/06/2017 12:10 PM, Mike Keehan wrote: Wouldn't it be possible to add a second Firewall VM to be used solely by your special single vm? Yes I believe this would def work, and also should be automatic/reliable across reboots, but I was really hoping to not give up 2-4GB of RAM just for

[qubes-users] Re: Possible to add second interface to sys-firewall?

2017-10-06 Thread filtration
> What I would like to do is add a second IP to both sys-firewall and > sys-net so that I can NAT traffic from one of my VM's in/out through > these IP's. So what I end up with is two IP's on sys-net, one handling > all the traffic for most of my VM's, the other handling traffic for one >

[qubes-users] Possible to add second interface to sys-firewall?

2017-10-06 Thread Ed
What I would like to do is add a second IP to both sys-firewall and sys-net so that I can NAT traffic from one of my VM's in/out through these IP's. So what I end up with is two IP's on sys-net, one handling all the traffic for most of my VM's, the other handling traffic for one specific VM.

Re: [qubes-users] Re: Possible to add second interface to sys-firewall?

2017-10-06 Thread Unman
On Fri, Oct 06, 2017 at 03:41:26PM -0400, Ed wrote: > On 10/06/2017 03:14 PM, Mike Keehan wrote: > > On Fri, 6 Oct 2017 12:17:26 -0400 > > Ed wrote: > > > > > On 10/06/2017 12:10 PM, Mike Keehan wrote: > > > > > > > > > > > Wouldn't it be possible to add a second Firewall VM

Re: [qubes-users] Re: Possible to add second interface to sys-firewall?

2017-10-06 Thread Mike Keehan
On Fri, 6 Oct 2017 12:17:26 -0400 Ed wrote: > On 10/06/2017 12:10 PM, Mike Keehan wrote: > > > > > Wouldn't it be possible to add a second Firewall VM to be used > > solely by your special single vm? > > > > Yes I believe this would def work, and also should be >

[qubes-users] Re: Possible to add second interface to sys-firewall?

2017-10-06 Thread Ed
On 10/06/2017 03:14 PM, Mike Keehan wrote: On Fri, 6 Oct 2017 12:17:26 -0400 Ed wrote: On 10/06/2017 12:10 PM, Mike Keehan wrote: Wouldn't it be possible to add a second Firewall VM to be used solely by your special single vm? Yes I believe this would def work, and

Re: [qubes-users] Re: Unable to uninstall or reinstall Whonix

2017-10-06 Thread Person
The Control Port is 9051. I’m not sure if that has anything to do with my problems. I chose Internal Relaying and started Tor through Arm, but it did not register that Tor was connected. I still received the bootstrap problem and the qrexec problem. -- You received this message because you

Re: [qubes-users] Qubes 3.2 dnsmasq update?

2017-10-06 Thread Unman
On Thu, Oct 05, 2017 at 12:41:32PM -0600, Ron Hunter-Duvar wrote: > On 10/05/2017 01:52 AM, Ilpo Järvinen wrote: > > On Wed, 4 Oct 2017, Ron Hunter-Duvar wrote: > > > > > Saw the news earlier today about the major dnsmasq vulnerabilities (remote > > > code execution), and already received the

Re: [qubes-users] Qubes 3.2 dnsmasq update?

2017-10-06 Thread Ron Hunter-Duvar
On October 6, 2017 5:05:49 PM MDT, Unman wrote: >On Thu, Oct 05, 2017 at 12:41:32PM -0600, Ron Hunter-Duvar wrote: >> On 10/05/2017 01:52 AM, Ilpo Järvinen wrote: >> > On Wed, 4 Oct 2017, Ron Hunter-Duvar wrote: ... >> > FC23 has been EOL'ed for long time, you should

Re: [qubes-users] Mac-Spoofing Doesn’t Work

2017-10-06 Thread Person
Cloning VMs is quite troublesome right now, so it is hard to update Fedora and Debian in order to use NetworkManager. -- 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

Re: [qubes-users] Error Creating Ubuntu VM in Qubes 3.2

2017-10-06 Thread Person
Once again, dom0 did not reply. I took this as a sign that the iso was successfully copied, but the Standalone VM did not register something to boot from and I could not find it in the dom0 filesystem again. This puzzles me, because I am sure that the file was originally at the exact location I

Re: [qubes-users] Mac-Spoofing Doesn’t Work

2017-10-06 Thread Chris Laprise
On 10/06/2017 11:26 PM, Person wrote: Cloning VMs is quite troublesome right now, so it is hard to update Fedora and Debian in order to use NetworkManager. You can easily install the Fedora 25 template that should already have the correct version of NM: $ sudo qubes-dom0-update