On 12/09/2016 05:56 PM, Eva Star wrote:
On 12/07/2016 07:48 AM, Andrew David Wong wrote:
FWIW, `systemctl restart qubes-firewall` fixed it for me last time.
Today one my VM losses network 2 times. Every time I tried `systemctl
restart qubes-firewall` and it not fix the issue. It's looks like
On 12/07/2016 07:48 AM, Andrew David Wong wrote:
FWIW, `systemctl restart qubes-firewall` fixed it for me last time.
Today one my VM losses network 2 times. Every time I tried `systemctl
restart qubes-firewall` and it not fix the issue. It's looks like the
issue at VM. Maybe, fedora-25 will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-12-06 09:01, Eva Star wrote:
> On 12/04/2016 05:19 PM, Marek Marczykowski-Górecki wrote:
>> 3. Restart qubes-firewall service and see whether it helps:
>>
>> sudo systemctl restart qubes-firewall
>>
>
> One my VM loss network access
On 12/04/2016 05:19 PM, Marek Marczykowski-Górecki wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, Nov 30, 2016 at 09:19:06PM +0300, Eva Star wrote:
On 11/27/2016 02:04 AM, Marek Marczykowski-Górecki wrote:
Do you see some correlation with:
- starting/stopping another VM?
-
On 12/04/2016 05:19 PM, Marek Marczykowski-Górecki wrote:
More troubleshooting steps:
1. When problem appears, try in sys-firewall:
qubesdb-read /qubes-iptables-error
This should print last error of firewall reload. I guess it may be about
some DNS resolution failure (if any rule use DNS
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, Nov 30, 2016 at 09:19:06PM +0300, Eva Star wrote:
> On 11/27/2016 02:04 AM, Marek Marczykowski-Górecki wrote:
>
> > Do you see some correlation with:
> > - starting/stopping another VM?
> > - affected VMs have or not firewall rules?
> >
On 11/27/2016 02:04 AM, Marek Marczykowski-Górecki wrote:
Do you see some correlation with:
- starting/stopping another VM?
- affected VMs have or not firewall rules?
Also, check if restarting qubes-firewall service in sys-firewall helps
(and check it status first).
Seems I have the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-11-26 09:42, Andrew David Wong wrote:
> A strange networking problem just started in the past day or so:
> [...]
Thanks for the tips, Jean-Philippe, Marek, and Chris!
On 2016-11-26 11:26, Jean-Philippe Ouellet wrote:
>> I'd start with:
On 11/26/2016 12:42 PM, Andrew David Wong wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
A strange networking problem just started in the past day or so:
Every few hours, around 2/3 of my VMs will suddenly lose network
access. I can still ping websites from sys-net and sys-firewall,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, Nov 26, 2016 at 09:47:46AM -0800, Andrew David Wong wrote:
> On 2016-11-26 09:42, Andrew David Wong wrote:
> > A strange networking problem just started in the past day or so:
> >
> > Every few hours, around 2/3 of my VMs will suddenly lose
On Sat, Nov 26, 2016 at 2:25 PM, Jean-Philippe Ouellet wrote:
> On Sat, Nov 26, 2016 at 12:42 PM, Andrew David Wong wrote:
>> Any ideas for logs or tools I should check to find out what's
>> failing, or where it's failing?
>
> I'd start with: dmesg, ifconfig -a
On Sat, Nov 26, 2016 at 12:42 PM, Andrew David Wong wrote:
> Any ideas for logs or tools I should check to find out what's
> failing, or where it's failing?
I'd start with: dmesg, ifconfig -a -v, tcpdump, iptables-save.
--
You received this message because you are subscribed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-11-26 09:42, Andrew David Wong wrote:
> A strange networking problem just started in the past day or so:
>
> Every few hours, around 2/3 of my VMs will suddenly lose network
> access. I can still ping websites from sys-net and sys-firewall,
13 matches
Mail list logo