Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Newfie]

I’ve kept the same setup on my router so I can see the difference, I’m not convinced this Vigor is acting correctly as I’m seeing high latency. iMessage should never cause an issue, never use to till swapping modem.
I’m still seeing 400 plus latency on upload, use to be sub 100ms.
I’ve a few routers with QoS but I’ve kept it basic to see what’s what.

[Newfie]

Watched it tonight, did some online gaming and just messed about.
I’ve got a few routers here as I Beta test for NG and Netduma so I thought I would swap out my RAX120 as it’s QoS is not great and best left off.
I used a Netduma router, limited my bandwidth and they have some testing tools in the software and setup QoS and yes as expected I lowered my latency down to very low figures resulting in A across the board with 15ms latency on up and download. Needless to say there are just slight yellow strips showing due to very low latency once I tuned in the settings.

[omegapoint]

Line stayed stable overnight so I've now dropped the MTU on mine down to 1492 and it doesn't seem to have made a difference so far. The MTU inside PPPoE link itself is still 1492 (I can send 1464 byte pings), they really need to document what the MTU on the modem's MPoA page refers to!

[underzone]

I hope that Draytek are watching this thread...

[onion]

mine is up and running (the uk version). I'm still in the dslam training period as changed providers, but had a weird thing overnight where the sync speed dropped from 71.5 to 67 and g.inp moved my SNR from 3db to 4db, Actual DS rate dropped from 69 to 63.5. may be because of the disconnect to change modems though so will keep you posted. I'm not having any MTU issues, but my entire connection is through a router configured VPN and the MTU is set smaller on all my LAN devices to accomodate this. I have MSS fixed at 1380. So far I'm not seeing any line errors where i was seeing them on the previous modem, but as they are stuck on 0 I have no idea if those figures are actually working! So far it seems good, and if the figures on error correction are correct, its far superior to the old modem (a netgear D7000 gen1 in modem mode - broadcom chip) but just hoping i get back down to 3db SNR to knock my speed back up.

on a side note - Has anyone else got a blank DSLAM CHIPSET VENDOR on the stats? mine just says DSLAM CHIPSET VENDOR : < ----- >

[omegapoint]

mine is up and running (the uk version). I'm still in the dslam training period as changed providers, but had a weird thing overnight where the sync speed dropped from 71.5 to 67 and g.inp moved my SNR from 3db to 4db, Actual DS rate dropped from 69 to 63.5. may be because of the disconnect to change modems though so will keep you posted. I'm not having any MTU issues, but my entire connection is through a router configured VPN and the MTU is set smaller on all my LAN devices to accomodate this. I have MSS fixed at 1380. So far I'm not seeing any line errors where i was seeing them on the previous modem, but as they are stuck on 0 I have no idea if those figures are actually working! So far it seems good, and if the figures on error correction are correct, its far superior to the old modem (a netgear D7000 gen1 in modem mode - broadcom chip) but just hoping i get back down to 3db SNR to knock my speed back up.

on a side note - Has anyone else got a blank DSLAM CHIPSET VENDOR on the stats? mine just says DSLAM CHIPSET VENDOR : < ----- >

My SNR target also changed from overnight 3 to 4 after I 1st connected the 166, though DS rate only dropped 2mb. Waiting to see if it will change back.

I also have the "< ----- >" DSLAM vendor, my 130 displayed it so I guess a firmware issue.

[j0hn]

If 2 of you have experienced DLM increasing the SNRM target that suggests the Draytek has a higher error rate than the previous modem both of you were using.

Give it another 2 days and your sync will probably drop further as it increases SNRM target again.

Being Drayteks Guinea Pig is not a good idea with OpenReach's DLM being live.

[onion]

My SNR target also changed from overnight 3 to 4 after I 1st connected the 166, though DS rate only dropped 2mb. Waiting to see if it will change back.

I also have the "< ----- >" DSLAM vendor, my 130 displayed it so I guess a firmware issue.

