On Wednesday, 28 February 2018 17:41:06 UTC, thorsten...@gmail.com wrote:
> > Could you try this:
> > qvm-prefs sys-firewall | grep netvm
> > it should say sys-net? Y/N
>
> yes, result is sys-net
>
>
> > Even if it states sys-net, let's try to force it again
> > qvm-prefs sys-firewall -s netvm
> Could you try this:
> qvm-prefs sys-firewall | grep netvm
> it should say sys-net? Y/N
yes, result is sys-net
> Even if it states sys-net, let's try to force it again
> qvm-prefs sys-firewall -s netvm sys-net
that command did not work due to wrong syntax, so I did:
qvm-prefs --set
On Tuesday, 27 February 2018 23:48:27 UTC, thorsten...@gmail.com wrote:
> A friend was using my PC and forgot to logout, so I accidently posted with
> his account. So here it goes again:
>
> > This is probably just because it tries to resolve the IPs and DNS times
> > out. if you use netstat
A friend was using my PC and forgot to logout, so I accidently posted with his
account. So here it goes again:
> This is probably just because it tries to resolve the IPs and DNS times out.
> if you use netstat -nr, it should be fast.
Yes, using "netstat -nr" I get a result immediately in
> This is probably just because it tries to resolve the IPs and DNS times out.
> if you use netstat -nr, it should be fast.
Yes, using "netstat -nr" I get a result immediately in sys-firewall:
Destination Gateway Genmask Flags MSS Window irtt
Iface
0.0.0.0
On Tuesday, 27 February 2018 18:46:52 UTC, thorsten...@gmail.com wrote:
> > Can you also try doing this against the template you're using for your
> > sys-firewall?
> >
> > qvm-features fedora-26-minimal qubes-firewall 1
>
> I did this and restarted everything, no difference.
>
>
> > Yes
> Can you also try doing this against the template you're using for your
> sys-firewall?
>
> qvm-features fedora-26-minimal qubes-firewall 1
I did this and restarted everything, no difference.
> Yes probably. For reference, to check (or enable):
> - go to start menu/System Tools/Qube Manager
On Monday, 26 February 2018 23:17:41 UTC, Thorsten Schierer wrote:
> Ok, I set up 2 new VMs (sys-net and
> sys-firewall) in case something went wrong during the setup, but the
> result was the same as before.
>
> Not sure how to enable the
> clocksync service in sys-net (fedora-26 template)
On Mon, February 26, 2018 11:17 pm, Thorsten Schierer wrote:
>
> So it seems like as soon as I create a new VM with "provides network"
> checked, it can not use the network connection of sys-net. Any other VM
> that does not provide network ifself can use sys-net directly and works
> fine. I
Ok, I set up 2 new VMs (sys-net and sys-firewall) in case something went
wrong during the setup, but the result was the same as before.
Not sure how to enable the clocksync service in sys-net (fedora-26
template) but the date/time settings are correct, so I assume it already is
syncing correctly.
On Monday, 26 February 2018 03:48:29 UTC, thorsten...@gmail.com wrote:
> I installed Qubes 4.0-rc4 and have a problem with my internet connection.
> sys-net itself has a working internet connection but sys-firewall does not.
> No need to mention that every other VM that uses sys-firewall as
11 matches
Mail list logo