Re: [qubes-users] How to solve ProxyVM (sys-firewall) becomming non-functional at runtime
Am 10/13/2016 um 04:12 PM schrieb Manuel Amador (Rudd-O): On 10/11/2016 09:42 AM, Robert Mittendorf wrote: Hey folks, sometimes the sys-firewall (more likely a service within it) crashes and does no longer allow connected VMs to resolve DNS. The ProxyVM must be the responsible entity, because the connection will be fine again If I restart the sys-firewall. You're onto it. I think I fixed this yesterday: https://github.com/QubesOS/qubes-core-agent-linux/pull/20 Quick-reading you link I dont think that this is the issue. My obervation is that it happens after several hours/days of a flawlessly working ProxyVM, not at boot. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c1fd7dc8-e572-897c-7ef8-215cd6a04479%40digitrace.de. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] How to solve ProxyVM (sys-firewall) becomming non-functional at runtime
On 10/11/2016 09:42 AM, Robert Mittendorf wrote: > Hey folks, > > sometimes the sys-firewall (more likely a service within it) crashes > and does no longer allow connected VMs to resolve DNS. > The ProxyVM must be the responsible entity, because the connection > will be fine again If I restart the sys-firewall. You're onto it. I think I fixed this yesterday: https://github.com/QubesOS/qubes-core-agent-linux/pull/20 > -- Rudd-O http://rudd-o.com/ -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ce32fd1c-6f16-d434-d80a-4dca00c387ba%40rudd-o.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] How to solve ProxyVM (sys-firewall) becomming non-functional at runtime
Hey folks, sometimes the sys-firewall (more likely a service within it) crashes and does no longer allow connected VMs to resolve DNS. The ProxyVM must be the responsible entity, because the connection will be fine again If I restart the sys-firewall. Restarting the ProxyVM is tedious, as you cannot simple restart it when running (App)VMs are attached. You have to change the NetVM setting of every running connected AppVM (or shut them down) in order to restart the sys-firewall. This does not happen very often, just once, twice a month - but is there a less tedious way to fix this? like a shell command to restart the corresponding service in the sys-firewall? One could use an intermediate proxy, so you have to change only the NetVM of a single connected "App"VM - but what if the same problem occurs with that additional ProxyVM What is the problem with restarting a connected ProxyVM anyway? Yes, there should be a warning - but it should be possible to bypass this warning I think. thanks for reading, Robert -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a706c75b-1aa9-18a3-9c35-6187c1087544%40digitrace.de. For more options, visit https://groups.google.com/d/optout.
