SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #489312
Ticket Status: Resolved

PoP: plpoz01 - Poznan Supercomputing and Networking Center (Poznan)

AYIYA problem with the plpoz01 PoP
[pl] Carmen Sandiego on Saturday, 03 March 2007 14:56:35
The problem is exclusive to my AYIYA tunnel T10997. I use AICCU 2007.01.15-console-linux by Jeroen Massar on a Linux hostname 2.6.19-1.2895.fc6 #1 SMP Wed Jan 10 18:50:56 EST 2007 x86_64 x86_64 x86_64 GNU/Linux. The following occurs: AICCU starts up properly, the aiccu test succeeds up to step 6, step 6 fails. When I ping6 my IPv6 2001:808:e100::2 from an external IP and I tcpdump this on the 2001:808:e100::2 machine on the eth interface, I get:
14:24:40.619503 IP 150.254.166.147.ayiya > 192.168.0.5.33076: UDP, length 148 14:24:40.619543 IP 192.168.0.5 > 150.254.166.147: ICMP 192.168.0.5 udp port 33076 unreachable, length 184
however, if I do a netstat I see:
udp 0 0 192.168.0.5:33076 212.126.28.49:5072 ESTABLISHED 18917/aiccu
It seems that a connection is already established between the aiccu running on my machine and 212.126.28.49. However, the packets corresponding to my ping6ing come from 150.254.166.147, as the tcpdump shows. Because of this established connection to 212.126.28.49, all packets from 150.254.166.147 are refused. I did a little debugging, and the aiccu listening thread indeed just hangs there on the recvfrom() in common/ayiya.c, receiving nothing from srv1.almainternet.pl. But there is a little bit of confusion about 212.126.28.49:
host 212.126.28.49 49.28.126.212.in-addr.arpa domain name pointer srv1.almainternet.pl. host srv1.almainternet.pl srv1.almainternet.pl has address 83.149.119.153 host 83.149.119.153 153.119.149.83.in-addr.arpa domain name pointer s6-a.trafficdivision.net. host s6-a.trafficdivision.net Host s6-a.trafficdivision.net not found: 3(NXDOMAIN)
Here is the traffic for 212.126.28.49 after restarting aiccu:
tcpdump -nn -i any host 212.126.28.49 14:50:13.258042 IP 192.168.0.5.32771 > 212.126.28.49.5072: UDP, length 44 14:50:13.259837 IP 192.168.0.5.32771 > 212.126.28.49.5072: UDP, length 44 14:50:13.260278 IP 192.168.0.5.32771 > 212.126.28.49.5072: UDP, length 44 14:50:13.260546 IP 192.168.0.5.32771 > 212.126.28.49.5072: UDP, length 92 14:50:17.247860 IP 192.168.0.5.32771 > 212.126.28.49.5072: UDP, length 92 14:50:21.248203 IP 192.168.0.5.32771 > 212.126.28.49.5072: UDP, length 92
NOTE: this tcpdump is from another session, that is why packets originate from 192.168.0.5.32771 and not from 192.168.0.5.33076 as above. The corresponding netstat is:
udp 0 0 192.168.0.5:32771 212.126.28.49:5072 ESTABLISHED 3977/aiccu
Nothing is received from 212.126.28.49. Please help, my AYIYA tunnel does not work because it refuses all the packets from 150.254.166.147! (I had both iptables and ip6tables down, of course, when doing this analysis.)
AYIYA problem with the plpoz01 PoP
[it] Carmen Sandiego on Sunday, 04 March 2007 01:29:05
from my localbox i use gentoo and run ndp-client only, without ntpd started, because this does not have aiccu connected to gateway to my PoP. try and let us know! :) (sorry to my translation) :P
AYIYA problem with the plpoz01 PoP
[pl] Carmen Sandiego on Monday, 05 March 2007 10:11:09
I am sorry I do not understand how your reply relates to my problem... ?
AYIYA problem with the plpoz01 PoP
[ch] Jeroen Massar SixXS Staff on Sunday, 04 March 2007 03:08:34
You can only use plpoz01 from address space managed by POZNAN (AS9112).
State change: resolved Locked
[ch] Jeroen Massar SixXS Staff on Sunday, 04 March 2007 03:08:39
Message is Locked
The state of this ticket has been changed to resolved

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

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