> I believe that is indeed the aim.
> You can either set to 255.255.255.0 or add specific route, as you have
> done. (Did you set a return route on the destination also?)
The return route is automatically added to the Proxy with the vif-route-qubes,
and the destination send all traffic to the
On Mon, Oct 08, 2018 at 03:27:43AM -0700, 3mp...@gmail.com wrote:
> On Tuesday, September 25, 2018 at 9:24:08 PM UTC+2, 3mp...@gmail.com wrote:
> > > Some obvious questions.
> > >
> > > You say the interface is correctly configured.
> > > Do you have any routes set in the Windows box?
> > > Do
On Tuesday, September 25, 2018 at 9:24:08 PM UTC+2, 3mp...@gmail.com wrote:
> > Some obvious questions.
> >
> > You say the interface is correctly configured.
> > Do you have any routes set in the Windows box?
> > Do you see traffic outbound on the 10.137.0.50 iface?
> >
> > If you sniff traffic
> Some obvious questions.
>
> You say the interface is correctly configured.
> Do you have any routes set in the Windows box?
> Do you see traffic outbound on the 10.137.0.50 iface?
>
> If you sniff traffic inbound on the vif attached to the Windows HVM, do
> you see anything there? (I mean
On Mon, Sep 24, 2018 at 05:40:16AM -0700, 3mp...@gmail.com wrote:
> Hi,
>
> I’m still working on my Qubes 4.0 migration and I’m trying to connect a
> Windows 10 XL created VM to Qubes Networking by adding this kind of line in
> the hvm file :
>
> vif = [ 'mac=00:16:3e:5e:6d:11,model=e1000,
>
Hi,
I’m still working on my Qubes 4.0 migration and I’m trying to connect a Windows
10 XL created VM to Qubes Networking by adding this kind of line in the hvm
file :
vif = [ 'mac=00:16:3e:5e:6d:11,model=e1000,
ip=10.137.0.50,script=vif-route-qubes,backend=sys-vpn’ ]
The backend is a
