Since you've pointed out that you're getting TCP errors on your network before zm reconnects (TCP Retransmissions in particualar): I'm not dealing with the TCP/IP layer in zm, that's the responsibility of the kernel. It seems that your router/nat has troubles to keep multiple connections open, it just closes them after some time.
I can monitor the network, but the funny thing is the network only does this with your miner, it does not happen with any other program or configuration. and it happens only on 1 computer. if what you suggest were true, it would have several disconnections for all computers at the same time. But it doesn't. Everything points to be something in your code triggering some weird configuration on the latest ubuntu update (since I updated both ubuntu and your miner at the same time).
I'll take a look at the NAT/routing tables in the kernel and see if I can find out what is going on.
Sigh.
That's what I was trying to say
ZM uses multiple constantly opened connection, it seems that your router/nat has troubles to keep multiple connections constantly open. That's most likely why you're not seeing this behavior with other programs which are using only one connection.Edit:
Quote
it would have several disconnections for all computers at the same time
Not necessarily. Your router might drop the connections to a particular host only.
Quote
and it happens only on 1 computer.
This might be very helpful to debug the issue. What's different on this PC? Does it have more GPUs such that it opens more connections? Are the GPUs faster/slower such that they produce more/less shares/network traffic?