Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 [2] 3 4

Author Topic: Few questions about a new line with IDNET - FTTC  (Read 1532 times)

meritez

  • Reg Member
  • ***
  • Posts: 402
Re: Few questions about a new line with IDNET - FTTC
« Reply #15 on: April 10, 2021, 11:48:44 AM »

OK so I bought a Tp-link Archer VR400 V3.

Current plans are install the new router tomorrow, hope and pray for an improvement and if it doesn't work out, cancel and send everything back after a few days.

According to a couple of suppliers, billion have supply issues at present.

Zyxel vmgxxxxb work well as modems, I'm using a vmg1312b10a at present.
Logged

tubaman

  • Addicted Kitizen
  • *****
  • Posts: 7190
Re: Few questions about a new line with IDNET - FTTC
« Reply #16 on: April 10, 2021, 12:01:32 PM »

...
As far as I can see, DLM shouldn't kick into high gear unless there are multiple dropouts within a very short amount of time.

That is correct. It is generally best to leave over 30mins following a disconnection before reconnecting, I think to ensure that there is at least one 15min stats collection period between the events. I must admit however that I have broken that rule on many occasions without issue.
Your line is still in its starting state as far as DLM is concerned, ie G.INP is off and interleaving is on for your Huawei based line, so I'd still be respectful and do your best not to upset it.
 :)
Logged
BT FTTC 80/20 Huawei Cab - Zyxel VMG8924-B10A

mattd

  • Just arrived
  • *
  • Posts: 7
Re: Few questions about a new line with IDNET - FTTC
« Reply #17 on: April 10, 2021, 02:00:36 PM »

So I know the fact I'm with IDNET and the fact that I have a new SOGEA line is just incidental information, just putting it out there first up.
...
So we're at an impasse, I don't want to risk being charged but I don't think the line is nessasarily behaving properly. They say there's no problem.

Their say on the matter is "it appears that the specific copper pair that you're connected to is already reaching it's potential" - (paraphrased)

Hi, also on IDNET now, similar situation to yours.

I moved in to new house about a month ago, the previous owners were with BT and I had checked the sync myself on their active line prior to moving in, it was at 58Mbps.

My Internet is via with IDNET on SOGEA and the OR engineer confirmed it is using the same pairs and route as the previously active line. But I get a solid 48Mbps at 6dB so I'm 10 down on what this line should be syncing at.

Idnets view is to wait and hopefully it will go to a 3dB profile, so far it has not moved off 6dB, it has not resync'd for the last 10 days - it only resync'd because I needed to power down the router, before that no rescyc's and still holding steady at 48.

Im on a Huawei cab, my modem is a commtrend vr-3030 firmware C031-416KRL-C01_R15
Code: [Select]
xdslctl info --show   tats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 14451 Kbps, Downstream rate = 48104 Kbps
Bearer: 0, Upstream rate = 14638 Kbps, Downstream rate = 48327 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): 6.4 5.8
Attn(dB): 17.8 0.0
Pwr(dBm): 14.2 7.6

VDSL2 framing
Bearer 0
MSGc: -6 26
B: 235 237
M: 1 1
T: 0 64
R: 12 16
S: 0.1554 0.5172
L: 12766 3929
D: 8 1
I: 248 127
N: 248 254
Q: 8 0
V: 1 0
RxQueue: 39 0
TxQueue: 13 0
G.INP Framing: 18 0
G.INP lookback: 13 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 112822397
OHFErr: 0 15600
RS: 2452496384 2924173038
RSCorr: 219378 109336
RSUnCorr: 0 0
Bearer 1
OHF: 58103408 0
OHFErr: 0 0
RS: 464826770 0
RSCorr: 8 0
RSUnCorr: 0 0

Retransmit Counters
rtx_tx: 21959 0
rtx_c: 8927 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 981 0
minEFTR: 48312 0
errFreeBits: 687826696 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 836689092 0
Data Cells: 3840293405 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: 0 10046
SES: 0 0
UAS: 34 34
AS: 933429

Bearer 0
INP: 47.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 8.30
OR: 0.01 30.81
AgR: 48404.08 14668.71

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: 865/865 32386/32386

