On Thursday, January 7, 2021 at 9:24:44 AM UTC [email protected] wrote: > On 1/6/21 6:11 PM, Ulrich Windl wrote: > > On 1/3/21 2:24 PM, haaber wrote: > > ... > >>> Maybe nmap causes the mirage death. That wouldn't be a good job by > >>> mirage though and should be reported as bug to the dev. > >> I thought that, too. How would verify it is really nmap? As a test, I > >> scanned two phones in my wifi (in the same dispVM), without any > trouble, > >> using the same command. I re-scanned the offensive object, 181 seconds > >> later mirage is dead again. Fascinating. > > > > Are there logs (the famous "last words")? > > (my) mirage does not log. It has a fixed size of 32 MB, not much space > for logging .. and dom0 has no useful info on that incident. >
It should log to the console, which is recorded by dom0 in guest-mirage-firewall.log (you can also get to it via qubes-manager IIRC). Most likely it ran out of memory adding NAT entries for all the ports. Is this the current release version (using mini-os and PV) or the Git version (using solo5 and PVH)? The solo5 version has some problems with memory at the moment (https://github.com/mirage/qubes-mirage-firewall/issues/120 - seems to be reporting inaccurate heap stats). -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/37174eba-4570-4b26-a002-acac85aa62d2n%40googlegroups.com.
