4
When using SSH from my Windows 7 desktop to Linux servers, via IPv6, I'm having the following two problems, because of IPv6 Privacy Extensions:
I'm used to keep ssh sessions open for days or weeks. Now, when using IPv6, they are disconnected after several hours of inactivity. I suppose this happens when my "private" IPv6 address changes.
Each time I log in, the "Last login" greeting shows a different IP address (naturally), since a new fresh "private" IPv6 address is used.
I don't want to disable IPv6 privacy extensions outright on my Windows 7 desktop, as it has its uses and enhances the privacy somewhat. I wonder, however, if I can make Windows use non-private IPv6 address as a source of some connections, or if I can prevent a private IPv6 address change if there are open TCP sessions using that address.
My SSH client is SecureCRT 6.1, and there are no options/settings there that are related to this issue.
1Why aren't you using such an old version of SecureCRT? Has your licence lapsed? I remember there being IPv6 support improvements several months ago, but I cannot remember if they were related. – paradroid – 2011-12-18T18:29:16.847
I've read their "history" and didn't find anything related to this specific issue. And yes, my license does not allow free updates any longer. – haimg – 2011-12-18T18:31:37.093
Adding a static route should work;
netsh in ipv6 add ro <serveraddress>/128 "Local Area Network" <localaddress>
– user1686 – 2011-12-18T19:05:01.343