Re: [qubes-users] Re: IPv6 connectivity and qubes proxy VM

2017-01-15 Thread daltong defourne
On Sunday, January 15, 2017 at 8:23:27 AM UTC+3, Chris Laprise wrote:
> On 01/13/2017 04:34 PM, *@gmail.com wrote:
> > On Thursday, January 12, 2017 at 1:30:07 PM UTC-5, daltong defourne wrote:
> >> On Thursday, January 12, 2017 at 6:47:00 PM UTC+3, daltong defourne wrote:
> >>> Hi!
> >>> I've created a VPN proxyvm (debian-8 based) according to existing 
> >>> documentation (more or less - I'm using the VPN provider's standalone 
> >>> client because, in a VM, why not?)
> >>>
> >>> For IPv4 it works flawlessly.
> >>>
> >>> For IPv6 it does not work at all for the VMs "behind" the proxyvm (VPN's 
> >>> IPv6 support works for a browser launched within proxyvm itself, but any 
> >>> VM behind the proxyvm can only use IPv4)
> >>>
> >>> what's up?
> >>> Can it be helped?
> >> Found this commit.
> >> https://github.com/marmarek/qubes-core-agent-linux/commit/789eb511266d9e8bd812e40f952ec2bce6d7a414
> >>
> >> Managed to activate the qubes-ipv6 service (worked!) on the appvm, the 
> >> firewallvm before the proxyvm, and the proxyvm.
> >>
> >> No budge, IPv6 still missing in action :(
> > isn't ipv6 unsafe?  You sure this is not by design in qubes? lol.  I'm 
> > probably wrong don't mind me.
> 
> Maybe 'naive' is a better word for ipv6 addressing.
> 
> IIRC, ipv6 won't be officially supported until Qubes Release 4.
> 
> Chris

Well, since I plan to move IPv6 only through the VPN (explicitly forbidding 
forwarding via eth device a-la what is already done for ipv4 in "normal" 
qubes-vpn-proxyvm documentation to prevent leaks) there are no security/privacy 
issues for me (beyond risk associated with the VPN itself lol ;-) )

I kind of hoped we'll eventually see v6 in 3.2 too (isn't 3.2 "Qubes LTS"?) 
https://www.qubes-os.org/news/2016/09/02/4-0-minimum-requirements-3-2-extended-support/

-- 
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/ab69fe11-1380-4559-afef-90980299853c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: IPv6 connectivity and qubes proxy VM

2017-01-14 Thread Chris Laprise

On 01/13/2017 04:34 PM, raahe...@gmail.com wrote:

On Thursday, January 12, 2017 at 1:30:07 PM UTC-5, daltong defourne wrote:

On Thursday, January 12, 2017 at 6:47:00 PM UTC+3, daltong defourne wrote:

Hi!
I've created a VPN proxyvm (debian-8 based) according to existing documentation 
(more or less - I'm using the VPN provider's standalone client because, in a 
VM, why not?)

For IPv4 it works flawlessly.

For IPv6 it does not work at all for the VMs "behind" the proxyvm (VPN's IPv6 
support works for a browser launched within proxyvm itself, but any VM behind the proxyvm 
can only use IPv4)

what's up?
Can it be helped?

Found this commit.
https://github.com/marmarek/qubes-core-agent-linux/commit/789eb511266d9e8bd812e40f952ec2bce6d7a414

Managed to activate the qubes-ipv6 service (worked!) on the appvm, the 
firewallvm before the proxyvm, and the proxyvm.

No budge, IPv6 still missing in action :(

isn't ipv6 unsafe?  You sure this is not by design in qubes? lol.  I'm probably 
wrong don't mind me.


Maybe 'naive' is a better word for ipv6 addressing.

IIRC, ipv6 won't be officially supported until Qubes Release 4.

Chris

--
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/da8e7488-38f4-f12f-77e0-b61b0d956d4e%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: IPv6 connectivity and qubes proxy VM

2017-01-13 Thread raahelps
On Thursday, January 12, 2017 at 1:30:07 PM UTC-5, daltong defourne wrote:
> On Thursday, January 12, 2017 at 6:47:00 PM UTC+3, daltong defourne wrote:
> > Hi!
> > I've created a VPN proxyvm (debian-8 based) according to existing 
> > documentation (more or less - I'm using the VPN provider's standalone 
> > client because, in a VM, why not?)
> > 
> > For IPv4 it works flawlessly.
> > 
> > For IPv6 it does not work at all for the VMs "behind" the proxyvm (VPN's 
> > IPv6 support works for a browser launched within proxyvm itself, but any VM 
> > behind the proxyvm can only use IPv4)
> > 
> > what's up?
> > Can it be helped?
> 
> Found this commit.
> https://github.com/marmarek/qubes-core-agent-linux/commit/789eb511266d9e8bd812e40f952ec2bce6d7a414
> 
> Managed to activate the qubes-ipv6 service (worked!) on the appvm, the 
> firewallvm before the proxyvm, and the proxyvm.
> 
> No budge, IPv6 still missing in action :(

isn't ipv6 unsafe?  You sure this is not by design in qubes? lol.  I'm probably 
wrong don't mind me.

-- 
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/98efa0e1-ffaf-48f5-b180-fd12b7877387%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: IPv6 connectivity and qubes proxy VM

2017-01-12 Thread daltong defourne
On Thursday, January 12, 2017 at 6:47:00 PM UTC+3, daltong defourne wrote:
> Hi!
> I've created a VPN proxyvm (debian-8 based) according to existing 
> documentation (more or less - I'm using the VPN provider's standalone client 
> because, in a VM, why not?)
> 
> For IPv4 it works flawlessly.
> 
> For IPv6 it does not work at all for the VMs "behind" the proxyvm (VPN's IPv6 
> support works for a browser launched within proxyvm itself, but any VM behind 
> the proxyvm can only use IPv4)
> 
> what's up?
> Can it be helped?

Found this commit.
https://github.com/marmarek/qubes-core-agent-linux/commit/789eb511266d9e8bd812e40f952ec2bce6d7a414

Managed to activate the qubes-ipv6 service (worked!) on the appvm, the 
firewallvm before the proxyvm, and the proxyvm.

No budge, IPv6 still missing in action :(

-- 
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/90c3fd3a-673d-43f2-8451-f8ad1655e927%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.