david at coova.com
Wed Apr 7 08:22:59 UTC 2010
> What would be the implication of this change with respect to rate limit ?
> Will per-user chilli attributes ( eg WISPr-Bandwidth-Max-Down ) continues to work in user mode ?
> Will it make "group rate limit" ( verses per-user rate limit ) easier to implement ?
It isn't there yet, but the simplistic "leaky bucket" rate shaping of
chilli could easily be also implemented in the kernel module. Or, as
Wichert mentioned, it could tap into more sophisticated kernel features
(any examples Wichert?). This would be required as chilli does not route
packets for authenticated traffic in this scenario. Chilli sees the
packets, but just ignores them.
Also, similar to how the 'recent' module, you can interact with the
kernel module in the /proc file system. This is also how chilli itself
updates client status and fetches up/down octets/packets for
More information about the Chilli