|
Ticket ID: SIXXS #7399430 Ticket Status: User PoP: nlams05 - SURFnet (Amsterdam)
T4700 can't ping PoP ipv6
![[nl]](/s/countries/nl.gif) Shadow Hawkins on Wednesday, 11 July 2012 11:20:13
Hi SixXS,
Since a short power-failure on our router/modem this morning, I don't seem to be able to ping the PoP ipv6 anymore, it seems (and all other ipv6 traffic is busted too).
ipv4 works fine, and I can reach the PoP over ipv4 without problems.
tcpdump shows the outgoing icmpv6 request, but no response comes back. To be sure, I disabled the firewalls and all, but to no avail :S
Tunnel details
--------------
PoP Name nlams05
PoP IPv4 192.87.102.107
Your IPv4 87.212.49.194 (static)
IPv6 Prefix 2001:610:600:20::1/64
PoP IPv6 2001:610:600:20::1
Your IPv6 2001:610:600:20::2
OS Type
-------
debian 6.0.5 (with a few testing/unstable bits)
uname -a
--------
Linux eru 2.6.32-5-amd64 #1 SMP Sun May 6 04:00:17 UTC 2012 x86_64 GNU/Linux
ip -6 route
-----------
2001:610:600:20::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth2 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 via :: dev sixxs proto kernel metric 256 mtu 1280 advmss 1220 hoplimit 4294967295
default via 2001:610:600:20::1 dev sixxs metric 1024 mtu 1280 advmss 1220 hoplimit 4294967295
ifconfig sixxs
--------------
sixxs Link encap:IPv6-in-IPv4
inet6 addr: 2001:610:600:20::2/64 Scope:Global
inet6 addr: fe80::a63:6301/64 Scope:Link
inet6 addr: fe80::c0a8:6306/64 Scope:Link
UP POINTOPOINT 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)
tcpdump (dev eth2) of ping pop ipv4 (192.87.102.107)
------------------------------------
tcpdump -n -i eth2 proto 1
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth2, link-type EN10MB (Ethernet), capture size 65535 bytes
11:15:31.893191 IP 192.168.99.6 > 192.87.102.107: ICMP echo request, id 7673, seq 1, length 64
11:15:31.920289 IP 192.87.102.107 > 192.168.99.6: ICMP echo reply, id 7673, seq 1, length 64
11:15:32.894652 IP 192.168.99.6 > 192.87.102.107: ICMP echo request, id 7673, seq 2, length 64
11:15:32.921638 IP 192.87.102.107 > 192.168.99.6: ICMP echo reply, id 7673, seq 2, length 64
11:15:33.895861 IP 192.168.99.6 > 192.87.102.107: ICMP echo request, id 7673, seq 3, length 64
11:15:33.922670 IP 192.87.102.107 > 192.168.99.6: ICMP echo reply, id 7673, seq 3, length 64
tcpdump (dev sixxs) of ping pop ipv6 (2001:610:600:20::1)
---------------------------------------------------------
tcpdump -n -i sixxs proto 41 or proto 58
tcpdump: WARNING: sixxs: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on sixxs, link-type RAW (Raw IP), capture size 65535 bytes
11:00:47.098776 IP6 2001:610:600:20::2 > 2001:610:600:20::1: ICMP6, echo request, seq 1, length 64
11:00:48.106219 IP6 2001:610:600:20::2 > 2001:610:600:20::1: ICMP6, echo request, seq 2, length 64
11:00:49.114469 IP6 2001:610:600:20::2 > 2001:610:600:20::1: ICMP6, echo request, seq 3, length 64
11:00:50.122429 IP6 2001:610:600:20::2 > 2001:610:600:20::1: ICMP6, echo request, seq 4, length 64
tcpdump (dev eht2) of ping pop ipv6 (2001:610:600:20::1)
--------------------------------------------------------
tcpdump -n -i eth2 proto 41 or proto 58
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth2, link-type EN10MB (Ethernet), capture size 65535 bytes
11:00:47.098812 IP 192.168.99.6 > 192.87.102.107: IP6 2001:610:600:20::2 > 2001:610:600:20::1: ICMP6, echo request, seq 1, length 64
11:00:48.106241 IP 192.168.99.6 > 192.87.102.107: IP6 2001:610:600:20::2 > 2001:610:600:20::1: ICMP6, echo request, seq 2, length 64
11:00:49.114519 IP 192.168.99.6 > 192.87.102.107: IP6 2001:610:600:20::2 > 2001:610:600:20::1: ICMP6, echo request, seq 3, length 64
11:00:50.122453 IP 192.168.99.6 > 192.87.102.107: IP6 2001:610:600:20::2 > 2001:610:600:20::1: ICMP6, echo request, seq 4, length 64
My local IP is 192.168.99.6, which gets NAT'ed by the adsl router/modem (as is has for years :) ).
Can you look into this, please ?
Thanks,
Taco IJsselmuiden.
State change: user
The state of this ticket has been changed to user
T4700 can't ping PoP ipv6
ifconfig sixxs ... inet6 addr: fe80::a63:6301/64 Scope:Link inet6 addr: fe80::c0a8:6306/64 Scope:Link
Looks like you have a 10.x.x.x/8 and a 192.168.0.0/16 on there, thus no public address
... RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
No packets on the interface?
11:15:31.893191 IP 192.168.99.6 > 192.87.102.107: ICMP echo request, id 7673, seq 1, length 64
And there it is a nice 192.168.x.x/16 address, you are really behind a NAT.
My local IP is 192.168.99.6, which gets NAT'ed by the adsl router/modem (as is has for years :) ).
Check your modem if it is still properly doing DMZ for proto-41.
Not much we can do to help you out with that.
Also check that your external IPv4 address is still 87.212.49.194.
T4700 can't ping PoP ipv6
Shadow Hawkins on Wednesday, 11 July 2012 12:47:16
Hello SixXS,
Thanks for looking into this already this quickly :)
ifconfig sixxs ... inet6 addr: fe80::a63:6301/64 Scope:Link inet6 addr: fe80::c0a8:6306/64 Scope:Link Looks like you have a 10.x.x.x/8 and a 192.168.0.0/16 on there, thus no public address
Correct. I'm (still) behind a NATing modem, as I have been for years :S
... RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) No packets on the interface?
Since I've been restarting networking stuff and interfaces while troubleshooting and writing the ticket, I probably took that ifconfig right after a restart :)
Currently, it reads:
ifconfig sixxs
sixxs Link encap:IPv6-in-IPv4
inet6 addr: 2001:610:600:20::2/64 Scope:Global
inet6 addr: fe80::a63:6301/64 Scope:Link
inet6 addr: fe80::c0a8:6306/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:49 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:4603 (4.4 KiB)
11:15:31.893191 IP 192.168.99.6 > 192.87.102.107: ICMP echo request, id 7673, seq 1, length 64 And there it is a nice 192.168.x.x/16 address, you are really behind a NAT.
Yup, still am and probably will be for years (until my ISP rolls out ipv6 :S ).
My local IP is 192.168.99.6, which gets NAT'ed by the adsl router/modem (as is has for years :) ). Check your modem if it is still properly doing DMZ for proto-41. Not much we can do to help you out with that.
Ah, good point about the DMZ for proto-41. So, I went and set up a simple ipv6 tunnel to a different box to test just that. The configuration is pretty much identical (bar the used ipv6 addresses, of course) as what I use for sixxs. A simple ping seems to work (and I can even log into the remote box with the fd00::1 address).
Note: this tunnel uses fd00::1 as endpoint on the remote side, and fd00::2 on my side.
this tunnel interface (ipv6 Test Tunnel)
----------------------------------------
ifconfig ipv6TT
ipv6TT Link encap:IPv6-in-IPv4
inet6 addr: fd00::2/64 Scope:Global
inet6 addr: fe80::a63:6301/64 Scope:Link
inet6 addr: fe80::c0a8:6306/64 Scope:Link
UP POINTOPOINT RUNNING NOARP MTU:1280 Metric:1
RX packets:39 errors:0 dropped:0 overruns:0 frame:0
TX packets:230 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:7049 (6.8 KiB) TX bytes:26545 (25.9 KiB)
tcpdump (dev ipv6TT) of ping tunnel-endpoint (fd00::1)
------------------------------------------------------
tcpdump -n -i ipv6TT proto 41 or proto 58
tcpdump: WARNING: ipv6TT: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on ipv6TT, link-type RAW (Raw IP), capture size 65535 bytes
12:30:08.758140 IP6 fd00::2 > fd00::1: ICMP6, echo request, seq 1, length 64
12:30:08.785282 IP6 fd00::1 > fd00::2: ICMP6, echo reply, seq 1, length 64
12:30:09.758959 IP6 fd00::2 > fd00::1: ICMP6, echo request, seq 2, length 64
12:30:09.786646 IP6 fd00::1 > fd00::2: ICMP6, echo reply, seq 2, length 64
12:30:10.760907 IP6 fd00::2 > fd00::1: ICMP6, echo request, seq 3, length 64
12:30:10.788373 IP6 fd00::1 > fd00::2: ICMP6, echo reply, seq 3, length 64
tcpdump (dev eth2) of ping tunnel-endpoint (fd00::1, REMOTE_IP is the IP of the remote endpoint)
------------------------------------------------------
tcpdump -n -i eth2 proto 41 or proto 58
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth2, link-type EN10MB (Ethernet), capture size 65535 bytes
12:30:08.758193 IP 192.168.99.6 > REMOTE_IP: IP6 fd00::2 > fd00::1: ICMP6, echo request, seq 1, length 64
12:30:08.785282 IP REMOTE_IP > 192.168.99.6: IP6 fd00::1 > fd00::2: ICMP6, echo reply, seq 1, length 64
12:30:09.759009 IP 192.168.99.6 > REMOTE_IP: IP6 fd00::2 > fd00::1: ICMP6, echo request, seq 2, length 64
12:30:09.786646 IP REMOTE_IP > 192.168.99.6: IP6 fd00::1 > fd00::2: ICMP6, echo reply, seq 2, length 64
12:30:10.760958 IP 192.168.99.6 > REMOTE_IP: IP6 fd00::2 > fd00::1: ICMP6, echo request, seq 3, length 64
12:30:10.788373 IP REMOTE_IP > 192.168.99.6: IP6 fd00::1 > fd00::2: ICMP6, echo reply, seq 3, length 64
So at least the NATing modem doesn't block proto 41 (or 58) and properly directs them to my box.
Also check that your external IPv4 address is still 87.212.49.194. Yup, confirmed that it's still the same (thankfully, or I wouldn't be able to reach the box remotely :) ).
If you have any other suggestions as to what might be wrong, don't hesitate to share them :)
Cheers,
Taco IJsselmuiden.
T4700 can't ping PoP ipv6
Shadow Hawkins on Wednesday, 11 July 2012 13:33:14
And then, suddenly, a few minutes ago, connectivity was restored :)
If that was your doing: lots of thanks !
If not: I'm baffled as to what was wrong ;)
Cheers,
Taco.
T4700 can't ping PoP ipv6
No changes on our side have been made to the best of my knowledge.
|
![[ch]](/s/countries/ch.gif)
on Wednesday, 11 July 2012 11:29:47
Posting is only allowed when you are