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

Add IPv6 support #109

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Add IPv6 support #109

wants to merge 1 commit into from

Conversation

nightah
Copy link

@nightah nightah commented Oct 24, 2020

This is the first part in a set of changes to add IPv6 support.

Tasks Remaining:

  • Add IPv6 support to lancachenet/docker-compose
  • Update docs

@nightah
Copy link
Author

nightah commented Oct 27, 2020

@GotenXiao, @Crabbey and @VibroAxe I know we briefly spoke about this on Discord, it's probably worthwhile unifying this along with the other IPv6 PR's where relevant.

Should I rebase this and change the ENABLE_IPV6 switch to be called ENABLE_V6 like lancachenet/lancache-dns#112, or should we have @Crabbey change the aforementioned PR?

Just looking for direction so the changes I'm making both to the docs and lancachenet/docker-compose can be introduced seamlessly by way of merging the relevant PR's.

@stale
Copy link

stale bot commented Jan 15, 2021

This issue has been automatically marked as inactive because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the inactive label Jan 15, 2021
@VibroAxe
Copy link
Member

Oops, forgot to flag this as an enhancement
We need a strategy about ipv6 @MathewBurnett and I were talking about this the other day.

The main issue is that ipv6 isn't the issue, it's the fact that the various tunnelling configs setup by the user tend to result in things missing the cache. Not really sure how we get round that until v6 in the house becomes more functional

@VibroAxe
Copy link
Member

We're also planning a large refactor to make generic depend on monolithic, not the other way round which will probably require some extensive modifications to this PR/moving it into monolithic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants