Facebook doesn't have a route to my ISP's (Cogeco) IPv6 space?

Thu Dec 20 20:13:09 UTC 2018

On Thu, 2018-12-20 at 21:48 +0200, Max Tulyev wrote:
> Well known problem.

Interesting.  As in a general problem across the Internet or a well
known problem with Cogeco specifically?

> You can use our tunnel broker connection (tb.netassist.ua) as a
> workaround.

Thanks.  But I actually already have a tunnel as well as a(nother)
native IPv6 ISP (yes, I have two consumer ISP connections) which routes
to Facebook properly.

The problem is that for the clients behind this router receiving RAs
for all three upstream connections and plumbing IPv6 addresses on each
of those networks, I know of no way to prevent them from choosing their
Cogeco IP address among the 3 and thus trying to use the Cogeco route.

I can (and have) put a rule into that router to refuse connections to
Facebook when using the Cogeco source address which sends TCP clients a
TCP reset with the hope that (good at least) clients/IPv6 stacks will
try a different source address but the results on that seem spotty at
best.

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20181220/2d39939a/attachment.sig>