Problem with IPV6 client connecting to IPV4 Server

[Macktek]

Hello,
My server is hosted IPV4 and tests OK except for port warning and "Warning: The entered address does not resolve to an IPv6 address."

I am using a Block ALL to IP Filter using: *

I currently Whitelist: 192.168.10.0/24 2001:459a:2240:afcd:202:7aff:fe30:cdfe/128
Is this the correct way to whitelist this client IPV6 address?

The client trying to connect is from IPV6: 2001:459a:2240:afcd:202:7aff:fe30:cdfe
But they are unable to connect.
(I can connect from other IPV4 addresses)

Does the fact that the client uses IPV6 prevent them from connecting despite my whitelist?

Thanks for any help.

[botg]

Make sure to use a hostname that resolves to an IPv6 address, ie. has an AAAA record.

[boco]

IPv4 and IPv6 are incompatible. So, if your server is hosted on IPv4 only, clients connecting will have to use IPv4. Likewise, servers hosted on only IPv6 can be reached only over IPv6.

For best compatibility, you need to host the server on true dualstack (IPv4+IPv6). NOT on DS-Lite or similar shenanigans.

[Macktek]

Hmm... so IPV4 and IPV6 are incompatible for FTP unless I have a "dual stack" from the ISP.

That severely hampers FTP.

Would Filezilla ever consider adding a different protocol to its capabilities to address this? ... because getting an ISP to provide "dual stack" access does not sound like its going to be easy or low cost at all.

I mean... it almost sounds like I am going to have to abandon filezilla.

On the odd chance that I can get dual stack from the ISP, does it work automatically or do I need to do some configuration?

[botg]

Ever single protocol in existence has the same problem. It's the way the Internet works. IPv6 is the future, abandon IPv4.

[boco]

Hmm... so IPV4 and IPV6 are incompatible for FTP unless I have a "dual stack" from the ISP.

The IPv4 / IPv6 problem is not only one of FTP. You will have the same problem with all protocols based on TCP/IP (HTTP, SFTP, SSH2, ...).

For example, this very site (filezilla-project.org, using HTTPS) is reachable over both IPv4 and IPv6. You're connecting via IPv4, I'm using IPv6. Now, if the site was reachable only over IPv6, you couldn't reach it, but I could.

So, your clients need IPv4 access of some sort in order to reach your server (no matter what protocol you use in the end). If they only have IPv6, they can't reach you (although IPv6-only is still a rare occurrence).

On the odd chance that I can get dual stack from the ISP, does it work automatically or do I need to do some configuration?

With any halfway modern OS (Vista+), the full IPv6 functionality is built-in and enabled. You will need dual stack from the ISP, and you will need an IPv6 capable network endpoint/gateway (router). If the router only supports IPv4 then even dual stack from the ISP won't get you anywhere.

With those preconditions met, you don't need further configuration. And, as botg said, your host-/domain name needs an AAAA record so it points to your IPv6 as well. The old A record only supports IPv4.

[Macktek]

I currently have a static IP. With dual stack wouldn't the AAAA record only be needed if people were connecting via Domain Name or if I was using dynamic DNS?

[boco]

Of course, the IPs work without a domain name. However, IPv6 addresses might be a bit harder to remember...

Majority of people have dynamic IPs, we didn't know you're on static until your previous post.