Total time = 10 days 19 hours 17 min 43 sec
FEC: 219378 109336
CRC: 0 15600
ES: 0 10046
SES: 0 0
UAS: 34 34
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Latest 15 minutes time = 2 min 43 sec
FEC: 0 34
CRC: 0 3
ES: 0 2
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 329 64
CRC: 0 13
ES: 0 8
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
HostInitRetr: N/A
FailedRetr: N/A
Latest 1 day time = 19 hours 17 min 43 sec
FEC: 20216 3876
CRC: 0 1146
ES: 0 728
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 22948 14761
CRC: 0 1595
ES: 0 1040
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Since Link time = 10 days 19 hours 17 min 9 sec
FEC: 219378 109336
CRC: 0 15600
ES: 0 10046
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
« Last Edit: April 12, 2021, 04:21:19 PM by mattd »
Logged

tubaman

  • Addicted Kitizen
  • *****
  • Posts: 7190
Re: Few questions about a new line with IDNET - FTTC
« Reply #18 on: April 10, 2021, 02:19:06 PM »

@mattd, G.INP is applied as you say and with ReTx Low (INPRein=0 on Bearer 0) which is good, but it's puzzling why it hasn't started stepping down the SNR. It'd certainly have expected it to given the very low errors you are seeing.  ???
Logged
BT FTTC 80/20 Huawei Cab - Zyxel VMG8924-B10A

mattd

  • Just arrived
  • *
  • Posts: 7
Re: Few questions about a new line with IDNET - FTTC
« Reply #19 on: April 10, 2021, 06:27:07 PM »

Yep! Really weird, Iím going to leave it be for another 5 days and perhaps then it itís still not lost sync or changed the profile idnet can reset it
Logged

meritez

  • Reg Member
  • ***
  • Posts: 402
Re: Few questions about a new line with IDNET - FTTC
« Reply #20 on: April 10, 2021, 07:14:43 PM »

Yep! Really weird, Iím going to leave it be for another 5 days and perhaps then it itís still not lost sync or changed the profile idnet can reset it

Welcome, was your comtrend from idnet?
Logged

mattd

  • Just arrived
  • *
  • Posts: 7
Re: Few questions about a new line with IDNET - FTTC
« Reply #21 on: April 10, 2021, 07:44:43 PM »

:-)

No, bought it off eBay. Was new :-)

If anyone would like the firmware btw, drop me a DM
Logged

cacoe

  • Member
  • **
  • Posts: 29
Re: Few questions about a new line with IDNET - FTTC
« Reply #22 on: April 11, 2021, 03:39:26 PM »

So the new router came (TP-Link VR400 v3)

The stats are extremely limited -
Line Status:
Connected
DSL Up Time:
0 days 0 hours 21 minutes

DSL Modulation Type:
VDSL2

Annex Type:
Annex auto

Upstream   Downstream
Current Rate (kbps)   12387   42338

Max Rate (kbps)   12413   54115

SNR Margin (dB)   6.2   5.2

Line Attenuation (dB)   3   16.1

Errors (pkts)   2   309


Stats are better than previously posted, however this had improved marginally prior to replacing the router.

If anyone has a method of accessing more connection stat data on this model, would be greatly appreciated. I've searched a bit but I've only found such info on much older models. Gotta say, this router's admin page is pretty weak.
Logged

cacoe

  • Member
  • **
  • Posts: 29
Re: Few questions about a new line with IDNET - FTTC
« Reply #23 on: April 11, 2021, 06:30:07 PM »

ok so the finally got telnet working and the full stats are -
Code: [Select]
enable=1
status=Up
dataPath=Fast
lineNumber=0
lineEncoding=
modulationType=VDSL2
interleaveDepth=0
X_TP_AnnexType=Annex auto
enable=1
X_TP_DisableAELEM=0
status=Up
linkEncapsulationRequested=
linkEncapsulationUsed=G.993.2_Annex_K_PTM
modulationType=VDSL2
lineEncoding=
allowedProfiles=8a,8b,8c,8d,12a,12b,17a,30a
currentProfile=
X_TP_VDSLProfiles_8a=1
X_TP_VDSLProfiles_8b=1
X_TP_VDSLProfiles_8c=1
X_TP_VDSLProfiles_8d=1
X_TP_VDSLProfiles_12a=1
X_TP_VDSLProfiles_12b=1
X_TP_VDSLProfiles_17a=1
X_TP_VDSLProfiles_30a=0
dataPath=Fast
interleaveDepth=0
lineNumber=0
upstreamCurrRate=12040
downstreamCurrRate=42334
upstreamMaxRate=12059
downstreamMaxRate=54439
upstreamNoiseMargin=63
downstreamNoiseMargin=52
upstreamAttenuation=31
downstreamAttenuation=159
upstreamPower=69
downstreamPower=119
usNegBandPlanDiscPresentation=0
dsNegBandPlanDiscPresentation=0
totalStart=14
showtimeStart=14
quarterHourStart=0
X_TP_LastUpMoment=84
X_TP_UpTime=1338
X_TP_Bitswap=On
X_TP_SRA=Off
X_TP_AdslModulationCfg=Multimode
X_TP_AnnexType=Annex auto
X_TP_SupportAdslMode=VDSL2:A,B;T1.413:A;G.dmt:A,B;ADSL2:auto,A,B,A/L;ADSL2+:auto,A,B,I,J,M,A/L,B/J,A/I/J/L/M;ADSL Auto Sync-up:auto,A/L,B/J,A/I/J/L/M;Auto Sync-up:auto,A/L,B/J,A/I/J/L/M;

