As Jeroen said, this is no bug. The problem may sit on some
configuration problems, but not on aiccu itself.
** Changed in: aiccu (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The 'behindnat' option only disables a warning, for the rest it does
absolutely nothing.
It figures out that it is behind NAT (well, it checks if that address is
RFC1918) it that is the case and when that is the case it warns the user
about this, 'behindnat' disables that warning, that is it.
Hmm - I may be wrong about this. IPv6 (e.g. ping6) was not working
yesterday when I first tried it, and I couldn't figure out why. I got
no error messages from aiccu. It worked this morning when I restarted
after adding behindnat true.
But now it also works when I go back to commenting that
If there was something wrong, I am very sure that the 'behindnat' option
had anything to do with solving it ;)
As for problems with connectivity, don't hesitate to report those in the
proper place as per http://www.sixxs.net/contact/ and of course, with
the details as per requested there.
--
