On 10/06/2017 01:41 PM, 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 to be used
solely by your special single vm?
Yes I
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
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
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
>
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
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
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
> 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
>