SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #6568038
Ticket Status: Remote Problem

PoP: nlams05 - SURFnet (Amsterdam)

Routing issue with reader.ipv6.xsnews.nl?
[nl] Shadow Hawkins on Friday, 02 March 2012 21:58:14
I think there is a routing problem with reader.ipv6.xsnews.nl and the nlams05 pop. From time to time I get connection timeouts when using the nlams05 pop. My friend is also using the nlams05 pop and he has exactly the same problem with reader.ipv6.xsnews.nl. He is also experiencing connection timeouts from time to time. Another friend is using the beanr01 pop. He has no connection timeout issues with reader.ipv6.xsnews.nl. I helped both friends with their tunnel setups, so it's not a configuration problem. Second, i tested with a HE tunnel and didn't experienced any connection timeouts. This must be a problem with nlams05. To give an example of the problem: C:\Users\Administrator>telnet reader.ipv6.xsnews.nl 119 Er wordt verbinding gemaakt met reader.ipv6.xsnews.nl...Kan geen verbinding met de host maken, op poort 119: Het maken van de verbinding is mislukt <----------------------- timeout C:\Users\Administrator>telnet reader.ipv6.xsnews.nl 119 Er wordt verbinding gemaakt met reader.ipv6.xsnews.nl...Kan geen verbinding met de host maken, op poort 119: Het maken van de verbinding is mislukt <----------------------- timeout C:\Users\Administrator>telnet reader.ipv6.xsnews.nl 119 201 reader-e01-08.ipv6.xsnews.nl NNRP Service Ready (no posting). <----------------------- working! quit 205 Transferred 67 bytes in 0 articles, 0 groups. Disconnecting De verbinding met de host is verbroken. C:\Users\Administrator>telnet reader.ipv6.xsnews.nl 119 Er wordt verbinding gemaakt met reader.ipv6.xsnews.nl...Kan geen verbinding met de host maken, op poort 119: Het maken van de verbinding is mislukt <----------------------- timeout C:\Users\Administrator>telnet reader.ipv6.xsnews.nl 119 Er wordt verbinding gemaakt met reader.ipv6.xsnews.nl...Kan geen verbinding met de host maken, op poort 119: Het maken van de verbinding is mislukt <----------------------- timeout etc. etc. Tracerts: C:\Users\Administrator>tracert reader.ipv6.xsnews.nl Traceren van de route naar reader.ipv6.xsnews.nl [2001:67c:174:101::1337] via maximaal 30 hops: 1 5 ms 5 ms 5 ms gw-2365.ams-05.nl.sixxs.net [2001:610:600:93c::1 ] 2 6 ms 5 ms 5 ms sixxs.surfnet.nl [2001:610:1:80bb:192:87:102:107 ] 3 6 ms 6 ms 5 ms vl163.sw14.amsterdam1.surf.net [2001:610:1:80bb: 192:87:102:97] 4 6 ms 6 ms 5 ms 2001:610:f01:9168::169 5 6 ms 6 ms 6 ms AE0.500.JNR02.Asd001A.surf.net [2001:610:e08:76: :77] 6 11 ms 6 ms 16 ms tge2-2.ams01-1.eu.as5580.net [2001:7f8:1::a500:5 580:2] 7 9 ms 15 ms 6 ms r1.ams5.nl.as5580.net [2a02:d28:5580::1:d] 8 * 7 ms * as48345-gw.r1.ams5.nl.as5580.net [2a02:d28:5580: <----------------------- takes long time 1::3303:2] 9 * * 6 ms 20ge-r1.as48345.net [2001:67c:174::1:1] <----------------------- takes long time 10 7 ms 7 ms 7 ms 2001:67c:174:101::1337 De trace is voltooid. C:\Users\Administrator>tracert reader.ipv6.xsnews.nl Traceren van de route naar reader.ipv6.xsnews.nl [2001:67c:174:101::1337] via maximaal 30 hops: 1 5 ms 5 ms 5 ms gw-2365.ams-05.nl.sixxs.net [2001:610:600:93c::1 ] 2 5 ms 5 ms 5 ms sixxs.surfnet.nl [2001:610:1:80bb:192:87:102:107 ] 3 6 ms 5 ms 5 ms vl163.sw14.amsterdam1.surf.net [2001:610:1:80bb: 192:87:102:97] 4 7 ms 5 ms 5 ms 2001:610:f01:9168::169 5 6 ms 6 ms 6 ms AE0.500.JNR02.Asd001A.surf.net [2001:610:e08:76: :77] 6 14 ms 6 ms 17 ms tge2-2.ams01-1.eu.as5580.net [2001:7f8:1::a500:5 580:2] 7 13 ms 15 ms 7 ms r1.ams5.nl.as5580.net [2a02:d28:5580::1:d] 8 * 6 ms * as48345-gw.r1.ams5.nl.as5580.net [2a02:d28:5580: <----------------------- takes long time 1::3303:2] 9 6 ms * * 20ge-r1.as48345.net [2001:67c:174::1:1] <----------------------- takes long time 10 12 ms 7 ms 7 ms 2001:67c:174:101::1337 De trace is voltooid. C:\Users\Administrator>tracert reader.ipv6.xsnews.nl Traceren van de route naar reader.ipv6.xsnews.nl [2001:67c:174:101::1337] via maximaal 30 hops: 1 5 ms 5 ms 5 ms gw-2365.ams-05.nl.sixxs.net [2001:610:600:93c::1 ] 2 5 ms 5 ms 5 ms sixxs.surfnet.nl [2001:610:1:80bb:192:87:102:107 ] 3 6 ms 6 ms 6 ms vl163.sw14.amsterdam1.surf.net [2001:610:1:80bb: 192:87:102:97] 4 6 ms 5 ms 5 ms 2001:610:f01:9168::169 5 6 ms 6 ms 6 ms AE0.500.JNR02.Asd001A.surf.net [2001:610:e08:76: :77] 6 6 ms 12 ms 6 ms tge2-2.ams01-1.eu.as5580.net [2001:7f8:1::a500:5 580:2] 7 6 ms 12 ms 6 ms r1.ams5.nl.as5580.net [2a02:d28:5580::1:d] 8 6 ms * 7 ms as48345-gw.r1.ams5.nl.as5580.net [2a02:d28:5580: <----------------------- takes long time 1::3303:2] 9 6 ms * 6 ms 20ge-r1.as48345.net [2001:67c:174::1:1] <----------------------- takes long time 10 9 ms 7 ms 6 ms 2001:67c:174:101::1337 De trace is voltooid. C:\Users\Administrator>tracert reader.ipv6.xsnews.nl Traceren van de route naar reader.ipv6.xsnews.nl [2001:67c:174:101::1337] via maximaal 30 hops: 1 5 ms 5 ms 5 ms gw-2365.ams-05.nl.sixxs.net [2001:610:600:93c::1 ] 2 6 ms 5 ms 5 ms sixxs.surfnet.nl [2001:610:1:80bb:192:87:102:107 ] 3 6 ms 6 ms 6 ms vl163.sw14.amsterdam1.surf.net [2001:610:1:80bb: 192:87:102:97] 4 5 ms 6 ms 5 ms 2001:610:f01:9168::169 5 6 ms 6 ms 6 ms AE0.500.JNR02.Asd001A.surf.net [2001:610:e08:76: :77] 6 10 ms 6 ms 15 ms tge2-2.ams01-1.eu.as5580.net [2001:7f8:1::a500:5 580:2] 7 10 ms 6 ms 16 ms r1.ams5.nl.as5580.net [2a02:d28:5580::1:d] 8 * 7 ms * as48345-gw.r1.ams5.nl.as5580.net [2a02:d28:5580: <----------------------- takes long time 1::3303:2] 9 * 6 ms * 20ge-r1.as48345.net [2001:67c:174::1:1] <----------------------- takes long time 10 9 ms 7 ms 7 ms 2001:67c:174:101::1337 De trace is voltooid. C:\Users\Administrator>tracert reader.ipv6.xsnews.nl Traceren van de route naar reader.ipv6.xsnews.nl [2001:67c:174:101::1337] via maximaal 30 hops: 1 5 ms 5 ms 5 ms gw-2365.ams-05.nl.sixxs.net [2001:610:600:93c::1 ] 2 5 ms 5 ms 5 ms sixxs.surfnet.nl [2001:610:1:80bb:192:87:102:107 ] 3 6 ms 6 ms 6 ms vl163.sw14.amsterdam1.surf.net [2001:610:1:80bb: 192:87:102:97] 4 6 ms 6 ms 5 ms 2001:610:f01:9168::169 5 6 ms 39 ms 6 ms AE0.500.JNR02.Asd001A.surf.net [2001:610:e08:76: :77] 6 6 ms 11 ms 6 ms tge2-2.ams01-1.eu.as5580.net [2001:7f8:1::a500:5 580:2] 7 6 ms 21 ms 15 ms r1.ams5.nl.as5580.net [2a02:d28:5580::1:d] 8 * 7 ms * as48345-gw.r1.ams5.nl.as5580.net [2a02:d28:5580: <----------------------- takes long time 1::3303:2] 9 7 ms * 6 ms 20ge-r1.as48345.net [2001:67c:174::1:1] <----------------------- takes long time 10 7 ms 7 ms 6 ms 2001:67c:174:101::1337 De trace is voltooid. With HE tunnel: C:\Users\Administrator>telnet reader.ipv6.xsnews.nl 119 201 reader-e01-08.ipv6.xsnews.nl NNRP Service Ready (no posting). <----------------------- working! quit 205 Transferred 67 bytes in 0 articles, 0 groups. Disconnecting De verbinding met de host is verbroken. C:\Users\Administrator>telnet reader.ipv6.xsnews.nl 119 201 reader-e01-08.ipv6.xsnews.nl NNRP Service Ready (no posting). <----------------------- working! quit 205 Transferred 67 bytes in 0 articles, 0 groups. Disconnecting De verbinding met de host is verbroken. C:\Users\Administrator>telnet reader.ipv6.xsnews.nl 119 201 reader-e01-08.ipv6.xsnews.nl NNRP Service Ready (no posting). <----------------------- working! quit 205 Transferred 67 bytes in 0 articles, 0 groups. Disconnecting De verbinding met de host is verbroken. C:\Users\Administrator>telnet reader.ipv6.xsnews.nl 119 201 reader-e01-08.ipv6.xsnews.nl NNRP Service Ready (no posting). <----------------------- working! quit 205 Transferred 67 bytes in 0 articles, 0 groups. Disconnecting De verbinding met de host is verbroken. C:\Users\Administrator>telnet reader.ipv6.xsnews.nl 119 201 reader-e01-08.ipv6.xsnews.nl NNRP Service Ready (no posting). <----------------------- working! quit 205 Transferred 67 bytes in 0 articles, 0 groups. Disconnecting De verbinding met de host is verbroken. Tracerts: C:\Users\Administrator>tracert reader.ipv6.xsnews.nl Traceren van de route naar reader.ipv6.xsnews.nl [2001:67c:174:101::1337] via maximaal 30 hops: 1 13 ms 12 ms 13 ms 2001:470:1f14:1cc7::1 2 6 ms 14 ms 6 ms gige-g2-20.core1.ams1.he.net [2001:470:0:7d::1] 3 23 ms 12 ms 21 ms 10gigabitethernet1-4.core1.lon1.he.net [2001:470 :0:3f::1] 4 12 ms 12 ms 12 ms 2001:7f8:17::c388:1 5 23 ms 23 ms 13 ms 2001:7f8:17::15cc:1 6 17 ms 23 ms 24 ms r1.ams2.nl.as5580.net [2a02:d28:5580::1:a2] 7 21 ms 63 ms 12 ms r2.ams5.nl.as5580.net [2a02:d28:5580::1:9] 8 19 ms 13 ms 12 ms as48345-gw.r2.ams5.nl.as5580.net [2a02:d28:5580: 1::3302:2] 9 13 ms 22 ms 24 ms 20ge-r1.as48345.net [2001:67c:174::1:1] 10 13 ms 13 ms 13 ms 2001:67c:174:101::1337 De trace is voltooid. C:\Users\Administrator>tracert reader.ipv6.xsnews.nl Traceren van de route naar reader.ipv6.xsnews.nl [2001:67c:174:101::1337] via maximaal 30 hops: 1 13 ms 12 ms 13 ms 2001:470:1f14:1cc7::1 2 5 ms 5 ms 13 ms gige-g2-20.core1.ams1.he.net [2001:470:0:7d::1] 3 12 ms 15 ms 12 ms 10gigabitethernet1-4.core1.lon1.he.net [2001:470 :0:3f::1] 4 12 ms 23 ms 12 ms 2001:7f8:17::c388:1 5 12 ms 14 ms 23 ms 2001:7f8:17::15cc:1 6 17 ms 19 ms 27 ms r1.ams2.nl.as5580.net [2a02:d28:5580::1:a2] 7 12 ms 15 ms 23 ms r2.ams5.nl.as5580.net [2a02:d28:5580::1:9] 8 19 ms 13 ms 12 ms as48345-gw.r2.ams5.nl.as5580.net [2a02:d28:5580: 1::3302:2] 9 13 ms 13 ms 20 ms 20ge-r1.as48345.net [2001:67c:174::1:1] 10 18 ms 12 ms 14 ms 2001:67c:174:101::1337 De trace is voltooid. C:\Users\Administrator>tracert reader.ipv6.xsnews.nl Traceren van de route naar reader.ipv6.xsnews.nl [2001:67c:174:101::1337] via maximaal 30 hops: 1 14 ms 12 ms 12 ms 2001:470:1f14:1cc7::1 2 10 ms 5 ms 5 ms gige-g2-20.core1.ams1.he.net [2001:470:0:7d::1] 3 12 ms 15 ms 12 ms 10gigabitethernet1-4.core1.lon1.he.net [2001:470 :0:3f::1] 4 17 ms 12 ms 12 ms 2001:7f8:17::c388:1 5 13 ms 22 ms 13 ms 2001:7f8:17::15cc:1 6 17 ms 19 ms 23 ms r1.ams2.nl.as5580.net [2a02:d28:5580::1:a2] 7 13 ms 14 ms 12 ms r2.ams5.nl.as5580.net [2a02:d28:5580::1:9] 8 19 ms 13 ms 13 ms as48345-gw.r2.ams5.nl.as5580.net [2a02:d28:5580: 1::3302:2] 9 13 ms 13 ms 18 ms 20ge-r1.as48345.net [2001:67c:174::1:1] 10 17 ms 12 ms 13 ms 2001:67c:174:101::1337 De trace is voltooid. C:\Users\Administrator>tracert reader.ipv6.xsnews.nl Traceren van de route naar reader.ipv6.xsnews.nl [2001:67c:174:101::1337] via maximaal 30 hops: 1 14 ms 14 ms 12 ms 2001:470:1f14:1cc7::1 2 5 ms 5 ms 5 ms gige-g2-20.core1.ams1.he.net [2001:470:0:7d::1] 3 12 ms 20 ms 12 ms 10gigabitethernet1-4.core1.lon1.he.net [2001:470 :0:3f::1] 4 13 ms 12 ms 15 ms 2001:7f8:17::c388:1 5 18 ms 22 ms 28 ms 2001:7f8:17::15cc:1 6 12 ms 25 ms 18 ms r1.ams2.nl.as5580.net [2a02:d28:5580::1:a2] 7 23 ms 13 ms 12 ms r2.ams5.nl.as5580.net [2a02:d28:5580::1:9] 8 13 ms 13 ms 12 ms as48345-gw.r2.ams5.nl.as5580.net [2a02:d28:5580: 1::3302:2] 9 13 ms 13 ms 19 ms 20ge-r1.as48345.net [2001:67c:174::1:1] 10 13 ms 12 ms 18 ms 2001:67c:174:101::1337 De trace is voltooid. C:\Users\Administrator>tracert reader.ipv6.xsnews.nl Traceren van de route naar reader.ipv6.xsnews.nl [2001:67c:174:101::1337] via maximaal 30 hops: 1 14 ms 13 ms 13 ms 2001:470:1f14:1cc7::1 2 5 ms 5 ms 5 ms gige-g2-20.core1.ams1.he.net [2001:470:0:7d::1] 3 23 ms 25 ms 12 ms 10gigabitethernet1-4.core1.lon1.he.net [2001:470 :0:3f::1] 4 12 ms 12 ms 13 ms 2001:7f8:17::c388:1 5 12 ms 17 ms 27 ms 2001:7f8:17::15cc:1 6 13 ms 23 ms 24 ms r1.ams2.nl.as5580.net [2a02:d28:5580::1:a2] 7 13 ms 15 ms 24 ms r2.ams5.nl.as5580.net [2a02:d28:5580::1:9] 8 19 ms 14 ms 13 ms as48345-gw.r2.ams5.nl.as5580.net [2a02:d28:5580: 1::3302:2] 9 13 ms 23 ms 24 ms 20ge-r1.as48345.net [2001:67c:174::1:1] 10 13 ms 13 ms 13 ms 2001:67c:174:101::1337 De trace is voltooid.
State change: remoteproblem Locked
[ch] Jeroen Massar SixXS Staff on Saturday, 03 March 2012 10:27:42
Message is Locked
The state of this ticket has been changed to remoteproblem
Routing issue with reader.ipv6.xsnews.nl?
[ch] Jeroen Massar SixXS Staff on Saturday, 03 March 2012 10:28:53
We do not run that service (reader.ipv6.xsnews.nl) and cannot do anything about it. Contact them for any problems you have with it.

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

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