@Michael Heimann
yeah, the idea IS to have a workaround for ssh, and only for it (or some other server-software).
with tempaddr = 2 you have a dynamic and a static ip, and softwares are using the dynamic by default, if not configured otherwise.
You can surf (more) anonymously, but your ssh-session uses the static ip, so the session does not die when the tempaddr is discarded. It should be a user decision to use the static ip, the default should be safe for the average user, which means that he's not exposed by a static ip.
Server software will bind to all intefaces by default, so a http or ssh server will be reachable on the dynamic address (mostly useless for you) and the static address (useful). Client software which needs long sessions often can be configured to use a specific from-ip, as i showed you the manual for the ssh-client.
@Michael Heimann
yeah, the idea IS to have a workaround for ssh, and only for it (or some other server-software).
with tempaddr = 2 you have a dynamic and a static ip, and softwares are using the dynamic by default, if not configured otherwise.
You can surf (more) anonymously, but your ssh-session uses the static ip, so the session does not die when the tempaddr is discarded. It should be a user decision to use the static ip, the default should be safe for the average user, which means that he's not exposed by a static ip.
Server software will bind to all intefaces by default, so a http or ssh server will be reachable on the dynamic address (mostly useless for you) and the static address (useful). Client software which needs long sessions often can be configured to use a specific from-ip, as i showed you the manual for the ssh-client.