Currently, the RPC driver can only control one RPC device at a time. Configurations with multiple RPC radios are not supported. (The underlying Parapin library currently has the same limitation.)
When using the fragmentation interface, the memory used by krpc will grow slowly over time (up to a certain limit). The driver currently does not implement garbage collection; it will in the future.
When providing an IP interface, the RPC driver really should do link-layer retransmissions. TCP performance is rather bad otherwise.
The implementation of fragmentation can be made somewhat more efficient; the first ``introduction'' fragment currently does not carry any data.
Please report other bugs and suggestions to the author, Jeremy Elson, at jelson@circlemud.org. I love getting feedback.