Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: mrbluepig on June 04, 2020, 06:30:28 PM
-
I got a XMG3927-B50A to replace my HG612 to try and get a bit more speed, however I can't seem to get it to connect properly in bridge mode. Can anyone see what I am doing wrong?
I have put the XMG3927-B50A into bridge mode and disabled the firewall, I then connected the RJ11 to it and the phone line, then a LAN cable into port 1 that connects to the WAN of my Asus router. Basically the same as how my HG612 is connected.
However my Asus says disconnected on the internet status, and gets a local WAN IP of 192.168.1.190 which isn't right.
I have put some image attachments of my config of the. I noticed the DSL doesn't show as being connected on interface status on the System Info page.
I'm using Sky FTTC and on my Asus router i have option 61 configured, which works fine with my HG612. Am I missing something obvious? Also do I need to delete ETHWAN?
I have gone back to using my HG612 for now.
-
Attached is What my Asus shows when I connect it.
-
Also the ip for my Zyxel is 192.168.1.1 my router is on 192.168.51.1, the router having a starting pool as 192.168.51.2 and end pool at 192.168.51.254.
Should I disable DHCP on my Zyxel and assign it a static IP of say 192.168.51.2 or something?
-
On the second picture where it says Broadband, can you try to delete the ETHWAN option ?
-
I know i have a different Zyxel router to yourself, the only difference i can see between my config and yours is the ETHWAN line in your broadband config. It may be worth removing that line and trying to connect again.
Andrew
-
No luck unfortunately, though it did change the message to "Your ISP's DHCP does not function properly". Gone back to my HG612 for, might look into returning XMG3927-B50A if I can't figure it out in the next couple of days.
Should the DSL show as grey with a - on the stats page? Maybe the DSL port is faulty but seems unlikely.
I'm running out of ideas, the last thing I can think of is to try turning off DHCP on the Zyxel.
-
Do you see any info in the WAN section of the Zyxel ?
-
Do you see any info in the WAN section of the Zyxel ?
Will have a look tomorrow as turning it on and off seems to disconnect my second line, not really sure why, but it is upsetting the other person using the second internet connection :lol:
I just checked on the Zyxel and DHCP is already disabled, I had to set a static ip on my PC to access the admin panel.
-
Also, when you configure the Zyxel in bridge mode, any of the 4 LAN ports can carry the WAN traffic, so it doesn't matter which LAN port you connect to the WAN port of the router...
But, why don't you try to create an interface group so that you'll have only one LAN port carring the Internet traffic, i.e. LAN1, have a read here: https://kitz.co.uk/routers/zyxel_VMG8324-B10A_bridge.htm
P.S.
I never play around with modem/routers when wife/kids are online, it can be life-threatening... :angel:
-
Thanks, I'll follow that guide exactly (and additionally delete ETHWAN) I'll report back tomorrow on the status. I have done a factory reset also to start a fresh, I think the time region was configured wrong also as I didn't go through the quick setup guide before, maybe it'll work tomorrow :fingers:
-
I set the Zxyel to 192.168.1.1
The Asus router to 192.168.1.2, the start pool as 192.168.1.3 and end pool as 192.168.1.254.
The Asus router shows the wan IP as 192.168.2.190, it is like it is being served a DHCP address by the Zyxel?
I set up the interface group on port 1 and a connected a second cable so I could still access the stats.
Still not having any luck.
-
wan status and asus screenshot
-
Puzzling. ???
I do not know either device but, from what you have described (and the images shown), I would expect the setup to work correctly.
-
That is puzzling. I do not know either device but, from what you have described and the images shown, I would expect the setup to work correctly.
Silly question time (from me): When performing your tests, have you actually connected the ZyXEL device to the incoming line? Or are you concerned about provoking DLM action and so are testing without that link in place?
I have been connecting the Zxyel directly to the line, probably going to get hit hard by DLM! :police: I was going to tell Sky I had multiple powercuts if I ever got it working and hope for a caution counter reset/ DLM reset.
One weird thing is that when I connect the Zxyel to the first line, it causes the second line to momentary drop, I'm not sure the drop on the second line happens when it is powered on or connecting, I haven't tested when it happens extensively. I didn't realise they would have any cross over, so I am unsure why that is happening, but the master socket for the second line is directly below the first line.
Weirdly the Zxyel makes a moderately loud double click sound each time it is booting up, never heard anything quite like it from a modem or router. It is enough to get the dogs attention. :lol:
I think I might go ahead and return it, get back to placing bids VMG1312-B10A / ZyXEL VMG8924-B10A. I couldn't find much information on the Zyxel XMG3927-B50A so took a bit of a risk ordering it in the first place, but then again it could be me doing something incorrectly.
-
You can manually set the Asus WAN IP to 192.168.1.1 in the WAN subsection. Where it says get WAN IP automatically select no set the IP address to 192.168.1.250, 255.255.255.0 and Gateway to 192.168.1.1. You will also have to set DNS manually too.
-
Hmm . . . I now see that the XMG3927-B series are G.Fast capable devices, which also provide VDSL2/ADSL2+/ADSL2/ADSL fall-back.
Suggestion. Isolate the ZyXEL from the incoming line and from the router. Power it on and let it stabilise. With your favourite straightened-out paper-clip operate the recessed reset button and hold it for, say, 30 seconds. Release the reset button and allow the device to re-initialise. Now perform a power-cycle. Make a direct connection to it from a computer and access the device's GUI. Ignore any "smart setup mode" or "configuration wizard" and step through each menu, turning off everything that is irrelevant to your proposed usage. Delete all the pre-defined "Broadband" interfaces and recreate the required VDSL2 line.
-
Hmm . . . I now see that the XMG3927-B series are G.Fast capable devices, which also provide VDSL2/ADSL2+/ADSL2/ADSL fall-back.
Suggestion. Isolate the ZyXEL from the incoming line and from the router. Power it on and let it stabilise. With your favourite straightened-out paper-clip operate the recessed reset button and hold it for, say, 30 seconds. Release the reset button and allow the device to re-initialise. Now perform a power-cycle. Make a direct connection to it from a computer and access the device's GUI. Ignore any "smart setup mode" or "configuration wizard" and step through each menu, turning off everything that is irrelevant to your proposed usage. Delete all the pre-defined "Broadband" interfaces and recreate the required VDSL2 line.
It worked! I deleted them all, disabled g.fast in advanced settings and then readded the VDSL2 bridge.
Thanks so much, I have probably been hit by DLM quite hard as I changed modem at least 10 times today :angel:
-
How do the stats look? I'm getting around 23.7 on speedtest.net, I was getting around 24.8 before I restarted / switched the modems over and over.
============================================================================
VDSL Training Status: Showtime
Mode: VDSL2 Annex B
VDSL Profile: Profile 17a
Traffic Type: PTM Mode
Link Uptime: 0 day: 0 hour: 21 minutes
============================================================================
VDSL Port Details Upstream Downstream
Line Rate: 5.257 Mbps 26.335 Mbps
Actual Net Data Rate: 5.229 Mbps 26.336 Mbps
Trellis Coding: ON ON
SNR Margin: 6.0 dB 3.1 dB
Actual Delay: 0 ms 0 ms
Transmit Power: 7.1 dBm 10.8 dBm
Receive Power: -9.0 dBm -22.9 dBm
Actual INP: 0.0 symbols 51.0 symbols
Total Attenuation: 16.1 dB 33.7 dB
Attainable Net Data Rate: 5.229 Mbps 26.223 Mbps
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 9.7 54.9 N/A N/A 23.1 67.5 102.3
Signal Attenuation(dB): 9.7 54.1 N/A N/A 31.9 67.0 N/A
SNR Margin(dB): 6.1 6.0 N/A N/A 3.1 3.0 N/A
Transmit Power(dBm): 0.6 6.0 N/A N/A 8.9 6.2 N/A
============================================================================
VDSL Counters
Downstream Upstream
Since Link time = 21 min 59 sec
FEC: 146557 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Latest 15 minutes time = 7 min 30 sec
FEC: 41373 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 105184 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 30 30
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
HostInitRetr: N/A
FastRetr: N/A
FailedRetr: N/A
FailedFastRetr: N/A
Latest 1 day time = 22 min 30 sec
FEC: 146557 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 30 30
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 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
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Total time = 22 min 30 sec
FEC: 146557 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 30 30
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
============================================================================
-
Out of curiosity, where did you buy the modem?
-
Out of curiosity, where did you buy the modem?
LambdaTek
Will have to see if it was worth the cost, if my line ever recovers from all the activity yesterday :'(. At least I can use it for G.fast in the future which could be handy if I ever move.
-
Stats after 9 hours, I will try to post them again in a week or so to see if they improve. Downstream speed has gone down, but upload speed has gone up.
Very bad bufferbloat on the upstream, but I think they may be because the HG612 has QOS on the upstream and now I don't have that anymore.
http://www.dslreports.com/speedtest/64378543
============================================================================
VDSL Training Status: Showtime
Mode: VDSL2 Annex B
VDSL Profile: Profile 17a
Traffic Type: PTM Mode
Link Uptime: 0 day: 9 hours: 37 minutes
============================================================================
VDSL Port Details Upstream Downstream
Line Rate: 5.929 Mbps 24.674 Mbps
Actual Net Data Rate: 5.930 Mbps 24.675 Mbps
Trellis Coding: ON ON
SNR Margin: 5.9 dB 4.1 dB
Actual Delay: 0 ms 0 ms
Transmit Power: 7.1 dBm 10.5 dBm
Receive Power: -9.4 dBm -23.0 dBm
Actual INP: 42.0 symbols 55.0 symbols
Total Attenuation: 16.5 dB 33.6 dB
Attainable Net Data Rate: 5.926 Mbps 24.752 Mbps
============================================================================
VDSL Band Status U0 U1 U2 U3 D1 D2 D3
Line Attenuation(dB): 9.7 54.9 N/A N/A 23.0 67.5 102.3
Signal Attenuation(dB): 9.7 53.9 N/A N/A 31.8 67.4 N/A
SNR Margin(dB): 5.9 5.9 N/A N/A 4.1 4.1 N/A
Transmit Power(dBm): 0.2 6.1 N/A N/A 8.7 6.0 N/A
============================================================================
VDSL Counters
Downstream Upstream
Since Link time = 37 min 19 sec
FEC: 1021684 124
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Latest 15 minutes time = 6 min 36 sec
FEC: 1533 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 11467 5
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
HostInitRetr: N/A
FastRetr: N/A
FailedRetr: N/A
FailedFastRetr: N/A
Latest 1 day time = 10 hours 36 min 36 sec
FEC: 1351886 128
CRC: 0 0
ES: 10 0
SES: 10 0
UAS: 69 59
LOS: 1 0
LOF: 6 0
LOM: 0 0
Retr: 1
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 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
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Total time = 10 hours 36 min 36 sec
FEC: 1351886 128
CRC: 0 0
ES: 10 0
SES: 10 0
UAS: 69 59
LOS: 1 0
LOF: 6 0
LOM: 0 0
Retr: 1
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
============================================================================
-
You've clearly had a resync, which has raised the SNR on the DS from 3dB to 4dB and applied G.INP to the US.
I'd leave it alone for a while now and hopefully it'll drop your DS SNR back to 3dB. If my line is anything to go by the G.INP on the US side won't last very long.
:)
-
You've clearly had a resync, which has raised the SNR on the DS from 3dB to 4dB and applied G.INP to the US.
I'd leave it alone for a while now and hopefully it'll drop your DS SNR back to 3dB. If my line is anything to go by the G.INP on the US side won't last very long.
:)
Sounds good, I won’t touch it anymore and hopefully it gets back to what it was or better. ;D I’ll try and remember to post some stats in 1/2 weeks for anyone interested.
-
I’ll try and remember to post some stats in 1/2 weeks for anyone interested.
Thank you, they will be interesting to see.
-
As for the bufferbloat, I would agree, its the QoS. I thought it was quite clever of Openreach to enable that, so that even people with p00 routers will partly be mitigated by never maxing the line.
I think we all turned it off, as we tend to use fancy routers with QoS anyway.
-
Question: can you get a different status report, a detailed one that shows framing parameters for the connection eg. B, S, L ?
[Moderator edited to split off the queries that followed and put them into a new topic (https://forum.kitz.co.uk/index.php?topic=24814).]
-
Here you go Weaver, stats with framing, how does it look? :)
ZySH> xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 5930 Kbps, Downstream rate = 24477 Kbps
Bearer: 0, Upstream rate = 5930 Kbps, Downstream rate = 24675 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.9 6.1
Attn(dB): 25.8 0.0
Pwr(dBm): 10.5 7.1
VDSL2 framing
Bearer 0
MSGc: -6 -6
B: 227 179
M: 1 1
T: 0 0
R: 12 10
S: 0.2939 0.9608
L: 6533 1582
D: 4 4
I: 240 190
N: 240 190
Q: 4 4
V: 0 3
RxQueue: 60 12
TxQueue: 12 4
G.INP Framing: 18 18
G.INP lookback: 12 4
RRC bits: 24 24
Bearer 1
MSGc: 90 58
B: 0 0
M: 2 2
T: 2 2
R: 16 16
S: 10.6667 16.0000
L: 24 16
D: 1 1
I: 32 32
N: 32 32
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 0
OHFErr: 0 0
RS: 1708158344 524501036
RSCorr: 5336787 2856
RSUnCorr: 0 0
Bearer 1
OHF: 7844046 7874445
OHFErr: 26 0
RS: 47063907 31497780
RSCorr: 287941 23
RSUnCorr: 30 0
Retransmit Counters
rtx_tx: 1936711 1643
rtx_c: 1931064 56
rtx_uc: 0 0
G.INP Counters
LEFTRS: 16 3
minEFTR: 24191 5931
errFreeBits: 48554522 11339369
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 1656519501 0
Data Cells: 325658185 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: 10 0
SES: 10 0
UAS: 69 59
AS: 125993
Bearer 0
INP: 55.00 42.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 0.00
OR: 0.01 0.01
AgR: 24728.80 5971.62
Bearer 1
INP: 2.50 4.00
INPRein: 2.50 4.00
delay: 0 0
PER: 16.06 16.06
OR: 47.81 31.87
AgR: 47.81 31.87
Bitswap: 19414/19917 2495/2495
Total time = 1 days 11 hours 59 min 8 sec
FEC: 5666989 2860
CRC: 0 0
ES: 10 0
SES: 10 0
UAS: 69 59
LOS: 1 0
LOF: 6 0
LOM: 0 0
Retr: 1
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Latest 15 minutes time = 14 min 8 sec
FEC: 106489 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 95130 4
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
HostInitRetr: N/A
FastRetr: N/A
FailedRetr: N/A
FailedFastRetr: N/A
Latest 1 day time = 11 hours 59 min 8 sec
FEC: 2102915 102
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 3564074 2758
CRC: 0 0
ES: 10 0
SES: 10 0
UAS: 69 59
LOS: 1 0
LOF: 6 0
LOM: 0 0
Retr: 1
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Since Link time = 1 days 10 hours 59 min 51 sec
FEC: 5336787 2856
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
ZySH>
-
Looks like a long line for-FTTC which is pretty clean and no problems. Able to run at 3dB downstream and with G.INP. I don’t think that you have been DLM’ed due to fiddling about with modems, and so it isn’t going to get faster later on.
-
Looks like g.inp has turned off on the upstream @tubaman so you were correct about it going quickly. Upstream speed was quicker with g.inp applied, is that normal?
ZySH> xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 5332 Kbps, Downstream rate = 24955 Kbps
Bearer: 0, Upstream rate = 5332 Kbps, Downstream rate = 25086 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.9 5.6
Attn(dB): 25.8 0.0
Pwr(dBm): 10.6 7.0
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 227 159
M: 1 1
T: 0 38
R: 12 14
S: 0.2891 0.9515
L: 6642 1463
D: 4 1
I: 240 87
N: 240 174
Q: 4 0
V: 0 0
RxQueue: 60 0
TxQueue: 12 0
G.INP Framing: 18 0
G.INP lookback: 12 0
RRC bits: 0 24
Bearer 1
MSGc: 90 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 10.6667 0.0000
L: 24 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 21260471
OHFErr: 4 54
RS: 2647785488 807553435
RSCorr: 7298085 1783
RSUnCorr: 0 0
Bearer 1
OHF: 11959346 0
OHFErr: 1 0
RS: 71755705 0
RSCorr: 14171 0
RSUnCorr: 3 0
Retransmit Counters
rtx_tx: 2557967 0
rtx_c: 2549890 0
rtx_uc: 14 0
G.INP Counters
LEFTRS: 16 0
minEFTR: 25079 0
errFreeBits: 146845871 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 641551053 0
Data Cells: 825989520 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: 148 65
SES: 72 0
UAS: 197 146
AS: 192092
Bearer 0
INP: 54.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 9.07
OR: 0.01 28.21
AgR: 25141.39 5360.21
Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01
Bitswap: 28167/28971 1742/1742
Total time = 4 days 12 hours 7 min 27 sec
FEC: 20565224 6140
CRC: 412 96
ES: 148 65
SES: 72 0
UAS: 197 146
LOS: 4 0
LOF: 22 0
LOM: 0 0
Retr: 4
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Latest 15 minutes time = 7 min 27 sec
FEC: 14676 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 44757 1
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
HostInitRetr: N/A
FastRetr: N/A
FailedRetr: N/A
FailedFastRetr: N/A
Latest 1 day time = 12 hours 7 min 27 sec
FEC: 1792735 891
CRC: 2 7
ES: 1 7
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 3616478 73
CRC: 2 25
ES: 4 25
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Since Link time = 2 days 5 hours 21 min 31 sec
FEC: 7298085 1783
CRC: 4 54
ES: 5 54
SES: 2 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
-
... Upstream speed was quicker with g.inp applied, is that normal?
If my line is 'normal' then unfortunately yes.
I've had G.INP on the US a few times, usually after I've been hit with a large number of errors, and it has never stuck for more than a few days.
:)
-
Another day and more stats.
Unfortunately we had a cut out so the modem was rebooted, seems that the downstream and upstream is above the max? Getting similar speeds to that of my HG612 now, maybe even slightly above.
Having some electrical work done on Friday so it is likely it will need rebooting, but it'll be off for over an hour so hopefully DLM ignores that reboot.
ZySH> xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 5399 Kbps, Downstream rate = 24477 Kbps
Bearer: 0, Upstream rate = 5730 Kbps, Downstream rate = 27062 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): 2.2 4.4
Attn(dB): 28.2 0.0
Pwr(dBm): 10.6 7.1
VDSL2 framing
Bearer 0
MSGc: -6 26
B: 227 175
M: 1 1
T: 0 38
R: 12 14
S: 0.2680 0.9744
L: 7165 1560
D: 4 1
I: 240 95
N: 240 190
Q: 4 0
V: 0 0
RxQueue: 65 0
TxQueue: 13 0
G.INP Framing: 18 0
G.INP lookback: 13 0
RRC bits: 0 24
Bearer 1
MSGc: 90 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 10.6667 0.0000
L: 24 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 7233389
OHFErr: 6 23
RS: 995316080 274776828
RSCorr: 15655836 63
RSUnCorr: 0 0
Bearer 1
OHF: 4167470 0
OHFErr: 42 0
RS: 25004452 0
RSCorr: 13952 0
RSUnCorr: 42 0
Retransmit Counters
rtx_tx: 1162063 0
rtx_c: 1154144 0
rtx_uc: 51 0
G.INP Counters
LEFTRS: 25 0
minEFTR: 27067 0
errFreeBits: 27473619 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 3467385247 0
Data Cells: 144401518 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 24
SES: 0 0
UAS: 259 259
AS: 66939
Bearer 0
INP: 54.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 9.29
OR: 0.01 27.54
AgR: 27121.05 5757.71
Bearer 1
INP: 2.50 0.00
INPRein: 2.50 0.00
delay: 0 0
PER: 16.06 0.01
OR: 47.81 0.01
AgR: 47.81 0.01
Bitswap: 12540/12890 670/670
Total time = 18 hours 39 min 58 sec
FEC: 15655836 63
CRC: 6 23
ES: 3 24
SES: 0 0
UAS: 259 259
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Latest 15 minutes time = 9 min 58 sec
FEC: 145876 1
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 170240 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
HostInitRetr: N/A
FastRetr: N/A
FailedRetr: N/A
FailedFastRetr: N/A
Latest 1 day time = 18 hours 39 min 58 sec
FEC: 15655836 63
CRC: 6 23
ES: 3 24
SES: 0 0
UAS: 259 259
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 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
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
Since Link time = 18 hours 35 min 37 sec
FEC: 15655836 63
CRC: 6 23
ES: 3 24
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FastRetr: 0
FailedRetr: 0
FailedFastRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0