Forum » Support and Bug Reports »

Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

manawyrm wrote:

That might be part of the problem :mrgreen:

I have used IPv6 addresses to connect in this log.

I do not think so. WinSCP logs the IP address exactly as your enter it. Can you please try again? Posting a screenshot and a corresponding log file?
manawyrm

That might be part of the problem :mrgreen:

I have used IPv6 addresses to connect in this log.
Does WinSCP internally use PuTTY to provide this tunneling feature?
If so: I figured out, that PuTTY needs square brackets around an IPv6 address to make it work.

It might be enough to just encapsulate every IPv6 address in [ ] if it is sent to your tunneling method.

So long,
Tobias
martin

Thanks for your response. Though I do not see any IPv6 address in the log.
manawyrm

Hi,
I will post a log shortly.

In the meantime I have figured out, that putting the IPv6 address in [ ] brackets fixes the problem.

EDIT: Log is now attached.

Best regards,
Tobias
martin

Re: IPv6 SSH-Tunneling

Please attach a full log file showing the problem.

To generate log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
manawyrm

IPv6 SSH-Tunneling

Hi,

I am currently trying to connect to an IPv6-only host via WinSCPs tunneling function.

This is the configuration I'm using:
<invalid link removed>
When connecting, instead of establishing the connection, it just shows this error message:
<invalid link removed>

I have tried the current nightly build, but apart from the nicer error icon :mrgreen: , nothing changes:
<invalid link removed>

The issue can be reproduced with OpenSSH and dropbear SSH servers.

Any ideas?

Thank you very much,
Tobias

Documentation

Support

Associations

Follow Us