On Friday, April 19, 2019 at 12:19:28 PM UTC+1, Claudio Chinicz wrote: > On 19/04/2019 12:05, Thomas Leonard wrote: > > On Thursday, April 18, 2019 at 9:53:25 AM UTC+1, Claudio Chinicz wrote: > >> Hi All, > >> > >> Once again I turn to the Qubes Community to ask for help. > >> > >> I have a Mirage Firewall VM that works with HVM (Linux Mint) and > >> Debian/Fedora template-based PVMs. > >> > >> My Windows 10 HVM, which works just fine through sys-firewall > >> (copy/paste and file sharing with other VMs dont, but I can live with it). > >> > >> I've tried setting up networking manually by adding its IP, mask and > >> gateway and rebooting but it did not work. It works with DHCP instead > >> when getting network through sys-firewall. > >> > >> I've followed all the ideas from here > >> (https://www.windowscentral.com/how-regain-internet-access-after-installing-update-windows-10) > >> and it still did not work. > >> > >> One last piece of information, my Windows 10 Pro was successfully > >> activated using a key I provided. > >> > >> Any ideas? This is not critical, since I can continue using > >> sys-firewall, but would love to free some memory by using Mirage. > > > > There might be clues in the firewall VM's logs. You can see them with Qubes > > Manager (right-click on mirage-firewall and choose Logs -> > > guest-mirage-firewall.log). Open the logs just after booting Windows and > > seeing that networking doesn't work and look at the end. > > > > You can also do "sudo xl console mirage-firewall" in dom0 to follow the > > logs and then boot Windows and watch for new entries. > > > > Hi Thomas, > > Thanks in advance. Please see below logs from guest-mirage-firewall.log. > My Windows VM is 10.137.0.21. > > What really surprises me is why I does not work even if I set my > ip/mask/gateway as it works with Linux Mint? What's different with Windows? > > Best Regards, > > Claudio > > 2019-04-18 11:20:11 -00:00: INF [qubes.db] got update: > "/mapped-ip/10.137.0.21/visible-ip" = "10.137.0.21" > 2019-04-18 11:20:11 -00:00: INF [qubes.db] got update: > "/mapped-ip/10.137.0.21/visible-gateway" = "10.137.0.23" [...] > 2019-04-18 11:20:22 -00:00: INF [client_eth] who-has 10.137.0.1? > 2019-04-18 11:20:22 -00:00: INF [client_eth] unknown address; not responding
(continued at https://github.com/mirage/qubes-mirage-firewall/issues/56) -- 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/90a21fd2-ae0b-4963-86ac-4c91155e7112%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.