Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: les-70 on February 11, 2020, 04:19:39 PM
-
I have been running with a HG612 for some years as that gave the lowest ES/SES rates and avoided a high risk of interleaving that I found with all other modems. The best alternative was a Billion 8800nl with about 2-3 times the error rate. The next best was a VMG1312-B10A with about 3 times the error rate.
I recently found a really cheap Netgear 6220 on ebay and given comments on that by others bought and tested it. The error rate was slightly less than with HG612 and it looked like a posible one box alternative setup. As noted by others the Netgear GUI really does put you off though.
The D6220 uses the "39u" dsl components so I wondered if the other routers might do better with a firmware update. The billion 8800nl has not had an availble update since I last tried it and it did the same as before at about 3 times the Hg612 error rate. The VMG1312-B10A tested with the old firmware using "39o" also was just the same as before with 3-4 times the HG612 error rate. However with an update to the latest firmware using "39v" the VMG1312-B10A modem is transformed and the error rate is a bit less than the both the D6220 and the HG612.
I have concluded that my writing off of things as no good needs to be rechecked when/if new firmware is available.
The Billion 8800nl and the VMG1312-B10A with old firmware maintained my upstream attainable at the same value as the HG612, a bit above 20Mb/s but gained about 1Mb/s extra downsteam. The D6220 and the VMG1312-B10A (with latest firmware) drop the upstream speed by 1Mb/s and are only a tiny barely signifcant bit faster downstream than the HG612 at about 68Mb/s.
On my line low errors are a priority as there are odd bad days which the DLM can react to. I have decided to adopt the VMG1312-B10A as a one box solution as I don't need a gigahertz LAN and most of my wireless use is a fair distance and a few walls distant and best at 2.4GHz. :)
-
Some interesting results. Thank you for posting.
-
Are you on a Huawei or ECI cabinet mate?
-
Are you on a Huawei or ECI cabinet mate?
ECI, hence the need to keep ES low to keep Interleaving off.
-
However with an update to the latest firmware using "39v" the VMG1312-B10A modem is transformed and the error rate is a bit less than the both the D6220 and the HG612.
Did you try the Johnson's firmware with "39x6" DSL modem code, by any chance?
-
@hushcoden I have not tried that firmware. Please can you point me to it? I did notice that Zyxel have the "39x" in other modems. It is pity that Billion seem not to issue very few updates it would have been good to try a recent dsl code in the 8800nl.
On my line it seems that the latest broadcom com dsl codes may have been adjusted for better stability at the expense of a little less speed.
and yes the line is on an ECI
-
@hushcoden I have not tried that firmware. Please can you point me to it? I did notice that Zyxel have the "39x" in other modems. It is pity that Billion seem not to issue very few updates it would have been good to try a recent dsl code in the 8800nl.
On my line it seems that the latest broadcom com dsl codes may have been adjusted for better stability at the expense of a little less speed.
and yes the line is on an ECI
https://github.com/johnson442/custom-zyxel-firmware/releases/download/V1.0/1312-B10A-17-jumbo-tel-x6-cmd.bin
Latest Zyxel release for the 1312, v17, with jumbo frames, multiple telnet sessions and the latest 39x6 adsl_phy.bin.
I have become lax at generating every permutation of the firmware, so I cant offer you a just x6 modem code version off hand, but if you want to test but have issues with the other features will be happy to make one later today.
-
Good to hear the Netgear performed well on your line too. I liked mine a lot performance-wise (GUI irritations aside), but it got poorly and had to go.
:)
-
https://github.com/johnson442/custom-zyxel-firmware/releases/download/V1.0/1312-B10A-17-jumbo-tel-x6-cmd.bin
Latest Zyxel release for the 1312, v17, with jumbo frames, multiple telnet sessions and the latest 39x6 adsl_phy.bin.
I have become lax at generating every permutation of the firmware, so I cant offer you a just x6 modem code version off hand, but if you want to test but have issues with the other features will be happy to make one later today.
I have just started running with this firmware and 39x shows. It is too soon to judge error rates.
The Sync rates are as with the "39v" but the measured download speeds are however reduced to about 38Mb/s c.f. the normal about 64Mb/s. SEE POSTS BELOW -THIS SPEED REDUCTION WAS NOTHING TO DO WITH THE TEST OF FIRMWARE I have left the MTU at 1492 and the unit is in modem router mode. Should I change the MTU to another value? I don't know much about MTU's!
Maybe a version with just multiple telnet and 39x6 would be more straightforward to test?
-
I have just started running with this firmware and 39x shows. It is too soon to judge error rates.
The Sync rates are as with the "39v" but the measured download speeds are however reduced to about 38Mb/s c.f. the normal about 64Mb/s. I have left the MTU at 1492 and the unit is in modem router mode. Should I change the MTU to another value? I don't know much about MTU's!
Maybe a version with just multiple telnet and 39x6 would be more straightforward to test?
Something is wrong there, building one with just the x6 adsl_phy now.
-
https://github.com/johnson442/custom-zyxel-firmware/releases/download/V1.0/1312-B10A-17-x6.bin
Just the x6 adsl_phy with nothing else, flashed to my testing 1312 (twice) with no problem.
If you are willing to flash again and test it would be really useful as this removes all other variables in the firmware, but be aware its quite possible this will be just as bad. But then we will know that the x6 on a 1312 is unsuitable for ECI cabs.
Give it a day if you are scared of DLM, but many thanks if you can spend the time to test.
-
Many thanks for the 39x only version, I have tried the 39x6 only but the issue persisted, I wondered if it was something else so I went back to the original 1.00(AAJZ.17)C0.bin and yes it is something else and not the 39x6.
Before today speed tests have been quite consistent and as you would expect from the sync. I will leave things and retest in few hours and then if things persist I will try another modem before blaming the line backhaul but that may be last test today in case the DLM notices. Hopefully I will move back to 39x tomorrow. If needed tomorrow I may try a factory reset and then a reload of the settings from a backup.
From past experience up to 7 resyncs without a gap seem OK on my line which is on the faster profile . I have not tried more though!
-
What ever the issue it was not there with the 8800nl and not there when I went back to the VMG1312-B10A. I had reset the VMG1312-B10A and used a config file from a few days ago. I did tinker with QOS yesterday but thought it back to default - maybe it wasn't. TheVMG1312-B10A is now on test with the 39x6 only. Assuming that runs OK for 24 hours I will report how it went and change to the 1312-B10A-17-jumbo-tel-x6-cmd.bin as the extra's in that would be very welcome if they don't impact normal use. I need to read the threads to see if there any merit in changing the MTU from 1492.
-
Something is wrong there, building one with just the x6 adsl_phy now.
@johnson - I've installed the 17jumbo-tel-stats-cmd and the webserver stats tab after 21 hours gives me no info, am I missing something or something is also wrong here ?
The only tabs where I'can see info are: SNRM / FEC / CRC
And the jumbo frames don't work from me as the max packet size without fragmentation is 1464 and not 1472 as expected... :'(
My ISP is Zen.
-
I have just started running with this firmware and 39x shows. It is too soon to judge error rates.
The Sync rates are as with the "39v" but the measured download speeds are however reduced to about 38Mb/s c.f. the normal about 64Mb/s. I have left the MTU at 1492 and the unit is in modem router mode. Should I change the MTU to another value? I don't know much about MTU's!
Maybe a version with just multiple telnet and 39x6 would be more straightforward to test?
That's worrying, my parents are on a eci cabinet, and the only modem I have found that plays well is the Netgear DM200.
Latest version is 1.0.0.61 and the dsl firmware included supports vectoring and g.inp
Luckily as Netgear is GPL compliant, you can download the sources and build it yourself: https://www.downloads.netgear.com/files/GPL/DM200-V1.0.0.61_gpl_src.tar.gz
I am curious if the newest dsl firmware could be added to the official image, but I have not had a chance to play
-
The "39x6" firmware has been run for one day. It had slightly lower errors inspite of a slight increase in downstream speed c.f. 3 days with "39v". This is promising but one day is is not enough to be sure of the small changes involved and I have started on a longer comparison of a few days with each firmware repeated a few times. This is no trouble to do but will of of course take a few weeks.
-
@johnson - I've installed the 17jumbo-tel-stats-cmd and the webserver stats tab after 21 hours gives me no info, am I missing something or something is also wrong here ?
The only tabs where I'can see info are: SNRM / FEC / CRC
And the jumbo frames don't work from me as the max packet size without fragmentation is 1464 and not 1472 as expected... :'(
My ISP is Zen.
Could you click the save button on the stats server and upload the resulting zip? If the SNRM FEC and CRC tabs are updating it is correcting storing information over time, but it sounds like the parsing of instantaneous info i.e. current SNR graph, and the stats that populate the overview tab is not working properly, probably a simply a new line that I have not accounted for as its not present in my xdslctl info --stats output.
As for the jumbo frames issues, I see from another thread you are using the modem in bridge mode and have the router set to 1500, could I ask that you try setting the MTU to 1508 on the external router and try again?
Also I notice you are on Zen, but dont mention the back haul, the SS has Sky_VDSL in it... I'm a little confused, but just wanted to make sure what ever provider you are using is indeed PPPoE.
-
Could you click the save button on the stats server and upload the resulting zip? If the SNRM FEC and CRC tabs are updating it is correcting storing information over time, but it sounds like the parsing of instantaneous info i.e. current SNR graph, and the stats that populate the overview tab is not working properly, probably a simply a new line that I have not accounted for as its not present in my xdslctl info --stats output.
Sure, too big to attach it: https://mega.nz/#!vYQECSBD!_W1tko4U8Q-MQlsqp1J8-NCc_C5AJvS3VlW3GA2k4Oc
As for the jumbo frames issues, I see from another thread you are using the modem in bridge mode and have the router set to 1500, could I ask that you try setting the MTU to 1508 on the external router and try again?
Will try and give you feedback
Also I notice you are on Zen, but dont mention the back haul, the SS has Sky_VDSL in it... I'm a little confused, but just wanted to make sure what ever provider you are using is indeed PPPoE.
Oh simply because I moved to Zen from Sky and I did name the connection that way at that time
-
Sure, too big to attach it: https://mega.nz/#!vYQECSBD!_W1tko4U8Q-MQlsqp1J8-NCc_C5AJvS3VlW3GA2k4Oc
Will try and give you feedback
Oh simply because I moved to Zen from Sky and I did name the connection that way at that time
This release should fix the javascript to parse your stats correctly:
https://github.com/johnson442/custom-zyxel-firmware/releases/tag/v1.1
Tested on a real device to have correct features, but as always, flashing at your own risk.