Here's a list of what "errors" the script can report, and a more human explanation of what they mean.
Code:
Client sent IP address *BLAH*. *BLEH* is unacceptible
Your "local IP" field (or --ip parameter) is set to a private IP address. Private IP addresses are blocked out on the Internet, and so will never work. Notable, 192.160.x.x and 10.x.x.x are private (for any numbers x). The script has aborted and will not check further.
Code:
NAT check failed. Client IP address override is correct though.
Script agreed with your choice of "local IP" field, but you're still firewalled.
Code:
Proxy detected, but NAT check OK and your IP override is correct. Best you can do.
Script agreed with your choice of "local IP" field, and you're not firewalled.
Code:
NAT check failed (with transpart proxy). Check for port forwarding.
A transparent proxy was detected and compensated for, but you're firewalled. Or possibly your transparent proxy is not reporting your real address correctly (I hope not).
Code:
Transparent proxy detected, but I can still connect to you. Adequate.
A trnasparent proxy was detected and compensated for, and you're not firewalled. Some PHP trackers may still cause you to appear firewalled if they don't check for transparent proxies.
Code:
NAT check failed to overrided IP address. Check for firewalls or port forwarding.
Your IP override field was not agreed with (though not necessarily wrong) and it seemed to be firewalled. If you believe you are not firewalled, double-check your Local IP setting.
Code:
Accepted IP override with perfect score. Not all trackers will accept it though.
Although the script disagreed with your choice of Local IP, it worked anyways. But you may not be able to use it with trackers that don't accept that field.
Code:
NAT check failed. Check for firewalls or port forwarding.
No transparent proxy was detected, but you seem to be firewalled.
Code:
I can connect to you. Perfect score.
SWEET!