> Technical detail is that fact operator changes IP time to time as well > there can missing pacets due operator switches radio mode of conection > between GRPS-UMTS-HSPA,....
That is not a *technical* detail, that is merely a description of the problem that you are seeing. As stated, the AYIYA and heartbeat protocols both handle the situation of an IP address change. > SHOREWALL6 How is this "shorewall6" configured, any connection tracking or other firewalling happening that is blocking packets? > I belive this somthing to do whit Operators way handle > incoming trafic and chage of IP4,.... If your operator intentionally (or not) is blocking AYIYA/heartbeat (you don't specify what you are using), then there is nothing that AICCU or the AYIYA/heartbeat protocols can do about this as they are not circumvention protocols. > sixxs IPV6 gose down > incoming direction but IPV4 works and sixxs IPV6 dose not > come back whitout reastarting aiccu,... I was planing to > to do script that pings my own site via sixxs and if not > find then restart,... >From the README and also mentioned on www.sixxs.net/tools/aiccu/ ------------------------ Notes Please read the README that is included with AICCU. Following is an important section of that text: WARNING: Never run AICCU from DaemonTools or a similar automated 'restart' tool/script. When AICCU does not start, it has a reason not to start which it gives on either the stdout or in the (sys)log file. The TIC server *will* automatically disable accounts which are detected to run in this mode. Use 'verbose true' to see more information which is especially handy when starting fails. Please also heed the notice in the TIC FAQ which explains what happens to clients that connect repeatively. ------------------------- Thus in case you did not bother reading that or: https://www.sixxs.net/news/2013/#tichammeringcontinuespleasecon-0722 now you are pointed to it. Thus be forewarned. Thus instead of going the "Something is broken, I don't know what, I'll just restart it" route, instead please actually provide *TECHNICAL DETAILS* of the problem (strace, netstat, tcpdump, interface and routing tables etc etc etc) without that there is little anyone can say about your situation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1261653 Title: aiccu can not route, looses route To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1261653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
