Skip to content

Add support for ipv6#4

Open
grasscarp00 wants to merge 2 commits intobpbradley:mainfrom
grasscarp00:main
Open

Add support for ipv6#4
grasscarp00 wants to merge 2 commits intobpbradley:mainfrom
grasscarp00:main

Conversation

@grasscarp00
Copy link

No description provided.

@grasscarp00 grasscarp00 reopened this Aug 23, 2025
@bpbradley
Copy link
Owner

Hey thanks for the PR. I have been traveling so haven't been able to test but as a quick look I understand the problem, but I wonder if it can be kept simpler. I dont love the embedded python script and rubbing an entrypoint as a cmd which can be overwritten etc.

I think I'd rather keep this feature simpler by simply allowing the user to specify the bind address with an env var TURNIFY_BIND_ADDR which you could set to [::] for ipv6.

If it must be automatic, perhaps a better way would probably be to bind to [::] and then map ipv4 to ipv6 automatically if it is not ipv4 already.

I can play around with what you've done here and do some testing on my own when I am home from traveling.

Thanks again for the PR though, I'm glad people are making some use of this.

@grasscarp00
Copy link
Author

grasscarp00 commented Nov 8, 2025

Hi! Sorry for this long wait. I've got what you meant but I don't have spare time until early next year. When I get time I will try for that. 😆

I'm also wondering how element call works and whether we can replace some components of element call.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants