Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IPv6 support #1

Open
lvlts opened this issue Feb 12, 2018 · 2 comments
Open

IPv6 support #1

lvlts opened this issue Feb 12, 2018 · 2 comments
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@lvlts
Copy link
Owner

lvlts commented Feb 12, 2018

Currently, IPv6 is not supported in the Travis environment. More information is available at:
https://docs.travis-ci.com/user/reference/overview/#Virtualisation-Environment-vs-Operating-System

Further exploration can be done in the following directions (or others):

  • 4to6 tunnel on Travis CI: not sure if it can be done without port forwarding, at least not with native iproute2 tooling; reliability is also questionable, depending on the 4to6 provider.
  • migration of the current project to another "test" build environment where native IPv6 is present; regular deployment to github pages can be done regularly via cron or other means.
@lvlts lvlts added enhancement New feature or request help wanted Extra attention is needed labels Feb 12, 2018
@lvlts lvlts self-assigned this Feb 12, 2018
@Mikaela
Copy link

Mikaela commented Nov 1, 2018

Crazy idea, could this be done using Teredo or does it require something Travic CI doesn't provide? I think it would be matter of installing miredo or at least is on normal machines.

Alternatively probably not much less crazy idea could it attempt using Tor proxy within hype that has in its torrc something like SocksPort [fc...]:1234 NoIPv4Traffic ?

@lvlts
Copy link
Owner Author

lvlts commented Nov 2, 2018

Crazy idea, could this be done using Teredo or does it require something Travic CI doesn't provide? I think it would be matter of installing miredo or at least is on normal machines.

Awesome idea, I've just had a go at it, but it seems that the miredo interface just won't get assigned an IP address. I have the strong feeling that this is because IPv6 is only available on loopback for trusty containers. For non-container trusty, IPv6 is not available at all, which might be the reason why it's also not showing up.

Alternatively probably not much less crazy idea could it attempt using Tor proxy within hype that has in its torrc something like SocksPort [fc...]:1234 NoIPv4Traffic ?

This one's even tougher to implement, and I'm afraid the result would be similar, as there's no IPv6 support enabled on the other interfaces.

Definitely something to test out for the future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants