Package: jdresolve Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Me intending to use it. * What exactly did you do (or not do) that was effective (or ineffective)? jdresolve logfile | less * What was the outcome of this action? Only half of it done. * What outcome did you expect instead? All of it done. *** End of the template - remove these lines *** (Gosh, templates are so shit). Consider the following log: --8<------------------------schnipp------------------------->8--- 213.146.108.162 - - [02/Feb/2012:22:11:27 +0000] "GET / HTTP/1.1" 200 994 "http://whatever/" "Mozilla/5.0 (X11; Linux x86_64)" 213.146.108.162 - - [02/Feb/2012:22:11:27 +0000] "GET /local_logo.png HTTP/1.1" 404 482 "http://whatever/" "Mozilla/5.0 (X11; Linux x86_64)" 2a01:198:5d0:0:21c:c0ff:fead:e3a3 - - [02/Feb/2012:22:11:27 +0000] "GET /favicon.ico HTTP/1.1" 200 13212 "-" "Mozilla/5.0 (X11; Linux x86_64)" --8<------------------------schnapp------------------------->8--- I want the IPs resolved, and jdresolve package desc let me believe it tries that. Unfortunately it only can do IPv4, so meh, it can't do its job as needed nowadays with all that v6 shit going around. Would be nice if it gains support for that. Alternatively at least the description adjusted to tell everyone its not ipv6 ready. -- bye, Joerg db.oftc.net? * Maulkin thinks Ganneff is doing evil ldap stuff again It's called the Ganneff fingerprint If somethign has 'db.foo.blah' it's had Ganneff involved