[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: HOWTO: Join the 6bone!



On Fri, 22 Sep 2000, Bernd Eckenfels wrote:

> > wakko{root}~#ip addr add 2002:186c:d162::1 dev sit0
> > wakko{root}~#ip -6 route add 2000::/3 via ::216.234.231.5
 
> 216.234.231.5. So far so good. But, the sender of this packet is not as you
> might simply expect ::24.108.209.98 (which can be handeled pretty well by
> masters sit0) but 2002:186c:d162::1. Thats why master hand the answer packet
> off to the 6bone as your trace indicates:

Well, the sender is whatever the socket is bound as, which often should be
2002:186c:d162::1. ::24.108.209.98 is not a globally routable address so
no packets must originate with that IP.
 
> so the question is, 3ffe:c00:e:4::1 seems to be ipv6-router.cisco.com which
> is obviously doing the 6to4 ipv4 tunneling for your answer packages. Are we

Yes, if 6-to-4 takes off then I'm sure almost all routers on the internet
will be doing what cisco is here. Right now it seems only cisco has
routers capable of this, so they are the only ones providing the routes.

If linux had 6to4 support then master itself would be able to formulate
the reply directly. But it doesn't so it won't.

> authorized to ue their facility? And if so, why we can't simply use it as
> the entry point, too? ipv6-router.cisco.com (192.31.7.104)

Cisco might not let you send packets to the 6bone to their site - but you
can try. They shouldn't care the other way, if they did/do then they
should/will restrict the route propogation.

Jason



Reply to: