|
Ticket ID: SIXXS #7191534 Ticket Status: User PoP: brudi01 - (Uberlandia)
aiccu doesn't automatic reconnect
![[br]](/s/countries/br.gif) Shadow Hawkins on Saturday, 09 June 2012 03:02:04
After adsl reconnection the tunnel stop working,
I need restart aiccu manualy to tunnel work again.
I made a script to log current ipv4 address and ping6 to google every 10mins.
After ipv4 change the tunnel stop working.
It was a heartbeat tunnel, and I changed to ayiya, same problem.
iptables -t nat -A POSTROUTING ! --proto 41 -o if -j MASQUERADE
iptables -t raw -A PREROUTING --proto 41 -j NOTRACK
didnt help.
aiccu version: 20070115-14.1ubuntu3
State change: user
The state of this ticket has been changed to user
aiccu doesn't automatic reconnect
After adsl reconnection the tunnel stop working,
What exactly stops working? Do packets still go outbound, do packets not come back, is routing lost?
I made a script to log current ipv4 address and ping6 to google every 10mins.
But pinging google could just mean that google is unreachable. Every ten minutes also does not keep any NAT state alive either.
After ipv4 change the tunnel stop working.
But what stops working?
It was a heartbeat tunnel, and I changed to ayiya, same problem.
Both should survice a IPv4 change perfectly fine.
iptables -t nat -A POSTROUTING ! --proto 41 -o if -j MASQUERADE iptables -t raw -A PREROUTING --proto 41 -j NOTRACK
Are you running AICCU on the host that NATs itself? Is there another NAT involved?
As you changed your tunnel type to AYIYA the above lines do not have any effect as AYIYA is UDP based.
Please provide the details as requested on the contact page, otherwise the only thing we can do is guess.
aiccu doesn't automatic reconnect
Shadow Hawkins on Saturday, 09 June 2012 03:23:03What exactly stops working? Do packets still go outbound, do packets not come back, is routing lost? But what stops working?
tunnel stop working, I cannot access ipv6 network, no ping, no http access, nothing over ipv6.
But pinging google could just mean that google is unreachable. Every ten minutes also does not keep any NAT state alive either.
Its just to I know when it stopped working.
As you changed your tunnel type to AYIYA the above lines do not have any effect as AYIYA is UDP based.
I changed to AYIYA to i figureout if was something to do with proto 41.
Are you running AICCU on the host that NATs itself? Is there another NAT involved?
adsl modem -> linux gateway -> lan computers
modem is set to dmz to linux
aiccu doesn't automatic reconnect
Please provide the list of items requested on the contact page, without that we really cannot say anything more on this subject.
And if possible check if there are any differences before and after it 'breaks'.
A tcpdump before and after is likely also very useful.
aiccu doesn't automatic reconnect
Shadow Hawkins on Saturday, 09 June 2012 03:33:10
Tunnel Information for T64489:
POP Id : brudi01
IPv6 Local : 2001:1291:200:19e::2/64
IPv6 Remote : 2001:1291:200:19e::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
aiccu doesn't automatic reconnect
Please actually read and follow the "Reporting Problems" section on the Contact page.
aiccu doesn't automatic reconnect
Shadow Hawkins on Saturday, 09 June 2012 04:35:15
Ubuntu 12.04
Linux 3.2.0-24-generic-pae #39-Ubuntu SMP Mon May 21 18:54:21 UTC 2012 i686 i686 i386 GNU/Linux
aiccu = 20070115-14.1ubuntu3
traceroute -I 201.48.254.14
traceroute to 201.48.254.14 (201.48.254.14), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.882 ms 1.099 ms 1.213 ms
2 gvt-l0.b6.cta.gvt.net.br (177.16.184.1) 7.825 ms 7.762 ms 8.636 ms
3 gvt-te-7-1.rd02.cta.gvt.net.br (200.139.125.36) 11.222 ms 11.201 ms 11.194 ms
4 gvt-te-0-3-2-0-rc02.cta.gvt.net.br (187.115.212.30) 14.868 ms 14.794 ms 14.889 ms
5 189.59.242.126.static.host.gvt.net.br (189.59.242.126) 16.222 ms 16.312 ms 19.418 ms
6 gvt-ge-0-3-4-0.rc04.spo.gvt.net.br (189.59.246.158) 33.967 ms 19.679 ms 19.260 ms
7 187.115.214.190.static.host.gvt.net.br (187.115.214.190) 21.469 ms 19.821 ms 19.381 ms
8 as16735.sp.ptt.br (187.16.216.24) 14.384 ms 12.272 ms 12.508 ms
9 xe-0-2-0-0.core-b.spo511.ctbc.com.br (201.48.44.209) 13.898 ms 14.359 ms 14.012 ms
10 xe-0-0-0-0.core-b.ula001.ctbc.com.br (201.48.44.13) 32.030 ms 30.729 ms 31.280 ms
11 ge-1-0-0-0.edge-a.ula001.ctbc.com.br (201.48.44.70) 32.230 ms 32.538 ms 32.640 ms
12 brudi01.sixxs.net (201.48.254.14) 33.225 ms 32.912 ms 33.252 ms
traceroute -6 -I 2001:1291:200:19e::1
traceroute to 2001:1291:200:19e::1 (2001:1291:200:19e::1), 30 hops max, 80 byte packets
1 gw-415.udi-01.br.sixxs.net (2001:1291:200:19e::1) 32.745 ms 34.436 ms 35.775 ms
tcpdump -n -i eth1 host 201.48.254.14
23:10:51.784693 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:10:52.163864 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:10:52.365311 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:10:52.551168 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:10:52.613210 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:10:53.045182 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:10:54.832212 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:10:54.893986 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:10:55.566585 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:10:57.031661 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:10:57.136445 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:02.875151 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 44
23:11:05.955524 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:06.172882 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:12.100948 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:12.162082 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:12.162525 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:12.391225 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:12.434031 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:12.535789 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:12.975147 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:12.979536 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:13.287795 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:13.545503 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:14.066383 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:14.137265 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:14.644770 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:14.780136 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:15.955094 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:16.173371 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:16.243309 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:16.465119 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:16.859019 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:17.120044 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 116
23:11:17.171454 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 116
23:11:17.176359 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 116
23:11:17.772358 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:18.120887 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 116
23:11:18.120980 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 116
23:11:18.171978 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 116
23:11:18.173176 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 116
23:11:18.174398 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 116
23:11:18.176173 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 116
23:11:21.082391 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:21.191072 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:21.286637 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:21.632552 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:21.946230 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:22.734117 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:23.458507 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:24.943864 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:25.955291 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:26.173078 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:26.482475 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:30.144146 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:30.507811 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:31.257100 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:32.739720 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:35.716697 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:37.181074 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 1072
23:11:37.181572 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 1072
23:11:40.144329 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:11:50.144267 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 104
23:12:02.875350 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 44
23:12:37.305496 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 1072
23:12:37.305930 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 1072
23:12:54.746737 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 148
23:12:54.799129 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 148
23:12:55.747737 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 148
23:12:55.798994 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 148
23:12:56.749582 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 148
23:12:56.818697 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 148
23:12:57.750936 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 148
23:12:57.802562 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 148
23:13:02.875573 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 44
23:13:37.272711 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 1072
23:13:37.273086 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 1072
// stopped somewhere here
23:13:51.394199 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 144
23:13:54.195508 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 143
23:14:01.405971 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 144
23:14:02.595860 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 133
23:14:02.875766 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 44
23:14:05.398152 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 132
23:14:07.398289 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 133
23:14:07.399879 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 139
23:14:07.401536 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 139
23:14:07.403042 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 139
23:14:07.404559 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 139
23:14:07.406302 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 139
23:14:07.407732 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 139
23:14:07.409324 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 139
23:14:07.410682 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 139
23:14:07.412115 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 139
23:14:07.413845 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 139
23:14:07.415549 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 139
23:14:09.090140 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 147
23:14:10.199584 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 132
23:14:12.609373 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 133
23:14:17.411082 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 133
23:14:18.601930 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:18.603838 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:18.605369 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:18.607387 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:18.608908 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:18.610456 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:18.612151 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:18.613763 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:18.615349 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:18.616912 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:18.618527 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:20.292191 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 136
23:14:20.601469 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 186
23:14:20.603902 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:20.605348 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:20.607001 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:20.608514 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:20.610131 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:20.611490 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:20.613154 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:20.614647 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:20.616153 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:20.617513 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:20.619081 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:20.621282 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 109
23:14:21.403721 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:21.405729 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:21.407229 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:21.408801 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:21.410426 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
23:14:21.411879 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 128
tcpdump -n -i sixxs
23:10:51.083375 IP6 2607:f8b0:4004:800::100f.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62311: Flags [F.], seq 861, ack 2814, win 318, length 0
23:10:51.171107 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62301: Flags [F.], seq 38972, ack 2631, win 329, length 0
23:10:51.784908 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62301: Flags [F.], seq 38972, ack 2631, win 329, length 0
23:10:52.164093 IP6 2800:3f0:4001:801::1008.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62313: Flags [F.], seq 3393, ack 7681, win 479, length 0
23:10:52.365580 IP6 2607:f8b0:4004:800::100f.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62311: Flags [F.], seq 861, ack 2814, win 318, length 0
23:10:52.551664 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62513: Flags [F.], seq 780, ack 915, win 255, length 0
23:10:52.613437 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62512: Flags [F.], seq 780, ack 915, win 255, length 0
23:10:53.045619 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62301: Flags [F.], seq 38972, ack 2631, win 329, length 0
23:10:54.832453 IP6 2800:3f0:4001:801::1008.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62313: Flags [F.], seq 3393, ack 7681, win 479, length 0
23:10:54.894219 IP6 2607:f8b0:4004:800::100f.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62311: Flags [F.], seq 861, ack 2814, win 318, length 0
23:10:55.566839 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62301: Flags [F.], seq 38972, ack 2631, win 329, length 0
23:10:57.031902 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62513: Flags [F.], seq 780, ack 915, win 255, length 0
23:10:57.136656 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62512: Flags [F.], seq 780, ack 915, win 255, length 0
23:11:05.955640 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62513: Flags [F.], seq 780, ack 915, win 255, length 0
23:11:06.173095 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62512: Flags [F.], seq 780, ack 915, win 255, length 0
23:11:12.101181 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62537: Flags [F.], seq 306316, ack 4187, win 393, length 0
23:11:12.162295 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62565: Flags [F.], seq 5045, ack 420, win 242, length 0
23:11:12.162985 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62564: Flags [F.], seq 5069, ack 420, win 242, length 0
23:11:12.391684 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62537: Flags [F.], seq 306316, ack 4187, win 393, length 0
23:11:12.434459 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62565: Flags [F.], seq 5045, ack 420, win 242, length 0
23:11:12.536224 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62564: Flags [F.], seq 5069, ack 420, win 242, length 0
23:11:12.975389 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62537: Flags [F.], seq 306316, ack 4187, win 393, length 0
23:11:12.979751 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62565: Flags [F.], seq 5045, ack 420, win 242, length 0
23:11:13.288013 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62564: Flags [F.], seq 5069, ack 420, win 242, length 0
23:11:13.545734 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62562: Flags [F.], seq 491, ack 2119, win 288, length 0
23:11:14.066616 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62565: Flags [F.], seq 5045, ack 420, win 242, length 0
23:11:14.137483 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62537: Flags [F.], seq 306316, ack 4187, win 393, length 0
23:11:14.644995 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62562: Flags [F.], seq 491, ack 2119, win 288, length 0
23:11:14.780534 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62564: Flags [F.], seq 5069, ack 420, win 242, length 0
23:11:15.955329 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62513: Flags [F.], seq 780, ack 915, win 255, length 0
23:11:16.173857 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62512: Flags [F.], seq 780, ack 915, win 255, length 0
23:11:16.243534 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62565: Flags [F.], seq 5045, ack 420, win 242, length 0
23:11:16.465360 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62537: Flags [F.], seq 306316, ack 4187, win 393, length 0
23:11:16.859249 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62562: Flags [F.], seq 491, ack 2119, win 288, length 0
23:11:17.119251 IP6 2001:1291:2af:666:4176:9500:1efe:ed97.35841 > 2800:3f0:4001:804::1017.80: Flags [F.], seq 1777, ack 1206, win 264, options [nop,nop,TS val 13059121 ecr 583628012], length 0
23:11:17.171689 IP6 2800:3f0:4001:804::1017.80 > 2001:1291:2af:666:4176:9500:1efe:ed97.35841: Flags [F.], seq 1206, ack 1778, win 280, options [nop,nop,TS val 583743468 ecr 13059121], length 0
23:11:17.176003 IP6 2001:1291:2af:666:4176:9500:1efe:ed97.35841 > 2800:3f0:4001:804::1017.80: Flags [.], ack 1207, win 264, options [nop,nop,TS val 13059135 ecr 583743468], length 0
23:11:17.772603 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62564: Flags [F.], seq 5069, ack 420, win 242, length 0
23:11:18.119519 IP6 2001:1291:2af:666:4176:9500:1efe:ed97.38274 > 2800:3f0:4001:802::1018.80: Flags [F.], seq 2446, ack 725, win 276, options [nop,nop,TS val 13059371 ecr 73064413], length 0
23:11:18.120111 IP6 2001:1291:2af:666:4176:9500:1efe:ed97.57722 > 2800:3f0:4001:800::101f.80: Flags [F.], seq 10103, ack 242756, win 1256, options [nop,nop,TS val 13059371 ecr 77026476], length 0
23:11:18.172203 IP6 2800:3f0:4001:802::1018.80 > 2001:1291:2af:666:4176:9500:1efe:ed97.38274: Flags [F.], seq 725, ack 2447, win 302, options [nop,nop,TS val 73180435 ecr 13059371], length 0
23:11:18.173404 IP6 2800:3f0:4001:800::101f.80 > 2001:1291:2af:666:4176:9500:1efe:ed97.57722: Flags [F.], seq 242756, ack 10104, win 559, options [nop,nop,TS val 77142293 ecr 13059371], length 0
23:11:18.173585 IP6 2001:1291:2af:666:4176:9500:1efe:ed97.38274 > 2800:3f0:4001:802::1018.80: Flags [.], ack 726, win 276, options [nop,nop,TS val 13059384 ecr 73180435], length 0
23:11:18.175550 IP6 2001:1291:2af:666:4176:9500:1efe:ed97.57722 > 2800:3f0:4001:800::101f.80: Flags [.], ack 242757, win 1256, options [nop,nop,TS val 13059385 ecr 77142293], length 0
23:11:21.082658 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62558: Flags [F.], seq 1832, ack 4425, win 364, length 0
23:11:21.191313 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62563: Flags [F.], seq 825, ack 3951, win 378, length 0
23:11:21.286872 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62562: Flags [F.], seq 491, ack 2119, win 288, length 0
23:11:21.632800 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62558: Flags [F.], seq 1832, ack 4425, win 364, length 0
23:11:21.946468 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62563: Flags [F.], seq 825, ack 3951, win 378, length 0
23:11:22.734345 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62558: Flags [F.], seq 1832, ack 4425, win 364, length 0
23:11:23.458747 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62563: Flags [F.], seq 825, ack 3951, win 378, length 0
23:11:24.944096 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62558: Flags [F.], seq 1832, ack 4425, win 364, length 0
23:11:25.955407 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62513: Flags [F.], seq 780, ack 915, win 255, length 0
23:11:26.173294 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62512: Flags [F.], seq 780, ack 915, win 255, length 0
23:11:26.482747 IP6 2800:3f0:4001:801::1002.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62563: Flags [F.], seq 825, ack 3951, win 378, length 0
23:11:30.144289 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62562: Flags [F.], seq 491, ack 2119, win 288, length 0
23:11:30.508049 IP6 2800:3f0:4001:802::1001.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62574: Flags [F.], seq 929, ack 1075, win 259, length 0
23:11:31.257334 IP6 2800:3f0:4001:802::1001.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62574: Flags [F.], seq 929, ack 1075, win 259, length 0
23:11:32.739971 IP6 2800:3f0:4001:802::1001.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62574: Flags [F.], seq 929, ack 1075, win 259, length 0
23:11:35.716950 IP6 2800:3f0:4001:802::1001.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62574: Flags [F.], seq 929, ack 1075, win 259, length 0
23:11:37.181307 IP6 2001:1291:200:19e::1 > 2001:1291:200:19e::2: ICMP6, echo request, seq 16059, length 988
23:11:37.181456 IP6 2001:1291:200:19e::2 > 2001:1291:200:19e::1: ICMP6, echo reply, seq 16059, length 988
23:11:40.144568 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62562: Flags [F.], seq 491, ack 2119, win 288, length 0
23:11:50.144502 IP6 2001:4860:800a::88.80 > 2001:1291:2af:666:50d5:4c83:f580:976d.62562: Flags [F.], seq 491, ack 2119, win 288, length 0
23:12:37.305636 IP6 2001:1291:200:19e::1 > 2001:1291:200:19e::2: ICMP6, echo request, seq 16060, length 988
23:12:37.305800 IP6 2001:1291:200:19e::2 > 2001:1291:200:19e::1: ICMP6, echo reply, seq 16060, length 988
23:12:54.746459 IP6 2001:1291:200:19e::2 > 2800:3f0:4001:800::1012: ICMP6, echo request, seq 1, length 64
23:12:54.799360 IP6 2800:3f0:4001:800::1012 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 1, length 64
23:12:55.747486 IP6 2001:1291:200:19e::2 > 2800:3f0:4001:800::1012: ICMP6, echo request, seq 2, length 64
23:12:55.799216 IP6 2800:3f0:4001:800::1012 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 2, length 64
23:12:56.749228 IP6 2001:1291:200:19e::2 > 2800:3f0:4001:800::1012: ICMP6, echo request, seq 3, length 64
23:12:56.818923 IP6 2800:3f0:4001:800::1012 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 3, length 64
23:12:57.750619 IP6 2001:1291:200:19e::2 > 2800:3f0:4001:800::1012: ICMP6, echo request, seq 4, length 64
23:12:57.802801 IP6 2800:3f0:4001:800::1012 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 4, length 64
23:13:37.272850 IP6 2001:1291:200:19e::1 > 2001:1291:200:19e::2: ICMP6, echo request, seq 16061, length 988
23:13:37.272979 IP6 2001:1291:200:19e::2 > 2001:1291:200:19e::1: ICMP6, echo reply, seq 16061, length 988
// stopped somewhere here
23:13:51.393908 IP6 2001:1291:200:19e::2.32020 > 2001:503:a83e::2:30.53: 10897 [1au] AAAA? googlemail.l.google.com. (52)
23:13:54.195217 IP6 2001:1291:200:19e::2.55104 > 2001:503:a83e::2:30.53: 49026 [1au] A? dart.l.doubleclick.net. (51)
23:14:01.405635 IP6 2001:1291:200:19e::2.16910 > 2001:503:231d::2:30.53: 25711 [1au] A? googlemail.l.google.com. (52)
23:14:02.595528 IP6 2001:1291:200:19e::2.40758 > 2001:503:231d::2:30.53: 41628 AAAA? googlemail.l.google.com. (41)
23:14:05.397857 IP6 2001:1291:200:19e::2.12800 > 2001:503:231d::2:30.53: 31116 A? dart.l.doubleclick.net. (40)
23:14:07.398005 IP6 2001:1291:200:19e::2.28531 > 2001:503:a83e::2:30.53: 50407 AAAA? googlemail.l.google.com. (41)
23:14:07.399505 IP6 2001:1291:200:19e::2.64228 > 2001:503:a83e::2:30.53: 47425% [1au] AAAA? f.gtld-servers.net. (47)
23:14:07.401142 IP6 2001:1291:200:19e::2.35976 > 2001:503:a83e::2:30.53: 7978% [1au] AAAA? c.gtld-servers.net. (47)
23:14:07.402752 IP6 2001:1291:200:19e::2.33040 > 2001:503:a83e::2:30.53: 6419% [1au] AAAA? d.gtld-servers.net. (47)
23:14:07.404268 IP6 2001:1291:200:19e::2.51239 > 2001:503:a83e::2:30.53: 54362% [1au] AAAA? e.gtld-servers.net. (47)
23:14:07.405909 IP6 2001:1291:200:19e::2.38664 > 2001:503:a83e::2:30.53: 1486% [1au] AAAA? g.gtld-servers.net. (47)
23:14:07.407421 IP6 2001:1291:200:19e::2.2496 > 2001:503:a83e::2:30.53: 32892% [1au] AAAA? h.gtld-servers.net. (47)
23:14:07.408971 IP6 2001:1291:200:19e::2.18183 > 2001:503:a83e::2:30.53: 30883% [1au] AAAA? i.gtld-servers.net. (47)
23:14:07.410434 IP6 2001:1291:200:19e::2.40104 > 2001:503:a83e::2:30.53: 40822% [1au] AAAA? j.gtld-servers.net. (47)
23:14:07.411843 IP6 2001:1291:200:19e::2.14367 > 2001:503:a83e::2:30.53: 60821% [1au] AAAA? k.gtld-servers.net. (47)
23:14:07.413438 IP6 2001:1291:200:19e::2.41727 > 2001:503:a83e::2:30.53: 61517% [1au] AAAA? l.gtld-servers.net. (47)
23:14:07.415196 IP6 2001:1291:200:19e::2.54882 > 2001:503:a83e::2:30.53: 56969% [1au] AAAA? m.gtld-servers.net. (47)
23:14:09.089808 IP6 2001:1291:200:19e::2.50509 > 2001:503:a83e::2:30.53: 54732 [1au] A? tc.v9.cache6.c.youtube.com. (55)
23:14:10.199293 IP6 2001:1291:200:19e::2.23509 > 2001:503:a83e::2:30.53: 6900 A? dart.l.doubleclick.net. (40)
23:14:12.609066 IP6 2001:1291:200:19e::2.9372 > 2001:503:a83e::2:30.53: 59502 A? googlemail.l.google.com. (41)
23:14:17.410775 IP6 2001:1291:200:19e::2.55830 > 2001:503:231d::2:30.53: 31685 A? googlemail.l.google.com. (41)
23:14:18.601590 IP6 2001:1291:200:19e::2.59200 > 2001:503:231d::2:30.53: 49767 AAAA? f.gtld-servers.net. (36)
23:14:18.603405 IP6 2001:1291:200:19e::2.27020 > 2001:503:231d::2:30.53: 40306 AAAA? c.gtld-servers.net. (36)
23:14:18.604986 IP6 2001:1291:200:19e::2.38825 > 2001:503:231d::2:30.53: 16285 AAAA? d.gtld-servers.net. (36)
23:14:18.606980 IP6 2001:1291:200:19e::2.4851 > 2001:503:231d::2:30.53: 55720 AAAA? e.gtld-servers.net. (36)
23:14:18.608533 IP6 2001:1291:200:19e::2.42911 > 2001:503:231d::2:30.53: 22260 AAAA? g.gtld-servers.net. (36)
23:14:18.610175 IP6 2001:1291:200:19e::2.33602 > 2001:503:231d::2:30.53: 27520 AAAA? h.gtld-servers.net. (36)
23:14:18.611750 IP6 2001:1291:200:19e::2.9934 > 2001:503:231d::2:30.53: 39541 AAAA? i.gtld-servers.net. (36)
23:14:18.613346 IP6 2001:1291:200:19e::2.5309 > 2001:503:231d::2:30.53: 55832 AAAA? j.gtld-servers.net. (36)
23:14:18.614977 IP6 2001:1291:200:19e::2.16070 > 2001:503:231d::2:30.53: 64349 AAAA? k.gtld-servers.net. (36)
23:14:18.616529 IP6 2001:1291:200:19e::2.28995 > 2001:503:231d::2:30.53: 44647 AAAA? l.gtld-servers.net. (36)
23:14:18.618159 IP6 2001:1291:200:19e::2.56533 > 2001:503:231d::2:30.53: 17685 AAAA? m.gtld-servers.net. (36)
23:14:20.291900 IP6 2001:1291:200:19e::2.8112 > 2001:503:231d::2:30.53: 22880 A? tc.v9.cache6.c.youtube.com. (44)
23:14:20.601176 IP6 2001:1291:200:19e::2.55115 > 2001:503:231d::2:30.53: 35852 [1au] A? api-proxy-api-global-latam-1723997207.us-east-1.elb.amazonaws.com. (94)
23:14:20.603607 IP6 2001:1291:200:19e::2.30472 > 2001:500:2d::d.53: 4694 AAAA? c.gtld-servers.net. (36)
23:14:20.605058 IP6 2001:1291:200:19e::2.58180 > 2001:500:2d::d.53: 19437 AAAA? d.gtld-servers.net. (36)
23:14:20.606643 IP6 2001:1291:200:19e::2.29019 > 2001:500:2d::d.53: 61506 AAAA? e.gtld-servers.net. (36)
23:14:20.608159 IP6 2001:1291:200:19e::2.54245 > 2001:500:2d::d.53: 24838 AAAA? f.gtld-servers.net. (36)
23:14:20.609775 IP6 2001:1291:200:19e::2.42016 > 2001:500:2d::d.53: 15753 AAAA? g.gtld-servers.net. (36)
23:14:20.611210 IP6 2001:1291:200:19e::2.30436 > 2001:500:2d::d.53: 61911 AAAA? h.gtld-servers.net. (36)
23:14:20.612774 IP6 2001:1291:200:19e::2.38744 > 2001:500:2d::d.53: 24802 AAAA? i.gtld-servers.net. (36)
23:14:20.614288 IP6 2001:1291:200:19e::2.46519 > 2001:500:2d::d.53: 23031 AAAA? j.gtld-servers.net. (36)
23:14:20.615800 IP6 2001:1291:200:19e::2.18533 > 2001:500:2d::d.53: 28646 AAAA? k.gtld-servers.net. (36)
23:14:20.617235 IP6 2001:1291:200:19e::2.7539 > 2001:500:2d::d.53: 39660 AAAA? l.gtld-servers.net. (36)
23:14:20.618731 IP6 2001:1291:200:19e::2.37595 > 2001:500:2d::d.53: 21517 AAAA? m.gtld-servers.net. (36)
23:14:20.620993 IP6 2001:1291:200:19e::2.59122 > 2001:500:2d::d.53: 38322 NS? . (17)
23:14:21.403432 IP6 2001:1291:200:19e::2.40813 > 2001:500:2f::f.53: 61487 AAAA? c.gtld-servers.net. (36)
23:14:21.405224 IP6 2001:1291:200:19e::2.2338 > 2001:500:2f::f.53: 62872 AAAA? d.gtld-servers.net. (36)
23:14:21.406874 IP6 2001:1291:200:19e::2.8941 > 2001:500:2f::f.53: 5809 AAAA? e.gtld-servers.net. (36)
23:14:21.408450 IP6 2001:1291:200:19e::2.58049 > 2001:500:2f::f.53: 10565 AAAA? f.gtld-servers.net. (36)
23:14:21.410051 IP6 2001:1291:200:19e::2.41625 > 2001:500:2f::f.53: 8695 AAAA? g.gtld-servers.net. (36)
23:14:21.411544 IP6 2001:1291:200:19e::2.43899 > 2001:500:2f::f.53: 58055 AAAA? h.gtld-servers.net. (36)
23:14:21.413098 IP6 2001:1291:200:19e::2.58307 > 2001:500:2f::f.53: 63004 AAAA? i.gtld-servers.net. (36)
23:14:21.414755 IP6 2001:1291:200:19e::2.62207 > 2001:500:2f::f.53: 32377 AAAA? j.gtld-servers.net. (36)
23:14:21.416332 IP6 2001:1291:200:19e::2.46011 > 2001:500:2f::f.53: 39226 AAAA? k.gtld-servers.net. (36)
23:14:21.417984 IP6 2001:1291:200:19e::2.9775 > 2001:500:2f::f.53: 19191 AAAA? l.gtld-servers.net. (36)
23:14:21.419588 IP6 2001:1291:200:19e::2.46293 > 2001:500:2f::f.53: 17148 AAAA? m.gtld-servers.net. (36)
23:14:21.421781 IP6 2001:1291:200:19e::2.6241 > 2001:500:2f::f.53: 41650 NS? . (17)
aiccu doesn't automatic reconnect
Shadow Hawkins on Saturday, 09 June 2012 04:37:22
adsl modem 192.168.1.1 - 192.168.1.6 linux gateway 192.168.6.1 - lan
aiccu doesn't automatic reconnect
Shadow Hawkins on Saturday, 09 June 2012 04:54:23
did a new test:
rebooted all devices,
ipv6 tunnel is working,
removed line cable from modem
network got disconnected
put back line cable
ipv4 network is working (new ipv4 address)
ipv6 tunnel is not working
manualy restarted aiccu
tunnel is working again
------
seems aiccu doesnt reconnect when ipv4 address change
aiccu doesn't automatic reconnect
seems aiccu doesnt reconnect when ipv4 address change
There is no need to reconnect, heartbeat and AYIYA take care of that in the protocol.
I am surprised that something breaks, but I think that it has to be the NAT state in your modem's NAT that is causing it. Your adding of NAT rules on your linux host does not help as it is the NAT rules in the modem that are the ones hurting the connection I think.
Please check that you do not load any connection tracker code on your linux box, or for that matter iptables rules as you do not need them unless you configured your modem into DMZ mode, in which case the below breakage would likely make sense again. If you have DMZ mode activated, try disabling it and see if it then survives the external IP address change, as it should.
As an example from the last few packets:
23:13:37.272711 IP 201.48.254.14.5072 > 192.168.1.6.51717: UDP, length 1072 23:13:37.273086 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 1072 // stopped somewhere here 23:13:51.394199 IP 192.168.1.6.51717 > 201.48.254.14.5072: UDP, length 144
Your local IP (192.168.1.6) does not change, as such there is no need to change anything for AICCU. I think though that your NAT forgets about it's state and does not create new state, which is strange as it should simply continue sending packets which will make the NAT create new state from the new source address, apparently it does not do that.
I have not seen this kind of behavior in NATs before, typically the problem is that the local IP changes and as the socket is in connected mode that breaks sending packets. Or does your local IPv4 IP change on the interface?
AYIYA is the right protocol for your tunnel though, as proto-41 will definitely break due to your NAT box.
aiccu doesn't automatic reconnect
Shadow Hawkins on Saturday, 09 June 2012 13:32:21
a new test:
notebook with ubuntu 12.04 x64
aiccu version = 20070115-14.1ubuntu3
no firewall
public ipv4 address, no nat
connected with 3g modem
started aiccu
ipv4 network is working (177.76.114.101)
ipv6 network is working (2001:1291:200:19e::2/64)
disconected 3g
network is down
connected 3g
ipv4 network is working (177.160.219.52)
ipv6 network is not working
restarted aiccu
ipv6 network is working (2001:1291:200:19e::2/64)
if i repeat the test, the result is same
aiccu doesn't automatic reconnect
Giving those details is nice, but what would be really useful is all the other configuration details and tcpdump outputs etc.
aiccu doesn't automatic reconnect
Shadow Hawkins on Saturday, 09 June 2012 22:18:17
Linux alacn3 3.2.0-24-generic #39-Ubuntu SMP Mon May 21 16:52:17 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
aiccu version: 20070115-14.1ubuntu3
no nat
no firewall
notebook connected with 3g modem
// connected 3g 177.76.198.6
tcpdump -n -i sixxs
17:01:48.927576 IP6 2001:1291:200:19e::2.39956 > 2001:4860:4006:802::1002.443: Flags [.], ack 3837, win 380, options [nop,nop,TS val 7188844 ecr 661015390], length 0
17:01:49.147393 IP6 2001:4860:4006:802::101d.443 > 2001:1291:200:19e::2.47914: Flags [R], seq 2982342289, win 0, length 0
17:01:49.177623 IP6 2001:4860:4006:802::101d.443 > 2001:1291:200:19e::2.47914: Flags [R], seq 2982342289, win 0, length 0
17:01:49.177700 IP6 2001:4860:4006:802::101d.443 > 2001:1291:200:19e::2.47914: Flags [R], seq 2982342289, win 0, length 0
17:01:51.848264 IP6 2001:1291:200:19e::2 > 2001:4860:4006:802::1010: ICMP6, echo request, seq 1, length 64
17:01:52.107491 IP6 2001:4860:4006:802::1010 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 1, length 64
17:01:52.848510 IP6 2001:1291:200:19e::2 > 2001:4860:4006:802::1010: ICMP6, echo request, seq 2, length 64
17:01:53.097552 IP6 2001:4860:4006:802::1010 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 2, length 64
17:01:53.848463 IP6 2001:1291:200:19e::2 > 2001:4860:4006:802::1010: ICMP6, echo request, seq 3, length 64
17:01:54.087542 IP6 2001:4860:4006:802::1010 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 3, length 64
17:01:54.848481 IP6 2001:1291:200:19e::2 > 2001:4860:4006:802::1010: ICMP6, echo request, seq 4, length 64
17:01:55.067666 IP6 2001:4860:4006:802::1010 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 4, length 64
// disconected 3g
// reconnected 3g 177.112.88.250
17:02:33.649634 IP6 2001:1291:200:19e::2.39956 > 2001:4860:4006:802::1002.443: Flags [P.], seq 1632:1669, ack 3837, win 380, options [nop,nop,TS val 7200024 ecr 661015390], length 37
17:02:40.351151 IP6 2001:1291:200:19e::2.39956 > 2001:4860:4006:802::1002.443: Flags [P.], seq 1632:1669, ack 3837, win 380, options [nop,nop,TS val 7201700 ecr 661015390], length 37
17:02:48.652906 IP6 2001:1291:200:19e::2.39956 > 2001:4860:4006:802::1002.443: Flags [FP.], seq 1669:1696, ack 3837, win 380, options [nop,nop,TS val 7203775 ecr 661015390], length 27
17:02:53.775155 IP6 2001:1291:200:19e::2.39956 > 2001:4860:4006:802::1002.443: Flags [FP.], seq 1632:1696, ack 3837, win 380, options [nop,nop,TS val 7205056 ecr 661015390], length 64
17:03:05.823160 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1011: ICMP6, echo request, seq 1, length 64
17:03:06.823291 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1011: ICMP6, echo request, seq 2, length 64
17:03:07.823254 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1011: ICMP6, echo request, seq 3, length 64
17:03:08.823205 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1011: ICMP6, echo request, seq 4, length 64
// restarted aiccu
17:10:22.655176 IP6 fe80::1091:200:19e:2 > ff02::2: ICMP6, router solicitation, length 8
17:10:26.663149 IP6 fe80::1091:200:19e:2 > ff02::2: ICMP6, router solicitation, length 8
17:10:32.403509 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 1, length 64
17:10:33.403257 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 2, length 64
17:10:34.292867 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 1, length 64
17:10:35.713052 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 2, length 64
17:10:40.773202 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 3, length 64
17:10:41.781394 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 4, length 64
17:10:44.573434 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 3, length 64
17:10:45.135262 IP6 2001:1291:200:19e::1 > 2001:1291:200:19e::2: ICMP6, echo request, seq 16898, length 988
17:10:45.135331 IP6 2001:1291:200:19e::2 > 2001:1291:200:19e::1: ICMP6, echo reply, seq 16898, length 988
17:10:46.656219 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 4, length 64
17:11:45.704131 IP6 2001:1291:200:19e::1 > 2001:1291:200:19e::2: ICMP6, echo request, seq 16899, length 988
17:11:45.704313 IP6 2001:1291:200:19e::2 > 2001:1291:200:19e::1: ICMP6, echo reply, seq 16899, length 988
17:12:16.015364 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 1, length 64
17:12:17.015278 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 2, length 64
17:12:18.015259 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 3, length 64
17:12:18.683151 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 1, length 64
17:12:19.563302 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 2, length 64
17:12:20.733087 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 3, length 64
17:12:28.213540 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 4, length 64
17:12:29.483277 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 4, length 64
17:12:45.223760 IP6 2001:1291:200:19e::1 > 2001:1291:200:19e::2: ICMP6, echo request, seq 16900, length 988
17:12:45.223920 IP6 2001:1291:200:19e::2 > 2001:1291:200:19e::1: ICMP6, echo reply, seq 16900, length 988
17:13:03.033690 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 1, length 64
17:13:04.041357 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 2, length 64
17:13:04.433358 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 1, length 64
17:13:05.263289 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 2, length 64
17:13:08.723449 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 3, length 64
17:13:09.723345 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 4, length 64
17:13:10.043246 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 3, length 64
17:13:10.924601 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 4, length 64
17:13:40.924210 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 1, length 64
17:13:41.923276 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 2, length 64
17:13:42.353732 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 1, length 64
17:13:43.463257 IP6 2607:f8b0:4008:800::1013 > 2001:1291:200:19e::2: ICMP6, echo reply, seq 2, length 64
17:13:45.463841 IP6 2001:1291:200:19e::1 > 2001:1291:200:19e::2: ICMP6, echo request, seq 16901, length 988
17:13:45.464005 IP6 2001:1291:200:19e::2 > 2001:1291:200:19e::1: ICMP6, echo reply, seq 16901, length 988
17:13:47.205162 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 3, length 64
17:13:48.213358 IP6 2001:1291:200:19e::2 > 2607:f8b0:4008:800::1013: ICMP6, echo request, seq 4, length 64
# aiccu test
Tunnel Information for T64489:
POP Id : brudi01
IPv6 Local : 2001:1291:200:19e::2/64
IPv6 Remote : 2001:1291:200:19e::1/64
Tunnel Type : ayiya
Adminstate : enabled
Userstate : enabled
aiccu doesn't automatic reconnect
no nat
As you are running Linux and unless you have specifically disabled the code, you will always have a connection tracker enabled in the kernel that can cause issues as it is tracking connections.
// connected 3g 177.76.198.6 tcpdump -n -i sixxs
// disconected 3g // reconnected 3g 177.112.88.250
That thus is showing the traffic that is sent into the tunnel (the sixxs interface). The "Reporting Problems" section on the contact page explicely states to look at the underlying interface, as then you would actually see also the IPv4 packets and especially important in this situation if the correct IPv4 address is being used.
I am btw surprised a bit that you get a public IPv4 address on a 3G connection as that rarely happens, but it is good to see that some ISPs do do that.
aiccu doesn't automatic reconnect
Shadow Hawkins on Sunday, 10 June 2012 03:29:18As you are running Linux and unless you have specifically disabled the code, you will always have a connection tracker enabled in the kernel that can cause issues as it is tracking connections.
ill check what happens with windows...
That thus is showing the traffic that is sent into the tunnel (the sixxs interface). The "Reporting Problems" section on the contact page explicely states to look at the underlying interface, as then you would actually see also the IPv4 packets and especially important in this situation if the correct IPv4 address is being used.
both 3g and adsl happens exactly same thing when ip changes, it stop receiving packets from PoP, it will just repeat already posted tcpdump
I am btw surprised a bit that you get a public IPv4 address on a 3G connection as that rarely happens, but it is good to see that some ISPs do do that.
i didnt know that ISPs used nat for 3g connections in other places
aiccu doesn't automatic reconnect
> As you are running Linux and unless you have specifically disabled the code, you will always have a connection tracker enabled in the kernel that can cause issues as it is tracking connections. ill check what happens with windows...
both 3g and adsl happens exactly same thing when ip changes, it stop receiving packets from PoP, it will just repeat already posted tcpdump
As long as valid packets are being sent to the PoP the PoP will be able to send packets back.
As your symptom is resolved with restarting AICCU, the only thing I can come up with is that your local parameters (the sockets it binds to etc) change and that allows the packet to be sent again.
In your first case, this problem could be caused by state in your modem which does the NAT, but there, AICCU cannot know (unless we ask an external website/resource once in a while) that your public IP changed. This is an issue in your NAT which apparently does not create new NAT entries for previously existing outbound flows.
In your second 3G case it could be that you are hitting the socket-still-bound-to-old-address issue, but that can only be seen in the packet dump.
aiccu doesn't automatic reconnect
Shadow Hawkins on Sunday, 10 June 2012 13:54:57
just noticed, when it stop working it produces this to syslog
Jun 9 17:02:33 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 153 bytes to network: Invalid argument (22)
Jun 9 17:02:33 alacn3 aiccu[7218]: [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Invalid argument (22)
Jun 9 17:02:40 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 153 bytes to network: Invalid argument (22)
Jun 9 17:02:48 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 143 bytes to network: Invalid argument (22)
Jun 9 17:02:53 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 180 bytes to network: Invalid argument (22)
Jun 9 17:03:05 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 148 bytes to network: Invalid argument (22)
Jun 9 17:03:09 aiccu[7218]: last message repeated 3 times
Jun 9 17:03:09 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 124 bytes to network: Invalid argument (22)
Jun 9 17:03:20 aiccu[7218]: last message repeated 3 times
Jun 9 17:03:20 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 180 bytes to network: Invalid argument (22)
Jun 9 17:03:24 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 124 bytes to network: Invalid argument (22)
Jun 9 17:03:33 alacn3 aiccu[7218]: [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Invalid argument (22)
Jun 9 17:03:40 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 124 bytes to network: Invalid argument (22)
Jun 9 17:03:57 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 148 bytes to network: Invalid argument (22)
Jun 9 17:04:14 aiccu[7218]: last message repeated 3 times
Jun 9 17:04:14 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 180 bytes to network: Invalid argument (22)
Jun 9 17:04:25 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 124 bytes to network: Invalid argument (22)
Jun 9 17:04:33 aiccu[7218]: last message repeated 3 times
Jun 9 17:04:33 alacn3 aiccu[7218]: [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Invalid argument (22)
Jun 9 17:04:40 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 124 bytes to network: Invalid argument (22)
Jun 9 17:05:11 aiccu[7218]: last message repeated 5 times
Jun 9 17:05:33 aiccu[7218]: last message repeated 4 times
Jun 9 17:05:33 alacn3 aiccu[7218]: [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Invalid argument (22)
Jun 9 17:05:35 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 124 bytes to network: Invalid argument (22)
Jun 9 17:06:33 aiccu[7218]: last message repeated 5 times
Jun 9 17:06:33 alacn3 aiccu[7218]: [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Invalid argument (22)
Jun 9 17:06:34 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 124 bytes to network: Invalid argument (22)
Jun 9 17:07:33 aiccu[7218]: last message repeated 8 times
Jun 9 17:07:33 alacn3 aiccu[7218]: [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Invalid argument (22)
Jun 9 17:07:34 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 124 bytes to network: Invalid argument (22)
Jun 9 17:08:33 aiccu[7218]: last message repeated 11 times
Jun 9 17:08:33 alacn3 aiccu[7218]: [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Invalid argument (22)
Jun 9 17:08:37 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 124 bytes to network: Invalid argument (22)
Jun 9 17:09:01 aiccu[7218]: last message repeated 15 times
Jun 9 17:09:09 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 124 bytes to network: Invalid argument (22)
Jun 9 17:09:33 aiccu[7218]: last message repeated 7 times
Jun 9 17:09:33 alacn3 aiccu[7218]: [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Invalid argument (22)
Jun 9 17:09:40 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 124 bytes to network: Invalid argument (22)
aiccu doesn't automatic reconnect
Is that the setup with the 3G or the one with the NAT?
aiccu doesn't automatic reconnect
Shadow Hawkins on Sunday, 10 June 2012 21:28:29
just checked, it happened only with 3g
aiccu doesn't automatic reconnect
From a previous reply:
In your second 3G case it could be that you are hitting the socket-still-bound-to-old-address issue, but that can only be seen in the packet dump.
I assume it is that issue. But that is unrelated to your original issue.
aiccu doesn't automatic reconnect
Shadow Hawkins on Saturday, 16 June 2012 17:58:39
i tested it with windows, it works fine with adsl or 3g reconnection,
with linux it doesnt work after ip changes, no matter what,
i had to make a script to check when ip changes and restart aiccu,
it was the only way to keep it working
aiccu doesn't automatic reconnect
Please provide a lot more details instead of stating something is broken.
aiccu doesn't automatic reconnect
Shadow Hawkins on Monday, 01 October 2012 04:23:36
I'm having the same problem whenever my connection (PPPoE) drops. I get the same type of errors in my log as this user (copying from his since openwrt uses a small buffer for busybox syslogd):
Jun 9 17:05:33 alacn3 aiccu[7218]: [AYIYA-beat] : Error (-1) while sending 44 bytes sent to network: Invalid argument (22)
Jun 9 17:05:35 alacn3 aiccu[7218]: [AYIYA-tundev->tun] : Error (-1) while sending 124 bytes to network: Invalid argument (22)
Jun 9 17:06:33 aiccu[7218]: last message repeated 5 times
Unfortunately, my ISP forces an IP change at least once every day, so I have to restart the tunnel every time that happens, which obviously sucks. I'll give more info whenever the problem happens again, but this looks like a widespread issue. I came across other people having similar problems on openwrt's bug tracker: https://dev.openwrt.org/ticket/10241
aiccu doesn't automatic reconnect
Looks a lot that you are hitting the connected UDP problem.
That https://dev.openwrt.org/ticket/10241 gives an NGINX error...
aiccu doesn't automatic reconnect
![[de]](/s/countries/de.gif) Shadow Hawkins on Sunday, 20 July 2014 23:03:49
With Ayiya I have the same issue when I roam from one Wi-fi network to another. In this case my wifi interface stays up, just my local IP and gateway changes and from aiccu I get an error like this whenever I try to send something via ipv6:
[AYIYA-tundev->tun] : Error (-1) while sending 148 bytes to network: Invalid argument (22)
It seems like this is fixed in the windows version 20080315: "* Change from connected UDP socket to unconnected UDP socket for
AYIYA tunnels This avoids cases where the local address changes and
the socket is still being used. This goes unnoticed when one is
behind a NAT as then the local address mostly remains the same." (from https://www.sixxs.net/tools/aiccu/changelog)
Strangely there hasn't been a linux version with this fix since 7 years.
aiccu doesn't automatic reconnect
Shadow Hawkins on Monday, 01 October 2012 23:33:07
There's something wrong with their servers, downloads.openwrt.org is 404ing as well.
Where can I read more about this UDP problem?
|
![[ch]](/s/countries/ch.gif)
on Saturday, 09 June 2012 03:05:06
Posting is only allowed when you are