| 1 | | I set up tc NetEm on a linux box, running apache, and used both the Netsurf and Webpositive browsers on a Haiku box to access it. The "latency/delay" was set to be random in the range of **2ms to 2s**, "packet loss" was set from **0% to 70%**, and "duplicates" were set from **0% to 40%**. Neither browser exhibited any problem whatsoever, even when the packet loss was very high, or the delay very high. In one instance, a warning message was displayed in Netsurf: //"Operation too slow: less than 1 byte/sec"// |
| 2 | | |
| 3 | | The network stack seems to be very resilient. I'm impressed. |
| 4 | | |
| 5 | | I did the "tc NetEm" test for maybe an hour, continuously. Admittedly, that's not much test time, because the original problem was very sporadic/occasional. Anyway, I suppose my ISP could have been resetting packets on the day I had the trouble with resets from Google and Haiku-OS.org. As it is, nothing's adding up very well on this. Probably ought to take a "wait and see" attitude on it. |
| | 1 | NA |