Interesting! I wonder why the SNR did the same thing to both of us? anyone got any ideas?

I'll leave it a few days until out of training period and if no change i'll probably run a "vdsl snr -10" command to see if i can force it down to 3db.

[meritez]

Is anyone willing to open the casing and give a picture of the printed circuit board?

[onion]

If 2 of you have experienced DLM increasing the SNRM target that suggests the Draytek has a higher error rate than the previous modem both of you were using.

Give it another 2 days and your sync will probably drop further as it increases SNRM target again.

Being Drayteks Guinea Pig is not a good idea with OpenReach's DLM being live.

Thank you!

Would / should i see these errors in the outputs? 24 hour(ish) uptime below. All of the other stats are pretty much identical to previous modem.

Code: [Select]

Type ? for command help
> vdsl status
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 63998000 bps US Actual Rate : 18948000 bps
DS Attainable Rate : 67630339 bps US Attainable Rate : 18944000 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 8 US Interleave Depth : 1
NE Current Attenuation : 17 dB Cur SNR Margin : 4 dB
DS actual PSD : 12. 9 dB US actual PSD : 7. 4 dB
NE CRC Count : 0 FE CRC Count : 0
NE ES Count : 0 FE ES Count : 0
Xdsl Reset Times : 0 Xdsl Link Times : 3
ITU Version[0] : 00000000 ITU Version[1] : 00000000
VDSL Firmware Version : 12-3-2-3-0-5 [with Vectoring support]
Power Management Mode : DSL_G997_PMS_L0
Test Mode : DISABLE
-------------------------------- ATU-C Info ---------------------------------
Far Current Attenuation : 0 dB Far SNR Margin : 5 dB
CO ITU Version[0] : 00b54442 CO ITU Version[1] : 4d4390c1
DSLAM CHIPSET VENDOR : < ----- >


[Guest_1]

mine is up and running (the uk version). I'm still in the dslam training period as changed providers, but had a weird thing overnight where the sync speed dropped from 71.5 to 67 and g.inp moved my SNR from 3db to 4db, Actual DS rate dropped from 69 to 63.5. may be because of the disconnect to change modems though so will keep you posted. I'm not having any MTU issues, but my entire connection is through a router configured VPN and the MTU is set smaller on all my LAN devices to accomodate this. I have MSS fixed at 1380. So far I'm not seeing any line errors where i was seeing them on the previous modem, but as they are stuck on 0 I have no idea if those figures are actually working! So far it seems good, and if the figures on error correction are correct, its far superior to the old modem (a netgear D7000 gen1 in modem mode - broadcom chip) but just hoping i get back down to 3db SNR to knock my speed back up.

on a side note - Has anyone else got a blank DSLAM CHIPSET VENDOR on the stats? mine just says DSLAM CHIPSET VENDOR : < ----- >

