Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upIPv6 routing between appvm and an IPv6-capable proxyvm #2570
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
This is duplicate of #718 |
marmarek
closed this
Jan 12, 2017
marmarek
added
the
duplicate
label
Jan 12, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tonsimple commentedJan 12, 2017
•
edited
Edited 1 time
-
tonsimple
edited Jan 12, 2017 (most recent)
Qubes OS version
( R3.2 ):
Affected TemplateVMs
presumably all of them, tested debian 8, fedora-24
Expected behavior:
some kind of basic IPv6 forwarding to maybe finally occur between VMs to allow NATing of ipv6 from an appVM through a proxyvm with (confirmed) ipv6 capability
Actual behavior:
no ipv6 connectivity for appvm
Steps to reproduce the behavior:
Create proxyvm with VPN as per existing instructions. No additional firewall changes made.
Run browser inside proxyvm and use ipleak.net and ipv6-test.com/ to confirm that
General notes:
I kind of understand why a privacy and security focused OS would treat ipv6 as cancer :)
But sooner rather than later ipv6 support will become vital.
"nattish-ing" ipv6 through a chain along the lines of
[IPv6-needy-AppVM] -> [dedicated-mini-firewall-VM] -> [IPv6-capable-proxyvm] -> [IPv4-only-net-vm]
seems like a reasonable solution
Related issues: