Error connecting to an SFTP server through ipv6

[Hoshino]

I am using FreeFileSync on Windows to connect to a server through SFTP with its ipv6 address. When I browse the directory, it works well and I can view the existing files. But after I confirm the settings, the last four hex digits of the address are dropped mysteriously so I can complete neither comparison nor synchronization.

[therube]

Oops, what I said was pertaining to IPv4.
Not familiar & don't know if that holds with IPv6?

the last four hex digits

Hex? In any case, aren't they going to be the "Port" number, & those 4 digits should be place in the Port: box, & not included directly into the Server/IP: box.

[Hoshino]

the last four hex digits

Hex? In any case, aren't they going to be the "Port" number, & those 4 digits should be place in the Port: box, & not included directly into the Server/IP: box.

Thank you for your reply! I am using the bare ipv6 address so there are some colons in it (e.g. 2000:1234:5678:9abc:def0:1234:5678:9abc). I guess that the address string is split incorrectly due the colons, and, I did find out a workaround by adding some trash characters to the end and it works now :D

Well, but I still wonder if it is a bug...

[therube]

adding some trash characters to the end

Example?

What I saw, was to add square brackets around the address.
So if IPv6 is:
fe80::219:99ff:fe20:c251
use:
[fe80::219:99ff:fe20:c251]

(I have no way of testing.)

[Hoshino]

adding some trash characters to the end

Example?

What I saw, was to add square brackets around the address.
So if IPv6 is:
fe80::219:99ff:fe20:c251
use:
[fe80::219:99ff:fe20:c251]

(I have no way of testing.)

I see... It works as well and should be the proper way. Thank you so much!

[xCSxXenon]

I'd say bug. FFS is assuming ipv4, I would guess based on this, and assumes anything after the last ':' character is the port number. This is incorrect behavior for ipv6 obviously. Zenju will have to look into this officially, but one option is to add a selection for ipv4/ipv6. Or possibly detect based on formatting

[Zenju]

I think the brackets might be required for IPv6 to distinguish the address from domain names? FreeFileSync doesn't do any parsing and just forwards to getAddrInfo.

[xCSxXenon]

Diving into that documentation brings back Networking memories that I'd like to stay forgotten lol
Maybe FFS SHOULD do parsing in this case? RegEx or some other way to detect ipv6 address and add the brackets before sending to getAAddrInfo?

[Hoshino]

I think the brackets might be required for IPv6 to distinguish the address from domain names? FreeFileSync doesn't do any parsing and just forwards to getAddrInfo.

I've further confirmed that it may fail even with the brackets. All characters after the last colon, just as the case without brackets, are dropped. I guess my initial "success" was accidental, and something has to be done to prevent this.

[Zenju]

Fixed! Converting the IPv6 server config to a single string and back indeed had a bug:
https://www.mediafire.com/file_premium/pt4vaju4rqj5kbc/FreeFileSync_13.8_%255BBeta%255D_Windows_Setup.exe

[Hoshino]

Fixed! Converting the IPv6 server config to a single string and back indeed had a bug:
https://www.mediafire.com/file_premium/pt4vaju4rqj5kbc/FreeFileSync_13.8_%255BBeta%255D_Windows_Setup.exe

Thank you so much! I've tested the beta version and everything is fine now.

[Petricor]

Fixed! Converting the IPv6 server config to a single string and back indeed had a bug:
https://www.mediafire.com/file_premium/pt4vaju4rqj5kbc/FreeFileSync_13.8_%255BBeta%255D_Windows_Setup.exe

I have the same error, in Microsoft Windows Server 2012 R2 Standard , version 6.3.9600 compile 9600

But I can't test v13.8 because the install has expired.

Could you share a new installer? Thanks !!