Can't ping beyond PoP endpoint from subnet host
Shadow Hawkins on Wednesday, 13 October 2004 15:21:48
Hi,
I'm having trouble accessing any ipv6 address outside the POP tunnel's endpoint from my winXP host (in subnet).
I've spend the last 4 days going through the FAQ's and Forum, and although there were some valid suggestions (e.g. adding 3 proto 41 entries to iptables firewall, adding subnet/64 to the routertable) I still can't get it to work.
This is my layout:
Internet <---> PoP <--tunnel--> [eth0]Linux Router[eth1] <--subnet--> WinXP
Redhat kernel 2.4.9-34 SP1
The tunnel works perfectly; from the router I can ping and access any IPv6 address. From my WinXP host I can ping6 my local tunnel endpoint AND the POP tunnel endpoint, but nothing beyond that. :?
I'm guessing something is wrong with the routing on eth1 (but I only started using IPv6 a week ago, so I don't know much yet!).
My IPv6 endpoint: 2001:960:2:37d::2
PoP IPv6 endpoint: 2001:960:2:37d::1
Subnet: 2001:960:72c::/48
This is my router setup:
(radvd is running)
radvd.conf:
interface eth1
{
AdvSendAdvert on;
prefix 2001:960:72c::/64
{
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
};
# ip -6 ro sho
2001:960:2:37d::/64 dev sixxs metric 256 mtu 1280 advmss 1220
2001:960:72c::/64 dev eth1 metric 256 mtu 1500 advmss 1440
fe80::/10 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440
fe80::/10 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440
fe80::/10 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220
ff00::/8 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440
ff00::/8 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440
ff00::/8 dev sixxs proto kernel metric 256 mtu 1280 advmss 1220
default via 2001:960:2:37d::1 dev sixxs metric 1024 mtu 1280 advmss 1220
unreachable default dev lo metric -1 error -101 advmss 1220
# ip -6 addr sho
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
inet6 ::1/128 scope host
2: eth0: <BROADCAST,PROMISC,NOTRAILERS,UP> mtu 1500 qdisc pfifo_fast qlen 100
inet6 fe80::201:2ff:fe0b:da9/10 scope link
3: eth1: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 100
inet6 fe80::2a0:24ff:fe33:892b/10 scope link
5: sixxs@NONE: <POINTOPOINT,NOARP,UP> mtu 1280 qdisc noqueue
inet6 fe80::d4bb:538d/10 scope link
inet6 2001:960:2:37d::2/64 scope global
inet6 fe80::c0a8:7fa/10 scope link
WinXP setup:
netsh interface ipv6 show address Querying active state...
Interface 5: Teredo Tunneling Pseudo-Interface
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Link Preferred infinite infinite fe80::5445:5245:444f
Interface 4: Local Area Connection
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Public Preferred 29d23h57m53s 6d23h57m53s 2001:960:72c:0:4a54:e8ff:fe21:cd
d2
Link Preferred infinite infinite fe80::4a54:e8ff:fe21:cdd2
Interface 2: Automatic Tunneling Pseudo-Interface
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Link Preferred infinite infinite fe80::5efe:192.168.7.21
Interface 1: Loopback Pseudo-Interface
Addr Type DAD State Valid Life Pref. Life Address
--------- ---------- ------------ ------------ -----------------------------
Loopback Preferred infinite infinite ::1
Link Preferred infinite infinite fe80::1
(So radvd seems to be working ok.)
netsh interface ipv6 show route Querying active state...
Publish Type Met Prefix Idx Gateway/Interface Name
------- -------- ---- ------------------------ --- ---------------------
no Autoconf 8 2001:960:72c::/64 6 Local Area Connection
no Autoconf 256 ::/0 6 fe80::2a0:24ff:fe33:892b
All looks ok to me.
Is there sombody who knows what is going on here?
Please help me. Any other ideas are more than welcome... 8-)
Can't ping beyond PoP endpoint from subnet host
Shadow Hawkins on Wednesday, 13 October 2004 16:43:02
Sorry, forgot to add the ping results:
ping6 2001:960:2:37d::1 (POP endpoint)
Pinging 2001:960:2:37d::1
from 2001:960:72c:0:4a54:e8ff:fe21:cdd2 with 32 bytes of data:
Reply from 2001:960:2:37d::1: bytes=32 time=32ms
Reply from 2001:960:2:37d::1: bytes=32 time=33ms
Reply from 2001:960:2:37d::1: bytes=32 time=33ms
Reply from 2001:960:2:37d::1: bytes=32 time=34ms
Ping statistics for 2001:960:2:37d::1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 34ms, Average = 33ms
ping6 www.sixxs.net
Pinging noc.sixxs.net [2001:838:1:1:210:dcff:fe20:7c7c]
from 2001:960:72c:0:4a54:e8ff:fe21:cdd2 with 32 bytes of data:
Reply from 2001:960:2:37d::2: Destination address unreachable.
Reply from 2001:960:2:37d::2: Destination address unreachable.
Reply from 2001:960:2:37d::2: Destination address unreachable.
Reply from 2001:960:2:37d::2: Destination address unreachable.
Ping statistics for 2001:838:1:1:210:dcff:fe20:7c7c:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Tcpdump on eth0 while pinging the POP endpoint shows activity, but while pinging sixxs.net not. Forwarding (sysctl) is also enabled.
Can't ping beyond PoP endpoint from subnet host
Shadow Hawkins on Wednesday, 13 October 2004 16:57:32
You wrote:
This is my layout:
Internet <---> PoP <--tunnel--> [eth0]Linux Router[eth1] <--subnet--> WinXP
Redhat kernel 2.4.9-34 SP1
Could be kernel related. Try adding route
2000::/3 dev sixxs metric 1024 mtu 1280 advmss 1220
and/or try a recent kernel.
Greets
Thorsten
Can't ping beyond PoP endpoint from subnet host
Shadow Hawkins on Wednesday, 13 October 2004 18:15:47
YES! That was it! (added 2000::/3) Now it's working... *D
Thanks! :7-
I was planning to upgrade to version 8 or 9 in the near future anyway; still examening the pro's and con's.
Can't ping beyond PoP endpoint from subnet host
Shadow Hawkins on Friday, 19 November 2004 21:21:58
I had the same problem
the 2000::/3 route helped ;)
what is the reason for that route?
Posting is only allowed when you are logged in. |