On Wednesday, August 7, 2019 at 9:45:51 AM UTC-4, Chris Laprise wrote:
>
> On 8/7/19 9:39 AM, thecodingn...@gmail.com wrote:
> >
> >
> > On Tuesday, August 6, 2019 at 9:45:51 PM UTC-4, Chris Laprise wrote:
> >
> > On 8/6/19 7:57 PM, thecodingn...@gmail.com wrote:
> > > Running
On Tuesday, August 6, 2019 at 9:45:51 PM UTC-4, Chris Laprise wrote:
>
> On 8/6/19 7:57 PM, thecodingn...@gmail.com wrote:
> > Running ```sudo iptables -C FORWARD -o eth0 -j DROP``` throws an error
> > itself: iptables: Bad rule (does matching rule exist in that chain?). So
> > how can this
Running ```sudo iptables -C FORWARD -o eth0 -j DROP``` throws an error
itself: iptables: Bad rule (does matching rule exist in that chain?). So
how can this ever run if running it directly in bash from inside the appvm
does not work?
On Tuesday, August 6, 2019 at 7:47:53 PM UTC-4,
So apparently the tasket repo does not work out of the box (obviously).
Working through everything, now ran into an unfamiliar issue: pre-start
firewall check fails with status 1. Looking at the code it seems the
firewall rules are not there although firewall service is running actively.
Hello,
I have a commercial VPN that does not have any options to pass a DNS
handling script. Following how i setup my qubes: sys-net <> sys-firewall <>
VPN <> AppVm. As you see here I've setup a service vm named VPN where the
VPN software is installed. I've also tried the other variation which
