<div dir="ltr">I recently had a similar issue with a system that had been using one of the LA gateways and suddenly failed to transfer traffic.<div><br></div><div style>After all other options had failed, we deleted the tunnel and recreated it via the HE broker and everything came up and ran properly.</div>
<div style><br></div><div style>When the tunnels were re-created the same addresses for the tunnel end-points and the routed /64 were assigned so no changes were made at the gateway.</div></div><div class="gmail_extra"><br>
<br><div class="gmail_quote">On Wed, Mar 6, 2013 at 3:18 PM, Nick Hilliard <span dir="ltr"><<a href="mailto:nick@foobar.org" target="_blank">nick@foobar.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 06/03/2013 22:59, Nick Edwards wrote:<br>
> traceroute now results in<br>
><br>
> 1 * * *<br>
> 2 * * *<br>
> 3 * * *<br>
<br>
</div>that's an iptables problem. the first hop should give a traceroute reply.<br>
<br>
For the moment, run your config with:<br>
<br>
# ip6tables -P INPUT ACCEPT<br>
# ip6tables -P FORWARD ACCEPT<br>
# ip6tables -P OUTPUT ACCEPT<br>
<br>
Once forwarding is working properly, you can concentrate on fixing up your<br>
firewall rules later on.<br>
<span class="HOEnZb"><font color="#888888"><br>
Nick<br>
<br>
<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br>Mark Grigsby<br>Network Operations Manager<br>PCINW (Preferred Connections Inc., NW)<br>1863 Pioneer Parkway E. #225<br>Springfield, OR 97477-3907<br>
Office 541-242-0808 ext 408<br><div>TF: 800-787-3806 ext 408<div>DID: 541-762-1171<br>Fax: 541-684-0283</div></div>
</div>