I have the same issue with the DSLAM chipset not being shown. When I first put my 166 up I lost 7MB having gained 3 MB the first day, this was however with the MTU set at default (I'm on a ECI cab) which was 1520. That's been changed to 1500 now and I'll see what happens. As far as being Draytecs guinea pig, the modem is on BT's approved list I believe, so we are at the mercy of Openreach/BT and Draytec

[onion]

I have the same issue with the DSLAM chipset not being shown. When I first put my 166 up I lost 7MB having gained 3 MB the first day, this was however with the MTU set at default (I'm on a ECI cab) which was 1520. That's been changed to 1500 now and I'll see what happens. As far as being Draytecs guinea pig, the modem is on BT's approved list I believe, so we are at the mercy of Openreach/BT and Draytec

Just changed mine to 1500 too. Lets see! Thanks for your help.

[omegapoint]

My line stats (normal & detailed). Only differences from Vigor 130 are the DS SNR & the DS Interleaving Depth which used to be 1 but now shows 8 even though I'm still Fast Path

Code: [Select]

> vdsl status

  ---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
   Running Mode            :      17A       State                : SHOWTIME
   DS Actual Rate          : 62394000 bps   US Actual Rate       : 15880000 bps
   DS Attainable Rate      : 66541716 bps   US Attainable Rate   : 15878000 bps
   DS Path Mode            :        Fast    US Path Mode         :        Fast
   DS Interleave Depth     :        8       US Interleave Depth  :        1
   NE Current Attenuation  :       16 dB    Cur SNR Margin       :        4  dB
   DS actual PSD           :    13. 8 dB    US actual PSD        :     7. 2  dB
   NE CRC Count            :        0       FE CRC Count         :        0
   NE ES Count             :        0       FE  ES Count         :        0
   Xdsl Reset Times        :        0       Xdsl Link  Times     :        1
   ITU Version[0]          : fe004452       ITU Version[1]       : 41590000
   VDSL Firmware Version   : 12-3-2-3-0-5   [with Vectoring support]
   Power Management Mode   : DSL_G997_PMS_L0
   Test Mode               : DISABLE
  -------------------------------- ATU-C Info ---------------------------------
   Far Current Attenuation :        0 dB    Far SNR Margin       :        5  dB
   CO ITU Version[0]       : 00b54442       CO ITU Version[1]    : 4d43a1a4
   DSLAM CHIPSET VENDOR    : < ----- >
> vdsl status more

  ---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
                      Near End                 Far End  Note
 Trellis      :      0                1
 Bitswap      :      0                0
 ReTxEnable       :      1                1
 VirtualNoise     :      0                0
 20BitSupport     :      0                0
 LatencyPath      :      0                0
 LOS          :      0                0
 LOF          :      0                0
 LPR          :      0                0
 LOM          :      0                0
 SosSuccess       :      0                0
 NCD          :      0                0
 LCD          :      0                0
 FECS          :      0                0 (seconds)
 ES           :      0                0 (seconds)
 SES          :      0                0 (seconds)
 LOSS          :      0                0 (seconds)
 UAS          :      0                0 (seconds)
 HECError      :      0                0
 CRC          :      0                0
 INP          :      0              210 (symbols)
 INTLVDelay       :    100                0 (1/100 ms)
 NFEC          :    254              244
 RFEC          :     16                8
 LSYMB          :   4262             17120
 INTLVBLOCK       :    127              244
 AELEM          :      0             ----
> 


[omegapoint]

My line stats (normal & detailed). Only differences from Vigor 130 are the DS SNR & the DS Interleaving Depth which used to be 1 but now shows 8 even though I'm still Fast Path

Correction, just found an old dump from my 130 and noticed the following differences.

Trellis is 0 for the Near End on the 166, the 130 was 1 (FE 1 on both)
Bitswap is 0 for both Near & Far end on the 166, the 130 was 1
ReTxEnable is 1 for the Near End on the 166,  the 130 was 0 (FE 1 on both)

[onion]

My line stats (normal & detailed). Only differences from Vigor 130 are the DS SNR & the DS Interleaving Depth which used to be 1 but now shows 8 even though I'm still Fast Path

very very similar to me -

Code: [Select]

> vdsl status more
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Near End Far End Note
Trellis : 0 1
Bitswap : 0 0
ReTxEnable : 1 1
VirtualNoise : 0 0
20BitSupport : 0 0
LatencyPath : 0 0
LOS : 0 0
LOF : 0 0
LPR : 0 0
LOM : 0 0
SosSuccess : 0 0
NCD : 0 0
LCD : 0 0
FECS : 0 0 (seconds)
ES : 0 0 (seconds)
SES : 0 0 (seconds)
LOSS : 0 0 (seconds)
UAS : 0 0 (seconds)
HECError : 0 0
CRC : 0 0
INP : 0 245 (symbols)
INTLVDelay : 100 0 (1/100 ms)
NFEC : 254 244
RFEC : 14 8
LSYMB : 5059 17277
INTLVBLOCK : 127 244
AELEM : 0 ----