Non-public IPs don't follow precendence. about django-ipware

[un33k]

That is correct. If the IP is not externally routeable (e.g. private ip), then your best bet might be to use the REMOTE_ADDR field which is the last item in the default precedence list. This might not be the case for everyone. If so, then you'd be passing in your own precedence list. This behavior is not an exact science and may not work for all setups.

[myq]

That makes sense, but, in general, do you expect that the desired precedence list for real (public) IPs will be the /reverse/ of the precedence list for non-public IPs? Because that's what your code does, currently.

[un33k]

Yep. That's the intended behavior.

[un33k]

I have changed the behavior so the private and the public IP address search follows the same precedence list. With one exception, and that is, any private IP will win over a loopback interface even if it is matched later.