chutney doesn't verify using IPv6 addresses
|Reported by:||teor||Owned by:|
|Severity:||Normal||Keywords:||SponsorS, testing, ipv6, tor-tests-integration|
Even when chutney is using IPv6 exits, it doesn't give clients an IPv6 address to connect to when verifying.
When chutney is using IPv6 bridges, I don't know if it gives their IPv6 address to bridge clients.
This is a significant coverage gap that I think is easily fixed by slight modifications to the chutney templating and verification code.
|#17013||Does chutney need to test various rare IPv6/IPv4 combinations?|
|#17090||chutney triggers tor warnings about ExitRelay not being set|
|#17812||Chutney tests for IPv6-only clients|
|#20067||Chutney should verify IPv6 SOCKSPorts||teor|
|#20068||Chutney tests for IPv6-only bridge clients||teor|
|#20142||chutney IPv6 HiddenServicePort tests||teor|
|#21001||Test that recent tor clients can use microdescriptors when configured to only use IPv6||teor|
Change History (7)
comment:3 Changed 17 months ago by teor
- Keywords ipv6 added
- Parent ID changed from #16949 to #17811
- Severity set to Normal
comment:4 Changed 11 months ago by nickm
- Keywords tor-tests-integration added
- Sponsor set to SponsorS-can