|
slow connection, with end-point
![[be]](/s/countries/be.gif) Carmen Sandiego on Wednesday, 16 March 2005 15:25:03
Hi there,
Here's my setup:
I have a router that has a IPv6 tunnel, with this tunnel I also have a subnet
With radvd I give my other computers like a Windows XP Pro client a IPv6 address of that subnet.
Now when I try to surf to a IPv6 website it works fine but really slow.
When I ping my routers ipv6 address and then go to the site it works nice and fast for like 10 seconds. After that it goes slow again unless I keep surfing.
So when I wait like a minute I have to ping my router again so it goes fast.
Is there any reason why it goes so slow again after a while and how can I fix it ?
Oh btw, I also noticed my irc connection from my router with ipv6 pings out alot unless I turn anti-idle on. This wasn't the case before I used the subnet and radvd
slow connection, with end-point
Please show traceroutes etc, because it could be a local problem but also remote. Also check your routing tables and many many others, see Reporting Problems on the Contact page
slow connection, with end-point
Carmen Sandiego on Wednesday, 16 March 2005 13:12:25
-> Windows XP Pro client
C:\Documents and Settings\Koen>ipv6 rt
2001:960:62f::/64 -> 4 pref 8 life 29d23h59m57s/6d23h59m57s (autoconf)
::/0 -> 4/fe80::220:18ff:fea0:43b4 pref 256 life 27s (autoconf)
-> Router (gentoo 2.4.26)
eth0 Link encap:Ethernet HWaddr 00:20:18:A0:43:B4
inet addr:192.168.0.8 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::220:18ff:fea0:43b4/64 Scope:Link
inet6 addr: 2001:960:62f::1/64 Scope:Global
inet6 addr: 2001:960:62f::/48 Scope:Global
inet6 addr: 2001:960:62f::2/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2021862 errors:0 dropped:35 overruns:0 frame:0
TX packets:425497 errors:0 dropped:0 overruns:0 carrier:0
collisions:2554 txqueuelen:1000
RX bytes:187469330 (178.7 Mb) TX bytes:65581693 (62.5 Mb)
Interrupt:11
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:185067 errors:0 dropped:0 overruns:0 frame:0
TX packets:185067 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:15780560 (15.0 Mb) TX bytes:15780560 (15.0 Mb)
sit0 Link encap:IPv6-in-IPv4
inet6 addr: ::192.168.0.8/96 Scope:Compat
inet6 addr: ::127.0.0.1/96 Scope:Unknown
UP RUNNING NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
sit1 Link encap:IPv6-in-IPv4
inet6 addr: fe80::c0a8:8/64 Scope:Link
inet6 addr: 2001:960:2:2cc::2/64 Scope:Global
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:89908 errors:0 dropped:0 overruns:0 frame:0
TX packets:80480 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:23492055 (22.4 Mb) TX bytes:8827248 (8.4 Mb)
mysteria root # route -A inet6
Kernel IPv6 routing table
Destination Next Hop Flags Metric Ref Use Iface
::1/128 :: U 0 4296 0 lo
::127.0.0.1/128 :: U 0 0 0 lo
::192.168.0.8/128 :: U 0 0 0 lo
::/96 :: U 256 0 0 sit0
2001:960:2:2cc::/128 :: U 0 0 0 lo
2001:960:2:2cc::2/128 :: U 0 29063 0 lo
2001:960:2:2cc::/64 :: U 256 18442 1 sit1
2001:960:62f::/128 :: U 0 0 0 lo
2001:960:62f::1/128 :: U 0 6227 0 lo
2001:960:62f::2/128 :: U 0 7 0 lo
2001:960:62f::/64 :: U 256 565 0 sit1
2001:960:62f::/64 :: U 256 0 0 eth0
2001:960:62f::/48 :: U 256 0 0 eth0
2000::/3 2001:960:2:2cc::1 UG 1 4640 2 sit1
fe80::/128 :: U 0 0 0 lo
fe80::c0a8:8/128 :: U 0 0 0 lo
fe80::220:18ff:fea0:43b4/128 :: U 0 171 0 lo
fe80::/64 :: U 256 0 0 eth0
fe80::/64 :: U 256 0 0 sit1
ff02::1/128 ff02::1 UC 0 2 1 eth0
ff00::/8 :: U 256 0 0 eth0
ff00::/8 :: U 256 0 0 sit1
::/0 :: U 256 0 0 sit1
::/0 2001:960:2:2cc::1 UG 1024 0 0 sit1
slow connection, with end-point
::/0 :: U 256 0 0 sit1 ::/0 2001:960:2:2cc::1 UG 1024 0 0 sit1
Two default routes, one going into oblivion, the other to the correct point.
After that, try traceroutes to identify what goes wrong where. If that does not reveal anything, try ethereal.
slow connection, with end-point
Carmen Sandiego on Wednesday, 16 March 2005 15:17:47
i'm not quite familiar with it so how do I remove the bad one?
slow connection, with end-point
ip -6 ro del :: via ::
see 'ip -6 ro help'
slow connection, with end-point
Carmen Sandiego on Wednesday, 16 March 2005 17:58:42
seems to be working very well now, thanks!
i'll be doing some testing, maybe it breaks down within 5 minutes i don't know :)
slow connection, with end-point
Carmen Sandiego on Wednesday, 16 March 2005 20:08:01
yeah its broken again, first 5 minutes it worked
Now i did a traceroute when it was broken:
Tracing route to noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c]
from 2001:960:62f:0:701e:5cb1:aa41:c9de over a maximum of 30 hops:
1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
and so on..
I also noticed on my router it wasn't possible anymore to ping to the Windows client:
mysteria root # ping6 2001:960:62f:0:701e:5cb1:aa41:c9de
PING 2001:960:62f:0:701e:5cb1:aa41:c9de(2001:960:62f:0:701e:5cb1:aa41:c9de) 56 data bytes
From 2001:960:2:2cc::1 icmp_seq=1 Destination unreachable: Address unreachable
From 2001:960:2:2cc::1 icmp_seq=2 Destination unreachable: Address unreachable
From 2001:960:2:2cc::1 icmp_seq=3 Destination unreachable: Address unreachable
From 2001:960:2:2cc::1 icmp_seq=4 Destination unreachable: Address unreachable
--- 2001:960:62f:0:701e:5cb1:aa41:c9de ping statistics ---
4 packets transmitted, 0 received, +4 errors, 100% packet loss, time 3029ms
But as soon as I started to ping from the Windows Client to the router, the router could ping back to the client, very strange
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 16 March 2005 12:58:28
Posting is only allowed when you are