Just a warning that when a coin forks the older clients can be quite aggressive with requesting blocks. They request the same set of blocks over and over, I guess because of a bug or oversight in the code.

For example, 148.251.13.39 appears to be on the old chain (starting height 251827). I tracked its bandwidth for a period of 60 seconds:

128804 bytes in
1398272 bytes out

... and it's constantly growing. It seems the older client can never internally resolve the fork, so it gets stuck in some sort of loop requesting the same blocks.

As mentioned earlier in this thread it has had an impact on my DSL link; I have had to resort to firewalling GLX peers that are on the old fork to stop them hogging it.

edit: there are currently 3 old chain GLX peers consuming about 0.5Mbps of my 1Mbps uplink speed (50% of my entire upload capacity)