The following are considered limitations of kplex rather than bugs.
- kplex cannot use "255.255.255.255" as an address for bi-directional broadcast sockets. This is not a limitation for inbound-only interfaces where no explicit system interface device is specified, nor a problem for outbound only interfaces. 255.255.255.255 should not in any case be used as a broadcast address in this context instead of the subnet broadcast address. This is a feature of how kplex binds to particular network devices to receive traffic arriving only from that source.
- Changes to parsing rules to accommodate TAG blogs mean that from version 1.1 kplex can no longer be used to route arbitrary data strings. Only data starting with '$','!' or the TAG delimiter '\' are now recognised and propagated. Checksums are not compulsory unless "checksum=yes" is specified