Dear Colleagues, The RIPE NCC has fixed the issue that caused the whois server to act strangely in response to queries sent with the '-k' flag. This should also fix the asused functionality problems. I have installed a fresh Debian instance with Debian's asused package and it all works fine on my machine. Please check your installations and contact ripe-dbm@ripe.net if you find any issues or strange behaviors. Sorry for the inconvenience caused by this bug. Kind Regards, Kaveh. --- Kaveh Ranjbar RIPE NCC Database Group Manager On Jan 18, 2012, at 12:01 PM, Nick Hilliard wrote:
On 18/01/2012 10:44, Kaveh Ranjbar wrote:
Thank you for the patch. Just wanted to clarify the issue over the '-M' query flag. The RIPE NCC would never make a change in functionality like this without getting community approval and proper communication. The syntax of '-M' has not changed at all. As we investigated further, the asused misbehavior is caused by the whois server acting weird with the '-k' flag. We are working to fix that as soon as possible and will have a fix in production very shortly.
ok, strange: "-M <range>" didn't work when I was testing, but "-M <prefix>/<netmask>" did. And as I mentioned previously, even if the semantics had changed, the hacky workaround I posted isn't a fix, and will break horribly in lots of situations (e.g. non-cidr aligned allocations, incorrectly specified allocations in asused.conf, etc).
Anyway, good to hear that there are plans to fix this properly.
Nick