Changes between Version 1 and Version 2 of Ticket #867
- Timestamp:
- 03/31/17 19:53:56 (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #867 – Description
v1 v2 51 51 1. Alternative, use ''either'' `--proto udp4` on the v2.4 side ''or'' `--proto udp6` on the v2.3 side 52 52 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- client` on the v2.4 side and `--proto tcp-server` on the v2.3 side. This also triggers a reconnect. The other way around does not work, as the v2.3 side will then listen to an IPv4 socket while the v2.4 side tries to connect using an IPv6 socket.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. 54 54 55 55 == Conclusion