IPv6 connectivity and qubes proxy VM

daltong defourne

unread,

Jan 12, 2017, 10:47:00 AM1/12/17

to qubes-users

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?

daltong defourne

unread,

Jan 12, 2017, 1:30:07 PM1/12/17

to qubes-users

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 :(

raah...@gmail.com

unread,

Jan 13, 2017, 4:34:19 PM1/13/17

to qubes-users

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

Chris Laprise

unread,

Jan 15, 2017, 12:23:27 AM1/15/17

to raah...@gmail.com, qubes-users

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

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

Chris

daltong defourne

unread,

Jan 15, 2017, 4:40:42 PM1/15/17

to qubes-users, raah...@gmail.com, tas...@openmailbox.org

On Sunday, January 15, 2017 at 8:23:27 AM UTC+3, Chris Laprise wrote:

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/

Reply all

Reply to author

Forward