Hi All -
I think I got what I needed on my own. It just took a bit more reading about
the Qubes Firewall to figure out where to put the logging line. I was really
just looking to monitor outgoing traffic to see what rules I needed to add to
allow.
I do have one other question though.. Where
Using Qubes 4.0 in Whonix 14 template
When using curl, the -x (or --proxy) parameter accepts the address
(127.0.0.1:8082) that redirects to Qubes Updates proxy over RPC, and
returns what you would expect.
But with wget (which I think is a better choice than curl), setting the
http_proxy
> I got close to quitting Qubes since I was not able to get the wifi working
> properly but everything is working great right now.
Glad for you ;-) Although the proper solution is to get rid of
Broadcom in favor of something better (like Atheros ath9k), also for
the security reasons...
--
You
On Sun, Mar 10, 2019 at 07:35:32AM -0700, cmsch...@gmail.com wrote:
> Hi All -
>
> I think I got what I needed on my own. It just took a bit more reading about
> the Qubes Firewall to figure out where to put the logging line. I was really
> just looking to monitor outgoing traffic to see what
@cooloutac: I'm using Qubes 4.0 right now
@American Qubist 001: I'm sorry but I beg your pardon, could you please be more
specific? An example at least of what you mean by using different syntax
Could you also specify which repos you used?
--
You received this message because you are
