On 8/6/19 7:57 PM, thecodingninjaisb...@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 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, thecodingn...@gmail.com
wrote:
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. Executing the for loop in a standalone
bash throws:|
|
|
Fatal:can't open lock file /run/xtables.lock: Permission denied
|
The file is there, but i'm thinking this denial is purposeful and i
prob should not sudo the loop execution. Any advice?
FYI, the qubes lists discourage top-posting. Please reply at the bottom.
The firewall rules should be in
/rw/config/qubes-firewall.d/90_tunnel-restrict. If they're not, this may
indicate the setup steps were not followed through to completion (i.e.
if you installed to your template, but forgot step 4).
--
Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/8a77bc32-2dff-64f6-55fd-0f25acdf5faf%40posteo.net.