Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: tubaman on February 04, 2018, 04:24:37 PM
-
I've just picked up one of these from my favourite auction site and my initial impressions are pretty favourable.
It's only been running since yesterday, but so far:-
The good:
It's Broadcom based and supports G.INP. :thumbs: Looks like it's a 63168. (thanks ejs for reminding my how to use 'cpuinfo' :-[)
Telnet was easy to open up so I can get line stats with xdslctl.
Line stats so far look decent on my circa 800m line. I'd say errors are looking a bit better than my Zyxel 8924.
Wireless performance seems pretty decent.
The not so good:
Some of the front panel LEDs are rather bright, but can be turned off in the GUI.
The GUI is the usual Netgear affair which isn't my favourite but works well enough.
Only very limited stats available in the GUI.
The darned right annoying:
Lots of what should be simple config changes trigger a full reboot to apply (eg adding a static DHCP assignment, or enabling IGMP Proxy). :rant:
-
/proc/cpuinfo cannot be run because it is not an executable file. What you type in to display its contents is
cat /proc/cpuinfo
-
thanks ejs, I was clearly have a bear of little brain moment ::)
Original post now modified.
:)
-
Here's my line stats:
BusyBox v1.17.2 (2018-01-29 16:38:20 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 7472 Kbps, Downstream rate = 49034 Kbps
Bearer: 0, Upstream rate = 7472 Kbps, Downstream rate = 48092 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 3.3 6.1
Attn(dB): 26.7 0.0
Pwr(dBm): 11.9 6.5
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 227 223
M: 1 1
T: 0 41
R: 10 0
S: 0.0000 0.9522
L: 12627 1882
D: 4 1
I: 238 112
N: 238 224
Q: 4 0
V: 0 0
RxQueue: 116 0
TxQueue: 29 0
G.INP Framing: 18 0
G.INP lookback: 29 0
RRC bits: 0 24
Bearer 1
MSGc: 122 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 8.0000 0.0000
L: 32 0
D: 1 0
I: 32 0
N: 32 0
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 1004107
OHFErr: 7 51
RS: 702220240 4241283
RSCorr: 4758771 0
RSUnCorr: 0 0
Bearer 1
OHF: 1654536 0
OHFErr: 0 0
RS: 13235797 0
RSCorr: 52 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 201391516 0
rtx_c: 86479 0
rtx_uc: 76 0
G.INP Counters
LEFTRS: 79 0
minEFTR: 48088 0
errFreeBits: 19470179 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2456529331 0
Data Cells: 75381880 0
Drop Cells: 0
Bit Errors: 0 0
Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0
ES: 3 47
SES: 0 0
UAS: 30 30
AS: 26577
Bearer 0
INP: 51.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 9.79
OR: 0.01 26.12
AgR: 48197.54 7498.70
Bearer 1
INP: 2.00 0.00
INPRein: 2.00 0.00
delay: 0 0
PER: 16.06 0.01
OR: 63.75 0.01
AgR: 63.75 0.01
Bitswap: 12799/12799 227/227
Total time = 7 hours 23 min 27 sec
FEC: 4758771 0
CRC: 7 51
ES: 3 47
SES: 0 0
UAS: 30 30
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
Latest 15 minutes time = 8 min 27 sec
FEC: 153363 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 237097 0
CRC: 0 1
ES: 0 1
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
Latest 1 day time = 7 hours 23 min 27 sec
FEC: 4758771 0
CRC: 7 51
ES: 3 47
SES: 0 0
UAS: 30 30
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
Previous 1 day time = 0 sec
FEC: 0 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
Since Link time = 7 hours 22 min 55 sec
FEC: 4758771 0
CRC: 7 51
ES: 3 47
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
#
And CPU info:
# cat /proc/cpuinfo
system type : 963168MBV17A302
processor : 0
cpu model : Broadcom BMIPS4350 V8.0
BogoMIPS : 397.31
wait instruction : yes
microsecond timers : yes
tlb_entries : 32
extra interrupt vector : no
hardware watchpoint : no
ASEs implemented :
shadow register sets : 1
kscratch registers : 0
core : 0
VCED exceptions : not available
VCEI exceptions : not available
processor : 1
cpu model : Broadcom BMIPS4350 V8.0
BogoMIPS : 403.45
wait instruction : yes
microsecond timers : yes
tlb_entries : 32
extra interrupt vector : no
hardware watchpoint : no
ASEs implemented :
shadow register sets : 1
kscratch registers : 0
core : 0
VCED exceptions : not available
VCEI exceptions : not available
# :)
-
A month on this is still performing very nicely.
Had some re-syncs but that's not unusual for this line.
For £17.49 (delivered) I think I did ok.
It's a keeper ;D
BusyBox v1.17.2 (2018-01-29 16:38:20 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
# xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 7401 Kbps, Downstream rate = 50623 Kbps
Bearer: 0, Upstream rate = 7401 Kbps, Downstream rate = 48164 Kbps
Bearer: 1, Upstream rate = 0 Kbps, Downstream rate = 0 Kbps
Link Power State: L0
Mode: VDSL2 Annex B
VDSL2 Profile: Profile 17a
TPS-TC: PTM Mode(0x0)
Trellis: U:ON /D:ON
Line Status: No Defect
Training Status: Showtime
Down Up
SNR (dB): 3.8 6.4
Attn(dB): 26.7 0.0
Pwr(dBm): 11.9 6.5
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 227 223
M: 1 1
T: 0 41
R: 10 0
S: 0.0000 0.9614
L: 12646 1864
D: 4 1
I: 238 112
N: 238 224
Q: 4 0
V: 0 0
RxQueue: 116 0
TxQueue: 29 0
G.INP Framing: 18 0
G.INP lookback: 29 0
RRC bits: 0 24
Bearer 1
MSGc: 122 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 8.0000 0.0000
L: 32 0
D: 1 0
I: 32 0
N: 32 0
Q: 0 0
V: 0 0
RxQueue: 0 0
TxQueue: 0 0
G.INP Framing: 0 0
G.INP lookback: 0 0
RRC bits: 0 0
Counters
Bearer 0
OHF: 0 1040004
OHFErr: 3321 1136
RS: 2028647232 1819789
RSCorr: 296955861 0
RSUnCorr: 0 0
Bearer 1
OHF: 65396544 0
OHFErr: 1 0
RS: 523171859 0
RSCorr: 4432 0
RSUnCorr: 1 0
Retransmit Counters
rtx_tx: 216941679 0
rtx_c: 13375434 0
rtx_uc: 237063 0
G.INP Counters
LEFTRS: 15551 0
minEFTR: 48153 0
errFreeBits: 3770890217 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 2695648305 0
Data Cells: 431238993 0
Drop Cells: 0
Bit Errors: 0 0
Bearer 1
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 0 0
Data Cells: 0 0
Drop Cells: 0
Bit Errors: 0 0
ES: 772 2526
SES: 196 0
UAS: 180 116
AS: 1050434
Bearer 0
INP: 51.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 9.89
OR: 0.01 25.87
AgR: 48270.06 7426.98
Bearer 1
INP: 2.00 0.00
INPRein: 2.00 0.00
delay: 0 0
PER: 16.06 0.01
OR: 63.75 0.01
AgR: 63.75 0.01
Bitswap: 649167/649169 6648/6668
Total time = 27 days 2 hours 53 min 26 sec
FEC: 668070372 0
CRC: 9127 2658
ES: 772 2526
SES: 196 0
UAS: 180 116
LOS: 3 0
LOF: 20 0
LOM: 0 0
Retr: 3
Latest 15 minutes time = 8 min 26 sec
FEC: 89199 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 86235 0
CRC: 0 3
ES: 0 3
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
Latest 1 day time = 2 hours 53 min 26 sec
FEC: 1404880 0
CRC: 0 6
ES: 0 6
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 21411632 0
CRC: 92 68
ES: 17 68
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
Since Link time = 12 days 3 hours 47 min 13 sec
FEC: 296955861 0
CRC: 3321 1136
ES: 397 1090
SES: 74 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
#
-
Can you piont me at the instructions for enabling telnet pleae?
Stuart
-
Dont worry I've sorted it...
Stuart
-
I too have no obtained one of these routers from my fave auction site.
I concur with tubaman about the annoying frequency of reboots when changing settings which in my view should not need a reboot and on most other routers do not do this, for example adding a fixed ip for a device on the lan!
It was a tad annoying getting the wan settings correct to get a connection, DSL was up OK but getting the net connection was just a little tricky as it has a habit of changing settings you have not messed with when saving.
Its only been up an hour or so and until I have 24 hours or so of data I wont know if it is better or worse than the VMG3925 I was using.
Stuart
Just to add the Shields Up reports all service ports as stealth, and the router does not respond to UPNP on the wan port either.
-
Hi Stuart,
I'll be interested to know how you get on with this.
With respect to the WAN setting I found it ok to configure but when you then go back to check the settings some of them seem to be random rubbish (eg ISP 'Adam'!). I assume this is a firmware bug as it actually works fine.
Mine is still working well and I have no plans to change it at present (unless another bargain comes along on Ebay :-[).
-
I found mine was not on the latest firmware so updated it. So far it has been OK, slightly better SNRM than the ZyXEL but no change in speed as I'm capped. Too early to say what the error rates are like.
Stuart
-
Been running now about 24 hours. Confirmed first impression that the SNRM is better than ZyXEL, been running around a reasonably stable 6.4 down and much less jitter than ZyXEL which was all over the shop varying from 6 down to 4.5 or so frequently. Noise in general is less as a result shows lower FEC rate and 2 ES down in 24 hours is not bad. I did make some changes to the layout of the LAN and power connections in that I now have a switch on LAN as well as I needed more than 4 wired connection. Power changes were to add surge protector plug on 4 way extension which now has router PSU in it. I now also put back a powerline on the LAN to make Wi-Fi better as it is very problematic in this house, as yet no increase in noise of error rate apparent from that. Obviously need to see how it fairs in week time as there has always been more noise around then.
Stuart
-
Looks like we might just have found a modem that performs better than a Zyxel - on two lines at least. :o
It's a shame the GUI is not so comprehensive, and the issue with reboots after simple config changes would drive you mad if you were making regular tweaks (which I don't).
Now mine is set up and running I'm very pleased with the performance.
Only time will tell if it's going to be reliable.
:)
-
One thing I have found is that the debug.htm page has been removed from the latest firmware however since I have not done a reset to factory settings it has not been disabled. The cfg file which is saved by the router cannot be edited as it stands but I am looking into that. There seems to be a program which can be run to enable telnet but as yet I have not had to try it. Over the reboot issue I dont normally need to change much so if I find anything for now I'll make a list and when I need to power cycle it for any reason I will make the changes during the 30 minutes I have it off for.
Stuart
-
... There seems to be a program which can be run to enable telnet ...
Stuart
I used the info/program from https://wiki.openwrt.org/toh/netgear/telnet.console (https://wiki.openwrt.org/toh/netgear/telnet.console) to unlock telnet on my one. Worked a treat.
I do seem to have lost the debug.htm page as I think (I've slept since then ::)) I did factory reset it after the firmware upgrade.
-
Yes I have a verion of that program which I need to compile as I run Linux.
Stuart
-
So how have you got telnet working - is it through the debug.htm page?
:)
-
My original f/w allowed access to the debug.htm page but it survived the f/w upgrade so I didn't need to do anything. I will compile the s/w so I can use it in future.
Stuart
-
Just a quick further update on my D6220. Because of the issues I have in this house with wifi I decided to try my powerline kit to get better wifi downstairs. Now I know that there are many here who think these are something which should not exist but anyway I thought OK if it screws up my connection I can remove them. Well my experience with these are quite different from my earlier trial with the ZyXEL routers. My error rate has not significantly changed since I started using them, I am getting the same relatively low FEC rates as before which are significantly lower than the ZyXELs anyway without powerline and virtually zero CRCs and my ES rate is still in single figures per day for D/S, U/S is a little higher but still the same as it was prior to powerline.
Now I have done things slightly differently in that the powerline near the router is not in the same socket as the router and my router and other kit is connected via a surge protector which was not how it was before. Anyway I see no reason now to remove the powerline, of course YMMV. ;)
Stuart