+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access)
+---- Thread: IPv6 Functionality (/t-ipv6-functionality)
IPv6 Functionality - wenzelja - 2024-12-17
TI have been meaning to ask questions about this option for awhile.
Why does enabling IPv6 functionality seemingly result in disabling IPv4 access to my server on 192.168.1.XXX:8096 even though both IPv4 and 6 are enabled in network settings? Does it mean that I can only access Jellyfin using the local IPv6 address (and do I still use 8096 as the port for IPv6, e.g. XXXX:XXXX:XXXX:XXXX:XXXX:XXXX%XX:8096), and if so, why does it disable IPv4 access?
Even though both IPv4 and IPv6 are enabled, based on my experience thus far it would seem that IPv4 is disabled when IPv6 is enabled, even though the Network settings aren't reflecting that reality, and are instead showing both enabled.
This is probably a matter of my not understanding IPv6 very well. What are the use cases for enabling IPv6 vs. IPv4? Any advantages/disadvantages either way?
RE: IPv6 Functionality - TheDreadPirate - 2024-12-17
It depends on how you have things configured. I have both enabled. But I also have remote connections enabled and I added my public IPv6 pre-fix to the "LAN Networks" setting.
If you have native IPv6 setup in your network, it is possible that connections from your LAN clients could be coming in with their public IPv6 address. Here is an example from my Android phone on the same network.
If you A) do NOT have remote connections enabled and B) did not add your public IPv6 pre-fix to LAN networks (see screenshot below) then clients connecting with their IPv6 address are "remote" and, therefore, blocked.