Bufferbloat Download with Hitron CODA-4680 Firmware 2.0.10.43b8
Mehdi B. 4237
Posts: 412 ✭✭
in Internet
Hi here,
It's a topic for expert technical problem.
I explain the problem with Hitron CODA-4680 Firmware 2.0.10.43b8
When i DOWNLOAD and try to PING the Bufferbload is big :
PING ping.ovh.ca (8.33.137.106): 56 data bytes
64 bytes from 8.33.137.106: icmp_seq=0 ttl=251 time=157.591 ms
64 bytes from 8.33.137.106: icmp_seq=1 ttl=251 time=189.238 ms
64 bytes from 8.33.137.106: icmp_seq=2 ttl=251 time=448.855 ms
64 bytes from 8.33.137.106: icmp_seq=3 ttl=251 time=339.850 ms
64 bytes from 8.33.137.106: icmp_seq=4 ttl=251 time=273.168 ms
64 bytes from 8.33.137.106: icmp_seq=5 ttl=251 time=482.245 ms
64 bytes from 8.33.137.106: icmp_seq=6 ttl=251 time=303.433 ms
64 bytes from 8.33.137.106: icmp_seq=7 ttl=251 time=497.887 ms
64 bytes from 8.33.137.106: icmp_seq=8 ttl=251 time=299.360 ms
64 bytes from 8.33.137.106: icmp_seq=9 ttl=251 time=219.606 ms
64 bytes from 8.33.137.106: icmp_seq=10 ttl=251 time=96.023 ms
64 bytes from 8.33.137.106: icmp_seq=11 ttl=251 time=369.478 ms
64 bytes from 8.33.137.106: icmp_seq=12 ttl=251 time=84.453 ms
64 bytes from 8.33.137.106: icmp_seq=13 ttl=251 time=416.066 ms
64 bytes from 8.33.137.106: icmp_seq=14 ttl=251 time=379.314 ms
Is only appear with Firmware 2.0.10.43b8
I have try with another people on this forum:
https://www.dslreports.com/forum/r32336410-Bufferbloat-en-Download-Avec-Modem-hiton-CODA-4680-de-Fizz
And we are all in trouble with this firmware, so PLEASE Fizz update the firmware or downgrade it
NO ISSUE with 2.0.10.41 firmware !!!!
Another page to speak for the Hitron CODA 4680 is Bad
https://badmodems.com/Forum/app.php/badmodems
Regards,
It's a topic for expert technical problem.
I explain the problem with Hitron CODA-4680 Firmware 2.0.10.43b8
When i DOWNLOAD and try to PING the Bufferbload is big :
PING ping.ovh.ca (8.33.137.106): 56 data bytes
64 bytes from 8.33.137.106: icmp_seq=0 ttl=251 time=157.591 ms
64 bytes from 8.33.137.106: icmp_seq=1 ttl=251 time=189.238 ms
64 bytes from 8.33.137.106: icmp_seq=2 ttl=251 time=448.855 ms
64 bytes from 8.33.137.106: icmp_seq=3 ttl=251 time=339.850 ms
64 bytes from 8.33.137.106: icmp_seq=4 ttl=251 time=273.168 ms
64 bytes from 8.33.137.106: icmp_seq=5 ttl=251 time=482.245 ms
64 bytes from 8.33.137.106: icmp_seq=6 ttl=251 time=303.433 ms
64 bytes from 8.33.137.106: icmp_seq=7 ttl=251 time=497.887 ms
64 bytes from 8.33.137.106: icmp_seq=8 ttl=251 time=299.360 ms
64 bytes from 8.33.137.106: icmp_seq=9 ttl=251 time=219.606 ms
64 bytes from 8.33.137.106: icmp_seq=10 ttl=251 time=96.023 ms
64 bytes from 8.33.137.106: icmp_seq=11 ttl=251 time=369.478 ms
64 bytes from 8.33.137.106: icmp_seq=12 ttl=251 time=84.453 ms
64 bytes from 8.33.137.106: icmp_seq=13 ttl=251 time=416.066 ms
64 bytes from 8.33.137.106: icmp_seq=14 ttl=251 time=379.314 ms
Is only appear with Firmware 2.0.10.43b8
I have try with another people on this forum:
https://www.dslreports.com/forum/r32336410-Bufferbloat-en-Download-Avec-Modem-hiton-CODA-4680-de-Fizz
And we are all in trouble with this firmware, so PLEASE Fizz update the firmware or downgrade it
NO ISSUE with 2.0.10.41 firmware !!!!
Another page to speak for the Hitron CODA 4680 is Bad
https://badmodems.com/Forum/app.php/badmodems
Regards,
12
Answers
-
Hi Mehdi,
Good find, at first I was skeptical at the ping times and I thought it was BGP's doing because it does try to choose the best path possible after the hand off is done from the modem to Videotron's servers. In this case the issue lies with the modem's QoS system which is inadvertently controlled by the firmware.
I read the DSLR posts, and it does seem to allude that 2.0.10.43b8 has tons of bugs, and that 2.0.10.41 doesn't have the same QoS issues along with 2.0.10.42b6 but these firmwares have their own issues, particularly wifi it seems.
I will open a ticket with Fizz support but I doubt they will do anything until Hitron and Videotron decide to change the firmware.3 -
Yes i think we are to open a multiple ticket to resolve the issue....
Is not good right now...and i think is very simple to solve it1 -
I can also confirm that the problems occurs at the firmware level. When we receive a new modem with Fizz, it comes with 2.0.10.41 and it eventually gets upgraded to 2.0.10.43b8 which is when the bufferbloat on the download side occurs.2
This discussion has been closed.