SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #590960
Ticket Status: Invalid

PoP: ittrn01 - ITgate (Torino)

Strange routing(?) problem
[it] Shadow Hawkins on Friday, 12 October 2007 23:34:45
Since last week I'm using ittrn01 tunnel from home fine(using libero infostrada ISP 151.23.191.184 was my last IP from there) using heartbeat. When I move to another ISP connection (Telecom Italia IP: 82.53.138.216 now) I can get tunnel up, status in my personal page on sixxs.net updates correctly displaying my new IP but IPv6 networking doens't work anymore. I can ping the PoP IPv4 213.254.12.34 but I can't ping 2001:1418:100:20d::1 (the PoP IPv6). Any traceroute doesn't succeed. Using another broker's tunnel (from go6.net Freenet6; 2001:5c0:8fff:fffe::7261 is my IP with them) IPv6 works correctly.
Strange routing(?) problem
[ch] Jeroen Massar SixXS Staff on Friday, 12 October 2007 23:55:33
* I have read and followed the "Reporting Problems" section on the Contact * page and * am providing the following details for this report based on the * list of items stated there: Please actually do so. That big orange box actually is there for a reason, the same that the above text is prefilled in the box. As you are not providing any details at all except "this work that doesn't" we really can't help.
State change: invalid Locked
[ch] Jeroen Massar SixXS Staff on Friday, 12 October 2007 23:55:38
Message is Locked
The state of this ticket has been changed to invalid
Strange routing(?) problem
[it] Shadow Hawkins on Saturday, 13 October 2007 00:46:03
I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: "Always include clear descriptive information about your problem or inquiry." I think I've already done it "When on a UNIX-alike platform that supports AICCU, please run AICCU and run it using "aiccu test"." I noticed that the aiccu test does exactly what I've done. It stops working when pinging PoP IPv6. here's the traceroute: traceroute to 213.254.12.34 (213.254.12.34), 30 hops max, 40 byte packets 1 192.168.0.1 (192.168.0.1) 0.676 ms 0.937 ms 1.437 ms 2 192.168.100.1 (192.168.100.1) 45.602 ms 47.910 ms 50.351 ms 3 217.141.255.201 (217.141.255.201) 53.111 ms 55.732 ms 58.656 ms 4 crs-rm004-r-pi30.opb.interbusiness.it (151.99.101.13) 67.100 ms 69.253 ms 71.882 ms 5 csr-rm003-csr-rm004.opb.interbusiness.it (151.99.99.121) 75.148 ms 77.787 ms 79.485 ms 6 crs-mi003-crs-rm003.opb.interbusiness.it (151.99.98.10) 91.210 ms 58.936 ms 57.568 ms 7 r-to71-crs-mi003.opb.interbusiness.it (151.99.101.106) 62.992 ms 65.600 ms 67.977 ms 8 r-to89-r-to71.opb.interbusiness.it (151.99.98.26) 70.751 ms 72.887 ms 75.577 ms 9 itgate-pub.topix.it (194.116.96.4) 78.813 ms 81.234 ms 84.117 ms 10 if-0-0.foxtrot.CBQ.trn.itgate.net (213.254.0.19) 88.167 ms 90.757 ms 93.168 ms 11 frejus.ITgate.net (213.254.12.34) 95.905 ms 98.540 ms 100.964 ms "When using AICCU, check that you are using the latest version, and of course please specify where the binary comes from." I'm using the latest binary from debian sid repository: ii aiccu 20070115-6 SixXS Automatic IPv6 Connectivity Client Utility "Always provide your NIC handle and if applicable the Tunnel or Route IDs you wish to discuss." Done. GPQ1-SIXXS "Use the email address you have provided in your handle as that is what we use as a contact handle." I was logged in, you have all my contacts. "Provide details of the setup, type of connections, where NATs are located." I'm always behind an ADSL router. In my home I'm in a DMZ, when I connect via the other ISP connection my computer is simply a LAN client with a firewall blocking incoming SYNs from 0-1023 ports. In this case, enabling "Provide information of your OS type, version and release (ie. uname -a), noting also the distribution name." uname -a Linux mymachine 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 GNU/Linux "Include full interface, routing and firewall tables" ifconfig eth1 Link encap:Ethernet HWaddr 00:16:D4:06:31:A6 inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::216:d4ff:fe06:31a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21893 errors:0 dropped:0 overruns:0 frame:0 TX packets:29924 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4488012 (4.2 MiB) TX bytes:2529738 (2.4 MiB) 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:1011 errors:0 dropped:0 overruns:0 frame:0 TX packets:1011 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:32107 (31.3 KiB) TX bytes:32107 (31.3 KiB) sixxs Link encap:IPv6-in-IPv4 inet6 addr: 2001:1418:100:20d::2/64 Scope:Global inet6 addr: fe80::c0a8:3/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) route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 * 255.255.255.0 U 0 0 0 eth1 default 192.168.0.1 0.0.0.0 UG 0 0 0 eth1 locally iptables has no rules. "Include a IPv4 and IPv6 traceroute to the PoP in question." Done above for the IPv4. IPv6 traceroute6 doesn't work: traceroute6 2001:1418:100:20d::1 traceroute to 2001:1418:100:20d::1 (2001:1418:100:20d::1) from 2001:1418:100:20d::2, 30 hops max, 16 byte packets 1 * * * "With heartbeat tunnels, first check clock synchronization or better: use AICCU." Clock in sync with ntpdate. "Check with Wireshark or tcpdumps of the interface over which the tunnel runs. Use -n (numeric) as an option and don't filter returning ICMP which could also come from routers between your endpoint and the PoP and also use -s 1500 so that one gets the full packet." No packets incoming. All showed packets are outgoing. thanks
Strange routing(?) problem
[ch] Jeroen Massar SixXS Staff on Saturday, 13 October 2007 00:52:35
1 192.168.0.1 (192.168.0.1) 0.676 ms 0.937 ms 1.437 ms
2 192.168.100.1 (192.168.100.1) 45.602 ms 47.910 ms 50.351 ms
You are behind NAT. proto-41 and NAT don't function very well together unless you explicitly configure the NAT host to forward your traffic. Change your tunnel to AYIYA to resolve this. "In this case, enabling ..." what?
sixxs Link encap:IPv6-in-IPv4
inet6 addr: 2001:1418:100:20d::2/64 Scope:Global
inet6 addr: fe80::c0a8:3/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)
Not a single packet was even attemped of being sent there, thus if you would actually do the wireshark/tcpdump and show the output this would also show no outbound packets. Also a IPv6 routing table is actually handy as the list requests.
Routing (?) problem? retry
[it] Shadow Hawkins on Saturday, 13 October 2007 00:48:08
When I move to another ISP connection (Telecom Italia IP: 82.53.138.216 now) I can get tunnel up, status in my personal page on sixxs.net updates correctly displaying my new IP but IPv6 networking doens't work anymore. I can ping the PoP IPv4 213.254.12.34 but I can't ping 2001:1418:100:20d::1 (the PoP IPv6). Any traceroute doesn't succeed. Using another broker's tunnel (from go6.net Freenet6; 2001:5c0:8fff:fffe::7261 is my IP with them) IPv6 works correctly. I have read and followed the "Reporting Problems" section on the Contact page and am providing the following details for this report based on the list of items stated there: "Always include clear descriptive information about your problem or inquiry." I think I've already done it "When on a UNIX-alike platform that supports AICCU, please run AICCU and run it using "aiccu test"." I noticed that the aiccu test does exactly what I've done. It stops working when pinging PoP IPv6. here's the traceroute: traceroute to 213.254.12.34 (213.254.12.34), 30 hops max, 40 byte packets 1 192.168.0.1 (192.168.0.1) 0.676 ms 0.937 ms 1.437 ms 2 192.168.100.1 (192.168.100.1) 45.602 ms 47.910 ms 50.351 ms 3 217.141.255.201 (217.141.255.201) 53.111 ms 55.732 ms 58.656 ms 4 crs-rm004-r-pi30.opb.interbusiness.it (151.99.101.13) 67.100 ms 69.253 ms 71.882 ms 5 csr-rm003-csr-rm004.opb.interbusiness.it (151.99.99.121) 75.148 ms 77.787 ms 79.485 ms 6 crs-mi003-crs-rm003.opb.interbusiness.it (151.99.98.10) 91.210 ms 58.936 ms 57.568 ms 7 r-to71-crs-mi003.opb.interbusiness.it (151.99.101.106) 62.992 ms 65.600 ms 67.977 ms 8 r-to89-r-to71.opb.interbusiness.it (151.99.98.26) 70.751 ms 72.887 ms 75.577 ms 9 itgate-pub.topix.it (194.116.96.4) 78.813 ms 81.234 ms 84.117 ms 10 if-0-0.foxtrot.CBQ.trn.itgate.net (213.254.0.19) 88.167 ms 90.757 ms 93.168 ms 11 frejus.ITgate.net (213.254.12.34) 95.905 ms 98.540 ms 100.964 ms "When using AICCU, check that you are using the latest version, and of course please specify where the binary comes from." I'm using the latest binary from debian sid repository: ii aiccu 20070115-6 SixXS Automatic IPv6 Connectivity Client Utility "Always provide your NIC handle and if applicable the Tunnel or Route IDs you wish to discuss." Done. GPQ1-SIXXS "Use the email address you have provided in your handle as that is what we use as a contact handle." I was logged in, you have all my contacts. "Provide details of the setup, type of connections, where NATs are located." I'm always behind an ADSL router. In my home I'm in a DMZ, when I connect via the other ISP connection my computer is simply a LAN client with a firewall blocking incoming SYNs from 0-1023 ports. In this case, enabling "Provide information of your OS type, version and release (ie. uname -a), noting also the distribution name." uname -a Linux mymachine 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 GNU/Linux "Include full interface, routing and firewall tables" ifconfig eth1 Link encap:Ethernet HWaddr 00:16biggrin4:06:31:A6 inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::216:d4ff:fe06:31a6/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:21893 errors:0 dropped:0 overruns:0 frame:0 TX packets:29924 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4488012 (4.2 MiB) TX bytes:2529738 (2.4 MiB) 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:1011 errors:0 dropped:0 overruns:0 frame:0 TX packets:1011 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:32107 (31.3 KiB) TX bytes:32107 (31.3 KiB) sixxs Link encap:IPv6-in-IPv4 inet6 addr: 2001:1418:100:20d::2/64 Scope:Global inet6 addr: fe80::c0a8:3/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) route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 * 255.255.255.0 U 0 0 0 eth1 default 192.168.0.1 0.0.0.0 UG 0 0 0 eth1 locally iptables has no rules. "Include a IPv4 and IPv6 traceroute to the PoP in question." Done above for the IPv4. IPv6 traceroute6 doesn't work: traceroute6 2001:1418:100:20d::1 traceroute to 2001:1418:100:20d::1 (2001:1418:100:20d::1) from 2001:1418:100:20d::2, 30 hops max, 16 byte packets 1 * * * "With heartbeat tunnels, first check clock synchronization or better: use AICCU." Clock in sync with ntpdate. "Check with Wireshark or tcpdumps of the interface over which the tunnel runs. Use -n (numeric) as an option and don't filter returning ICMP which could also come from routers between your endpoint and the PoP and also use -s 1500 so that one gets the full packet." No packets incoming. All showed packets are outgoing. thanks
State change: duplicate Locked
[ch] Jeroen Massar SixXS Staff on Saturday, 13 October 2007 01:01:44
Message is Locked
The state of this ticket has been changed to duplicate

Please note Posting is only allowed when you are logged in.

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker