|
Concepts tunnelserver problems?
![[gb]](/s/countries/gb.gif) Shadow Hawkins on Monday, 26 May 2003 15:40:48
I've got three tunnels to the Concepts POP. One of these (2001:838:300:3b::1/64) is working fine, and is shown as such.
Another has yet to be updated to the new prefix (it's currently on 3ffe:4007:300:3a::1/64) - but the tunnelrobot says it's auto-disabled it (and it's shown as disabled), yet it still works.
The third (2001:838:300:5::1/64) isn't working: traceroutes to even the POP end of the tunnel from other Concepts tunnels and ipng.nl tunnels all fail[1], regardless of whether the tunnel is shown as enabled or disabled. I'm not sure how long it takes for tunnels to be enabled or disabled, so I left it enabled for 24 hours, but still got the same results.
It seems, then, that there's a problem enabling or disabling tunnels. Is this related to the transition to the RIPE prefix perhaps?
[1] [chris@solsparc ~]$ traceroute 2001:838:300:5::1
traceroute: Warning: Multiple interfaces found; using 3ffe:8114:1000::3f5 @ ip.tun0:1
traceroute to 2001:838:300:5::1, 30 hops max, 60 byte packets
1 gw-507.ams-02.nl.sixxs.net (3ffe:8114:1000::3f4) 97.835 ms 93.181 ms 94.425 ms
2 Amsterdam.core.ipv6.intouch.net (2001:6e0::2) 97.717 ms 96.376 ms 95.449 ms
3 ams-ix.ipv6.concepts.nl (2001:7f8:1::a501:2871:1) 95.166 ms 171.771 ms 94.350 ms
4 2001:838:0:1:2a0:24ff:feab:3b53 95.997 ms !A 96.545 ms !A 94.024 ms !A
Concepts tunnelserver problems?
Another has yet to be updated to the new prefix (it's currently on 3ffe:4007:300:3a::1/64) - but the tunnelrobot says it's auto-disabled it (and it's shown as disabled), yet it still works.
That's correct, the autodisable is a warning for users still using the old prefix. This prefix will cease to exist in only a couple of days (1st of June 2003)
The third (2001:838:300:5::1/64) isn't working: traceroutes to even the POP end of the tunnel from other Concepts tunnels and ipng.nl tunnels all fail[1], regardless of whether the tunnel is shown as enabled or disabled.
As was written in the email about the transition: the syncing process is not active because of the double prefixes for which the system was not designed ;)
And unless we are going to do massive multihoming it is not planned to be implemented.
Some 'manual' syncs are done at random intervals and if your tunnel is enabled it will be configured too.
Concepts tunnelserver problems?
![[de]](/s/countries/de.gif) Shadow Hawkins on Sunday, 01 June 2003 20:47:44
is the following Problem based on the same reasons?
-------------------------
20:44:57.516156 213.217.108.xx > 213.197.27.252: 2001:838:300:53::2 > 2001:838:300:53::1: icmp6: echo request
20:44:57.542191 213.197.27.252 > 213.217.108.xx: icmp: 213.197.27.252 protocol 41 unreachable [tos 0xc0]
-------------------------
Concepts tunnelserver problems?
You just re-enabled your tunnel and the POP's don't get reconfigured at the same instant. Also see FAQ.
Seems to be working quite well in the mean time.
PING 2001:838:300:53::2(2001:838:300:53::2) 56 data bytes
64 bytes from 2001:838:300:53::2: icmp_seq=1 ttl=61 time=29.2 ms
The POP started syncing again since this (1 June 2003) morning 0:00 before that it didn't sync from the day we started the transition.
|
![[ch]](/s/countries/ch.gif)
on Monday, 26 May 2003 23:03:52
Posting is only allowed when you are