Enabling (and pinging) IPv6

[tog]

I’m (still) very new to Qubes, so please be considerate. I’m using Qubes 4.0.4.
I’ve enabled (or so I thought) IPv6 support by running qvm-features sys-net ipv6 1 in dom0. I have sys-firewall using sys-net and sys-whonix using sys-firewall.
Furthermore, I have untrusted using sys-firewall and work using sys-whonix. In no qube, I seem to have proper IPv6 support - or so it seams: The command ping6 ipv6.google.com always fails with the error From fd09:<...> (<...>): icmp_seg=4 Destination unreachable: Address unreachable (for qubes using sys-whonix) or <...> icmp_seq=2 Destination unreachable: no route (for qubes using sys-firewall).
Interestingly, in the disposable whonix qube, I can access the site using the Tor browser (though I also can’t ping it).
What am I doing wrong?
Please let me know if I can provide further helpful information.

[muntedcrocodile]

I’m having a simmillar issue. Can u run ip -6 addr show in sys-net it should show u all the ipv6 address u have. I’m only being assigned link local addresses (addresses starting with fe80) which will only work on lan not wan.

I see this post is old did u end up managing to resolve the issue? If so how?

[muntedcrocodile]

I have partially resolved the issue see: https://lemm.ee/post/53023077

[solene]

Enabling ipv6 prevents sys-whonix from working for me, can you still connect to Tor when after enabling ipv6?

Sys-whonix does not connect anymore

Mystery solved! There is a Qubes OS bug Setting qvm-features sys-net ipv6 1 creates troubles in sys-whonix like eth0 not being up, and not having route. However, setting qvm-features sys-net ipv6 0 does solve nothing, one must use qvm-features --unset sys-net ipv6 to really revert the ipv6 setting.