Hello, thanks for your reply.
Am 02.07.2012 um 16:32 schrieb Guus Sliepen: > >> -> What IPv6-address and netmask will be assigned to the tun/tap-interfaces >> of the three nodes (Gateway, AP 1, AP 2)? If a public v6 address is >> assigned, is it done regarding to RFC 3578? > > Tinc itself does not assign addresses to interfaces, that is left up to you. > For example, in the tinc-up script on AP 1, you could add: > > #!/bin/sh > ip addr add 10.0.1.1/16 dev $INTERFACE > ip addr add 2001:470:780f:1::1/56 dev $INTERFACE > ip link set $INTERFACE up > I'm not sure that this works regarding to RFC 3587 (sorry for the typo above) "(...) also requires that all unicast addresses, except those that start with binary value 000, have Interface IDs that are 64 bits long and to be constructed in Modified EUI-64 format." By that I'm not sure, whether running an non-/64-Bit network is going to cause any side-affects. Is it possible to assign a /64 network on $INTERFACE when working in routed mode? Eg ip -6 addr add 2001:470:780f::1/64 dev $INTERFACE ip -6 route add 2001:470:780f::1/56 dev $INTERFACE Are there any pros and cons? Keep smiling yanosz
_______________________________________________ tinc mailing list [email protected] http://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
