<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hello,<div><br></div><div>thanks for your reply.</div><div><br><div><div>Am 02.07.2012 um 16:32 schrieb Guus Sliepen:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br><blockquote type="cite">-> 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? <br></blockquote><br>Tinc itself does not assign addresses to interfaces, that is left up to you.<br>For example, in the tinc-up script on AP 1, you could add:<br><br>#!/bin/sh<br>ip addr add 10.0.1.1/16 dev $INTERFACE<br>ip addr add 2001:470:780f:1::1/56 dev $INTERFACE<br>ip link set $INTERFACE up<br><font class="Apple-style-span" color="#006312"><br></font></div></blockquote><br></div><div>I'm not sure that this works regarding to RFC 3587 (sorry for the typo above)</div><div>"(...) also requires that all unicast addresses, except those that</div><div> start with binary value 000, have Interface IDs that are 64 bits long</div><div> and to be constructed in Modified EUI-64 format." </div><div><br></div></div><div>By that I'm not sure, whether running an non-/64-Bit network is going to cause any side-affects. </div><div>Is it possible to assign a /64 network on $INTERFACE when working in routed mode?</div><div><br></div><div>Eg </div><div>ip -6 addr add 2001:470:780f::1/64 dev $INTERFACE </div><div>ip -6 route add 2001:470:780f::1/56 dev $INTERFACE</div><div><br></div><div>Are there any pros and cons?</div><div><br></div><div>Keep smiling</div><div>yanosz</div><div><br></div></body></html>