This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] cmd line asused and webasused
- Previous message (by thread): [db-wg] cmd line asused and webasused
- Next message (by thread): [db-wg] cmd line asused and webasused
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at inex.ie
Wed Jan 18 12:01:41 CET 2012
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
- Previous message (by thread): [db-wg] cmd line asused and webasused
- Next message (by thread): [db-wg] cmd line asused and webasused
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]