Comment 5 for bug 1261653

> If operator could block AYIA I belive aiccu did not start !

Even if AYIYA is blocked (or otherwise caused to be broken), AICCU can still start.

This as AICCU fetches it's configuration using the TIC protocol, which is independent of the tunnel protocol used afterwards (proto-41, optionally with heartbeat or AYIYA).

> Restarting is not due aiccu is down or not running,...
>.... reason or another it hangs ,... sudo restart aiccu
>start's incoming ipv6 trafic,.... ping6 send's packages
>while aiccu/tunnel is hangig but no response nor error!!!

Where are the interface tables, tcpdumps and other details that would maybe show an error? See previous comment for other details that would be very useful.

> ANY IDEAS HOW TO TEST THAT OPERATOR IS NOT
> DISTURBIN AYIA / AICCU ???

Providing the requested information would be a good start.

> joni@mpi2:~$ sudo cat /etc/aiccu.conf

There is very little that one can do wrong in the AICCU config; keeping the default options and just having username/password/tunnel_id is all one needs (typically at least).

But that is a config,not the output of AICCU when it is running, not a tcpdump nor any other useful technical detail.