Port numbers are incorrect?

It seems that (under certain, still unknown) conditions, the traffic can be stuck in the buffer and a copy will be sent every second, regardless of actual traffic. In the sample below, this occurred. tcpdump confirmed that no actual relevant traffic was going on at the time.

{"command":"traffic","argument":"","result":{"flows":[{"from":1,"to":2,"protocol":6,"from_port":26326,"to_port":23303,"size":319,"count":2}],"timestamp":1579183535,"total_size":319,"total_count":2}}
{"command":"traffic","argument":"","result":{"flows":[{"from":1,"to":2,"protocol":6,"from_port":26326,"to_port":23303,"size":319,"count":2}],"timestamp":1579183536,"total_size":319,"total_count":2}}
{"command":"traffic","argument":"","result":{"flows":[{"from":1,"to":2,"protocol":6,"from_port":26326,"to_port":23303,"size":319,"count":2}],"timestamp":1579183537,"total_size":319,"total_count":2}}
{"command":"traffic","argument":"","result":{"flows":[{"from":1,"to":2,"protocol":6,"from_port":26326,"to_port":23303,"size":319,"count":2}],"timestamp":1579183538,"total_size":319,"total_count":2}}
{"command":"traffic","argument":"","result":{"flows":[{"from":1,"to":2,"protocol":6,"from_port":26326,"to_port":23303,"size":319,"count":2}],"timestamp":1579183539,"total_size":319,"total_count":2}}
{"command":"traffic","argument":"","result":{"flows":[{"from":1,"to":2,"protocol":6,"from_port":26326,"to_port":23303,"size":319,"count":2}],"timestamp":1579183540,"total_size":319,"total_count":2}}
{"command":"traffic","argument":"","result":{"flows":[{"from":1,"to":2,"protocol":6,"from_port":26326,"to_port":23303,"size":319,"count":2}],"timestamp":1579183541,"total_size":319,"total_count":2}}
{"command":"traffic","argument":"","result":{"flows":[{"from":1,"to":2,"protocol":6,"from_port":26326,"to_port":23303,"size":319,"count":2}],"timestamp":1579183542,"total_size":319,"total_count":2}}

I will update this issue with more information when available.

SIDN / spin

Port numbers are incorrect? #73