Quote:
Originally Posted by foddy
Yes, but can it ever do what I need?
2. Simply put, the feature set will be aimed at the majority of users. It'll be simple to use rather than technical and functionally complete. I don't see there ever being a "one size fits all" solution for this.
|
The solution is already out there, add as many features as possible to cater for as many people as possible. I have never heard of someone complain about too many features before alex brown mentioned it.
As for making it suitable for the majority, making tcp timeout after only 60 seconds is not doing that, I think others as well as myself are curious why that is such a low value, I suspect they set low so torrent users wouldnt be complaining about the superhub dieing as I suspect its set like that to hide a small NAT table. A timeout value to ensure compatability with apps would have been something along the lines of 1800secs or 3600secs. or even 7200secs. I tend to tune routers down to a lower number like 180, 300 or 900 seconds but I would only ever go down to 60 or lower if I was getting a high pps ddos. Of course the problem here is I cannot tune the superhub to fix the breakage, as VM have decided I am too dumb to do that.