When using the user-space transport, the netlink frame sent to user-space has a rate index and retry count, and nothing else. Is there a reliable way to know in user-space what index maps to what actual rate? If not, any suggestions for how to improve this? Maybe add a new object that passes up a bunch more info about the actual rates instead of just the rate idx? Thanks, Ben -- Ben Greear <greearb@xxxxxxxxxxxxxxx> Candela Technologies Inc http://www.candelatech.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html