No idea if anything here implies g.imp enabled or not - not that there's anything anyone can do unless DLM decides to enable it.

This seems to imply I'm connected via fastpath now, which seems to hold true, my pings have dropped about 9-10ms

I'm not sure I actually trust some of these stats, isn't G.993.2_Annex_K_PTM usually for countries outside the UK?
« Last Edit: April 11, 2021, 07:47:11 PM by cacoe »
Logged

meritez

  • Reg Member
  • ***
  • Posts: 402
Re: Few questions about a new line with IDNET - FTTC
« Reply #24 on: April 12, 2021, 12:07:01 AM »

To quote ejs: https://forum.kitz.co.uk/index.php?action=post;quote=353899;topic=20266.0;last_msg=353911

Quote
Every VDSL2 modem supports PTM.

The reference to "Annex K" is because PTM is described in Annex K of the ITU-T ADSL2 G.992.3 document. Annex K of the ITU-T VDSL2 G.993.2 document is actually just a placeholder saying it is "for further study".

Those are interesting stats

Logged

cacoe

  • Member
  • **
  • Posts: 29
Re: Few questions about a new line with IDNET - FTTC
« Reply #25 on: April 12, 2021, 10:39:16 AM »

What do you think? Misreporting or actually connected weird?

Speaking of stats, from the actual router page, you reckon this amount of errors in such a short amount of time should be cause for concern? (I actually at least trust the actual router stats vs what telnet reports) -

Quote
Line Status:
Connected
DSL Up Time:
0 days 15 hours 15 minutes
DSL Modulation Type:
VDSL2
Annex Type:
Annex A
Upstream   Downstream
Current Rate (kbps)   12107   42081
Max Rate (kbps)   12159   53447
SNR Margin (dB)   6.4   5.1
Line Attenuation (dB)   3.1   15.9
Errors (pkts)   35   91062

« Last Edit: April 12, 2021, 10:44:36 AM by cacoe »
Logged

tubaman

  • Addicted Kitizen
  • *****
  • Posts: 7190
Re: Few questions about a new line with IDNET - FTTC
« Reply #26 on: April 12, 2021, 11:11:18 AM »

...
Speaking of stats, from the actual router page, you reckon this amount of errors in such a short amount of time should be cause for concern? (I actually at least trust the actual router stats vs what telnet reports) -

It's unfortunately not clear what type of errors they are. If they are CRCs then it's bad but if FECs then it's perfectly fine.
 :-\
Logged
BT FTTC 80/20 Huawei Cab - Zyxel VMG8924-B10A

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 32682
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: Few questions about a new line with IDNET - FTTC
« Reply #27 on: April 12, 2021, 11:44:56 AM »

You may be able to get more detailed stats using StatPOSTer which works with most TPlink modems

https://forum.kitz.co.uk/index.php/topic,14377.msg269624.html#msg269624



---

I've not used a TPlink modem for a while and I may be dreaming, but I'm sure some people got DSLstats working with the TPlinks too.    ETA have a read through the thread linked above - its seems possible with the VR400 v3.

Disclaimer this is experimental and you do so at your own risk.   
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

cacoe

  • Member
  • **
  • Posts: 29
Re: Few questions about a new line with IDNET - FTTC
« Reply #28 on: April 12, 2021, 11:57:12 AM »

It's unfortunately not clear what type of errors they are. If they are CRCs then it's bad but if FECs then it's perfectly fine.
 :-\

I agree, this router's admin page is horrendous! (no offence to the person who suggested it, the only criteria when asking for a router was that it had a broadcom chipset)

You may be able to get more detailed stats using StatPOSTer which works with most TPlink modems

https://forum.kitz.co.uk/index.php/topic,14377.msg269624.html#msg269624



---

I've not used a TPlink modem for a while and I may be dreaming, but I'm sure some people got DSLstats working with the TPlinks too.    ETA have a read through the thread linked above - its seems possible with the VR400 v3.

