tievolu
On our wavelength
Joined 15 years ago
User Profile
User Widgets
Contributions
Re: UDP issues on SuperHub3 - collective thread
After some more testing I've found that Bittorrent does overload the SH3 if I'm downloading several torrents with large number of seeds and peers with uTP enabled. As with the pathological DNS test (described a few posts up), the problem only happens when several thousand UDP connections are opened in a short period of time. Disabling uTP in the Bittorrent client prevents the problem from happening. I think I can put up with this until CityFibre complete their rollout in my area.2.1KViews1like1CommentRe: UDP issues on SuperHub3 - collective thread
I've just switched from a SH2 to a SH3 to upgrade from 200M to 350M, and so far everything has been fine with normal use (~25 devices connected, with lots of concurrent usage including MS Teams, Skype, webex, torrents, gaming, two work VPNs, streaming, and the usual web browsing. I'm running the SH3 in modem mode with an Intel-based OpenWRT device doing the routing. Out of curiosity I have reproduced the overloading of the SH3 by running a command similar to the one mentioned earlier in this thread: while ( true ) do nslookup www.google.co.uk 1.1.1.1; done However, I'm not sure whether the SH3 is struggling with the amount of UDP traffic generated by this command, which is actually pretty small (about 100 packets per second), or whether it's the number of connections that causes the problem. In my tests the SH3 only starts to struggle when there are ~4500 UDP connections created by the DNS lookups. 4500 concurrent UDP connections is obviously a pretty large number, and is unlikely to happen with normal home usage. I'm not saying it isn't a problem per se, but I think I'm unlikely to hit it unless I'm really trying. Generating a similar number of UDP packets per second, but on a single connection, exhibits no problems: iperf3 -c ping.online.net -p 5207 -R -u -t 1002.5KViews2likes3Comments