Changes between Version 2 and Version 3 of Ticket #867


Ignore:
Timestamp:
03/31/17 19:58:04 (4 years ago)
Author:
David Sommerseth
Comment:

Sorry about the mess when updating the tcp-{client,server} stuff. My notes confused me.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #867 – Description

    v2 v3  
    5151 1. Alternative, use ''either'' `--proto udp4` on the v2.4 side ''or'' `--proto udp6` on the v2.3 side
    5252 1. Alternative, add `--keepalive 10 20` on the v2.4 side.  This triggers a re-connect which will use another resolved IP address
    53  1. Alternative, switch to TCP using `--proto tcp-server` on the v2.4 side and `--proto tcp-client` on the v2.3 side.  This makes the v2.4 listen to both IPv4 and IPv6 by default.  The other way around does not work, as the v2.3 client results in an IPv4/IPv6 address mismatch again.
     53 1. Alternative, switch to TCP using `--proto tcp-client` on the v2.4 side and `--proto tcp-server` on the v2.3 side.  This triggers a re-connect which swaps the IP address from IPv6 to IPv4.  The other way around does not work, as the v2.3 client results in an IPv4/IPv6 address mismatch again.  The v2.4 side expects an IPv6 address while the v2.3 side uses an IPv4 address.
    5454
    5555== Conclusion