socketman: sequence number comparisons don't handle wraparound

If a segment arrives or is sent with a sequence number that starts at or near the top of 32-bit numerical limit, and then a later segment carries a sequence number that wraps around to 0 but is still within the sliding window, any comparisons done on it don't account for this and will fail erroneously. Comparisons should be done using modular arithmetic.