You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently ipv6 is disabled/ the new frontend only accepts ipv4 for allocations.
I'm pretty sure ipv6 does actually work (on the backend) but we should do some tests and enable ipv6 support.
I'v previously made a PR #429 for this but i couldn't answer before it get close so here it is:
IPV6 does work both on wings and the panel #429 (comment)
I'v tried it and used it even on ptero without any issue (you have to use pelican_nw ipv6 gw fdba:17c8:6c94::1011 which is like binding to 172.18.0.1) or use an ipv6 that's actually configured on the machine (just like for ipv4) @parkervcp also told me that he would have talk this out if he was there at the time so i believe we can just merge that PR
hey guys
first: i can not overstate how amazing this project is, thank you so much for your work here
second: this feature would be beyond amazing
In germany we almost never have static ipv4 addresses and are also limited by DSLite
so internet hosting over ipv4 is not possible (for peoplbe like me at least)
ipv6 allocations would fix this because the docker container would open up these ports then right?
That would make dns entries also available :)
Of course given if this feature is just as easy as enabling/disabling some filters in the frontend forms 👍🏼
I also have to say that this is mission critical for my setup. I currently have several services maintained with Pterodactyl that rely on IPv6 allocations. I also have several wings that are only reachable via IPv6 (only AAAA record). I hope that Pelican will also work as well with IPv6 environments as Pterodactyl did.
Currently ipv6 is disabled/ the new frontend only accepts ipv4 for allocations.
I'm pretty sure ipv6 does actually work (on the backend) but we should do some tests and enable ipv6 support.
https://github.com/pelican-dev/panel/blob/main/app/Filament/Resources/NodeResource/RelationManagers/AllocationsRelationManager.php#L81
https://github.com/pelican-dev/panel/blob/main/app/Filament/Resources/ServerResource/RelationManagers/AllocationsRelationManager.php#L77
https://github.com/pelican-dev/panel/blob/main/app/Filament/Resources/ServerResource/Pages/CreateServer.php#L189
The text was updated successfully, but these errors were encountered: