On Sunday, May 5, 2019 at 4:29:11 PM UTC+1, Marek Marczykowski-Górecki wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Sun, May 05, 2019 at 05:51:28AM -0700, tal...@gmail.com wrote:
> > On Sunday, May 5, 2019 at 1:15:12 PM UTC+1, Marek Marczykowski-Górecki
> > wrote:
> > >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, May 05, 2019 at 05:51:28AM -0700, tal...@gmail.com wrote:
> On Sunday, May 5, 2019 at 1:15:12 PM UTC+1, Marek Marczykowski-Górecki wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > On Sun, May 05, 2019 at 03:19:50AM
On Sunday, May 5, 2019 at 1:15:12 PM UTC+1, Marek Marczykowski-Górecki wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Sun, May 05, 2019 at 03:19:50AM -0700, tal...@gmail.com wrote:
> > Hi,
> >
> > I'm trying to find out why HVM qubes using DHCP don't work with
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sun, May 05, 2019 at 03:19:50AM -0700, tal...@gmail.com wrote:
> Hi,
>
> I'm trying to find out why HVM qubes using DHCP don't work with
> mirage-firewall (https://github.com/mirage/qubes-mirage-firewall/issues/56).
>
> The process seems to go
Hi,
I'm trying to find out why HVM qubes using DHCP don't work with mirage-firewall
(https://github.com/mirage/qubes-mirage-firewall/issues/56).
The process seems to go like this:
1. The HVM qube makes a DHCP request over its emulated network device.
2. The DHCP server in the stub domain
