ipv6 network fail (newbie alert)
Mark Grigsby
mark at pcinw.net
Thu Mar 7 00:36:01 CET 2013
I recently had a similar issue with a system that had been using one of the
LA gateways and suddenly failed to transfer traffic.
After all other options had failed, we deleted the tunnel and recreated it
via the HE broker and everything came up and ran properly.
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.
On Wed, Mar 6, 2013 at 3:18 PM, Nick Hilliard <nick at foobar.org> wrote:
> On 06/03/2013 22:59, Nick Edwards wrote:
> > traceroute now results in
> >
> > 1 * * *
> > 2 * * *
> > 3 * * *
>
> that's an iptables problem. the first hop should give a traceroute reply.
>
> For the moment, run your config with:
>
> # ip6tables -P INPUT ACCEPT
> # ip6tables -P FORWARD ACCEPT
> # ip6tables -P OUTPUT ACCEPT
>
> Once forwarding is working properly, you can concentrate on fixing up your
> firewall rules later on.
>
> Nick
>
>
>
--
Mark Grigsby
Network Operations Manager
PCINW (Preferred Connections Inc., NW)
1863 Pioneer Parkway E. #225
Springfield, OR 97477-3907
Office 541-242-0808 ext 408
TF: 800-787-3806 ext 408
DID: 541-762-1171
Fax: 541-684-0283
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20130306/102d9695/attachment.htm>
More information about the ipv6-ops
mailing list