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. This thing is more a thing for the UI than for the daemon version that is for the linux platforms. When one is behind a NAT, in 99% of the cases you are using AYIYA, and AYIYA does not care that it is behind a NAT. I think what happened in your case is that you requested a tunnel and it did not work directly as the PoP only gets re-configured every 10 minutes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/794579 Title: aiccu: debconf should ask if you're behind a NAT -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
