|
Problems with a windows xp client
![[be]](/s/countries/be.gif) Shadow Hawkins on Sunday, 27 March 2005 15:25:36
Hi all :P
Yesterday, I've got my 'brand' new subnet. But I have some strange problems with the configuration of the clients espcecially the xp one.
Let me explain,
My tunnel's endpoint : 2001:6f8:202:16::2
My subnet : 2001:6f8:30d::/48
My client's config :
C:\>ipconfig
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 10.0.0.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 2001:6f8:30d:10:2e0:18ff:fef1:807d
IP Address. . . . . . . . . . . . : fe80::2e0:18ff:fef1:807d%5
Default Gateway . . . . . . . . . : 10.0.0.1
fe80::204:76ff:feef:d355%5
netsh interface ipv6>show route
Querying active state...
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- ---- ------------------------ --- ---------------------
no Autoconf 8 2001:6f8:30d:10::/64 5 Local Area Connection
no Autoconf 256 ::/0 5 fe80::204:76ff:feef:d355
From the client, I can ping6 my gateway and the two ends of my tunnel(2001:6f8:202:16::2 & 2001:6f8:202:16::1) :
C:\>ping6 2001:6f8:202:16::2
Pinging 2001:6f8:202:16::2
from 2001:6f8:30d:10:2e0:18ff:fef1:807d with 32 bytes of data:
Reply from 2001:6f8:202:16::2: bytes=32 time<1ms
Reply from 2001:6f8:202:16::2: bytes=32 time<1ms
C:\>ping6 2001:6f8:202:16::1
Pinging 2001:6f8:202:16::1
from 2001:6f8:30d:10:2e0:18ff:fef1:807d with 32 bytes of data:
Reply from 2001:6f8:202:16::1: bytes=32 time=7ms
Reply from 2001:6f8:202:16::1: bytes=32 time=7ms
But ! I can't ping any outside address, for example :
C:\>ping6 www.kame.net
Pinging www.kame.net [2001:200:0:8002:203:47ff:fea5:3085]
from 2001:6f8:30d:10:2e0:18ff:fef1:807d with 32 bytes of data:
Reply from 2001:6f8:30d:10::1: No route to destination.
Reply from 2001:6f8:30d:10::1: No route to destination.
Here's my server's config (On debian) :
eth0 Lien encap:Ethernet HWaddr 00:04:76:EF:D3:55
inet adr:10.0.0.1 Bcast:10.0.0.255 Masque:255.255.255.0
adr inet6: 2001:6f8:30d:10::1/64 Scope:Global
adr inet6: fe80::204:76ff:feef:d355/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:87353278 errors:0 dropped:0 overruns:15293 frame:0
TX packets:87482902 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
RX bytes:3393842449 (3.1 GiB) TX bytes:1441958879 (1.3 GiB)
Interruption:11 Adresse de base:0xe800
eth1 Lien encap:Ethernet HWaddr 00:04:E2:23:A4:4C
inet adr:192.168.0.1 Bcast:192.168.0.255 Masque:255.255.255.0
adr inet6: fe80::204:e2ff:fe23:a44c/64 Scope:Lien
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:31019936 errors:709 dropped:0 overruns:709 frame:709
TX packets:24762767 errors:2 dropped:0 overruns:0 carrier:4
collisions:0 lg file transmission:1000
RX bytes:3902159693 (3.6 GiB) TX bytes:2434625496 (2.2 GiB)
Interruption:12 Adresse de base:0xec00
lo Lien encap:Boucle locale
inet adr:127.0.0.1 Masque:255.0.0.0
adr inet6: ::1/128 Scope:Hôte
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6301 errors:0 dropped:0 overruns:0 frame:0
TX packets:6301 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:0
RX bytes:748026 (730.4 KiB) TX bytes:748026 (730.4 KiB)
ppp0 Lien encap:Protocole Point-Ã -Point
inet adr:81.242.224.81 P-t-P:81.242.224.1 Masque:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:43221 errors:0 dropped:0 overruns:0 frame:0
TX packets:44859 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:3
RX bytes:23440038 (22.3 MiB) TX bytes:9441094 (9.0 MiB)
sixxs Lien encap:IPv6-dans-IPv4
adr inet6: 2001:6f8:202:16::2/64 Scope:Global
adr inet6: fe80::a00:1/64 Scope:Lien
adr inet6: fe80::51f2:f7b4/64 Scope:Lien
adr inet6: fe80::c0a8:1/64 Scope:Lien
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:41304 errors:0 dropped:0 overruns:0 frame:0
TX packets:32357 errors:18 dropped:0 overruns:0 carrier:18
collisions:0 lg file transmission:0
RX bytes:31908294 (30.4 MiB) TX bytes:3406658 (3.2 MiB)
my ip -6 route :
2001:6f8:202:16::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 64
2001:6f8:30d:10::/64 dev eth0 metric 256 mtu 1500 advmss 1440 hoplimit 64
fe80::/64 via :: dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 64
fe80::/64 dev eth0 metric 256 mtu 1500 advmss 1440 hoplimit 64
fe80::/64 dev eth1 metric 256 mtu 1500 advmss 1440 hoplimit 64
ff00::/8 dev sixxs metric 256 mtu 1280 advmss 1220 hoplimit 1
ff00::/8 dev eth0 metric 256 mtu 1500 advmss 1440 hoplimit 1
ff00::/8 dev eth1 metric 256 mtu 1500 advmss 1440 hoplimit 1
default via 2001:6f8:202:16::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 64
unreachable default dev lo proto none metric -1 error -101 advmss 1220 hoplimit 255
... and my /etc/radvd.conf :
interface eth0
{
AdvSendAdvert on;
prefix 2001:6f8:30d:10::/64
{
AdvOnLink on;
AdvAutonomous on;
};
};
Of course, I have turned on the forwarding on my router.
I don't know what's is wrong with my configuration (i'm still a noob :(), maybe some of you (hope so) could help.
Thanks in advance. :D
Ps : sorry for the very long message.
Problems with a windows xp client
8<------------
C:\>ping6 www.kame.net
Pinging www.kame.net [2001:200:0:8002:203:47ff:fea5:3085]
from 2001:6f8:30d:10:2e0:18ff:fef1:807d with 32 bytes of data:
Reply from 2001:6f8:30d:10::1: No route to destination.
----------->8
This says "Hi I am your gateway and I have no route to the destination you requested" as such, check your routing table. Then you can realize two things "I have linux" "Linux used to have some weird things with default routes".
Solution:
ip -6 ro add 2000::/3 dev sixxs via 2001:6f8:202:16::1
but better upgrade your kernel to something that doesn't have this default-is-not-entirely-default sillyness.
Problems with a windows xp client
Shadow Hawkins on Sunday, 27 March 2005 18:25:59
Problem solved !
Thank you :)
|
![[ch]](/s/countries/ch.gif)
on Sunday, 27 March 2005 16:45:05
Posting is only allowed when you are