Disclaimer this is experimental and you do so at your own risk.   

I've tried everything I can think to get this to work, cleared the username as blank (my router doesn't seem to require one to log into the admin panel or telnet)

Deffo entering the correct password, tried both models on the dropdown but no matter what, I just get -

Code: [Select]
2021.04.12 11:52:22 xDSL Stats:
java.io.IOException: Server returned HTTP response code: 500 for URL: http://192.168.1.1/cgi?1&5

I'd very much like to be able to use this, or DSLstats but it's the same situation with that, just doesn't want to connect no matter what.

I assume I've "hacked" the router correctly seeing as I can telnet at all Į\_(ツ)_/Į

DSLstats states that I've used the wrong username+pass


Update on that... it appears the fact that I had an active telnet session running already was stopping it from connecting...

Now instead of login errors, I get -
Code: [Select]
12 Apr 2021 12:04:09 Recording started
12 Apr 2021 12:04:24 Timeout while retrieving stats
12 Apr 2021 12:04:24 No stats received


Thinking about it, maybe it already had rudimentary telnet access and I in fact did not fully unlock it? Does this deffo look unlocked?



Failing everything else, I am still happy to return everything I've already bought if required. If anyone can still suggest a VDSL modem or router (That I can actually buy) with decent stat reporting and a broadcom chipset for the modem, I am still willing to move to yet another device  ;D


« Last Edit: April 12, 2021, 12:37:43 PM by cacoe »
Logged

mattd

  • Just arrived
  • *
  • Posts: 7
Re: Few questions about a new line with IDNET - FTTC
« Reply #29 on: April 12, 2021, 04:20:45 PM »

Well my idnet one is still holding it's 6dB profile and removes to budge, coming up to 13 days now without a re-sync.

Code: [Select]
> dsluptime
DSL Uptime: 12 days:23 hours:0 mins:27 secs

 > xdslctl info --stats
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 14638 Kbps, Downstream rate = 48161 Kbps
Bearer: 0, Upstream rate = 14638 Kbps, Downstream rate = 48327 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): 6.4 6.0
Attn(dB): 17.8 0.0
Pwr(dBm): 14.2 7.4

VDSL2 framing
Bearer 0
MSGc: -6 26
B: 235 237
M: 1 1
T: 0 64
R: 12 16
S: 0.1554 0.5172
L: 12766 3929
D: 8 1
I: 248 127
N: 248 254
Q: 8 0
V: 1 0
RxQueue: 39 0
TxQueue: 13 0
G.INP Framing: 18 0
G.INP lookback: 13 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 135331058
OHFErr: 0 18009
RS: 2931227936 69462158
RSCorr: 249499 117458
RSUnCorr: 0 0
Bearer 1
OHF: 69695501 0
OHFErr: 1 0
RS: 557563517 0
RSCorr: 8 0
RSUnCorr: 1 0

Retransmit Counters
rtx_tx: 25202 0
rtx_c: 10097 0
rtx_uc: 0 0

G.INP Counters
LEFTRS: 1122 0
minEFTR: 48312 0
errFreeBits: 825053876 0

Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 961383324 0
Data Cells: 2369506610 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: 0 11609
SES: 0 0
UAS: 34 34
AS: 1119654

Bearer 0
INP: 47.00 0.00
INPRein: 0.00 0.00
delay: 0 0
PER: 0.00 8.30
OR: 0.01 30.81
AgR: 48404.08 14668.71

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: 1026/1026 37953/37953

Total time = 12 days 23 hours 1 min 28 sec
FEC: 249499 117458
CRC: 0 18009
ES: 0 11609
SES: 0 0
UAS: 34 34
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Latest 15 minutes time = 1 min 28 sec
FEC: 26 28
CRC: 0 9
ES: 0 4
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Previous 15 minutes time = 15 min 0 sec
FEC: 25 85
CRC: 0 16
ES: 0 11
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: N/A
HostInitRetr: N/A
FailedRetr: N/A
Latest 1 day time = 23 hours 1 min 28 sec
FEC: 14878 3682
CRC: 0 1163
ES: 0 749
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Previous 1 day time = 24 hours 0 sec
FEC: 10206 3295
CRC: 0 974
ES: 0 645
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
Since Link time = 12 days 23 hours 53 sec
FEC: 249499 117458
CRC: 0 18009
ES: 0 11609
SES: 0 0
UAS: 0 0
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
HostInitRetr: 0
FailedRetr: 0
NTR: mipsCntAtNtr=0 ncoCntAtNtr=0
Logged
Pages: 1 [2] 3 4
 

anything