IPv6 not possible

[MarkV]

It's becoming more and more popular now. There are a few old posts from 2009 that mention it, but nothing since then.

Please consider it. 

[rejetto]

i know very little about it, can you list what's (apparently) missing in HFS to support it?

[bmartino1]

i've not tested it on ipv6, if HFS binds to the interface, then the interface could use ipv6 with out adding new support to hfs...

I'm not 100% sure how hfs "binds" to the interface....
https://en.wikipedia.org/wiki/Language_binding

some info on java might help you here...
http://stackoverflow.com/questions/1555591/how-to-convert-an-address-from-ipv4-to-ipv6

https://en.wikipedia.org/wiki/IPv6#IPv4-mapped_IPv6_addresses

[MarkV]

Currently HFS either doesn't bind to IPv6 sockets (like [::1]:80 or [2001:db8:1::2ac]:80), or it can't respond. Trying http://[::1] in Firefox gets me a 'Problem loading page' error, even if I set it as custom IP (might also mean HFS can't handle the IPv6 address format).

Unfortunately I know nothing about coding. But, for testing, as per the IPv6 definition, every system since Vista does have at least the ::1 (localhost) and the fe80:: (Interface) IPv6 addresses.

[bmartino1]

i don't quite have time to test it, but i will test ipv6 and show what i find....

there sin't any "enhanced security between the two, ipv6 just has more ip address...

in regards to the local host, that is because of the host file and the dns bind within windows see the host file for more info on localhost:

# localhost name resolution is handled within DNS itself.
#   127.0.0.1       localhost
#   ::1             localhost

i believe i can map an ipv6 ip address (by first disable-ing ipv4 and enabling only ipv6), then supply a ipv4 mapped ipv6 ip adderss....

I'm not surprised that "custum" didn't work, to my understanding of that field, that is for dns names....

i will post my finding when i have more free time to test

[MarkV]

There is *much* more than just a difference in number of possible IPs. The restoration of the "end-to-end" principle, requiring no more NAT or port forwarding, for example. No requirement of DHCP due to automatic self-configuration of IP addresses, another one.

There's even the problem of transitioning technologies like DS-Lite. With DS-Lite, HFS users are out of luck since they won't get any public IPv4 address anymore, only an IPv6. That makes HFS unreachable in those environments.

[LeoNeeson]

This is interesting,  but sadly I don't have a real IPv6 to make tests (my ISP doesn't provide IPv6 yet)

The only solution it comes to my mind, is some kind of "workaround", like forwarding IPv4 local ports to IPv6. It's like a proxy between the IPv6 to the IPv4 of our local server (HFS). I've read here of using the tool "Socat" as TCP forwarder. A Win32 version of Socat, can be found here and here.

Anyway, this is only a workaround, since having native support in HFS will work better and be more easier.

[MarkV]

For testing IPv6 in LAN:
- All adapters in Windows should have their respective fe80:: addresses already. One of the strengths of IPv6 - self configuration of at least the basic IP addresses.
- You can distribute ULAs (equvalent to LAN IPs in IPv4) via tools like dibbler or Jagornet. Use IPv6 addresses in the fd00::1 to fdff:ffff:ffff:ffff:ffff:ffff:ffff:ffff range.
- Many Routers can already distribute ULAs even if the ISP doesn't support IPv6, yet. So you can test in LAN without using one of the tools mentioned above.

Check IPv6 addresses:

Code: [Select]

netsh int ipv6 show addr or

Code: [Select]

ipconfig /all