<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div>On 7 Feb 2011, at 14:31, Simon Perreault wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>On 2011-02-07 09:23, Jared Mauch wrote:<br><blockquote type="cite">Anyone gotten the MacOS PPTP/VPN client to obtain an IPv6 address? I'm using a Cisco router on the other end, and am looking for anything obvious i'm missing. It appears to be sending the traffic out the virtual-access interface just fine, but I'm not seeing an IPv6 address on the ppp0 interface.<br></blockquote><br>Maybe this will be helpful:<br><a href="http://marcblanchet.blogspot.com/2010/08/ipv6-pppoe-on-macosx.html">http://marcblanchet.blogspot.com/2010/08/ipv6-pppoe-on-macosx.html</a><br><br>Especially this part:<br><br><blockquote type="cite">However, the IPv6 global addresses are now shown anywhere, either in the Network Settings Panel, nor with ifconfig ppp0. The IPv6 PPP specification(RFC5072) says that the global address is obtained by router advertisements on the PPP link or by DHCPv6.<br></blockquote><blockquote type="cite">Inspection of MacOSX shows that router advertisements were not enabled (surprisingly, becauseI'm using IPv6 RA at the office without having to do any change in the kernel config) in the kernel, so I enable them.<br></blockquote><blockquote type="cite"># sudo sysctl -w net.inet6.ip6.accept_rtadv=1<br></blockquote><blockquote type="cite">net.inet6.ip6.accept_rtadv: 0 -> 1<br></blockquote></div></blockquote></div><br><div>I've been using a similar config for a couple of years now, but with L2TP/IPsec instead of PPTP.</div><div><br></div><div>Older versions of Mac OS X needed a ppp up script to add the ipv6 defaut route, but more </div><div>recently that seems to have been fixed.</div><div><br></div><div>Since enabling IPv6 on my office network I've noticed another bug with the v6 default route.</div><div><br></div><div>With a IPv6 address and default route on the underlying interface (ethernet, wifi) if I make a v6 </div><div>enabled VPN connection to my Cisco at home it gets a v6 address on the ppp interface just fine </div><div>but then it wont install an additional IPv6 default route. A secondary IPv4 default route to the </div><div>ppp interface is installed as you'd expect with the 'send all traffic over vpn connection' box </div><div>ticked.</div><div><br></div><div>Manually adding a ipv6 default route results with this message:</div><div><div></div></div><blockquote class="webkit-indent-blockquote" style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div># route add -inet6 default -interface ppp0</div></div><div><div>route: writing to routing socket: File exists</div></div><div><div>add net default: gateway ppp0: File exists</div></div></blockquote><div><br></div><div>I can remove the ethernet default and then add one via ppp0 but ping6 still wants to bind to the</div><div>IPv6 address of the ethernet interface not the ppp interface.</div><div><br></div><div>If I take the VPN down, disable IPv6 on the ethernet interface and bring the VPN back up all works</div><div>as expected and v6 works fine on the ppp interface.</div><div><br></div><div>Any ideas?</div><div><br></div><div>Bill.</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div></body></html>