SixXS::Sunset 2017-06-06

Kewlio.net problem ...
[si] Carmen Sandiego on Sunday, 11 January 2004 16:46:47
Hello I have a little problem when I configure ipv6 on my other box ... with same configuration like on my box it doesn`t work. It works localy ping6 but if I ping it from outside it sais: ping6 3ffe:4005:1000:5::2 PING 3ffe:4005:1000:5::2(3ffe:4005:1000:5::2) from 2001:6f8:910::20 : 56 data bytes From 2001:618:c00:4:10:5cab:6a47:5555 icmp_seq=4 Destination unreachable: Address unreachable From 2001:618:c00:4:10:5cab:6a47:5555 icmp_seq=8 Destination unreachable: Address unreachable and the configuration file: MYIPv4="193.95.199.107" # My IPv4 address XSIPv4="62.24.229.120" # PoP's IPv4 address MYIPv6="3ffe:4005:1000:5::2" TUNLIF="sit1" DEV="ppp0" ifconfig $TUNLIF add $MYIPv6 iptunnel add $TUNLIF mode sit local $MYIPv4 remote $XSIPv4 ttl 64 dev $DEV ifconfig $TUNLIF up route -A inet6 add 2000::/3 dev $TUNLIF ifconfig $TUNLIF add $MYIPv6
Kewlio.net problem ...
[ch] Jeroen Massar SixXS Staff on Sunday, 11 January 2004 16:54:10
- What OS - How does the result of your routing/interfaces etc tables look like? You didn't specify the POP IPv6 address to route over btw.
Kewlio.net problem ...
[si] Carmen Sandiego on Sunday, 11 January 2004 17:09:17
emm I`m running Debian and I don`t have set POP IPv6 on my home box and it works fine(Easynet) From the not working box: 1: lo: <LOOPBACK,UP> inet6 ::1/128 scope host 3: eth0: <BROADCAST,MULTICAST,UP> qlen 1000 inet6 fe80::230:4fff:fe22:e057/64 scope link 4: eth1: <BROADCAST,MULTICAST,UP> qlen 1000 inet6 fe80::230:4fff:fe23:781e/64 scope link 36: sit1: <POINTOPOINT,NOARP,UP> inet6 fe80::c15f:c76b/128 scope link inet6 3ffe:4005:1000:5::2/0 scope global 2000::/3 dev sit1 metric 1 mtu 1472 advmss 1412 fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1220 fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1440 fe80::/64 via :: dev sit1 metric 256 mtu 1472 advmss 1412 ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1220 ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1440 ff00::/8 dev sit1 metric 256 mtu 1472 advmss 1412 default dev eth0 proto kernel metric 256 mtu 1500 advmss 1220 default dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 default via :: dev sit1 metric 256 mtu 1472 advmss 1412 unreachable default dev lo proto none metric -1 error -101 advmss 1220 Is this what you meant with results od routing/interface?
Kewlio.net problem ...
[ch] Jeroen Massar SixXS Staff on Sunday, 11 January 2004 17:13:00
emm I`m running Debian and I don`t have set POP IPv6
on my home box and it works fine(Easynet)
Which Debian? There are a lot of flavours and each has a different kernel and you might have even compiled and hopefully installed your own. Debian GNU/hurd maybe ? :)
36: sit1: <POINTOPOINT,NOARP,UP>
inet6 fe80::c15f:c76b/128 scope link
inet6 3ffe:4005:1000:5::2/0 scope global
/0 ? :) That should be a /64. Four 'default' routes:
2000::/3 dev sit1 metric 1 mtu 1472 advmss 1412
default dev eth0 proto kernel metric 256 mtu 1500 advmss 1220
default dev eth1 proto kernel metric 256 mtu 1500 advmss 1440
default via :: dev sit1 metric 256 mtu 1472 advmss 1412
Fortunatly for you the first one takes precedence.
Kewlio.net problem ...
[si] Carmen Sandiego on Sunday, 11 January 2004 17:29:52
hmm i`m running debian woody with 2.4.24-grsec kernel and ipv6 support is compiled ... <*> The IPv6 protocol (EXPERIMENTAL) ;) It`s a GNU/Linux :) oh and I changed to /64 and it the same
Kewlio.net problem ...
[ch] Jeroen Massar SixXS Staff on Sunday, 11 January 2004 17:31:44
A grsec patch, now there is a 'default' config. Nevertheless, use tcpdump and find out what is really happening. "the same" doesn't tell anything.
Kewlio.net problem ...
[si] Carmen Sandiego on Sunday, 11 January 2004 17:41:04
hmmm I noticed i don`t get any requests from mv POP. Than I checked if I forget to enable my tunnel, but it`s enabled ... what should I look for with tcpdump? icmp requests? or sth else :)
Kewlio.net problem ...
[ch] Jeroen Massar SixXS Staff on Sunday, 11 January 2004 17:42:26
What do you mean with 'requests'? And ofcourse, if something goes wrong you look at icmp, what else would there be to look at?
Kewlio.net problem ...
[si] Carmen Sandiego on Sunday, 11 January 2004 17:48:06
17:47:14.985487 62.24.229.120 > 193.95.199.107: gw-6.lon-01.gb.sixxs.net > cl-6.lon-01.gb.sixxs.net: icmp6: echo request (encap) 17:47:14.985939 193.95.199.107 > 62.24.229.120: cl-6.lon-01.gb.sixxs.net > gw-6.lon-01.gb.sixxs.net: icmp6: echo reply (encap) 17:47:16.496114 62.24.229.120 > 193.95.199.107: gw-6.lon-01.gb.sixxs.net > cl-6.lon-01.gb.sixxs.net: icmp6: echo request (encap) 17:47:16.496569 193.95.199.107 > 62.24.229.120: cl-6.lon-01.gb.sixxs.net > gw-6.lon-01.gb.sixxs.net: icmp6: echo reply (encap) 17:47:17.925718 62.24.229.120 > 193.95.199.107: gw-6.lon-01.gb.sixxs.net > cl-6.lon-01.gb.sixxs.net: icmp6: echo request (encap) 17:47:17.926166 193.95.199.107 > 62.24.229.120: cl-6.lon-01.gb.sixxs.net > gw-6.lon-01.gb.sixxs.net: icmp6: echo reply (encap) This is what tcpdump | grep sixxs.net said ... should it said more? :)
Kewlio.net problem ...
[ch] Jeroen Massar SixXS Staff on Sunday, 11 January 2004 17:52:02
Which tells us that it works. What was the problem again? When you tcpdump, use -n, that makes the output much better to be read.
Kewlio.net problem ...
[si] Carmen Sandiego on Sunday, 11 January 2004 17:53:13
traceroute to 3ffe:4005:1000:5::2 (3ffe:4005:1000:5::2) from 2001:6f8:910::20, 30 hops max, 16 byte packets 1 gw-15.muc-01.de.sixxs.net (2001:6f8:900:e::1) 32.16 ms 30.999 ms 31.404 ms 2 fe0-1-1-524.br1.enmuc.de.easynet.net (2001:6f8:800:1003::209:55) 31.696 ms 30.742 ms 32.962 ms 3 so0-0-1-0.br0.ixfra.de.easynet.net (2001:6f8:800::51:1:1) 41.542 ms 37.747 ms 41.226 ms 4 2001:6f8:0:210::1 (2001:6f8:0:210::1) 38.102 ms 40.134 ms 37.931 ms 5 2001:6f8::51:20:1 (2001:6f8::51:20:1) 50.526 ms 45.921 ms 46.846 ms 6 so0-1-0-0.gr0.bbpar.fr.easynet.net (2001:6f8::51:11:2) 47.407 ms 47.672 ms 49.088 ms 7 2001:6f8::65:120:1 (2001:6f8::65:120:1) 55.032 ms 54.35 ms 56.537 ms 8 ge1-3-0-0.br1.bllon.uk.easynet.net (2001:6f8:0:600::44:2) 56.566 ms 54.662 ms 54.431 ms 9 2001:6f8:600::61:0:1 (2001:6f8:600::61:0:1) 54.978 ms 53.487 ms 58.869 ms 10 2001:6f8:600:200:290:69ff:fea2:fc00 (2001:6f8:600:200:290:69ff:fea2:fc00) 60.482 ms 60.526 ms 59.809 ms 11 2001:7f8:4:1::cb9:1 (2001:7f8:4:1::cb9:1) 59.431 ms 58.889 ms 58.767 ms 12 so-3-0-0.lon12.ip6.tiscali.net (2001:668:0:2::e1) 59.649 ms 62.066 ms 59.413 ms 13 2001:618:c00:4:10:5cab:6a47:5555 (2001:618:c00:4:10:5cab:6a47:5555) 61.159 ms 60.748 ms 61.045 ms 14 * * 2001:618:c00:4:10:5cab:6a47:5555 (2001:618:c00:4:10:5cab:6a47:5555) 3838.79 ms !H 15 2001:618:c00:4:10:5cab:6a47:5555 (2001:618:c00:4:10:5cab:6a47:5555) 3986.7 ms !H 3971.89 ms !H 3999.84 ms !H emmm traceroute comes to the wrong ip, just like the ping6 ... where in conf file should I set pop ipv6 endpoint?
Kewlio.net problem ...
[ch] Jeroen Massar SixXS Staff on Sunday, 11 January 2004 17:56:08
traceroute to 3ffe:4005:1000:5::2 (3ffe:4005:1000:5::2) from 2001:6f8:910::20, 30 hops max, 16 byte packets You have two tunnels and you will need to fix the routing between/to/from whatever them yourself. Next time say that you are multihoming, not that the POP is having a problem.

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker