>FreeBSD 4.0-20000522-STABLE
>
>6to4 tunnelling via the stf interface:
>
>       stf0: flags=8041<UP,RUNNING,MULTICAST> mtu 1280
>               inet6 fe80::2c0:95ff:fef0:3e20%stf0 prefixlen 64 scopeid 0xb 
>               inet6 2002:180c:a043::1 prefixlen 16 
>
>Outgoing packets travel by default via Freenet6, with the gif interface
>using the same address as the stf interface:
>
>       gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
>               inet6 fe80:7::2c0:95ff:fef0:3e20  prefixlen 64 
>               inet6 2002:180c:a043::1 --> 3ffe:b00:c18:1fff::3ac  prefixlen 127 
>               physical address inet 24.12.160.67 --> 206.123.31.102
(snip)
>But pinging www.kame.net does not work:
>
>       PING6(56=40+8+8 bytes) 2002:180c:a043::1 --> 
>3ffe:501:4819:2000:5054:ff:fedc:50d2
>       [yawn...]
>
>The traceroute to www.kame.net might be more informative:
>       traceroute to kame212.kame.net (3ffe:501:4819:2000:5054:ff:fedc:50d2), 30 hops 
>max, 12 byte packets
>        1  3ffe:b00:c18:1fff::3ac  399.275 ms  360.014 ms
>        2  3ffe:b00:c18:1:290:27ff:fe17:fc0f  365.612 ms  365.586 ms
>        3  3ffe:b00:c18::13  410.858 ms  437.977 ms
>        4  3ffe:1810:0:ffff::14  433.558 ms  469.157 ms
>        5  3ffe:1810:ffff::13  449.495 ms  446.731 ms
>        6  3ffe:1800:0:3:290:27ff:fe14:cd9c  464.434 ms  417.067 ms
>        7  3ffe:1801:ffff::2  473.318 ms  433.492 ms
>        8  * *
>        9  * *
>       10  * *
>       11  * *
>       12  * *
>       13  * *

        this can be Japan domestic routing issue, or issue in your
        configuration.  first of all, let me check about your environment:
        - you should have an IPv6 address assigned from freenet6.  since you
          are transmitting from freenet6, you need to use source address
          from freenet6.  however, you do not assign one on gif0.  this seems
          to be configuration mistake.

>       gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
>               inet6 fe80:7::2c0:95ff:fef0:3e20  prefixlen 64 
>               inet6 2002:180c:a043::1 --> 3ffe:b00:c18:1fff::3ac  prefixlen 127 
>               physical address inet 24.12.160.67 --> 206.123.31.102

        - next.  if you use 6to4 address and you are hooked to native IPv6
          cloud, you need to announce 2002::/16 to the native IPv6 cloud
          and you need to become a public relay for everybody (see 6to4
          specification).  you fall into this category (since you
          are connected to freenet6 too).  do you advertise 2002::/16
          to the backbone?

itojun

---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]

Reply via email to