|
Windows XP unable to ping internal/external ipv6 address's
![[ie]](/s/countries/ie.gif) Shadow Hawkins on Thursday, 18 March 2004 03:49:53
Hi,
I'm currently having a problem with my XP machine not able to ping internal ipv6 or external via my subnet, the tunnel is setup on a FreeBSD 5.2 machine and the tunnnel is working fine. Any ideas or docs that might help much apreciated. my configuration is as follows
radvd.conf
interface sis1
{
AdvSendAdvert on;
prefix 2001:770:111::/64
{
};
};
-----------------------------------------------------
ifconfig
sis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 fe80::202:e3ff:fe14:72a3%sis0 prefixlen 64 scopeid 0x1
inet6 2001:770:111::1 prefixlen 64
inet6 2001:770:111::4 prefixlen 64
inet 81.111.80.240 netmask 0xffffff00 broadcast 255.255.255.255
ether 00:02:e3:14:72:a3
media: Ethernet autoselect (10baseT/UTP)
status: active
sis1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
inet6 fe80::202:e3ff:fe12:39b4%sis1 prefixlen 64 scopeid 0x2
inet6 2001:770:111::1 prefixlen 64
ether 00:02:e3:12:39:b4
media: Ethernet autoselect (10baseT/UTP)
status: active
plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
gif0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1280
tunnel inet 81.111.80.240 --> 193.1.31.74
inet6 fe80::202:e3ff:fe14:72a3%gif0 prefixlen 64 scopeid 0x5
inet6 2001:770:100:1f::2 --> 2001:770:100:1f::1 prefixlen 128
Windows config
netsh int ipv6 show neigh
Interface 4: Local Area Connection
Internet Address Physical Address Type
--------------------------------------------- ----------------- -----------
fe80::202:e3ff:fe12:39b4 00-02-e3-12-39-b4 Stale (router)
fe80::20c:76ff:fe54:fff3 00-0c-76-54-ff-f3 Permanent
2001:770:111:0:20c:76ff:fe54:fff3 00-0c-76-54-ff-f3 Permanent
2001:770:111:0:2dea:9ed3:42ea:885e 00-0c-76-54-ff-f3 Permanent
ipconfig
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 2001:770:111:0:2dea:9ed3:42ea:885e
IP Address. . . . . . . . . . . . : 2001:770:111:0:20c:76ff:fe54:fff3
IP Address. . . . . . . . . . . . : fe80::20c:76ff:fe54:fff3%4
Default Gateway . . . . . . . . . : 192.168.0.1
fe80::202:e3ff:fe12:39b4%4
ipv6 if
Interface 4: Ethernet: Local Area Connection
Guid {7D0F573D-2394-4C9C-8DE4-98E4D5C5278E}
uses Neighbor Discovery
uses Router Discovery
link-layer address: 00-0c-76-54-ff-f3
preferred global 2001:770:111:0:2dea:9ed3:42ea:885e, life 6d23h46m10s/23h43m
23s (temporary)
preferred global 2001:770:111:0:20c:76ff:fe54:fff3, life 29d23h55m35s/6d23h5
5m35s (public)
preferred link-local fe80::20c:76ff:fe54:fff3, life infinite
multicast interface-local ff01::1, 1 refs, not reportable
multicast link-local ff02::1, 1 refs, not reportable
multicast link-local ff02::1:ff54:fff3, 2 refs, last reporter
multicast link-local ff02::1:ffea:885e, 1 refs, last reporter
link MTU 1500 (true link MTU 1500)
current hop limit 128
reachable time 24000ms (base 30000ms)
retransmission interval 1000ms
DAD transmits 1
default site prefix length 48
the following is a tcpdum from the bsd box when i try to ping 6bone from the windows XP machine
emboss# tcpdump -i sis1 icmp6
tcpdump: listening on sis1
02:36:01.693804 2001:770:111:0:2dea:9ed3:42ea:885e > www.6bone.net: icmp6: echo request
02:36:05.241348 2001:770:111:0:2dea:9ed3:42ea:885e > www.6bone.net: icmp6: echo request
02:36:06.240979 fe80::20c:76ff:fe54:fff3 > fe80::202:e3ff:fe12:39b4: icmp6: neighbor sol: who has fe80::202:e3ff:fe12:39b4
02:36:06.241070 fe80::202:e3ff:fe12:39b4 > fe80::20c:76ff:fe54:fff3: icmp6: neighbor adv: tgt is fe80::202:e3ff:fe12:39b4
02:36:09.241209 2001:770:111:0:2dea:9ed3:42ea:885e > www.6bone.net: icmp6: echo request
02:36:11.624349 fe80::202:e3ff:fe12:39b4 > fe80::20c:76ff:fe54:fff3: icmp6: neighbor sol: who has fe80::20c:76ff:fe54:fff3
02:36:11.624666 fe80::20c:76ff:fe54:fff3 > fe80::202:e3ff:fe12:39b4: icmp6: neighbor adv: tgt is fe80::20c:76ff:fe54:fff3
02:36:13.241063 2001:770:111:0:2dea:9ed3:42ea:885e > www.6bone.net: icmp6: echo request
Windows XP unable to ping internal/external ipv6 address's
Unimportant bits cut out, we see:
sis0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 2001:770:111::1 prefixlen 64
inet6 2001:770:111::4 prefixlen 64
sis1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet6 2001:770:111::1 prefixlen 64
Same address on two different network interfaces?
You have a /48, thus push a different /64 on each one.
Next to that you might want to check XP's firewall settings which might cause ICMPv6 to be filtered.
And last but not least: did you enable forwarding ?
Windows XP unable to ping internal/external ipv6 address's
Shadow Hawkins on Friday, 19 March 2004 01:28:16
Hi Jeroen
I didn't think it mattered if you aliased the same ip to two different cards?
No firewall on the XP machine
and forwarding is enabled.
Windows XP unable to ping internal/external ipv6 address's
I didn't think it mattered if you aliased the same ip to two different cards?
It does, because you know have two /64 routes to two different interfaces and where does your router need to send packets destined to that /64 to?
First come first serve and that is probably the wrong interface.
No firewall on the XP machine
XP SP1 has a default builtin firewall and one really should run SP1 because of the many patches, thus you have a firewall, unless you disabled it of course.
(see: netsh int ipv6 firewall)
Windows XP unable to ping internal/external ipv6 address's
Shadow Hawkins on Friday, 19 March 2004 17:47:41It does, because you know have two /64 routes to two different interfaces and where does your router need to send packets destined to that /64 to? First come first serve and that is probably the wrong interface.
Yes did seem to be causing the problem I removed the IPv6 address from sis1 and everything now works fine.
XP SP1 has a default builtin firewall and one really should run SP1 because of the many patches, thus you have a firewall, unless you disabled it of course.
I should have made it more clear in my post, the builtin firewall was disabled
Thanks for your help
happy IPv6 camper :)
|
![[ch]](/s/countries/ch.gif)
on Thursday, 18 March 2004 22:56:46
Posting is only allowed when you are