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