Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: Robbie on September 29, 2020, 04:00:09 PM
-
Draytek Vigor 166 G.fast Modem / Router Review
Looking around on the web I could find very little regarding the Vigor 166, other than how long it has gone from product announcement to actual product on the shelves. In the absence of any reviews here is my first impressions of it when operating in pure G.fast bridged / modem mode.
The shipping box is typical DrayTek fair and it was nice to see a proper code sticker on the box to show the firmware version and date as shipped. I did see pictures on the web of this product labelled as either Vigor 165 or Vigor 166, depending on version purchased. This one is labelled as ‘Vigor 160 Series’ and seems to cover both the 165 and 166 but with some caveats on the 165 feature set:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_a-20200928_Vigor166_Box.jpeg)
The box includes a drilling template should you wish to mount the unit to something; although judicious use of velcro usually suits me fine:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_b-20200928_Vigor166_Box_Contents.jpeg)
DrayTek is clearly embracing plastic as the packaging medium of choice, even managing to wrap plastic things in plastic with bonus plastic. To avoid landfill I will feed the plastic to the local grey seal colony but keep the telco cable, Cat5e and quick start guide in a suitable dust-gathering space:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_c-20200928_Vigor166_Contents.jpeg)
For those familiar with the older Vigor 130 VDSL modem/router you can see that DrayTek didn’t expend anything on the new design - it is identical in form to the previous model. Nothing particularly wrong with the design though as it is relatively small, lightweight and can be easily mounted or fit on a 1U rack shelf. It will also fit with the existing aftermarket rack mount kits produced for the Vigor 130 [130 left - 160 right]:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_d-20200928_Vigor166_vs_Vigor130.jpeg)
One very welcome change for some users will be the doubling of LAN ports on the rear - now sporting 2 ports that are routed and capable of hosting their own subnets. Otherwise it is the standard RJ11/12 WAN port, reset button (can be software disabled) and a power/dying gasp switch for the 12vdc barrel socket:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_e-20200928_Vigor166_Rear_Ports.jpeg)
The revised Vigor 160 Series labelling is carried on the top/front of the unit, together with 4 green LED indicators:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_f-20200928_Vigor166_Front.jpeg)
Powering-up the unit is a bit quicker than the Vigor 130 and you are treated to some reasonably vocal relay switching. Plugging in an ethernet cable results in the Vigor grabbing the 192.168.1.0 subnet, giving itself the 192.168.1.1. address and its DHCP server giving out a 192.168.1.10 address to the first connected client:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_1-20200928_Vigor166_Network_Default_DHCP.jpg)
DrayTek have yet to employ randomised passwords and the default Username and Password are both set as ‘admin’ as standard. You do get a warning during the setup process to remind you that the default password should be changed:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_2-20200928_Vigor166_Default_IP.jpg)
Going to the 192.168.1.1. web page reveals a familiar DrayTek Dashboard. Unlike the Vigor 130 the time can be set via browser or ntp and the inbuilt browser is noticeable quicker to respond when compared to the 130. MAC addresses can be changed and this unit shipped with firmware V4.0.5_STD. At default the unit powers-up in router-mode so it has all the typical router features and controls exposed to the GUI:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_3-20200928_Vigor166_Default_Login.jpg)
First order of battle was to update the firmware to one dated earlier this month. The firmware comes in 2 flavours with ‘all’ suffix being the normal load that preserves any configuration and the ‘rst’ version resetting the unit to factory-fresh defaults during the firmware update. I didn’t time the update but it wasn’t quick:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_4-20200928_Vigor166_Firmware_Upgrade.jpg)
It should be noted that the v4.1.0_STD contains 2 different modem codes that can be set via the GUI. The readme file contains no detail as to which should be used or why and the inclusion of 2 modem codes in one firmware load is not something I have seen before with DrayTek. More of that later:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_5-20200928_Vigor166_Dashboard_Initial_Setup.jpg)
There is a Quick Start Wizard to set the typical range of parameters. Most are set to ‘auto’ anyway with sensible settings to get most users going. You can of course define the DSL protocols used for quicker reboots and quicker handshakes. Most of these changes will prompt a reboot though, extending the setup time somewhat:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_6-20200928_Vigor166_DSL_Modes.jpg)
The option to set the router (ie default mode) to Modem/Bridge Mode can be found under the lefthand Operation Mode menu item. Again, this prompts another reboot:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_7-20200928_Vigor166_Router_Mode.jpg)
Once up and running again in Modem mode the various router-only modes are removed from the menu tree, leaving just the basics required for modem / PPPoE modem use:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_8-20200928_Vigor166_Bridge_Mode.jpg)
Under the LAN - General Setup menu you can set the subnet to match your town opology. The 2 LAN ports can be set independently and run their own DHCP server if required. For my use I just switched the subnet to 10.0.0.0/24 and as the WAN interface on my router is set as 10.0.0.1 I set the modem itself to 10.0.0.2:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_9-20200928_Vigor166_Setting_IP_Range.jpg)
To provide easy access to the modem GUI from the WAN side of the router you have 3 reasonable options. The second modem LAN port could be used as a hardwired and out-of-band management port, or a NAT masquerade rule could be set on a compliant router or, as the Vigor modem is still a router at its heart you can set a simple static route via the CLI. In my case this was a simple ip route add 10.0.1.0 255.255.255.0 10.0.0.1 static to link to my management subnet which resides on 10.0.1.0. A quick ip route status confirms the route has been set:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_10-20200928_Vigor166_Static_Route_Set.jpg)
Under Internet Access - General Setup I chose to set the WAN VLAN tag and set the DSL mode to G.fast only. I understand that these should auto-populate to the Openreach settings if left alone, but I did not try that:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_11-20200928_Vigor166_General_Setup_VLAN_Tag_101.jpg)
The final setting is under Internet - MPoA to set the MTU. Disappointingly and unusually for DrayTek the MTU has a hard cap of 1500, rather than their usual 1520 byte limit. This means no baby jumbo frames as defined by the Openreach SINs so the PPPoE overhead has to be carried inside the 1500 MTU limit. One hopes this will be changed by DrayTek in later firmware loads. I have not experimented with the CLI as yet to see if it exposes a greater MTU range:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_12-20200928_Vigor166_MTU_1500_Max.jpg)
Once the settings are complete and boredom with reboots has set-in installing a WAN cable will send the unit into DSL READY mode:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_13-20200928_Vigor166_Web_DSL_Stats_Ready.jpg)
After a suitable amount of relay clicks and flashing lights the modem settles into TRAINING mode for a minute or 2:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_14-20200928_Vigor166_DSL_Training.jpg)
Before achieving G.fast SHOWTIME state and it populates the various DSL statistics and connection details. I am on a capped package at 160/30 Mbps:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_15-20200928_Vigor166_DSL_Stats_G_fast_Showtime.jpg)
An abridged set of stats can be found under Online Status - Physical Connection. It is these statistics that are reported downstream to DrayTeks own routers as a parameter set, with the basic SNR, Actual Connection Speed and Tx/Rx packets:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_16-20200928_Vigor166_Physical_Connection.jpg)
The CLI also exposes the line stats but there was some oddities in this data and not all of it correlated with the GUI so there may be a mapping or lookup table issue somewhere:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_17-20200928_Vigor166_CLI_Modem_Stats.jpg)
So finally, the Dashboard when cruising the dead-end technology highway that is G.fast:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_18-20200928_Vigor166_Dashboard_Live.jpg)
I say cruising but in truth there are a few things to iron out. I suspect that the modem code may be incorrect (more experiments to come) and between that and the MTU not playing well with the rest of my network settings did lead to some latency spikes. The raw speed was there but the hesitations need to be sorted. I’ll contact DrayTek with my observations and see when the next firmware drop is due as that is expected to resolve some of the issues with UK use. Till then I will experiment on the LAN side and have installed the Openreach Huawei Modem back on its shelf, hidden under a chest of drawers. Nobody needs to see a modem:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_g-20200928_Vigor166_Openreach.jpeg)
Hope this helps those who are researching the slim-pickings of G.fast capable modems & routers.
👍
-
Thanks Robbie, very helpful indeed !
-
Thanks very much for that Robbie, excellent review.
Is the Vigor 130 capable of being a router ? I tried one of the 1x0 series units out, probably a 130 but my memory has failed me. I just somehow assumed that this device would be a mere modem, so I was surprised to read that it can be a router too.
You pointed out that this device when being a modem can talk to a Draytek router and send it stats. That’s an excellent bit of design; I wonder how they do it in protocol terms? Presumably some proprietary protocol over ethernet rather than IP. I wish there was a standard for this, including more information than just DSL link stats as well. Can other Draytek modem and router combinations do this?
-
Great write up, thanks ;D
-
@Robbie
Are you able to check somehow the connection speed with the Openreach modem or it's a sort of black box?
-
Is the Vigor 130 capable of being a router ?
You pointed out that this device when being a modem can talk to a Draytek router and send it stats. That’s an excellent bit of design; I wonder how they do it in protocol terms?
Can other Draytek modem and router combinations do this?
Yes, the Vigor 130 is capable of being a router and I think the previous V120 was similarly capable. The 2 typical firmware loads for the UK (BT - for Huawei cabs, Alt for ECI) does redact the router functions from the GUI display but the full functionality is still there via CLI. There are a number of other firmware loads that retain the router GUI too.
The downstream stats is a DrayTek thing and is enabled via a checkbox on the modem GUI for display via a suitable DrayTek router (pretty much all of them I think). Whilst this was a mechanism to provider easy stats access across the WAN interface to the potentially single LAN port on the modem the format itself is not proprietary. I did have a 'shark capture of it but I did an overly enthusiastic purge of old files recently(!). Of course, any open router design can gain access to the full stats via CLI anyway so it is pretty easy to pull the details to a log file or a suitable monitoring package.
👍
The V120 and V130 are not particularly powerful routers though and it would not take too much effort to stress them. They seem to make extensive use of hardware acceleration with dedicated offload silicon and running packets direct to the CPU would prob them to their knees. The V160 seems more powerful in that regard and offers the option of running without hardware acceleration, so DrayTek must think the CPU has credible capability for packets not eligible for offload.
-
@Robbie
Are you able to check somehow the connection speed with the Openreach modem or it's a sort of black box?
I asked that question myself but message seems to be that it is well-and-truly strapped-down. The Openreach/Huawei G.fast modem is very new to me so in truth I have very little knowledge of what can or cannot be done.
I do intend to tap the LAN port at some point to have a good look at the PPPoE traffic but I am not expecting anything of interest. The PPPoE handshake on G.fast is unremarkable:
admin@Router-4:~$ show interfaces pppoe pppoe0 log
Thu Sep 10 14:09:43 BST 2020: PPP interface pppoe0 created
Thu Sep 10 14:09:46 BST 2020: Stopping PPP daemon for pppoe0
Thu Sep 10 14:09:46 BST 2020: Starting PPP daemon for pppoe0
Connected to 40:7c:7d:xx:xx:xx via interface eth0
using channel 1
Renamed interface ppp0 to pppoe0
Using interface pppoe0
Connect: pppoe0 <--> eth0
sent [LCP ConfReq id=0x1 <magic 0x8efc3b17>]
rcvd [LCP ConfReq id=0x99 <mru 1500> <auth chap MD5> <magic 0x3a61xxxx>]
sent [LCP ConfAck id=0x99 <mru 1500> <auth chap MD5> <magic 0x3a61xxxx>]
rcvd [LCP ConfAck id=0x1 <magic 0x8efc3xxx>]
sent [LCP EchoReq id=0x0 magic=0x8efc3xxx]
rcvd [CHAP Challenge id=0x1 <7e72cad24afcb7f80dde36d6f027be1a1d16892708056fab3af4b6b76074775fe642323240ea2bcc496124b908e253a4xxxxxxxxxx>, name = "acc-aln1.gb-tny"]
sent [CHAP Response id=0x1 <2c302e3509955f04fc74cxxxxxxxxxxe>, name = "01xxxxxxxxx@idnet"]
rcvd [LCP EchoRep id=0x0 magic=0x3a61xxxx]
rcvd [LCP ConfReq id=0x59 <mru 1500> <auth chap MD5> <magic 0x3a61xxxx>]
sent [LCP ConfReq id=0x2 <magic 0x2e93xxxx>]
sent [LCP ConfAck id=0x59 <mru 1500> <auth chap MD5> <magic 0x3a61xxxx>]
rcvd [LCP ConfAck id=0x2 <magic 0x2e9xxxx2>]
sent [LCP EchoReq id=0x0 magic=0x2e93xxxx]
rcvd [CHAP Challenge id=0x1 <0557db8b671df7cf871538c99dd4xxxx>, name = "bng2.th-lon"]
sent [CHAP Response id=0x1 <7bcbae3655fc2a782b602addd3a7xxxx>, name = "01xxxxxxxxx@idnet"]
rcvd [LCP EchoRep id=0x0 magic=0x3a61xxxx]
rcvd [CHAP Success id=0x1 ""] 40 0f ac 5a xx 06 xx xx
CHAP authentication succeeded
CHAP authentication succeeded
peer from calling number 40:7C:7D:xx:xx:xx authorized
sent [IPCP ConfReq id=0x1 <addr 0.0.0.0>]
sent [IPV6CP ConfReq id=0x1 <addr fe80::3c9a:fd62:xxxx:xxxx>]
rcvd [IPCP ConfReq id=0x1 <addr 212.69.xx.xx>] 00 00
sent [IPCP ConfAck id=0x1 <addr 212.69.xx.xx>]
rcvd [IPV6CP ConfReq id=0x1 <addr fe80::02a3:8eff:xxxx:xxxx>]
sent [IPV6CP ConfAck id=0x1 <addr fe80::02a3:8eff:xxxx:xxxx>]
rcvd [IPCP ConfNak id=0x1 <addr 91.xxx.xx.xx>] 40 0f
sent [IPCP ConfReq id=0x2 <addr 91.xxx.xx.xx>]
rcvd [IPV6CP ConfAck id=0x1 <addr fe80::3c9a:fd62:xxxx:xxxx>]
local LL address fe80::3c9a:fd62:xxxx:xxxx
remote LL address fe80::02a3:8eff:xxxx:xxxx
Script /etc/ppp/ipv6-up started (pid 3408)
rcvd [IPCP ConfAck id=0x2 <addr 91.xxx.xx.xx>] 00 00
Script /etc/ppp/ip-pre-up started (pid 3409)
Script /etc/ppp/ip-pre-up finished (pid 3409), status = 0x0
local IP address 91.xxx.xx.xx
remote IP address 212.69.xx.xx
Script /etc/ppp/ip-up started (pid 3462)
Script /etc/ppp/ipv6-up finished (pid 3408), status = 0x0
Script /etc/ppp/ip-up finished (pid 3462), status = 0x0
admin@Router-4:~$
👍
-
Thanks Robbie, very helpful indeed !
Great write up, thanks ;D
Thanks guys. Sorry about some of the imbedded screenshots not displaying correctly. They look ok at my end but I am rather new to this forum and will endeavour to find what works best.
👍
-
Sorry about some of the imbedded screenshots not displaying correctly.
They are there, complete, displaying correctly. Those of us viewing on smaller screens just need to horizontal scroll.
-
The reply from DrayTek was not particularly helpful. Hopefully this may change at some point:
If and when we release this product. We'll have a UK based firmware for it. At the moment there's no information on our side regarding this product.
For the last bit they could read this review!
;)
-
How much support will this version of the Vigor 166 get, considering it's basically going to be obsolete by the end of the year, it was already over a year late & isn't to original spec.
In the original spec. released by DrayTek it included coverage of both 106Mhz & 212Mhz G.Fast bands, but this stop-gap model, called the GEN1 version, is 106Mhz only.
It's due to be replaced at the end of Q4 with the GEN2 version which will support both 106Mhz & 212Mhz as per the original spec. & will sport a different chipset to do it.
I was going to try one (as I had assumed the 212Mhz fix would be via a firmware update) until I double-checked with DrayTek EU (not UK) on this matter prior to purchase.
They confirmed that the GEN1 model isn't & never will be compatible with 212Mhz due to hardware limitations, so I'm going to wait for the new version to arrive.
It's only a theory but could it be that DrayTek aren't going to the expense of getting the GEN1 version UK certified, instead waiting on the GEN2 version.
-
Are we expecting the higher frequency range here in the UK?
We don't have it yet; it has even less range than the current frequencies; g.fast is a dead-end technology (even for those of us stuck with it) and precisely no one is clamouring for next generation g.fast.
I could be wrong and let's face it, OFCOM and Openreach have had a history in daft ideas, but I just don't see all the current Gen 1 kit being stripped-out for Gen 2 equipment - the RoI on the stillborn g.fast market is unlikely to cover any technology refreshes between now and an eventual back-of-the-queue FTTP future.
-
It may only require a line card swap to accommodate higher frequencies.
I wouldn't be surprised if it never appeared though.
It would likely only help those with very short lines who get the top end of the current G.Fast.
-
Presumably new customer premises equipment too. Reasonably sure the current Openreach/Huawei modem is not capable of the higher frequencies.
If they were looking to increase speed for the very close they could just lift the 330/50 cap to allow max attainable rate to flow. No physical changes required for that (clearly I don't think they would do such a thing - just musing).
-
Who can say what Openreach will do next? FTTP looks like it's going to take several years to fully implement, & you can bet that G.Fast enabled areas will go to the bottom of the list.
Swisscom in Switzerland have already gone the G.Fast route & say they will offer a 1.5GB service using the 212Mhz band soon, other EU countries currently using the 106Mhz band may follow.
I think for now UK G.Fast users will need to source kit from the EU, as manufacturers don't seem very interested in releasing G.Fast equipment into a limited UK market, probably due to certification costs.
Until BT make a decent router (probably never), or at least add a bridge mode, there will be a market for non-BT G.Fast products such as the Vigor 166.
Does anyone know what chipset the VIGOR 166 GEN2 will be using?
-
Update: As of 22/10/2020 most stockists in the EU have run out of stock, the few still with stock have hiked the price by 30-50 euro.
Unusually dealers aren't quoting an expected restock date which makes me think Draytek themselves have none left to sell.
Amazon were 'out of stock' but have today changed the status to 'Not available at the moment. We don't know if or when this item will be back in stock'.
So the big question is will the next shipment be more of the GEN1 version or will the GEN2 model make an appearance?
-
Not sure it matters here in the UK, aside from a potential price rise for including (unused) Gen 2 chipsets.
I just hope that G.fast in my area is gone within the next 2 years. Until then I am marking time until FTTP arrives.
-
Just because Openreach doesn't offer 212Mhz G.Fast at the moment doesn't mean to say they won't in the future.
A lot would depend on whether the current equipment supports it, there's very little info on what's actually been installed.
They keep changing direction when it comes to their broadband plans, currently G.Fast can serve 2.8m homes.
However new G.fast deployments are currently on hold until a review in March next year.
They're currently way behind in their FTTP rollout, & keep extending the target date for the project's completion.
In fact earlier this year they admitted that the rollout was so far behind that more homes could still get G.fast vs FTTP.
-
It's starting to veer a bit off topic, but utilising 212 MHz in OR's current G.fast deployment (via cabinets) is going to provide very little benefit since line lengths would probably need to be approx. 150m or less under real world conditions for it to make a difference.
Some old data from TBB says 20% of premises are 150m or shoter, and those people could already exceed 330 Mbps without 212 MHz. I am ~190m at I have seen attainables around 400 Mbps for the downstream. Those closer to 100m probably could see over 500 Mbps on 106 MHz.
It probably doesn't make sense to deploy 212 MHz unless you're doing it from nodes much closer to the property, where the distance is ≤100m (which is about 11% when it comes to cabinets overall, but will vary area to area) where 1 Gbps is possible downstream. Even at my distance, I do not think my line is capable of frequencies above ~90 MHz so it doesn't bother me.
The key to increasing speeds and distance for all is finding a way to reduce the starting frequency for G.fast, but without interrupting VDSL signals. With low takeup, maybe it is just best it is treated as a stopgap and not focus on upgrading existing cabinet-based deployments at least. With the cabinet-based approach, it looks like 1/6 of those who could get G.fast would see a good benefit from 212 MHz, with the rest being marginal or no benefit at all - and how many customers would actually take up new packages?
-
I can't see them introducing the faster 212MHz on a technology with an artificial cap in place already.
If they want to boost G.Fast speeds for those closest to their cabinet (the only people 212MHz would benefit anyway) then they simply need to remove the 330Mb cap.
They are already overbuilding G.Fast with FTTP in many areas.
The rollout is dead.
I predict 212MHz will never come to PCP deployed G.Fast in the UK.
Perhaps if they change the deployment method and start using G.Fast in MDU's that can't get FTTP due to wayleave issues then higher frequencies would make more sense.
Higher frequencies being available doesn't mean they will be used and the VDSL2 rollout is the perfect example of that.
VDSL2 profile 30a and 35b have been around for many years.
35b looked particularly appealing being wholly compatible with profile 17a.
I've been reading posts asking when profile 30a was coming pretty much since the day they upgraded to 17a.
-
If they want to boost G.Fast speeds for those closest to their cabinet (the only people 212MHz would benefit anyway) then they simply need to remove the 330Mb cap.
^ Absolutely this. People with line lengths up to around 200m should notice a small difference at least. I wouldn't mind 400 Mbps if they got rid of that cap. :)
-
I had an email today from Draytek (in Germany) to say that the Vigor 166 GEN2 (due Q4 2020) has been delayed slightly.
The first batch should now arrive in Germany around Jan 15th & will cost around €140
No word regarding a UK launch though.
-
Coming late to this party......but want to check first before pulling the trigger.
I had G.Fast installed yesterday from Shell using TalkTalk backhaul/infrastructure.
I currently have an MT992 with Technicolor Router, speeds are OK so far but I'm going to find my local cabinet and get an idea what the rough distance is.
I'd read that the German Vigor 166s were configured for Annex B but the UK uses Annex A, from a quick bit of research this doesn't matter as above circa 18Mhz up to 106Mhz they're both the 'same' standard, is this correct or have I (in all likelyhood) misunderstood?
So, in a nutshell if I could find a MK I Vigor 166 (I know the MK II is due mid/end next month....but based on this and other threads the UK only seem to be supporting up to 106Mhz range on the cabinet cards anyway?) what would be a sensible price to pay for it?
Great threads here guys, I think this is going to be my goto place for all info re G.Fast.
-
Welcome to the Kitz forum. :)
I'd read that the German Vigor 166s were configured for Annex B but the UK uses Annex A, . . .
In the UK, the basic hardware annex is for xDSL over POTS. That is Annex A.
In Germany, the basic hardware annex is for xDSL over ISDN. That is Annex B.
It's important not to confuse the above, basic, hardware annexes with those for software features.
-
Openreach uses an Annex B bandplan from VDSL2 ITU-T G.993.2 over Annex A physical infrastructure (POTS).
Germany use Annex B (ISDN).
I don't believe an Annex B modem will sync in the UK.
Edit: the annex B models usually have an rj45 xdsl port and the UK Annex A version usually has an rj11 xdsl port.
-
I don't believe an Annex B modem will sync in the UK.
I, too, share that belief.
-
What made it confusing was that on the Amazon reviews some UK buyers said theirs did work, while others said theirs didn't. Therefore based on the comments here I can only conclude inconsistency in what model individual users were provided.
So, I MUST buy an Annex A unit, given that is my supposition regarding the 106Mhz to 212hz status of cards in the street cabs likely correct (i.e. Existing cards won't support 212Mhz due to hardware limitation, new cards installed going forward by OR might)? If this is correct I should work on the basis that G.Fast for me is a stop gap solution (be that 2 years or 5 years) until FTTP is rolled out to my area?
So, if I'm correct on the above assumptions and can find an Annex A MK I 166, what would be a fair price to pay?
Thanks for the pointers guys.
-
Annexe A&B only refers to the VDSL part, G.Fast doesn't have A&B.
As this router isn't a UK model it's quite likely that it won't work on G.Fast here in the UK 'out of the box' & will need a manual setup.
This may be what's been causing problems with people not being able to set it up properly.
Certainly the ZyXel XMG3927 suffers from this problem as the auto-setup wizard can't even detect the G.Fast signal in the UK, but a manual setup works fine
-
Annexe A&B only refers to the VDSL part, G.Fast doesn't have A&B.
It may not have the A&B Annex (software) part (bandplan) but there is still the physical infrastructure Annex A or Annex B to consider.
Draytek even include Annex A and Annex B cables in their 160 range, so it still exists.
Many Annex B modems will not sync in the UK.
YMMV
I've tried both a German Asus DSL-AC87VG (Annex B) and a German Draytek Vigor 165.
I couldn't get either to sync on VDSL2 in the UK.
The Draytek 165 is supposed to be Annex A and B and even included...
- RJ-11 to RJ-11 Cable
(Annex A) - RJ-11 to RJ-45 Cable
(Annex B) - RJ-45 to RJ-45 Cable
(Annex B)
It still wouldn't sync.
The fact Draytek now seem to make a single model with an rj45 xdsl port in the 160 range suggests it should work.
That's why i purchased it after my failed experiment with the Asus a number of years earlier.
No luck though.
I couldn't find any UK specific firmware for the 165 at the time.
-
As I said, Annex A/B refers to the VDSL service only.
If you are buying a Vigor 166 to use on G.Fast then there shouldn't be a problem.
I looked at this before buying a ZyXel XMG3927 for UK G.Fast use from Germany.
-
There seems to be some confusion about what is meant by Annex A/B. 'Annex' in this context is a Euro word meaning 'Appendix'. It refers to an appendix to an official document. There are two relevant documents being mixed up here, one describing the hardware for a DSL service and one describing the band plan configuration. A modem described as Annex A means that its hardware supports xDSL over POTS (the UK system) and Annex B means that its hardware supports xDSL over ISDN (the German system) Some modems may support both, but most don't. An Annex B modem is no use in the UK.
-
Agreed, I'm stll pretty confused about it... I did read somewhere that Openreach uses an Annex B bandplan from the VDSL2 spec (G.993.2) over Annex A physical infrastructure, so for the UK, the modem hardware/firmware needs to be Annex A, but it will sync using Annex B
From my stats, see 'Mode':
xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 1
Last initialization procedure status: 0
Max: Upstream rate = 28192 Kbps, Downstream rate = 86998 Kbps
Bearer: 0, Upstream rate = 20000 Kbps, Downstream rate = 72929 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
As for G.fast, according to smallal it shouldn't matter...
-
As I said, Annex A/B refers to the VDSL service only.
Annex A B does absolutely not apply to VDSL only.
The physical infrastructure remains Annex A or B whether you run ADSL, VDSL or G.Fast.
If you are buying a Vigor 166 to use on G.Fast then there shouldn't be a problem.
I looked at this before buying a ZyXel XMG3927 for UK G.Fast use from Germany.
G.Fast may run over either, or those modem manufacturers may have made their devices to run on either.
It's still Annex A and B infrastructure. Just with a modem that handles both.
Draytek include an Annex A and Annex B cable in the box.
Agreed, I'm stll pretty confused about it... I did read somewhere that Openreach uses an Annex B bandplan from the VDSL2 spec (G.993.2) over Annex A physical infrastructure, so for the UK, the modem hardware/firmware needs to be Annex A
Correct.
but it will sync using Annex B
From my stats, see 'Mode':
Incorrect, sort of.
That Annex B reported is the bandplan.
It's Annex A, with an Annex B bandplan.
Some modems report 1 Annex, while other modems report the other Annex, confusing things further.
I've tried 2 Annex B (infrastructure Annex) modems on OpenReach VDSL2 and neither synced.
I've read other posts that have also failed to get the Vigor 165 syncing in the UK
There are also sites selling the Draytek that specifically label it as a Vigor 165-A, advising it won't work with ISDN
Suitable for VDSL2 and ADSL2 / 2 +
The integrated modem of the Draytek Vigor 165 is suitable for both VDSL2 and ADSL2 connections. This model supports analog ADSL2 / 2 + connections. If you are looking for a similar model supports ADSL connections via ISDN, please refer to the Draytek Vigor 122 annex B .
The 1st Google result for "Vigor 165 OpenReach" has a thread with the following
Will Vigor 165 Annex B work in UK?? (FTTC VDSL connection) (https://www.overclockers.co.uk/forums/threads/will-vigor-165-annex-b-work-in-uk-fttc-vdsl-connection.18847385/)
Containing the posts...
I have just tried a Vigor 165 bought in Germany.
The 165's firmware supports Annex A and B, still I was not able to get a sync on my line.
Will have to see, whether I can make some adjustment to the settings to get it to make a sync
and
I have acquired a Draytek Vigor 165 (Annex A, not B) imported from the Netherlands, working with PlusNet in the UK.
I can happily confirm this seems to work A-OK.
If you're in the UK and want one of the 165's - make sure it is indeed Annex A.
I'm still not sure if there are 2 models of the 165 (an A and B variant) or if there's only 1 model.
As for the Vigor 166... It might well sync on G.Fast and not VDSL2.
It might sync on both.
The Vigor 165 would not sync on OpenReach VDSL2 though and that also appears to have a single EU model, but that's contradicted by retailers who specify Annex A or B.
-
I dunno.....
New poster asks a simple question and starts a riot ;) ;) :D >:D ......sorry folks.
Now you understand why I had to ask the question, this is about as clear as pea soup, simplistically, without wishing to be anal, has anyone on the thread actually plugged a Vigor 166 into OR infrastructure and got it to work fully and properly without limitations (please no theoretical answers, actual first hand experience answers)? If you did was the one you used an Annex A, Annex B or Annex neutral? Lastly what settings are you using?
On the flip side happy crimble everyone and on a slightly more serious note remember, on January 1st Hindsight really will be 2020 thank frack.
-
The 1st post (the review) in this thread is for the version sold in Germany.
The review seems to be a UK based one with the Vigor 166 working.
Why don't you PM the author & ask to confirm if you're in doubt, just to be sure.
Sourcing a GEN1 may be a bit tricky as they're getting rare, amazon.de were doing them for €120 but they ran out last month.
For some reason most German online traders won't supply to the UK.
As for Annex A or B, I've only seen 1 version for sale so far, I read this in a review which may explain why:
The Vigor166 works with VDSL / Supervectoring / G connections.Fast Vigor166 generation 1 supports G.Fast with 106 MHz and is supported in generation 2 in Q4 / 2020 also 212 MHz.
Please also note that by eliminating ADSL support for the Vigor166, there are no longer separate Annex A and Annex-B variants, as these are only for ADSL spectra.
-
Please also note that by eliminating ADSL support for the Vigor166, there are no longer separate Annex A and Annex-B variants, as these are only for ADSL spectra.
Where do people come to with that nonsense?
You just said in a previous post Annex A & B was VDSL only.
Now it's ADSL only
The Vigor166 has NOT, absolutely NOT, dropped ADSL support.
It's listed on their product page.
https://www.draytek.com/products/vigor166/#specs
ADSL Standards ANSI T1.413, ITU-T G.992.1(G.dmt), G.992.2 (G.lite)
ADSL2 Standards ITU-T G.992.3
ADSL2+ Standards ITU-T G.992.5
The Annex remains regardless of ADSL, VDSL or G.Fast.
Draytek have simply made a model that does both.
They claim to have done the same with the 165, but I and others can't get it to sync in the UK on VDSL2.
The only report of the 165 syncing on VDSL2 is a 165-A (AnnexA) model, which the retailers specifically warns doesn't work on ISDN (AnnexB).
Draytek list a single variant, with modem code that is labelled both Annex A&B
Draytek are clear as mud on this.
-
The vigor 166 support page, at the very top says VDSL & G.FAST - NO ADSL!
The ref further down to ADSL is out of date, just like the ref to 212Mhz which is GEN 2 only.
What page are you reading? I can't see anywhere that says NO ADSL.
https://www.draytek.com/products/vigor166/
It makes no less than 9 statements claiming ADSL operability.
Vigor166 is a G.fast modem/router, delivering fiber-like DSL speed up to 1.3 Gbps. The built-in DSL modem is backward compatible with VDSL2 profile 35b supervectoring and ADSL2+. With 1 RJ-11 port and 2 GbE LAN ports, Vigor166 is also configurable to be a small yet powerful router, offering SPI firewall and content filtering by URL keywords and web features.
11x RJ-11 for G.fast/VDSL2 35b/ADSL2
There are 6 mentions of ADSL on the specs page.
I have never, ever, seen a modem do VDSL that isn't backwards compatible with ADSL.
Edit: post I've replied to has been deleted?
-
VIGOR 166 official UK Model is on it's way!
Draytek (UK Division) has confirmed that the official UK (Openreach/BT certified) model is imminent.
Designated the V166-K (EAN 4712909128230) they've posted details here:
https://draytek.co.uk/products/business/vigor-166
It seems to have UK specific firmware for easier setup.
Quote: The Vigor 166 modem is designed exclusively for use in the UK, with the required network settings pre-set, such as the Openreach VLAN tag.
-
Excellent.
No doubt on that syncing then.
WAN Features
Pre-Configured with OpenReach network VLAN tag 101
WAN1 Service & Customer (double-tag) VLAN support
Maximum MTU 1508
G.fast & DSL Compatibility
BT Infinity Option 1 & Option 2 Compatible
Compliant with Openreach SIN 527 & SIN 498
Auto Detection of G.fast and VDSL line modes
Support for G.INP & Vectoring
G.fast Standards:
ITU-T G.9700, G.9701 G.fast
Profile: 106MHz
-
MTU=1508 will be welcome
The EU version has a max=1500 (so no baby jumbo frames as defined by the Openreach SINs)
I wonder if the UK firmware (once released) can be loaded into an existing EU model?
-
I notice the UK one only supports the 106Mhz profile, so if OR do install 212Mhz cards going forward you may not be able to benefit (I realise that the benefit will apply only to people less then 150m from their street cabinet).
-
(I realise that the benefit will apply only to people less than 150m from their street cabinet).
... and can get Gfast. We qualify on the less than 150m, but have no Gfast on our ECI cabinet.
-
... and can get Gfast. We qualify on the less than 150m, but have no Gfast on our ECI cabinet.
So that might mean if/when your cab is enabled you might get a 212Mhz card installed in it that supports the higher speeds, so there could be an upside to your delay.
-
So that might mean if/when your cab is enabled you might get a 212Mhz card installed in it that supports the higher speeds, so there could be an upside to your delay.
If/when? What delay?
The G.Fast rollout is dead.
If you don't have access to it now in the uk it is very very unlikely you ever will get it.
I'm not sure anyone actually wants it rolled out to them.
They are even overbuilding existing G.Fast with FTTP, meaning the numbers with access to G.Fast now will start shrinking.
I personally can't see OpenReach upgrading all their line cards to 212Mhz cards.
Some of the bigger ISP's only sell 160/30 already and above 212Mhz would benefit a tiny proportion of G.Fast users, of who there are few.
Take up rates have been disastrous.
-
The question is would the line cards need an upgrade or are they already 212Mhz capable?
As for FTTP, the project has fallen way behind, just yesterday a news report said that the new lower 2025 Govt. coverage target probably wouldn't be met.
Speaking to a local Openreach engineer he told me that there were no plans for local domestic FTTP installs in my area for at least 2 years (except for new build estates).
Therefore I'm stuck with G.Fast for quite some time to come. (especially as Virgin have reneged on their promise to cable my street)
-
They will need upgraded.
Don't think 212Mhz was even finalised when OpenReach started the G.Fast rollout.
The current Huawei lines cards definitely don't support 212Mhz.
I haven't got a clue on the Nokia kit but I'd be amazed if it wasn't the same story.
-
I see Broadband Buyer are now accepting pre-orders for the UK version V166-K.
Priced at £96.94 inc VAT (excludes delivery which starts at £3 via Royal Mail).
https://www.broadbandbuyer.com/products/41275-draytek-v166-k
-
Amazon seller NetXL claiming 100 in stock (I spoke to them on the phone and they say they got the stock at 11am this morning).
https://www.amazon.co.uk/DrayTek-Vigor-166-G-Fast-Supervectoring/dp/B08CRZCXBL/ref=sr_1_1?dchild=1&keywords=vigor+166&qid=1608378481&quartzVehicle=1505-10&replacementKeywords=166&sr=8-1
They had them listed at £117 inc shipping originally, they've now upped their price to £140 so no order going to be placed by me as that's not the crimble spirit as far as I'm concerned.
-
I expect prices will stabilise once everyone's got their stock, it's increased again to £144.49 on Amazon!
Ordering direct from netxl it's £139.19 (£130.80 + £8.39 delivery by DPD next day)
So it's actually slightly more expensive via their Amazon shop at the moment
-
They really should have made a new Amazon listing specific for the UK version.
Half the reviews are either German, or English and complaining it doesn't work.
No way to tell what you are ordering without messaging each seller.
-
I see Broadband Buyer are now accepting pre-orders for the UK version V166-K.
Priced at £96.94 inc VAT (excludes delivery which starts at £3 via Royal Mail).
https://www.broadbandbuyer.com/products/41275-draytek-v166-k
That's a not unreasonable price and given it exposes line stats and I don't need a router, I am very, very tempted.
We got G.Fast in my area because Virgin ran in cable and BT suddenly found themselves at a severe speed disadvantage with no immediate plans for FTTP.
-
They really should have made a new Amazon listing specific for the UK version.
Half the reviews are either German, or English and complaining it doesn't work.
No way to tell what you are ordering without messaging each seller.
Totally agree, Amazon have messed up (not for the 1st time)
However, sometimes going directly to the sellers own website helps, as is the case with NetXL.
There are currently only 2 versions of the Vigor 166 that I can find:
The V166-A (also known as GEN1) for the EU & V166-K for the UK, another EU model (GEN2 with 212Mhz support) is due soon.
I've got one on back order from Broadbandbuyer who I've used before, hopefully they'll get them in next week.
-
hello !
does anyone know what SOC they used in that modem ? always a lantiq ?
-
hello !
does anyone know what SOC they used in that modem ? always a lantiq ?
Yes. They aren't called Lantiq any more though.
It's an Intel chipset.
I'm not sure on the 166 chipset
The Vigor 165 has an Intel VRX518.
The Intel VRX618 and VRX619 both support G.Fast.
Looks like the VRX618 does up to 106 MHz and the VRX619 does up to 212 MHz.
-
I expect prices will stabilise once everyone's got their stock, it's increased again to £144.49 on Amazon!
Ordering direct from netxl it's £139.19 (£130.80 + £8.39 delivery by DPD next day)
So it's actually slightly more expensive via their Amazon shop at the moment
Something odd going on at Amazon UK?
The V166-K price keeps changing several times a day, even though the supplier remains the same (NetXL)
As of 27/12 @ 15:00 it's risen again to £159 via Amazon, however NetXL's own website still shows it @ £130.80 + P&P
-
Something odd going on at Amazon UK?
The V166-K price keeps changing several times a day, even though the supplier remains the same (NetXL)
As of 27/12 @ 15:00 it's risen again to £159 via Amazon, however NetXL's own website still shows it @ £130.80 + P&P
That's very normal.
They are using automatic software that adjusts the pricing based on the competitors price.
Every time 1 of the other 2 sellers drops or increases their prices then NetXL automatically adjust theirs.
I've sold a number of items on Amazon.
If i ever lowered my price then about 4 other sellers of the same item automatically lowered their price to be 1p cheaper and remain the top seller on the listing.
If I put my price back up then the other sellers did the same, remaining 1p cheaper again.
This pricing software is used by thousands of sellers across millions of items and I believe was the cause of the huge 1p glitch Amazon sellers suffered a couple years ago.
-
And that's where Amazon have screwed up!
There is no competition for the V166-K, only NetXL sell this model on Amazon at the moment.
Amazon is using the price of the EU model V166-A as a comparison!
-
Rather stupid yes.
It's not Amazon's fault though. When you use Fulfilled by Amazon they follow your instructions.
NetXL should have made a new separate listing.
They've simply sent Amazon their stock and said "it's this listing here" and told Amazon to use the existing listing of the EU model.
-
So my Vigor 166 UK unit arrived this morning.
They are Version 1 units rather then Version 2
I've obviously obfuscated the serial and other identifiable numbers for privacy reasons.
I'll set it up on the weekend when I have time to do it properly and will feedback here.
-
Great news, thanks for updating about it.. can not wait to see it in action :thumbs:
-
I received my 166 from Broadband buyer today - it was replacing a 130 and I have stats from both. I think my line is pretty good anyway, so only saw a minor improvement.
Vigor 130
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 78922000 bps US Actual Rate : 20000000 bps
DS Attainable Rate : 78831336 bps US Attainable Rate : 24024960 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 1 US Interleave Depth : 1
NE Current Attenuation : 13 dB Cur SNR Margin : 5 dB
DS actual PSD : 2. 2 dB US actual PSD : 2. 4 dB
NE CRC Count : 186 FE CRC Count : 688
NE ES Count : 138 FE ES Count : 588
Xdsl Reset Times : 0 Xdsl Link Times : 1
ITU Version[0] : fe004452 ITU Version[1] : 41590000
VDSL Firmware Version : 05-07-09-0F-01-07 [with Vectoring support]
Power Management Mode : DSL_G997_PMS_L0
Test Mode : DISABLE
-------------------------------- ATU-C Info ---------------------------------
Far Current Attenuation : 12 dB Far SNR Margin : 6 dB
CO ITU Version[0] : b5004946 CO ITU Version[1] : 544eb206
DSLAM CHIPSET VENDOR : < IFTN >
Vigor 166
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 79992000 bps US Actual Rate : 20000000 bps
DS Attainable Rate : 81014426 bps US Attainable Rate : 24761463 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 1 US Interleave Depth : 1
NE Current Attenuation : 14 dB Cur SNR Margin : 6 dB
DS actual PSD : 3. 8 dB US actual PSD : 3. 7 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 : 9 dB
CO ITU Version[0] : 00b54649 CO ITU Version[1] : 4e5406b2
DSLAM CHIPSET VENDOR : < ----- >
-
@Craig
I've noticed that in Online Status --> Physical Connection it's got Google's DNS servers, 8.8.8.8 as Router Primary DNS and 8.8.4.4 as Router Secondary DNS...
Can you delete them or change them?
Thanks.
-
Are you asking if you can change DNS servers on a Draytek? :D
Having never touched a 166 even I can answer that.
Yes.
-
It may be funny, but I've checked all the settings, and those Google addresses are nowhere...
Are they hard-coded perhaps?
-
It may be funny, but I've checked all the settings, and those Google addresses are nowhere...
Are they hard-coded perhaps?
There's nowhere to manually choose DNS servers?? or changing them has no effect?
That would be very odd indeed. Understatement.
-
There's nowhere to manually choose DNS servers??
Yes, there is (of course)
or changing them has no effect?
Exactly, DNS servers fields are blank/empty, so I thought it must take those Google addresses from somewhere in the firmware which is not actually displayed in the GUI ??
That would be very odd indeed. Understatement.
It is odd indeed... hopefully someone who actually owns the unit can shed some light on this...
-
I've recorded a quick click-through of the 166 web interface. I can't see anywhere to change the DNS settings shown on the Online Status > Physical Connection screen. I've even included a view of my router DHCP config - showing that these don't match.
I do have a theory though. Googles DNS servers might be the default, and when the device is operating in Bridge Mode the DNS servers are probably ignored as they're configured on the device initiating the PPPoE connection.
Edit: Forgot to include the link to the video https://www.youtube.com/watch?v=FzFlXL74GDo
-
Hi
I just purchased one of these.
I’ll link below to the full operating manual, dns is mentioned on page 53 if it helps. In modem mode the DNS will be reliant on your routers dns selection.
https://draytek.co.uk/support/downloads/vigor-166/send/920-vigor-166/2117-ug-v166-v11
-
Hi, can you test the baby jumbo frame support please. You will need to set MTU to 1500 (1508).
Linux command:
ping -c4 -M do -s 1472 1.1.1.1
Windows command:
ping -f -l 1472 1.1.1.1
Thanks, ;D
-
Hi, can you test the baby jumbo frame support please. You will need to set MTU to 1500 (1508).
PING 1.1.1.1 (1.1.1.1) 1472(1500) bytes of data.
1480 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=20.7 ms
1480 bytes from 1.1.1.1: icmp_seq=2 ttl=60 time=20.5 ms
1480 bytes from 1.1.1.1: icmp_seq=3 ttl=60 time=20.6 ms
1480 bytes from 1.1.1.1: icmp_seq=4 ttl=60 time=20.5 ms
--- 1.1.1.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 20.476/20.561/20.669/0.075 ms
-
Perfect! Thanks very much ;D
Was it ever confirmed what chipset brand/model is being used?
-
Got one yesterday and have twice now had periods of 10% packet loss that were only resolved by restarting the modem.
(https://www.thinkbroadband.com/broadband/monitoring/quality/share/thumb/9cd769cdf79e185a482014524918a305ecba136e-12-01-2021.png) (https://www.thinkbroadband.com/broadband/monitoring/quality/share/9cd769cdf79e185a482014524918a305ecba136e-12-01-2021)
1st one was at around 5pm the 2nd at 4am. Both times my connection was almost idle when it started & the error count for the line showed 0 both up & down.
Running 4.1.1_BT firmware on VDSL2 rather than G.fast
-
Vigor 166 modem chipset looks to be either a VRX619 or VRX618, see: https://bbf-gfast-cert.iol.unh.edu/product/123
CPE Chipset
Intel VRX619
CPE Manufacturer
Intel
CPE Model
EASY550 2000 V2
CPE Software Version
UGW8.1.1 SW V5.3.24
CPE Chipset Firmware Version
12.3.2.1.0.31
-
Got one yesterday and have twice now had periods of 10% packet loss that were only resolved by restarting the modem.
(https://www.thinkbroadband.com/broadband/monitoring/quality/share/thumb/9cd769cdf79e185a482014524918a305ecba136e-12-01-2021.png) (https://www.thinkbroadband.com/broadband/monitoring/quality/share/9cd769cdf79e185a482014524918a305ecba136e-12-01-2021)
1st one was at around 5pm the 2nd at 4am. Both times my connection was almost idle when it started & the error count for the line showed 0 both up & down.
Running 4.1.1_BT firmware on VDSL2 rather than G.fast
After 24 hours up I ended up with my ping doubled from 7ms to 14ms and losing 7Mbps from a already lacklustre 51Mbps (due to crosstalk I used to get 63Mbps) Also upstream is all over the place on the 166 with a constant bufferbloat for me of F on Thinkbroadband and spikes up to 312ms on upload too. Ive put my old ECI modem back on today and will be sending the 166 back, I'll await improvements if they come in the future but streaming UHD I need all the throughput I can get with background tasks running and Video chat is bad with upstream on this router on VDSL2 if something starts downloading in the background, of you get a few emails with images in etc, its really needs some work.
-
I am using my 166 in VDSL mode and haven't experienced the issues @Killhippie and @omegapoint are reporting. I've attached screenshots from the thinkbroadband tester - is there any chance you might have got a defective unit?
-
It all depends on your line and since you are so close to your cab that's probably why you are not seeing the issues, it does does not like my longer line so its being returned. :( Its nothing to do with it being faulty as I have seen others with issues too on longer lines it seems. Glad it worked for you.
-
Mines going to have to be returned too. I lost 11Mbps on DL and I did gain better download grade on thinkbroadband but upload was F and it’s the fact I had 3 DLM adjustment so I’ve ended up from 64 to 53.
The first drop went to 58, then 56 and today I’m hitting 53.
I also noticed on thinkbroadband the upload test was as it I had constant freezing.
Sadly this does not suit my line so I’ve put my HG612 back up.
Perhaps at some stage the firmware will be improved as it’s bleeding edge at the moment.
I could not see any line errors either. Onwards and upwards as they say.
-
Switched back to a Vigor 130 for now. Did the packet loss thing again, seems to happen every 8 hours so I'm guessing some sort of memory leak in the firmware.
I'll try to report to DrayTek, though their support form is missing the 166
-
Switched back to a Vigor 130 for now. Did the packet loss thing again, seems to happen every 8 hours so I'm guessing some sort of memory leak in the firmware.
I'll try to report to DrayTek, though their support form is missing the 166
I noticed last night a brief packet loss, nothing severe but I also noticed an increase in latency even though I had nothing on the network, constant throughout the night.
Switched back now to the 612 and it’s showing no latency when nothing is connected. I had high hopes but at the same time knew it would be a gamble as like routers they tend to need some work.
-
I noticed last night a brief packet loss, nothing severe but I also noticed an increase in latency even though I had nothing on the network, constant throughout the night.
Switched back now to the 612 and it’s showing no latency when nothing is connected. I had high hopes but at the same time knew it would be a gamble as like routers they tend to need some work.
Background latency is more or less the same as my 130, until the packet loss kicks in.
-
As for the packet loss, could this be related to the MTU value, i.e. if you leave the default value of 1520 that may cause the packet loss ??
-
Since its in modem only mode surely the MTU set by the router applies, not the Vigor 166?
-
Has anyone spoken to Draytek Support regarding the packet loss?
-
Has anyone spoken to Draytek Support regarding the packet loss?
I've sent a support e-mail this morning.
I did consider the MTU setting, but I can't see why that would only cause an issue after 8 hours of uptime.
-
I've sent a support e-mail this morning.
I did consider the MTU setting, but I can't see why that would only cause an issue after 8 hours of uptime.
I was in modem mode so I would say the MTU setting in the vigor should not be applicable.
Running the thinkbroadband monitor the vigor when the network was quiet at night showed constant latency spike all be it not much but the HG612 shows nothing during night and a hint of the latency spikes.
I also noticed on a speed test the latency on the 166 upload was 400ms plus and the 612 is around 100ms.
Killhippie and myself know each other, he’s on an ECI cab and I’m not. We both experience lower latency on download but also experienced high latency on upload. His thinkbroadband showed F and latency going into the 400ms and he’s changed back to his ECI modem and the upload has returned to around 23ms.
We chatted about our results and that we both suffered lines being lowered due to errors and we both feel the upload is the cause. Download was fine and an improvement but upload is an issue.
-
I did connect a Vigor 166 this morning at 08:00 to my ECI line and also started the Thinkbroadband monitor service, and it doesn't look like good (see attachment).
Not sure if return it or awaiting a new firmware ??
-
I lost 6Mbps on my download due to 24 hours use on DLM and doubled my ping, I had to remove mine as it was damaging my connection, returning it Friday unless I hear from Draytec. Can you do a thinkbroadband speed test and post the results showing latency in bufferbloat on the upload, as mine was over 350 to 400ms range and this is what I believe caused my issues. Contacting Draytec may also be worth while so the more people tell them the faster they may work on a fix. Until then I cannot leave the unit on my line. The high latency on upload caused issues with video chat breaking up if there is to much background activity, my old ECI is not having these issues and my upload is back to 23ms with a bufferbloat score of B. Sadly my ping and loss of throughput remain, until the DLM god smiles on me.
-
I did connect a Vigor 166 this morning at 08:00 to my ECI line and also started the Thinkbroadband monitor service, and it doesn't look like good (see attachment).
Not sure if return it or awaiting a new firmware ??
Results showing the vigor vs hg612. Top image is the vigor.
-
I lost 6Mbps on my download due to 24 hours use on DLM and doubled my ping, I had to remove mine as it was damaging my connection, returning it Friday unless I hear from Draytec. Can you do a thinkbroadband speed test and post the results showing latency in bufferbloat on the upload, as mine was over 350 to 400ms range and this is what I believe caused my issues. Contacting Draytec may also be worth while so the more people tell them the faster they may work on a fix. Until then I cannot leave the unit on my line. The high latency on upload caused issues with video chat breaking up if there is to much background activity, my old ECI is not having these issues and my upload is back to 23ms with a bufferbloat score of B. Sadly my ping and loss of throughput remain, until the DLM god smiles on me.
I've been advised to select a different modem code (Internet Access -> General Setup) so will be trying that overnight once I reconnect the 166.
My bufferbloat score is the same (A) as with my 130, however my router has a "smart queues" feature so not totally indicative. Ping even under full load is 23ms (8ms idle), however my router effectively caps the speed at ~90% of the sync speed to I'm never fully loading my line.
-
Can you do a thinkbroadband speed test and post the results showing latency in bufferbloat on the upload, as mine was over 350 to 400ms range and this is what I believe caused my issues.
I've attached a test with thinkbroadband and DSLReports: the bufferbloat issue is actually the same I have with my Zyxel VMG1312-B10A
-
I've been advised to select a different modem code (Internet Access -> General Setup) so will be trying that overnight once I reconnect the 166.
Which one? Mine is currently on default
-
Which one? Mine is currently on default
Mines default too, not sure which one either.
-
Which one? Mine is currently on default
The 10_14 one. There is a "DSL version" displayed in the dashboard which displays the one it is currently using (without the "_").
Also I've been told to turn "Hardware Acceleration" on.
-
Thanks, I’ll give it a shot
-
The V130 had an alternative modem code for use with ECI VDSL cabinets - it shares the same version number but without the BT bit. It did add some extra performance to bring it close to parity with a Huawei cabinet but even running the other firmware it did not have the scale of issues shown above.
As I understood it, the Hardware Acceleration should make no difference when used in modem mode, especially with VDSL throughput, unless there is an odd parameter that looks for it.
Has anyone tried the revised UK-specific firmware on a G.fast line yet?
-
Thanks, I’ll give it a shot
Tried it, lowered my download speed even more, latency on upload still there and after 2 thinkbroadband speed checks my line went dead. Had to resort back to my hg612. Gut feeling the Vigor 166 is it’s not right somewhere.
-
Great review and off the back of this I bought a Vigor 166 from broadbandbuyer.
I am a little disappointed though. Using mine as a modem / bridge The DSL status page is not in the menu under diagnostics.
Also from the CLI - VDSL status shows very little information. Most things show as zero (zero crc errors etc)
I wonder if you see this status page because yours is running in Router mode, and also perhaps because I am using official BT firmware ?
-
Tried it, lowered my download speed even more, latency on upload still there and after 2 thinkbroadband speed checks my line went dead. Had to resort back to my hg612. Gut feeling the Vigor 166 is it’s not right somewhere.
Are you on ECI or Huawei line?
-
Are you on ECI or Huawei line?
Huawei line.
-
Tried it, lowered my download speed even more, latency on upload still there and after 2 thinkbroadband speed checks my line went dead. Had to resort back to my hg612. Gut feeling the Vigor 166 is it’s not right somewhere.
Same here. Switch the modem code back to default but keeping hardware acceleration & the MTU lowered to 1500 to see if that helps
-
Same here. Switch the modem code back to default but keeping hardware acceleration & the MTU lowered to 1500 to see if that helps
Keep us updated, thanks.
-
So with the default modem code with hardware acceleration & the MTU at 1500 the connection is unusable. Line stays up but my router can't hold a stable PPPoE session over it.
Switched hardware acceleration back off and am just keeping the MTU at 1500 to see if the packet loss issue still happens. Luckily hardware acceleration doesn't need a reboot to change so hoping I'll avoid punishment from the DLM gods for all the experimenting.
-
So with the default modem code with hardware acceleration & the MTU at 1500 the connection is unusable. Line stays up but my router can't hold a stable PPPoE session over it.
Switched hardware acceleration back off and am just keeping the MTU at 1500 to see if the packet loss issue still happens. Luckily hardware acceleration doesn't need a reboot to change so hoping I'll avoid punishment from the DLM gods for all the experimenting.
The DLM gods punished me ;D, thanks again for update.
-
I cant see much difference in the changelog between 4.0.5 and 4.1.1?
ftp://ftp.draytek.com/Vigor166/Firmware/
-
Looks like changing the MTU from 1520 to 1500 solved the issues I was seeing. Connected around 3pm yesterday and still up with no packet loss issues.
(https://www.thinkbroadband.com/broadband/monitoring/quality/share/thumb/a4fb7a71aa4e478dd660e5fb4b0cce058f4d59eb-14-01-2021.png) (https://www.thinkbroadband.com/broadband/monitoring/quality/share/a4fb7a71aa4e478dd660e5fb4b0cce058f4d59eb-14-01-2021)
Sync is a little lower then my 130 was but that could be due to swapping modems several times.
-
Glad changing the MTU sorted your issues out, for myself the loss of 8Mbps after 24 hours is a no go, and the doubling of my ping as well along with the massive upload spikes doing a speedtest on TTB, 300-400ms when its normally 20ms on my current modem shows something isn't right for me still. Hope it continues to work well for you. Whats your speedtest like on upload? Also if you dont mind me asking whats the amount dropped from the 130 throughput wise.
-
That's the current status of my Vigor 166: how bad is it?
(https://www.thinkbroadband.com/broadband/monitoring/quality/share/thumb/ddcdaa1ea17ca65ea19f892c76c2f1e75590f8d3-14-01-2021.png) (https://www.thinkbroadband.com/broadband/monitoring/quality/share/ddcdaa1ea17ca65ea19f892c76c2f1e75590f8d3-14-01-2021)
-
That's the current status of my Vigor 166: how bad is it?
(https://www.thinkbroadband.com/broadband/monitoring/quality/share/thumb/ddcdaa1ea17ca65ea19f892c76c2f1e75590f8d3-14-01-2021.png) (https://www.thinkbroadband.com/broadband/monitoring/quality/share/ddcdaa1ea17ca65ea19f892c76c2f1e75590f8d3-14-01-2021)
Do you know what it was like with your previous modem? Those spikes regular could be caused by the router (see "My graph has lots of very regularly spaced yellow spikes on it!" on https://www.thinkbroadband.com/faq/broadband-quality-monitor)
-
That's the current status of my Vigor 166: how bad is it?
(https://www.thinkbroadband.com/broadband/monitoring/quality/share/thumb/ddcdaa1ea17ca65ea19f892c76c2f1e75590f8d3-14-01-2021.png) (https://www.thinkbroadband.com/broadband/monitoring/quality/share/ddcdaa1ea17ca65ea19f892c76c2f1e75590f8d3-14-01-2021)
Did you change your MTU to 1500?
-
Did you change your MTU to 1500?
Yes, since day 1
-
Yes, since day 1
Could I ask what router you are using?
-
Could I ask what router you are using?
OPNsense
-
OPNsense
I've been advised turning the MTU down to 1492 might help further but not trying it myself at the moment as I want to leave my line stable for a few days.
-
I've been advised turning the MTU down to 1492 might help further but not trying it myself at the moment as I want to leave my line stable for a few days.
Done, let's see if it makes any difference, thanks.
-
Done, let's see if it makes any difference, thanks.
I’ve also been on to tech support and the same advice is to try 1492. Am testing now.
-
I've been advised turning the MTU down to 1492 might help further but not trying it myself at the moment as I want to leave my line stable for a few days.
That great, thanks for the info. I’m using a RAX120 so that could be why I don’t have your latency at night possibly.
-
That great, thanks for the info. I’m using a RAX120 so that could be why I don’t have your latency at night possibly.
I've got a Ubiquiti UDM Pro, but my line has always had pretty variable latency. I'm guessing there is either a lot of cross-talk (the cabinet refuses to turn on downstream vectoring), or congestion from the cabinet as the latency increases early morning even if my line itself is idle.
-
I’m still seeing large latency on the upload on thinkbroadband test compared to the HG612 but I’ve QoS on the upload on the 612 and so I’m not sure if that and being a different chipset is the cause.
I’m a router guy so never spent much time on the modem side so a learning curve hear.
-
Still having dropped packets and I’ve used PingPlotter to look more at it. A simple small photo sending to a friend results in drop packets, send a photo to myself on say iMessage results in drop packets.
I’ll leave it on for to night with thinkbroadband monitoring going.
Here’s a link to the live monitoring if anyone wishes to look.
https://www.thinkbroadband.com/broadband/monitoring/quality/share/9c9377a3e70d21f7b9bdec1a6705a614c8c6385d
-
Still having dropped packets and I’ve used PingPlotter to look more at it. A simple small photo sending to a friend results in drop packets, send a photo to myself on say iMessage results in drop packets.
I’ll leave it on for to night with thinkbroadband monitoring going.
Here’s a link to the live monitoring if anyone wishes to look.
https://www.thinkbroadband.com/broadband/monitoring/quality/share/9c9377a3e70d21f7b9bdec1a6705a614c8c6385d
Without some sort of QoS it isn't unusual to see packet loss when a line is busy, especially as pings can be dropped sooner then other traffic by some routers. Though I'd be surprised if iMessage was pushing enough traffic to trigger it on it's own without something being wrong somewhere.
I'm using smart queues on my UDM Pro which is the equivalent of share evenly traffic shaping in OPNsense (https://docs.opnsense.org/manual/how-tos/shaper_share_evenly.html). I do have to cap it at a couple of Mb below my sync speed but it means even a heavy download won't cause enough of a latency change to be a problem for video calls. I'm happy to trade a bit of speed for the stability it gives.
-
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.
-
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.
-
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!
-
I hope that Draytek are watching this thread...
-
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 : < ----- >
-
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.
-
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.
-
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.
-
Is anyone willing to open the casing and give a picture of the printed circuit board?
-
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.
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 : < ----- >
-
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 ;)
-
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.
-
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
> 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 ----
>
-
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)
-
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 -
> 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 ----
-
Those stats look odd.
Retx (G.INP) shown as enabled on upstream and downstream.
Interleave depth suggests otherwise.
Error counts look broken. Not even a single FEC.
If everyone else is showing 0 errors in every field then those are being incorrectly reported.
Can't trust anything you read in those stats.
Safe to say with 2 of you suffering a drop in SNRM target that the error counts are far from zero.
-
Safe to say with 2 of you suffering a drop in SNRM target that the error counts are far from zero.
Yep - this isn't right for sure. Is anyone from Draytek on these forums? Dunno whether to switch back to the old modem.
-
Going though I've noticed two of the fields are showing different byte ordering, which might explain some of the stats weirdness of it is getting the endianness of some of the fields wrong
166 - CO ITU Version[0] : 00b54442 CO ITU Version[1] : 4d43a1a4
130 - CO ITU Version[0] : b5004244 CO ITU Version[1] : 434da4a1
I've reported to Draytek & pointed them at this thread.
-
Those stats look odd.
Retx (G.INP) shown as enabled on upstream and downstream.
Interleave depth suggests otherwise.
Error counts look broken. Not even a single FEC.
If everyone else is showing 0 errors in every field then those are being incorrectly reported.
Can't trust anything you read in those stats.
Safe to say with 2 of you suffering a drop in SNRM target that the error counts are far from zero.
I’ve had 3 so far and yes we spotted 0 errors too and thought it can’t be right. I’m down 14mbps on download.
Yes I can solve issues using a SQM but I’m fairly sure there is something going on as a 3.5mb picture should not be hogging 11Mbps up went sent and causing packet loss.
It’s the same for my friend so we are stumped at the moment and just feel it’s like a early release router waiting for firmware fixes, oh the joy of WiFi 6 all over again lol.
-
Going though I've noticed two of the fields are showing different byte ordering, which might explain some of the stats weirdness of it is getting the endianness of some of the fields wrong
166 - CO ITU Version[0] : 00b54442 CO ITU Version[1] : 4d43a1a4
130 - CO ITU Version[0] : b5004244 CO ITU Version[1] : 434da4a1
I've reported to Draytek & pointed them at this thread.
That’s great, thanks as I’m also in touch with them too but before I go back I want to see what they suggested with the MTU.
Switched back to my normal router and I’ll see what happens over the weekend.
-
Has anyone on here successfully used the modem without speed implications or performance issues in the UK?
I'm down to 1492 MTU now and will hold my breath overnight. If it drops again this things coming out.
-
Has anyone on here successfully used the modem without speed implications or performance issues in the UK?
I'm down to 1492 MTU now and will hold my breath overnight. If it drops again this things coming out.
I decided to keep it as I want to test that with the G.fast line (it will go live hopefully in three weeks).
I noticed no difference with MTU=1500 (1508 bay jumbo) or 1492.
I'm sharing my stats:
DrayTek> vdsl status
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 79996000 bps US Actual Rate : 20000000 bps
DS Attainable Rate : 80563990 bps US Attainable Rate : 29625626 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 1 US Interleave Depth : 1
NE Current Attenuation : 13 dB Cur SNR Margin : 6 dB
DS actual PSD : 1. 4 dB US actual PSD : 1. 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 : 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 : 12 dB
CO ITU Version[0] : 00b54649 CO ITU Version[1] : 4e5406b2
DSLAM CHIPSET VENDOR : < ----- >
(https://www.thinkbroadband.com/broadband/monitoring/quality/share/thumb/6c60d53ef4b1cecba6c4238fdb79b4ff87f67299-15-01-2021.png) (https://www.thinkbroadband.com/broadband/monitoring/quality/share/6c60d53ef4b1cecba6c4238fdb79b4ff87f67299-15-01-2021)
-
Has anyone on here successfully used the modem without speed implications or performance issues in the UK?
I'm down to 1492 MTU now and will hold my breath overnight. If it drops again this things coming out.
I swapped out an MT992 with the 166 in the UK on BT network.
I am on the Fibre 100 g.fast product which gives me speeds of up to 160mbps downstream. Looking at the max achievable rate I could go up to around 210mbps if I had the Fibre 250 product.
The MT992 used to drop around once a day. Since installing the 166 I've not yet had a drop other than when I've manually rebooted. Much improved. DSL checker shows improved figures than with the MT992.
I do not seem to have any problems with packet loss whatsoever, with my MTU left at its default setting perhaps I'm just lucky?
-
My line is getting absolutely destroyed by SNR margin increases. Up another db over night from 4 to 5 resulting in yet more speed loss. I'm going back to the old modem for now.
> vdsl status
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 61063000 bps US Actual Rate : 19152000 bps
DS Attainable Rate : 64587240 bps US Attainable Rate : 19148000 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 : 5 dB
DS actual PSD : 12. 8 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 : 2
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 : < ----- >
> 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 235 (symbols)
INTLVDelay : 100 0 (1/100 ms)
NFEC : 254 244
RFEC : 14 8
LSYMB : 5096 16764
INTLVBLOCK : 127 244
AELEM : 0 ----
>
Edit - old modem back in and clawed some speed back, still stuck at 5db SNR target obviously but hope that reverts to 3db as previous over the coming days. New stats below if anyones interested. These modems are definitely broken for non-G.fast connections.
/usr/sbin/xdslctl: ADSL driver and PHY status
Status: Showtime
Last Retrain Reason: 0
Last initialization procedure status: 0
Max: Upstream rate = 19058 Kbps, Downstream rate = 69496 Kbps
Bearer: 0, Upstream rate = 19058 Kbps, Downstream rate = 68833 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): 5.2 6.0
Attn(dB): 16.6 0.0
Pwr(dBm): 13.1 6.9
VDSL2 framing
Bearer 0
MSGc: -6 21
B: 243 239
M: 1 1
T: 0 64
R: 10 14
S: 0.1129 0.4007
L: 18002 5071
D: 8 1
I: 254 127
N: 254 254
Q: 8 0
V: 0 0
RxQueue: 77 0
TxQueue: 11 0
G.INP Framing: 18 0
G.INP lookback: 11 0
RRC bits: 0 24
Bearer 1
MSGc: 154 -6
B: 0 0
M: 2 0
T: 2 0
R: 16 0
S: 6.4000 0.0000
L: 40 0
D: 3 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 22007
OHFErr: 0 0
RS: 4941880 1408170
RSCorr: 17 0
RSUnCorr: 0 0
Bearer 1
OHF: 8777 0
OHFErr: 0 0
RS: 87159 0
RSCorr: 0 0
RSUnCorr: 0 0
Retransmit Counters
rtx_tx: 9038716 0
rtx_c: 0 0
rtx_uc: 0 0
G.INP Counters
LEFTRS: 0 0
minEFTR: 68822 0
errFreeBits: 148043 0
Bearer 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 18664287 0
Data Cells: 1070036 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 0
SES: 0 0
UAS: 29 29
AS: 141
Bearer 0
INP: 58.00 0.00
INPRein: 1.00 0.00
delay: 0 0
PER: 0.00 6.43
OR: 0.01 33.55
AgR: 68903.88 19091.40
Bearer 1
INP: 4.50 0.00
INPRein: 4.50 0.00
delay: 3 0
PER: 16.06 0.01
OR: 79.68 0.01
AgR: 79.68 0.01
Bitswap: 51/51 2/2
Total time = 2 min 50 sec
FEC: 17 0
CRC: 0 0
ES: 0 0
SES: 0 0
UAS: 29 29
LOS: 0 0
LOF: 0 0
LOM: 0 0
Retr: 0
-
The MT992 used to drop around once a day. Since installing the 166 I've not yet had a drop other than when I've manually rebooted.
How can you even tell it's the MT992 dropping sync?
It has zero stats to show sync has dropped and resyncs only take a couple seconds.
-
My line stayed up overnight, SNR still 4 however I’ve reset the MTU to 1500 as started getting constant low level packet loss.
-
My line stayed up overnight, SNR still 4 however I’ve reset the MTU to 1500 as started getting constant low level packet loss.
I run a lot of backups overnight which results in a good 3 hours of upload maxxed out, so i wonder if thats got anything to do with it. may be making it worse for me.
Do you know if the SNR stats on the draytek are showing the same for upload and download? on my old modem my upload has a different SNR to the download under g.inp, i wonder if the upload requires 6db to be stable and the download required 3db, but the draytek was forcing the same SNR for up and down, causing stability issues on the up, then dropping the SNR for both? (i dont know enough about networking if i'm honest!)
-
I run a lot of backups overnight which results in a good 3 hours of upload maxxed out, so i wonder if thats got anything to do with it. may be making it worse for me.
Do you know if the SNR stats on the draytek are showing the same for upload and download? on my old modem my upload has a different SNR to the download under g.inp, i wonder if the upload requires 6db to be stable and the download required 3db, but the draytek was forcing the same SNR for up and down, causing stability issues on the up, then dropping the SNR for both? (i dont know enough about networking if i'm honest!)
The UI shows the same up and down but the "vdsl status" command shows 4 down, 5 up. I trust the "vdsl status" value as that matches the 130's value and my upstream speed is the same
-
How can you even tell it's the MT992 dropping sync?
It has zero stats to show sync has dropped and resyncs only take a couple seconds.
Hi are you U.K. based as I noticed Annex B was being used in your older modem stats?
-
Hi are you U.K. based as I noticed Annex B was being used in your detailed stats?
I think you may have quoted the wrong person as I haven't posted any stats in this thread.
The UK uses Annex A infrastructure (POTS) with an Annex B bandplan on VDSL2.
The Draytek shows this nicely...
ATU-R Info (hw: annex A, f/w: annex A/B/C)
Hardware Annex A, firmware Annex B is used on VDSL2.
Broadcom modems report the bandplan Annex...
Mode: VDSL2 Annex B
-
I think you may have quoted the wrong person as I haven't posted any stats in this thread.
The UK uses Annex A infrastructure (POTS) with an Annex B bandplan on VDSL2.
The Draytek shows this nicely...
Hardware Annex A, firmware Annex B is used on VDSL2.
Broadcom modems report the bandplan Annex...
I have, multi tasking with router firmware and testing is taking it toll 😊
-
How can you even tell it's the MT992 dropping sync?
It has zero stats to show sync has dropped and resyncs only take a couple seconds.
I cannot be certain it was the MT992, but the BT Smart hub 2 didn't suffer the same daily loss of DSL sync. The Draytek seems to be more stable so far than the MT992 but its early days. I am disappointed with the lack of line stats, not really much more than the MT992 - at least I know the SNR now!
-
Just had a resync and my SNR has now been increased to 5. I've now swapped back to my old Vigor 130 until they've figured out whatever firmware bug is causing this. Hopefully I'll gain my 4mb of speed back by then too.
-
Ive had no more re syncs for a few days now, I hope you get your 4Mbps back. As log as I can stream UHD and video chat I'm happy in on a almost full cab and a max rate on my line of 53Mbps down and 15 up (which I get.) When I started out on FTTC in 2013 I could get 69Mbps Down and 17Mbps up. The joys of crosstalk and ECI cabs. ;)
-
No more drops for me either. I’ve got to contact support to let them know my results.
-
I see that a Vigor 166 on G.FAST is working well, but all of these other reports are on FTTC.
-
4.1.1 BT is Initial firmware for UK/Ireland I'm sure there will be improvements as more firmware becomes available.
-
Ive had no more re syncs for a few days now, I hope you get your 4Mbps back. As log as I can stream UHD and video chat I'm happy in on a almost full cab and a max rate on my line of 53Mbps down and 15 up (which I get.) When I started out on FTTC in 2013 I could get 69Mbps Down and 17Mbps up. The joys of crosstalk and ECI cabs. ;)
I used to get mid 70's on a Huawei cabinet but now it is full and for some reason no vectoring, so stuck with mid 60's at best. Not going to risk leaving it connected until I know what is going on. Bad experience last April when a 12 hour cabinet/exchange faulty back left my line stuck at 40mb. That time I ended up switching ISPs at my previous one refused to acknowledge a sync speed 15mb below the handback threshold for my line was actually a fault.
-
and for some reason no vectoring
OpenReach don't deploy Vectoring on any of their commercially funded VDSL2 cabinets.
It's only used on specific targeted BDUK funded cabinets to increase the number of properties that can achieve SuperFast speeds (30Mb/s+).
Cabinets with VDSL2 Vectoring in the UK are few and far between.
-
I used to get mid 70's on a Huawei cabinet but now it is full and for some reason no vectoring, so stuck with mid 60's at best. Not going to risk leaving it connected until I know what is going on. Bad experience last April when a 12 hour cabinet/exchange faulty back left my line stuck at 40mb. That time I ended up switching ISPs at my previous one refused to acknowledge a sync speed 15mb below the handback threshold for my line was actually a fault.
The best option is open a support ticket with them so they are aware of any issues. Ive never dealt with DrayTek before but so far support has started well.
My self and my friend do this with NG but it’s different there as we have a more formal relationship with them but normally it helps and we’ve seen firmware fixes for bugs we’ve seen patched fairly quickly.
-
The best option is open a support ticket with them so they are aware of any issues. Ive never dealt with DrayTek before but so far support has started well.
My self and my friend do this with NG but it’s different there as we have a more formal relationship with them but normally it helps and we’ve seen firmware fixes for bugs we’ve seen patched fairly quickly.
I've already got a support request open with them & have sent them the details of the speed drops.
-
That’s great :) I’ve got to contact them shortly with my findings so hopefully something good will come from it.
-
Any update from anyone else? Support basically told me to do a snr tweak without understanding the issues. They do seem to be looking in to the vdsl status reporting being untrustworthy though. Mines still unplugged :'(
-
Any update from anyone else? Support basically told me to do a snr tweak without understanding the issues. They do seem to be looking in to the vdsl status reporting being untrustworthy though. Mines still unplugged :'(
I’ve just sent some info to them. Waiting to hear back. I take it they want you to lower your SNR to 3db.
-
I’ve just sent some info to them. Waiting to hear back. I take it they want you to lower your SNR to 3db.
They do indeed! Well they actually told me to raise it "if it wasnt high enough" - So i'm not convinced i'm through to the right department just yet....
-
Mines still on so once they give me further instructions I’ll do as they say. So far supports been fast and pretty good.
-
Was it ever confirmed what chipset brand/model is being used?
Intel AnyWAN SoC GRX350 + Intel AnyWAN Transceiver VRX618 (Gen1)
-
1st post - Hi all!
I just acquired the Vigor 166 (UK version) and an Asus ax11000 to connect to our current service (BT Infinity 2 FTTC 76/20). We've had this service since 2011 and over the years acquired every model of BT hub as the only fix BT seem to have to any complaint is to send a new hub. As it happens, I also still have the old HG612 3B from years ago.
First, hopefully this saves someone else time as I wasted a good day trying to figure this one out: The 166 UK manual clearly states that the default IP of the modem is 192.168.1.1, this is :no: It is actually 192.168.2.1
I saw coincidentally that the v130 ip is different and I was out of options so thought worth the punt, and it worked
Second, after setting up and connecting everything together, the WAN connection keeps cycling on/off every 5-10 minutes.
After some fruitless troubleshooting (the Router logs only show that WAN was terminated) and not being able to access the Modem's webui (because of the IP issue I mentioned above), I swapped the Draytek for the HG612 and its been steady for 24hrs without any disconnects.
I will post a follow-up once I find the time to reconnect the Draytek and be able to access the webUI to get more info about why it might be disconnecting (SNR? DLM?). Any suggestions?
FYI
1) the UK version ships already in bridge mode (with service tag 101 configured) so in theory should work out of the box
2) connecting master socket--> v166 modem -->Router
3) The router WAN config was copied from the HH (PPPoE, username, dynamic IP)
4) everything booted up, lights green, internet working but disconnects and reconnects every 5-10 mins
-
That’s strange as the manual in mine states 192.168.2.1.
Did you turn off the Asus before connection?
On the modem a lot of us have altered the MTU to 1500 as per support recommendation.
Why did you copy the HH info over to the Asus? Surely on setup it will pick up your PPPoE connection and you just type in your username and password and the router will add all the info that’s required to get a connection.
On the box does yours say 166k?
There’s also a sticker that’s says applied area U.K. with the flag.
-
1st post - Hi all!
Second, after setting up and connecting everything together, the WAN connection keeps cycling on/off every 5-10 minutes.
@Galaleo Hi! Welcome to Kitz
There's a couple of options here if the rest of the household does not object:
- Put the Vigor 166 in router mode, enter your username and password directly and see if disconnects after 5 - 10 minutes.
- Leave the Vigor 166 in bridge mode, directly connect it to a firewalled pc and create a ppp connection using your username and password and see if it connects.
- Will prove if the 166 is holding the connection.
- Will prove if the Asus is forcing the reauthentication.
[Moderator edited to fix the two ordered lists.]
-
Thanks so much for the reply!
That’s strange as the manual in mine states 192.168.2.1.
Perhaps you have a different version?
I downloaded the user guide from here - https://draytek.co.uk/support/downloads/vigor-166
On page 15 it says "the default IP address of Vigor router 192.168.1.1"
In hindsight, the screenshots the WebUI posted by @Robbie show the correct LAN IP (x.x.2.1)
Did you turn off the Asus before connection?
Yes. Asus and modem off. Switch on modem, wait for DSL light to be on, then switch router on.
On the modem a lot of us have altered the MTU to 1500 as per support recommendation.
Now that I am able to access the WebUI, I will definitely try it.
Why did you copy the HH info over to the Asus? Surely on setup it will pick up your PPPoE connection and you just type in your username and password and the router will add all the info that’s required to get a connection.
Sorry if I wasn't clear. When I connected to the Asus once it was up, I made sure WAN connection type was set to PPPoE, entered Username and password, and selected dynamic IP. I didn't copy anything else from the HH.
On the box does yours say 166k?
There’s also a sticker that’s says applied area U.K. with the flag.
Yes. I definitely have the UK version. says so on the box. Now that I have access to the webUI I can see it also has the OR Service Tag configured.
What I haven't done yet is check that my unit has the latest firmware.
Funny enough, I literally just got an email from BT, "We’ve added BT Halo 1 to your existing package for no extra cost." :lol:
-
1st post - Hi all!
I just acquired the Vigor 166 (UK version) and an Asus ax11000 to connect to our current service (BT Infinity 2 FTTC 76/20). We've had this service since 2011 and over the years acquired every model of BT hub as the only fix BT seem to have to any complaint is to send a new hub. As it happens, I also still have the old HG612 3B from years ago.
First, hopefully this saves someone else time as I wasted a good day trying to figure this one out: The 166 UK manual clearly states that the default IP of the modem is 192.168.1.1, this is :no: It is actually 192.168.2.1
I saw coincidentally that the v130 ip is different and I was out of options so thought worth the punt, and it worked
Second, after setting up and connecting everything together, the WAN connection keeps cycling on/off every 5-10 minutes.
After some fruitless troubleshooting (the Router logs only show that WAN was terminated) and not being able to access the Modem's webui (because of the IP issue I mentioned above), I swapped the Draytek for the HG612 and its been steady for 24hrs without any disconnects.
I will post a follow-up once I find the time to reconnect the Draytek and be able to access the webUI to get more info about why it might be disconnecting (SNR? DLM?). Any suggestions?
FYI
1) the UK version ships already in bridge mode (with service tag 101 configured) so in theory should work out of the box
2) connecting master socket--> v166 modem -->Router
3) The router WAN config was copied from the HH (PPPoE, username, dynamic IP)
4) everything booted up, lights green, internet working but disconnects and reconnects every 5-10 mins
I had no issues, sadly like you did. However my booklet also stated 192.168.2.1 as the login, You may need to factory reset the Asus after the update, Merlin does suggest this on smallnetbuilder. Also maybe change your MTU in the Vigor 166-K to either 1500 (1508 baby jumbo frames) or just 1500 as that may help also. Also what firmware is the Vigor running? It should be 4.11_BT. Good luck.
-
@Galaleo Hi! Welcome to Kitz
There's a couple of options here if the rest of the household does not object:
- 1. Put the Vigor 166 in router mode, enter your username and password directly and see if disconnects after 5 - 10 minutes
2. Leave the Vigor 166 in bridge mode, directly connect it to a firewalled pc and create a ppp connection using your username and password and see if it connects
1. Will prove if the 166 is holding the connection and 2. will prove if the Asus is forcing the reauthentication.
[/list]
Thank you, this is a really good suggestion. I might have to setup an alternative home wifi network (5G phone + Wireless AP) in the evening to keep the family happy while I run these tests. I will come back with results later.
-
I had no issues, sadly like you did. However my booklet also stated 192.168.2.1 as the login, also confused as to why you copied your dynamic IP when after setting up the Asus you would have been given a new IP, also did the Asus give you a firmware update? As most come with older firmware. You may need to factory reset the Asus after the update, Merlin does suggest this on smallnetbuilder. Hope Also maybe change your MTU in the Vigor 166-K to either 1500 (1508 baby jumbo frames) or just 1500 as that may help also. Also what firmware is the Vigor running? It should be 4.11_BT. Good luck.
Ah that’s great, is this your first third party router?
Killhippie has suggested a reset as I too am guessing it’s updated it’s firmware on setup like our Netgears routers do and sometimes you have low level code left in the NVram that creates issues so many of us factory reset after any type of firmware update.
-
), I swapped the Draytek for the HG612 and its been steady for 24hrs without any disconnects.
Then it isn't your Asus. Wasting your time factory reseting it.
Until they fix the stats (every single error figure is always zero, Retx is reported incorrectly also) there's absolutely no way to tell if the chipset is stable on your line.
The fact a few users have already had the DLM increase their SNRM targets shows the Draytek has a higher error rate than their previous modems.
Impossible to know just how bad the chipset/modem performs without the error counters being fixed.
Less of a problem for those on ECI cabinets with Interleaving.
Not so good for anyone on fastpath or G.INP with reduced SNRM.
-
They sent me a RC1 firmware. Its made no difference to missing line stats and no difference to slow speeds etc. 10mb down now on a 60mb line. :( support are responding daily though so hope we get somewhere soon.
-
Then it isn't your Asus. Wasting your time factory reseting it.
Until they fix the stats (every single error figure is always zero, Retx is reported incorrectly also) there's absolutely no way to tell if the chipset is stable on your line.
The fact a few users have already had the DLM increase their SNRM targets shows the Draytek has a higher error rate than their previous modems.
Impossible to know just how bad the chipset/modem performs without the error counters being fixed.
Less of a problem for those on ECI cabinets with Interleaving.
Not so good for anyone on fastpath or G.INP with reduced SNRM.
My friend is on an ECI cab and having the same issue and a reset while it may not cure it should be carried out and Merlin who codes for Asus has a post explaining why a reset should be carried out after firmware updates on Smallnetbuilders. Many of us who Beta test for Netgear for example or Alpha test will do this as standard practise to remove old code.
Saved config files should also never be used from one firmware to another as it introduces old code.
-
I also recommend performing a reset on Asus routers after upgrading firmware.
I do so on my Asus RT-AC68U running Merlin.
I was making the point that if it works with the HG612 then the above issue isn't the issue.
Hard to pinpoint the cause with so little stats.
-
The trouble is I’ve seen routers behave like this and a reboot fixed it for it to return later on so a reset while the modem was up and running would have been a good starting point.
-
They sent me a RC1 firmware. Its made no difference to missing line stats and no difference to slow speeds etc. 10mb down now on a 60mb line. :( support are responding daily though so hope we get somewhere soon.
Support have been back to me and I’ve had to try both DSL modem codes which resulted in a very slight drop but no improvement.
I would imagine we will see new firmware as time goes on. Just keep helping support and try to minimise the amount of reboots on the modem.
Ive lost around 12mbps but it’s fine for me as 50 down and 12 up is fine. New tech always brings its early issues so hang in there.
-
They sent me a RC1 firmware. Its made no difference to missing line stats and no difference to slow speeds etc. 10mb down now on a 60mb line. :( support are responding daily though so hope we get somewhere soon.
The speed loss could take weeks to undo once the firmware is sorted as it is likely to be reliant on the Openreach DLM deciding your line is once again worthy of extra speed. Otherwise I'd have gone my speed back when I reconnected by 130 but I haven't yet.
At least once the stats are sorted we'll be able to tell if what is going on.
-
Ive lost around 12mbps but it’s fine for me as 50 down and 12 up is fine. New tech always brings its early issues so hang in there.
Would be good advise if the DLM wasn't such a **** at relenting on its actions.
Some might never get back to the same lower SNRM target.
It's impossible to tell if each firmware is improving performance or making things worse without error counters.
The speed loss could take weeks to undo once the firmware is sorted as it is likely to be reliant on the Openreach DLM deciding your line is once again worthy of extra speed.
Exactly this.
Otherwise I'd have gone my speed back when I reconnected by 130 but I haven't yet.
I believe you need lower errors to get DLM to drop the target SNRM than you do to hold it at its current target.
Sometimes you need to cap your sync lower (or increase your SNRM in the case of Drayteks) to get the counters low enough for the DLM to drop the target. Even if it had previously dropped the target on its own.
Hopefully nobody in this thread has issues getting there sync back where it was.
At least once the stats are sorted we'll be able to tell if what is going on.
It would be the single biggest issue I'd be pushing Draytek to fix.
Have they acknowledged the issue or offered an ETA on a fix?
Also does anyone know if the EU model of the 166 has working accurate stats?
If it doesn't have working counters then it doesn't bode well for the UK model getting a fix anytime soon.
-
The speed loss could take weeks to undo once the firmware is sorted as it is likely to be reliant on the Openreach DLM deciding your line is once again worthy of extra speed. Otherwise I'd have gone my speed back when I reconnected by 130 but I haven't yet.
At least once the stats are sorted we'll be able to tell if what is going on.
Only thing is, when i plug the broadcom modem in i instantly get 7mb higher sync speed. So something weird is going on. Its not going back to where it was pre 166 destruction, but its notably higher instantly.
-
No stats are working but how to you verify any results if they are shown? I don’t believe half the stats I’ve seen on routers that work well so I’m not sure how you can verify what you see.
I’ve not asked them to fix or ETA that’s one thing a company never responds well too. Deadlines are rarely kept so I’m not pushing but working with support.
To be fair I’ve yet to see any tech come out as new without issues, from Cisco, ubiquity, NG or Asus. Part of the parcel when picking up new gear and yes there’s a risk of DLM.
I would imagine as it was delayed it’s another product where Covid has had its impact on its outcome a little just as it has with routers.
-
Would be good advise if the DLM wasn't such a **** at relenting on its actions.
Some might never get back to the same lower SNRM target.
It's impossible to tell if each firmware is improving performance or making things worse without error counters.
Exactly this.
I believe you need lower errors to get DLM to drop the target SNRM than you do to hold it at its current target.
Sometimes you need to cap your sync lower (or increase your SNRM in the case of Drayteks) to get the counters low enough for the DLM to drop the target. Even if it had previously dropped the target on its own.
Hopefully nobody in this thread has issues getting there sync back where it was.
It would be the single biggest issue I'd be pushing Draytek to fix.
Have they acknowledged the issue or offered an ETA on a fix?
Also does anyone know if the EU model of the 166 has working accurate stats?
If it doesn't have working counters then it doesn't bode well for the UK model getting a fix anytime soon.
I have to say the DLM is not that unrelenting monster people think it is, but yes banding can happen and most ISP's can if you get banded now get that removed, well I know my ISP can anyway. Draytec said it took longer than expected to get the BT firmware and the 166 out, its on initial firmware, I could put my ECI back (plays better than HG612's on my line) but that wont solve the issues present.
Like most routers I have had and beta tested it has bugs and the only way to resolve them is to help. Asking for a ETA will put pressure on any company and then more mistakes get made as they crunch to fix. I had one drop the day after the modem was placed after gaining a dizzying 3Mbps on my line. I can still stream UHD, game and do all the things I could before, yes my ping went up to 15ms from 7ms but thats hardly a disaster. DLM can take weeks to sort issues out but I feel making pre-emptive statements don't always help, so I don't know when and how long things will take sort so I'll sit and wait it out.
Giving Draytec what they need which is space (look at the disaster that was Cyberpunk 2077 was because developers were pushed to hard) Draytec and BT/OR will come up with new modem codes and firmware, in the mean time I shall use the modem provide stats as requested. After all I can use the net, I have still got good enough thoughput a loss on download of a small amount for at least myself is are not a worry. I am sure it will get fixed and like most things I would rather wait for a good patch than a rushed hotfix that causes more issues. :)
-
Only thing is, when i plug the broadcom modem in i instantly get 7mb higher sync speed. So something weird is going on. Its not going back to where it was pre 166 destruction, but its notably higher instantly.
That suggests the DSL driver is completely unoptimised for FTTC.
Any idea if you have a Huawei or Eci cabinet?
-
Thank you for all your suggestions - for now, v166 is connected and appears to be stable. I managed to find some time this evening to convince the tribe to use my phone's hotspot while I test a few things.
There was a question on if this is my first 3rd party router - its not, but the first in a few years.
Here is how I got on:
-I'm on a Huawei cabinet ~150m away. Just wanted to validate, as I know this could be a factor.
-Before disconnecting the HG612 3B (unlocked with Howlingwolf's firmware B030SP08), I checked the xDSL status page (attached). I'm not qualified to tell if this is all as it should be. My observation is the lower than expected downstream sync compared to attainable.
Swiftly moving on to the Draytek, connected it directly to the laptop and opened the webUI
-Firmware on the Vigor 166 is the 4.1.1 UK version
-Attempted to connect directly via PPPoE and then realized I have little time to learn how to do this in Windows 10.
-I changed the modem's LAN IP config so that it can work on my router's subnet with a static IP. I'm hoping this might help enable access the webUI later. Reboot and reconnect via laptop
-Left modem in bridge mode, set DSL mode to VDSL2 only, changed MTU to 1500 (reboot again)
-Connect P1 on Vigor to WAN port on router, and P2 to one of the LAN ports (this is also how I had the HG612 setup)
-Restart router, connect laptop to wifi, direct browser to the modem's LAN IP. Draytek login page loaded - at least this works!
-Check WAN status on router UI: connected. Public internet working.
-Back to the Draytek webUI. Sync rate same as the HG612 (59.9mbps down, 19.9mbps up), errors all 0, down SnR is lower (9dB vs 13.9dB)
-I spent a couple of hours checking the system logs on the router every few minutes, connection is still up.
So at least for now it appears to be working and stable. The next few days will tell more.
EDIT/UPDATE: after several hours of stability the WAN connection started to cycle again.
-
No stats are working but how to you verify any results if they are shown? I don’t believe half the stats I’ve seen on routers that work well so I’m not sure how you can verify what you see.
Which modem would that be?
The reported stats from Broadcom chipsets and the Lantiq chipsets used on previous Draytek modems match what is reported at the ISP end.
The stats that show the line profile matches the current DLM line profile.
They are all very accurate.
I've never seen a modem with access to the full Broadcom CLI or detailed Lantiq stats report incorrect error counters.
This Draytek isn't reporting incorrect error numbers either. That would actually be worse than the zero figures being shown.
The CLI also exposes the line stats but there was some oddities in this data and not all of it correlated with the GUI so there may be a mapping or lookup table issue somewhere:
(https://www.disco3.co.uk/gallery/albums/userpics/10700/normal_17-20200928_Vigor166_CLI_Modem_Stats.jpg)
Hey Robbie,
That's the EU version of the 166 yes?
It looks like it has the same 0 error counters as the UK model. Is that the case or was the screen grab taken immediately after sync?
-
Thank you for all your suggestions - for now, v166 is connected and appears to be stable. I managed to find some time this evening to convince the tribe to use my phone's hotspot while I test a few things.
There was a question on if this is my first 3rd party router - its not, but the first in a few years.
Here is how I got on:
-I'm on a Huawei cabinet ~150m away. Just wanted to validate, as I know this could be a factor.
-Before disconnecting the HG612 3B (unlocked with Howlingwolf's firmware B030SP08), I checked the xDSL status page (attached). I'm not qualified to tell if this is all as it should be. My observation is the lower than expected downstream sync compared to attainable.
Swiftly moving on to the Draytek, connected it directly to the laptop and opened the webUI
-Firmware on the Vigor 166 is the 4.1.1 UK version
-Attempted to connect directly via PPPoE and then realized I have little time to learn how to do this in Windows 10.
-I changed the modem's LAN IP config so that it can work on my router's subnet with a static IP. I'm hoping this might help enable access the webUI later. Reboot and reconnect via laptop
-Left modem in bridge mode, set DSL mode to VDSL2 only, changed MTU to 1500 (reboot again)
-Connect P1 on Vigor to WAN port on router, and P2 to one of the LAN ports (this is also how I had the HG612 setup)
-Restart router, connect laptop to wifi, direct browser to the modem's LAN IP. Draytek login page loaded - at least this works!
-Check WAN status on router UI: connected. Public internet working.
-Back to the Draytek webUI. Sync rate same as the HG612 (59.9mbps down, 19.9mbps up), errors all 0, down SnR is lower (9dB vs 13.9dB)
-I spent a couple of hours checking the system logs on the router every few minutes, connection is still up.
So at least for now it appears to be working and stable. The next few days will tell more.
Sounds like it not dropping any more which is good. Monitor the router to insure it’s working correctly, it should be nice and stable now as the firmware is pretty much matured on the Broadcom chipset side.
See how your connection goes now.
-
Good morning! Unfortunately the stability didn't last. after about 4.5 hours of being up and running, from 1 am this morning the WAN link started cycling every 5-10 minutes and continued non-stop through the night.
Router system logs full of these messages:
Jan 21 06:19:16 pppd[6296]: Serial link appears to be disconnected.
Jan 21 06:19:19 WAN Connection: Fail to connect with some issues.
Jan 21 06:19:22 pppd[6296]: Connection terminated.
Jan 21 06:19:22 pppd[6296]: Modem hangup
Jan 21 06:19:32 pppd[6296]: Connected to 20:e0:9c:c2:49:dd via interface eth0
Jan 21 06:19:32 pppd[6296]: Connect: ppp0 <--> eth0
Jan 21 06:19:32 pppd[6296]: CHAP authentication succeeded
Jan 21 06:19:32 pppd[6296]: peer from calling number 20:E0:9C:C2:49:DD authorized
Jan 21 06:19:32 pppd[6296]: local IP address x.x.x.x
Jan 21 06:19:32 pppd[6296]: remote IP address x.x.x.x
Jan 21 06:19:32 pppd[6296]: primary DNS address 81.139.57.100
Jan 21 06:19:32 pppd[6296]: secondary DNS address 81.139.56.100
Jan 21 06:19:33 wan: finish adding multi routes
Jan 21 06:19:35 WAN Connection: WAN was restored.
I noticed that the Draytek webUI does not have a facility to show logs. Is there a way to easily check these from CLI? I don't know what command to run once logged in via telnet/ssh or where the logs would be...
Swiftly switched back to the HG612 before I start hearing complaints :D
Will try to find time this weekend to run some tests with the Draytek in router mode.
-
-Before disconnecting the HG612 3B (unlocked with Howlingwolf's firmware B030SP08), I checked the xDSL status page (attached). I'm not qualified to tell if this is all as it should be. My observation is the lower than expected downstream sync compared to attainable.
It would appear your line has been banded by DLM in the H612 stats page, usually due to many disconnects or high/bursts of errors. This can be seen from the 60MBit sync with very high SNR. So something is amiss with the line if this hadn't happened before you started changing routers, as well as now the possible V.166 issues.
-
Morning all - kept the Draytek in overnight and got moved again from a SNRM of 5db to 6db so i'm down even more on speed again. This thing is a disaster!
-
Hi, can you test the baby jumbo frame support please. You will need to set MTU to 1500 (1508).
Linux command:
ping -c4 -M do -s 1472 1.1.1.1
Windows command:
ping -f -l 1472 1.1.1.1
Thanks, ;D
I tried using my UK model in Router mode on G.Fast but the default setting for the MTU is 1520, which I'm sure is too high.
Some reviews say set to 1500 others 1508, anyone know which is correct?
Whilst the modem mode seems to be tuned for BT use the same doesn't seem to be true for router mode (unless I'm missing something?)
-
I tried using my UK model in Router mode on G.Fast but the default setting for the MTU is 1520, which I'm sure is too high.
Some reviews say set to 1500 others 1508, anyone know which is correct?
Whilst the modem mode seems to be tuned for BT use the same doesn't seem to be true for router mode (unless I'm missing something?)
1500 for the Vigor 166, 1508 for your routers ethernet WAN port.
-
1500 for the Vigor 166, 1508 for your routers ethernet WAN port.
Ah, I've obviously missed a setting then!
I only saw 1 MTU setting in the 166, but as it's being used in router mode there must be a 2nd setting somewhere (probably for the WAN)
-
If you're using the Vigor 166 also as a router, then it's important you set up the 'correct' value there, i.e. if you are on a PPPoE connection then use 1508 (if you want the so called 'baby jumbo frames' and the MTU final value will be 1500), and if you are on a DHCP/IPoE connection just use 1500.
I'm on a PPPoE connection and frankly I see no tangible difference between MTU 1508 (=1500) or 1492.
-
Thanks for the info, I'm sure these niggles will be ironed out in future firmware updates, I'll tweak it down from 1520 to 1508
The default value of 1520 (which is also the max. value) does work but I don't know what the negative effects of a setting this high are.
-
They sent me a RC1 firmware. Its made no difference to missing line stats and no difference to slow speeds etc. 10mb down now on a 60mb line. :( support are responding daily though so hope we get somewhere soon.
They also sent me a beta firmware, 423RC1, and in case I won't bother to install it. Can you confirm you've tried that RC1 firmware and still no errors/stats showing?
Thanks.
-
They also sent me a beta firmware, 423RC1, and in case I won't bother to install it. Can you confirm you've tried that RC1 firmware and still no errors/stats showing?
Thanks.
Firmware Version: 4.2.3_RC1_BT
Edit - FYI - System Up Time: 42:37:55
No line stats, but i dont think it made anything "worse" - i had a stable line overnight for the first time ever at 6db, but i'm down from 3db and 71mb sync to 6db and 59mb now. Dont see any harm in installing it and also trying?
Edit 2 - I am going round in circles with support who dont seem to acknowledge there is an issue with the modem. I get one email back every day or two without actually improving anything. The latest email reads "SNR value and the DSL stats aside, could you help clarify the issue you are experincing with the V166 modem?", after multiple emails fully explaining and providing all line stats, it appears they don't see the huge drops in stablility as a fault. Getting a little fed up now.
vdsl status more
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 : 59564000 bps US Actual Rate : 19977000 bps
DS Attainable Rate : 59890368 bps US Attainable Rate : 20238000 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 8 US Interleave Depth : 4
NE Current Attenuation : 17 dB Cur SNR Margin : 6 dB
DS actual PSD : 12. 8 dB US actual PSD : 7. 1 dB
NE CRC Count : 0 FE CRC Count : 0
NE ES Count : 0 FE ES Count : 0
Xdsl Reset Times : 0 Xdsl Link Times : 2
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 : 6 dB
CO ITU Version[0] : 00b54442 CO ITU Version[1] : 4d4390c1
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 : 225 235 (symbols)
INTLVDelay : 0 0 (1/100 ms)
NFEC : 255 244
RFEC : 10 8
LSYMB : 5251 15498
INTLVBLOCK : 255 244
AELEM : 0 ----
>
-
... after multiple emails fully explaining and providing all line stats, it appears they don't see the huge drops in stablility as a fault. Getting a little fed up now.
Because it's not a fault. It's how the chipset performs on your line. I wouldn't touch Lantiq/Intel when I was on VDSL2 or ADSL2+, and I would still be a bit wary now on G.fast.
I would be fed up, too. But I would just return it and find an equivalent Broadcom-based product.
If there is a firmware that comes out that somehow manages to "fix" this and get everyone back up and running on 3 dB, I will eat my words.
I am not denying there might be issues on the router side that can be fixed, but the modem is held back by the chipset.
-
Because it's not a fault. It's how the chipset performs on your line. I wouldn't touch Lantiq/Intel when I was on VDSL2 or ADSL2+, and I would still be a bit wary now on G.fast.
I would be fed up, too. But I would just return it and find an equivalent Broadcom-based product.
If there is a firmware that comes out that somehow manages to "fix" this and get everyone back up and running on 3 dB, I will eat my words.
I am not denying there might be issues on the router side that can be fixed, but the modem is held back by the chipset.
Thank you! really good points and I haven't actually thought about it that way. I just assume that when draytek release a modem like this, it should at least be comparable / within 5% of alternatives. But i'm learning the hard way that the chipset is a huge factor that i didnt really take in to consideration. Are others on vdsl going to do the same thing or wait out and hope? Can you recommend any broadcom based modems which are decent?
-
Mines still up and being a beta tester for other manufacturers I’m more than happy to help out regardless of the time scale, so in between testing routers I’ll help out with the modem.
No issues with support so far.
-
Can you recommend any broadcom based modems which are decent?
I typically only use modem-router combos - if you are looking for a modem-only device, I cannot advise.
For some time I used a Billion BiPac 8800NL (not R2) in bridge mode for its modem when I was on VDSL2 - lacking jumbo frame support, if that's something you really care about. Pretty sure it's EOL now anyway.
I found the Zyxel XMG3927-B50A to be a great modem-router combo on G.fast, and I imagine VDSL2 performance would be just as good. Would be overkill to use as only a modem, however.
-
Thank you for all your suggestions - for now, v166 is connected and appears to be stable. I managed to find some time this evening to convince the tribe to use my phone's hotspot while I test a few things.
There was a question on if this is my first 3rd party router - its not, but the first in a few years.
Here is how I got on:
-I'm on a Huawei cabinet ~150m away. Just wanted to validate, as I know this could be a factor.
-Before disconnecting the HG612 3B (unlocked with Howlingwolf's firmware B030SP08), I checked the xDSL status page (attached). I'm not qualified to tell if this is all as it should be. My observation is the lower than expected downstream sync compared to attainable.
Swiftly moving on to the Draytek, connected it directly to the laptop and opened the webUI
-Firmware on the Vigor 166 is the 4.1.1 UK version
-Attempted to connect directly via PPPoE and then realized I have little time to learn how to do this in Windows 10.
-I changed the modem's LAN IP config so that it can work on my router's subnet with a static IP. I'm hoping this might help enable access the webUI later. Reboot and reconnect via laptop
-Left modem in bridge mode, set DSL mode to VDSL2 only, changed MTU to 1500 (reboot again)
-Connect P1 on Vigor to WAN port on router, and P2 to one of the LAN ports (this is also how I had the HG612 setup)
-Restart router, connect laptop to wifi, direct browser to the modem's LAN IP. Draytek login page loaded - at least this works!
-Check WAN status on router UI: connected. Public internet working.
-Back to the Draytek webUI. Sync rate same as the HG612 (59.9mbps down, 19.9mbps up), errors all 0, down SnR is lower (9dB vs 13.9dB)
-I spent a couple of hours checking the system logs on the router every few minutes, connection is still up.
So at least for now it appears to be working and stable. The next few days will tell more.
EDIT/UPDATE: after several hours of stability the WAN connection started to cycle again.
If you are using Merlin's firmware, here is a definitely working way of accessing modem interface through the router:
1. Give your modem an IP that is outside the router's ip range. (Your IP numbers 192.168.0.1 for modem and 192.168.1.1 for router are ok).
2. Enable jffs partition.
3. You need to add two scripts to the /jffs/scripts directory, namely wan-start and nat-start scripts.
wan-start script :
#!/bin/sh
ifconfig `nvram get wan0_ifname`:0 192.168.0.2 netmask 255.255.255.0
Note : the IP number shown in bold must be one more than your modem's IP. If your modem's ip is 192.168.0.1 then it must be written as 192.168.0.2.
[Moderator edited to add the bbc code markup for bold text at the IP address, so as to correspond with what is written in the above note.]
nat-start script :
#!/bin/sh
iptables -t nat -I POSTROUTING -o `nvram get wan0_ifname` -j MASQUERADE
Before adding scripts, you can check if this works for you easily. Just SSH to your router and enter the commands in the scripts (you can use copy-paste). Then open a browser session to your modem (192.168.0.1 in your case) and there is your modem interface.
Adding scripts just makes sure that the commands are run on router startup.
-
I see some EU retailers are now taking pre-orders for the 2nd generation (212Mhz) model (V166-A GEN 2).
The price seems to be about the same as the GEN 1.
-
Not sure Gen 2 is worth it tbh as I cant see BT using G.Fast 212Mhz for quite a while and the Gen 1 is capable enough. I think we wont see a UK variant for a while as I don't know anywhere 212Mhz is being used, although I may be wrong there. FTTP is better than spending time sweating copper for those within a few hundred meters. G.Fast should have always been to the DP not the cab. Its really just a stop gap as I see it.
-
OpenReach originally talked about G.Fast being FTTrN (fibre to the remote node).
Something similar to how FTTP is deployed from the splitter works best, but even that is overkill
A single G.Fast pod serving multiple DP's.
Deeper in the network than the PCP but not right to the DP.
G.Fast to the DP would be madness. It's just overkill.
If you bring fibre that far then FTTP should be installed.
-
Its still sweating copper, its out of date, and with the dial tone being removed on new and in 5 years old lines, and with my ISP offering SOGEA now, a FTTP rollout instead of G.Fast would have been a better move. Have a nice Day.
-
Hi all
Just wanted to give a little update - I'm going to return the modem now. I've dropped from 71mb down to 52.6mb using this modem and it just gets worse every day. Thank you for all your help and advice - really great forum! wish you all the best of luck with this modem going forward!
> vdsl status
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 52617000 bps US Actual Rate : 18628000 bps
DS Attainable Rate : 60126500 bps US Attainable Rate : 18632000 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 4 US Interleave Depth : 1
NE Current Attenuation : 17 dB Cur SNR Margin : 6 dB
DS actual PSD : 11. 6 dB US actual PSD : 7. 1 dB
NE CRC Count : 0 FE CRC Count : 0
NE ES Count : 0 FE ES Count : 0
Xdsl Reset Times : 0 Xdsl Link Times : 6
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 : 6 dB
CO ITU Version[0] : 00b54442 CO ITU Version[1] : 4d4390c1
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 : 1 1
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 285 (symbols)
INTLVDelay : 100 0 (1/100 ms)
NFEC : 254 236
RFEC : 14 8
LSYMB : 4958 14319
INTLVBLOCK : 127 236
AELEM : 0 ----
>
-
No idea how you've lost so much throughput mines stayed the same for almost a week now. Guess you have a line issue or maybe its turning on and off to many times that's upset the DLM as the modem isn't causing those issues for me. Unless you had a faulty unit of course. Draytec Support have been most helpful too. The fact your inteleave depth is only 4 is odd as well. I would chat with your ISP as you are on fastpath.
-
Absolutely no idea! My service provider have been great and are issuing a DLM profile reset in the coming days so just going to use the old modem again. They said they can see the line has been capped. Draytek support have been very poor for me. After issuing me the beta (RC1) firmware and that not making any difference, they said they have passed to their 3rd Line support engineers and will let me know on an update. The next email i get 2 days later from them says 'our engineers have suggested you try this firmware xxxx'. This was just a link to the original firmware (its actually the direct link from the website) which gave me the problems in the first place. I gave them my final stats, told them to close the ticket and wished them well. Seems like a totally different experience for you.
-
The fact your inteleave depth is only 4 is odd as well. I would chat with your ISP as you are on fastpath.
Perfectly normal for G.INP for the interleave depth to be 4.
It's only 1 on ECI cabinets with no error protection enabled.
There's 3 members in this thread who have lost Downstream sync.
All have dropped sync because the DLM has increased the target SNRM. This happens due to an increase in errors.
If you don't have a 3, 4 or 5dB target then you wouldn't be affected.
-
Absolutely no idea! My service provider have been great and are issuing a DLM profile reset in the coming days so just going to use the old modem again. They said they can see the line has been capped. Draytek support have been very poor for me. After issuing me the beta (RC1) firmware and that not making any difference, they said they have passed to their 3rd Line support engineers and will let me know on an update. The next email i get 2 days later from them says 'our engineers have suggested you try this firmware xxxx'. This was just a link to the original firmware (its actually the direct link from the website) which gave me the problems in the first place. I gave them my final stats, told them to close the ticket and wished them well. Seems like a totally different experience for you.
Sorry to hear that you’ve not had much luck. I’m holding steady and support did ask me to alter my SNR but I’ve asked some more questions and waiting to hear back.
I’m not expecting an instant fix, just have to keeping working with support to aid them.
-
Perfectly normal for G.INP for the interleave depth to be 4.
It's only 1 on ECI cabinets with no error protection enabled.
There's 3 members in this thread who have lost Downstream sync.
All have dropped sync because the DLM has increased the target SNRM. This happens due to an increase in errors.
If you don't have a 3, 4 or 5dB target then you wouldn't be affected.
Now i've got the old modem back in i can see my SNRM for downstream is actually set at 8.7db!! (it was stable on 3 before), the downstream sync was just dropping consistently every single night. I couldnt keep holding out, may have ended up with adsl speeds!
Sorry to hear that you’ve not had much luck. I’m holding steady and support did ask me to alter my SNR but I’ve asked some more questions and waiting to hear back.
I’m not expecting an instant fix, just have to keeping working with support to aid them.
I really wanted to hold out, but the lack of true technical support from Draytek I personally received, and the consistent degredation of the line overnight has forced my hand somewhat. If i had of been stable at a reduced rate I'd have held but we are getting to the point where my actual day to day experience will be impacted from further drops so its just one of those things. Will be sure to keep an eye on the thread going forward!
-
Support is what it is, many are the same unless you have direct contact inside where it’s easier. I’m in the same boat as you as unlike the other companies I know I have no way to get to the engineers so it’s the long route with DrayTek.
-
I see that bitswap is disabled for both DS/US, do not know if this could cause more frequent resyncs. if some tones are affected and make the DLM take action. if it can affect the line then it can be turned on by CLI command as I believe there is no setting for it in the GUI. If ECI cabinets support bitswap after all
-
I see that bitswap is disabled for both DS/US, do not know if this could cause more frequent resyncs. if some tones are affected and make the DLM take action. if it can affect the line then it can be turned on by CLI command as I believe there is no setting for it in the GUI. If ECI cabinets support bitswap after all
Didnt notice that! My broadcom modem plugged in now says this - Bitswap: 1788/1794 288/288
Not actually sure about these technical things or what bitswap actually is(!) but seems like the broadcom is doing something on Bitswap, but the draytek wasn't.
Edit - then again, we actually have no idea if it was enabled, because the status pages are totally broken and misreporting!
-
Perfectly normal for G.INP for the interleave depth to be 4.
It's only 1 on ECI cabinets with no error protection enabled.
There's 3 members in this thread who have lost Downstream sync.
All have dropped sync because the DLM has increased the target SNRM. This happens due to an increase in errors.
If you don't have a 3, 4 or 5dB target then you wouldn't be affected.
Oddly I would have thought with such a loss of throughput G.INP would be changed to Interleave as Vdsl 2 can use much greater interleaving depths, the maximum interleaving depth is 3072 (for profile 17a) so 4 with that drop seems odd hence my mention of it. My Interleaving is 1087 when it was on fast path before the modem change, on an ECI cab. If the poster is on a Huawei cab I would have thought that interleaving would have been applied until the line was stable then G.INP reapplied at some point. Since not everyone is having re-syncs saying what cab they are on would help in this thread. What do you think?
-
Oddly I would have thought with such a loss of throughput G.INP would be changed to Interleave as Vdsl 2 can use much greater interleaving depths, the maximum interleaving depth is 3072 (for profile 17a) so 4 with that drop seems odd hence my mention of it. My Interleaving is 1087 when it was on fast path before the modem change, on an ECI cab. If the poster is on a Huawei cab I would have thought that interleaving would have been applied until the line was stable then G.INP reapplied at some point. Since not everyone is having re-syncs saying what cab they are on would help in this thread. What do you think?
Mine is definitely Huawei - just checked :)
-
I am approximately 235m (as the crow flies) the ECI cab I'm connected to.
Here are updated stats from my 166
f8lure graph: https://f8lure.mouselike.org/proxyfirebrick.asp?ID=59492
thinkbroadband graph: https://www.thinkbroadband.com/broadband/monitoring/quality/share/3e3858033e7e057f7049e78b7ddcd21a5c55fa55-25-01-2021
DrayTek> vdsl status
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 79992000 bps US Actual Rate : 20000000 bps
DS Attainable Rate : 81043380 bps US Attainable Rate : 24488100 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 1 US Interleave Depth : 1
NE Current Attenuation : 13 dB Cur SNR Margin : 6 dB
DS actual PSD : 3. 5 dB US actual PSD : 3. 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 : 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 : 9 dB
CO ITU Version[0] : 00b54649 CO ITU Version[1] : 4e5406b2
DSLAM CHIPSET VENDOR : < ----- >
DrayTek> 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 0 (symbols)
INTLVDelay : 100 100 (1/100 ms)
NFEC : 255 255
RFEC : 16 6
LSYMB : 5410 20577
INTLVBLOCK : 255 255
AELEM : 0 ----
-
Hey Robbie,
That's the EU version of the 166 yes?
It looks like it has the same 0 error counters as the UK model. Is that the case or was the screen grab taken immediately after sync?
Hi j0hn,
EU version with latest EU firmware. It did appear to have the same 0 errors reported issue and the firmware itself seemed to be more of a rough beta than ready for production use.
I've not had a chance to run tests on the UK firmware yet so still running on the OR modem for now. I was catching up on this thread to see if it was worth trying again this weekend but there seems to be only one other on this forum using the v166 with g.fast.
-
I swapped out an MT992 with the 166 in the UK on BT network.
I am on the Fibre 100 g.fast product which gives me speeds of up to 160mbps downstream. Looking at the max achievable rate I could go up to around 210mbps if I had the Fibre 250 product.
The MT992 used to drop around once a day. Since installing the 166 I've not yet had a drop other than when I've manually rebooted. Much improved. DSL checker shows improved figures than with the MT992.
I do not seem to have any problems with packet loss whatsoever, with my MTU left at its default setting perhaps I'm just lucky?
Hi Oakserver - could you post your modem stats as you are one of the few running a 166 on g.fast?
Regards.
-
I'm running a 166 (UK version) on G.Fast on it's original firmware & it's been stable so far, run to cab is just over 100m
I noticed mention of a beta firmware 423RC1 for the UK model, anyone know what's changed & where it can be downloaded from?
My line stats:
ATU-R Information
Type:
Hardware: Annex A
Firmware: 12-3-2-3-0-5
Power Mngt Mode: DSL_G997_PMS_L0
Line State: SHOWTIME
Running Mode: G.fast
Vendor ID: 00000000 00000000
ATU-C Information
Vendor ID: 00b54442 4d4390c1 [-----]
Line Statistics
Downstream Upstream
Actual Rate 328793Kbps 48157Kbps
Attainable Rate 457270Kbps 50991Kbps
Path Mode Fast Fast
Interleave Depth 0 0
Actual PSD 0. 0 dB -5.-8 dB
Near End Far End
Trellis ON ON
Bitswap OFF OFF
ReTx 1 1
SNR Margin 16dB 10dB
Attenuation 127dB 127dB
CRC 0 0
Every stat below this shows as 0 with this firmware
-
I'm running a 166 (UK version) on G.Fast on it's original firmware & it's been stable so far, run to cab is just over 100m
I noticed mention of a beta firmware 423RC1 for the UK model, anyone know what's changed & where it can be downloaded from?
Here: https://www.draytek.co.uk/download/support/files/v166_bt_423RC1.zip
They say it should fix the stats showing '0' but not in my case...
-
Oddly I would have thought with such a loss of throughput G.INP would be changed to Interleave as Vdsl 2 can use much greater interleaving depths, the maximum interleaving depth is 3072 (for profile 17a) so 4 with that drop seems odd hence my mention of it. My Interleaving is 1087 when it was on fast path before the modem change, on an ECI cab. If the poster is on a Huawei cab I would have thought that interleaving would have been applied until the line was stable then G.INP reapplied at some point. Since not everyone is having re-syncs saying what cab they are on would help in this thread. What do you think?
My thoughts... I'll try cover all your points.
The DLM doesn't ever change from G.INP to interleaving.
G.INP is the default on Huawei cabinets.
G.INP is now retained after a DLM reset or ISP migration (recent change).
New activations on Huawei cabinets have Interleaving applied for 2 days then G.INP is applied instead. That may also have changed and G.INP might even be applied immediately.
The Interleaving depth is usually 4 or 8 with G.INP applied.
It's only in the hundreds/thousands if INP/interleaving is applied instead.
The loss of throughput is due to the DLM increasing the target SNRM (noise margin).
The default target is 6dB down and up.
It's always 6dB on the upstream.
It's always 6dB on the downstream on ECI cabinets (due to no completed G.INP rollout).
If a line with G.INP in a Huawei cabinet is stable enough and has low enough errors the DLM lowers the target downstream SNRM to 5, 4 or 3dB, in 1dB steps.
There's 3 users in this thread with the Vigor 166 on VDSL2 who have had the DLM increase the target SNRM since connecting the Draytek.
This is due to an increase in errors. With the Draytek connected the DLM would never have lowered the target from 6dB in the 1st place.
At least 1 of the lines have gone from 3db to 4db to 5db all the way back to 6dB.
That's a considerable drop in stability compared to the users previous modem.
That's why having the error counters fixed is so important.
It's impossible to tell how stable the chipset is or how good/poor it is performing without being able to see the stats.
It's impossible to tell if each new firmware revision improves performance or not.
They say it should fix the stats showing '0' but not in my case...
Well that's a shame.
I'm very interested in seeing the full stats in the hope of seeing what's going on that's making the DLM so harsh.
It's a shame as the Vigor 130 is rock solid and lines regularly drop to 3dB using it.
I wonder if the Vigor 165 suffers the same 0 errors bug.
So far my Google search has been futile.
-
My thoughts... I'll try cover all your points.
The DLM doesn't ever change from G.INP to interleaving.
G.INP is the default on Huawei cabinets.
G.INP is now retained after a DLM reset or ISP migration (recent change).
New activations on Huawei cabinets have Interleaving applied for 2 days then G.INP is applied instead. That may also have changed and G.INP might even be applied immediately.
The Interleaving depth is usually 4 or 8 with G.INP applied.
It's only in the hundreds/thousands if INP/interleaving is applied instead.
The loss of throughput is due to the DLM increasing the target SNRM (noise margin).
The default target is 6dB down and up.
It's always 6dB on the upstream.
It's always 6dB on the downstream on ECI cabinets (due to no completed G.INP rollout).
If a line with G.INP in a Huawei cabinet is stable enough and has low enough errors the DLM lowers the target downstream SNRM to 5, 4 or 3dB, in 1dB steps.
There's 3 users in this thread with the Vigor 166 on VDSL2 who have had the DLM increase the target SNRM since connecting the Draytek.
This is due to an increase in errors. With the Draytek connected the DLM would never have lowered the target from 6dB in the 1st place.
At least 1 of the lines have gone from 3db to 4db to 5db all the way back to 6dB.
That's a considerable drop in stability compared to the users previous modem.
That's why having the error counters fixed is so important.
It's impossible to tell how stable the chipset is or how good/poor it is performing without being able to see the stats.
It's impossible to tell if each new firmware revision improves performance or not.
Well that's a shame.
I'm very interested in seeing the full stats in the hope of seeing what's going on that's making the DLM so harsh.
It's a shame as the Vigor 130 is rock solid and lines regularly drop to 3dB using it.
I wonder if the Vigor 165 suffers the same 0 errors bug.
So far my Google search has been futile.
Great post I do like to have people point out when I'm wrong its how we learn after all. However I'm still sure interleaving would have been applied with a 10mb drop. After all G.inp which I really have not read up that much on so my knowledge is a tad lacking, mainly because my cab fails to use it, would apply interleaving to stabilise the line. G.inp (from my limited knowledge) is used to control low levels of errors without out the need to drop throughput I believed.
On my ECI cab I have gone from Fastpath level interleaving level 1 on the downstream to a interleaving depth 1087 with a 10Mb drop, after a initial gain of 3Mbps on the first day from 51Mbps to 53Mbps. So I still think Interleaving would have been applied with so many errors, although we cant see them we can assume they must be there and on the downstream, as my upstream is Fastpath level 1 still.
-
Great post I do like to have people point out when I'm wrong its how we learn after all. However I'm still sure interleaving would have been applied with a 10mb drop. After all G.inp which I really have not read up that much on so my knowledge is a tad lacking, mainly because my cab fails to use it, would apply interleaving to stabilise the line. G.inp (from my limited knowledge) is used to control low levels of errors without out the need to drop throughput I believed.
On my ECI cab I have gone from Fastpath level interleaving level 1 on the downstream to a interleaving depth 1087 with a 10Mb drop, after a initial gain of 3Mbps on the first day from 51Mbps to 53Mbps. So I still think Interleaving would have been applied with so many errors, although we cant see them we can assume they must be there and on the downstream, as my upstream is Fastpath level 1 still.
Applying Interleaving would presumably be DLMs next step after increasing the target SNR if errors are still above its thresholds. It's just working back the normal way it progresses in the same steps.
-
Maybe Draytek are hiding the detailed stats on purpose.
They must have spent some time testing the device before releasing it.
Hiding the stats may mask the poor performance of the device.
-
The default target is 6dB down and up.
It's always 6dB on the upstream.
It's always 6dB on the downstream on ECI cabinets (due to no completed G.INP rollout).
A good while back they changed from a default target of 6dB on ECI cabs to 5dB. A very small bonus when it was (somewhat belatedly) rolled-out.
> v s
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 79995000 bps US Actual Rate : 20000000 bps
DS Attainable Rate : 89316472 bps US Attainable Rate : 22633768 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 1 US Interleave Depth : 1
NE Current Attenuation : 10 dB Cur SNR Margin : 5 dB
DS actual PSD : -1.-7 dB US actual PSD : -1.-6 dB
NE CRC Count : 0 FE CRC Count : 302
NE ES Count : 0 FE ES Count : 72
Xdsl Reset Times : 0 Xdsl Link Times : 2
ITU Version[0] : fe004452 ITU Version[1] : 41590000
VDSL Firmware Version : 05-07-09-0F-01-07 [with Vectoring support]
Power Management Mode : DSL_G997_PMS_L0
Test Mode : DISABLE
-------------------------------- ATU-C Info ---------------------------------
Far Current Attenuation : 10 dB Far SNR Margin : 6 dB
CO ITU Version[0] : b5004946 CO ITU Version[1] : 544eb206
DSLAM CHIPSET VENDOR : < IFTN >
-
I am using my 166 in VDSL mode and haven't experienced the issues @Killhippie and @omegapoint are reporting. I've attached screenshots from the thinkbroadband tester - is there any chance you might have got a defective unit?
Well my line overnight adjusted and I now have 52Mbps and my ping of 7ms back using the release candidate firmware and using a MTU of 1500 (my line does not support baby Jumbo frames so 1508 wasn't really needed) and my routers will only allow a MTU of 1492. :)
-
Well my line overnight adjusted and I now have 52Mbps and my ping of 7ms back using the release candidate firmware and using a MTU of 1500 (my line does not support baby Jumbo frames so 1508 wasn't really needed) and my routers will only allow a MTU of 1492. :)
Sounds promising. I wasn't sent the RC firmware so my 166 is still sitting unplugged until something stable is released
For reference, it took my line a full week to go to back a SNR of 4 (from 5) after my 130 was back in place, still waiting to be back to 3.
-
A good while back they changed from a default target of 6dB on ECI cabs to 5dB. A very small bonus when it was (somewhat belatedly) rolled-out.
> v s
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 79995000 bps US Actual Rate : 20000000 bps
DS Attainable Rate : 89316472 bps US Attainable Rate : 22633768 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 1 US Interleave Depth : 1
NE Current Attenuation : 10 dB Cur SNR Margin : 5 dB
DS actual PSD : -1.-7 dB US actual PSD : -1.-6 dB
NE CRC Count : 0 FE CRC Count : 302
NE ES Count : 0 FE ES Count : 72
Xdsl Reset Times : 0 Xdsl Link Times : 2
ITU Version[0] : fe004452 ITU Version[1] : 41590000
VDSL Firmware Version : 05-07-09-0F-01-07 [with Vectoring support]
Power Management Mode : DSL_G997_PMS_L0
Test Mode : DISABLE
-------------------------------- ATU-C Info ---------------------------------
Far Current Attenuation : 10 dB Far SNR Margin : 6 dB
CO ITU Version[0] : b5004946 CO ITU Version[1] : 544eb206
DSLAM CHIPSET VENDOR : < IFTN >
The Upstream target SNRM is 6dB on all FTTC/VDSL2 lines on all cabinets.
A copy of SIN 498
https://www.cvf.openreach.co.uk/cpportal/content/dam/cpportal/public/images-and-documents/home/help-and-support/sins/documents/SIN_498_v7.7_apr_2020.pdf
Specifically Asked A.1.1
Parameter
Downstream Target Noise Margin 6dB
Upstream Target Noise Margin 6dB
Section 1.2.2 covers the charges to Downstream noise margin
1.2.2 VDSL2 noise margins Currently the default target downstream noise margin is set to 6dB. From March 2017 the target downstream noise margin shall be set to either 3, 4, 5 or 6dB – the actual value shall be determined by the Dynamic Line Management (DLM) algorithm based on line stability.
If you got your ISP to run a GEA test it would confirm a 6dB target.
Many lines run off target for multiple reasons.
-
Great post I do like to have people point out when I'm wrong its how we learn after all. However I'm still sure interleaving would have been applied with a 10mb drop. After all G.inp which I really have not read up that much on so my knowledge is a tad lacking, mainly because my cab fails to use it, would apply interleaving to stabilise the line. G.inp (from my limited knowledge) is used to control low levels of errors without out the need to drop throughput I believed.
On my ECI cab I have gone from Fastpath level interleaving level 1 on the downstream to a interleaving depth 1087 with a 10Mb drop, after a initial gain of 3Mbps on the first day from 51Mbps to 53Mbps. So I still think Interleaving would have been applied with so many errors, although we cant see them we can assume they must be there and on the downstream, as my upstream is Fastpath level 1 still.
Interleaving isn't by the Huawei DLM.
All lines with modems that are capable of using G.INP, use it.
The DLM has put the line on a 6dB target likely with Retransmission High.
That's the highest target with the highest error protection.
Applying Interleaving would presumably be DLMs next step after increasing the target SNR if errors are still above its thresholds. It's just working back the normal way it progresses in the same steps.
It is indeed working back but it won't go to Interleaving.
It will sit stable on 6dB Retx High.
Should the chipset improve performance or the user switches back to the previous modem then the DLM should start working back down the targets and switch to Retx Low.
-
Interleaving isn't by the Huawei DLM.
All lines with modems that are capable of using G.INP, use it.
The cab has to support G.inp. ECI cabs have no vectoring or G.inp support, and OR have been trying to get G.inp working on ECI cabs for years. Huawei cabs use G.inp as it was part of a firmware update to the cabs as the line cards supported both technologies, OR has tried and failed to get G.inp working on ECI cabs, as you can see read in the link below. If the cab does not support G.inp you wont get G.inp even if your modem does support it so the ECI cabs wont use G.inp just because the Vigor does alas.
https://www.ispreview.co.uk/index.php/2020/08/openreach-g-inp-trial-on-eci-fttc-broadband-lines-hits-snag.html
-
Hi all,
I'm new to this forum so be kind :)
anyways here's my question I purchased the vigor 166 as my vigor 130 was playing up, so having read Robbie's review I wanted to access the 166 to update to the new 4.1.1_BT firmware as the 4.0.5_BT firmware was allegedly buggy, however having connected the 166 directly to my laptop I have failed miserably to access the 166 web login page.
The manual states a web address of 192.168.2.1 identical to my 130 so naturally I didnt think there was going to be an issue, however having attempted all possible IP addreses I decided to just swap out the 166 in place of the 130 thinkng I could access it like my 130 once it was connected to my network, although still no joy :no:
any help would be much appreciated -TIA
-
The cab has to support G.inp. ECI cabs have no vectoring or G.inp support, and OR have been trying to get G.inp working on ECI cabs for years. Huawei cabs use G.inp as it was part of a firmware update to the cabs as the line cards supported both technologies, OR has tried and failed to get G.inp working on ECI cabs, as you can see read in the link below. If the cab does not support G.inp you wont get G.inp even if your modem does support it so the ECI cabs wont use G.inp just because the Vigor does alas.
https://www.ispreview.co.uk/index.php/2020/08/openreach-g-inp-trial-on-eci-fttc-broadband-lines-hits-snag.html
I'm aware of that...
Interleaving isn't by the Huawei DLM.
I did write "Huawei" cabinets, "Huawei" lines and "Huawei" DLM in about 5 of my previous posts.
I was also quite specific when I mentioned that the DLM only lowers the target SNRM on Huawei lines and only if G.INP is enabled.
I only made the point that the 166 obviously has some high error counters as 3 users have had the DLM increase their SNRM targets. 1 went all the way from 3dB to 6dB.
Threads gone way off topic.
-
Hi all,
I'm new to this forum so be kind :)
anyways here's my question I purchased the vigor 166 as my vigor 130 was playing up, so having read Robbie's review I wanted to access the 166 to update to the new 4.1.1_BT firmware as the 4.0.5_BT firmware was allegedly buggy, however having connected the 166 directly to my laptop I have failed miserably to access the 166 web login page.
The manual states a web address of 192.168.2.1 identical to my 130 so naturally I didnt think there was going to be an issue, however having attempted all possible IP addreses I decided to just swap out the 166 in place of the 130 thinkng I could access it like my 130 once it was connected to my network, although still no joy :no:
any help would be much appreciated -TIA
Have you tried to assign a static IP address - i.e. 192.168.2.10 - to your laptop LAN port ?
-
Hi all,
I'm new to this forum so be kind :)
anyways here's my question I purchased the vigor 166 as my vigor 130 was playing up, so having read Robbie's review I wanted to access the 166 to update to the new 4.1.1_BT firmware as the 4.0.5_BT firmware was allegedly buggy, however having connected the 166 directly to my laptop I have failed miserably to access the 166 web login page.
The manual states a web address of 192.168.2.1 identical to my 130 so naturally I didnt think there was going to be an issue, however having attempted all possible IP addreses I decided to just swap out the 166 in place of the 130 thinkng I could access it like my 130 once it was connected to my network, although still no joy :no:
any help would be much appreciated -TIA
I don't think any units shipped with 4.0.5_BT firmware, despite what's printed on the box!
Mine certainly arrived with 4.1.1_BT installed, although the box said 4.0.5_BT
If you need more help with setting the Static IP read this: https://pureinfotech.com/set-static-ip-address-windows-10/#static_ip_controlpanel_windows10
Connect directly between laptop & modem with cable. The 3 settings you need to enter are:
IP address 192.168.2.10
subnet mask 255.255.255.0
Default gateway 192.168.2.1
Once saved open a web search & type 192.168.2.1 into the address box to get to the log-on page.
(One other point, if you switch it from MODEM to ROUTER mode the default for DHCP seems to be OFF (which is unusual) it needs to be ON for most people)
-
:thumbs:Great review many thanks.
-
Can someone tell me if the Vigor 166 Gen 1 will work then properly on a UK g.fast line (Zen Internet) and if it is better than what the Openreach modem (MT992?) would do? Thanks.
-
Can someone tell me if the Vigor 166 Gen 1 will work then properly on a UK g.fast line (Zen Internet) and if it is better than what the Openreach modem (MT992?) would do? Thanks.
Thought i'd try and help you by summarising - There are users on here on g.fast lines where the 166 works well and is stable. There are multiple users on non-g.fast lines where the modem works poorly (on my line - incredibly poorly and had to be returned - 71mb down to 55mb). As the line stats do not currently work, I doubt anyone with any certainty can state whether this modem works better than x. If i were you, i'd use the MT992 and see what happens over the next 6 months in terms of firmware updates on 166, but i believe the MT992 is meant to be relatively decent and stable. I think there is some question over use of the 166 with huawei cabs but we dont have enough data to make any solid comment.
-
Can someone tell me if the Vigor 166 Gen 1 will work then properly on a UK g.fast line (Zen Internet) and if it is better than what the Openreach modem (MT992?) would do? Thanks.
Do you have a UK model (V166-K) or an EU one (V166-A)?
The UK model has special firmware approved by Openreach/BT & is configured to work just the same as an MT992 without any setting up.
Therefore it should work on any Openreach supplied G.Fast line, regardless of ISP.
I'm not sure if the Vigor would give a better connection, but at least you can check your basic upload & download speeds in the stats page.
However not all stats are currently shown, hopefully a firmware upgrade is on its way to fix the issue.
No one has managed to hack the Openreach (Huawei or ZTLink) MT992 yet so there is no access to such info.
I've also heard that some buyers of the Vigor EU model have tried to load the UK firmware, but so far without success.
-
Thanks very much for both the previous 2 replies.
Essentially am feeling my way into the new world (to me) of g.fast. I have an order placed to upgrade my existing line to g.fast, although it seems that this is in a queue and will take a few weeks for the engineer to come and do it.
Anyway on the back of the order I bought a Vigor 166 - which does look to be the UK version and on firmware 4.0.5 BT (on the box) - it just says Applied Area UK on the bottom of it. Whatever firmware is available or recommended when my line goes live is likely to be what I would put on it. From reading through the thread, would that be beta firmware 423RC1?
Background on me, am naturally curious with tech and currently run with a Vigor 130 and Asus RT-AC86U router on Merlin - not one to stick with the first thing am provided with ;D. It's a very stable setup. Have used other Asus routers with Tomato and with HG612 routers (which I have unlocked) in the past. Always interested in getting the best out what setup I can.
Edit: my initial research looks to suggest am on a Huawei cab - so we'll see what happens.
Look forward to contributing more as we go.
-
Edit: my initial research looks to suggest am on a Huawei cab - so we'll see what happens.
There's 2 VDSL2 Vendors (types of VDSL2 cabinets) in use in the UK. They are ECI and Huawei.
Huawei use Broadcom chipset line cards.
ECI use IFTN/Lantiq line cards (Lantiq is now owned by Intel). Draytek use an Intel chipset in the modem.
The issues so far with the 166 appear to be that the DLM is increasing the target noise margin.
This isn't necessarily an issue with Huawei cabinets but could be how the 166 handles all VDSL2 G.INP.
As there's very little G.INP on the ECI cabinets there's no way to tell if these issues would happen on ECI cabinets also.
The lack of error counters makes it impossible to tell how stable the modem actually performs.
With regards to G.Fast there are again 2 Vendors in the UK. They are Huawei and Nokia.
They both appear to use Broadcom chipsets.
There's no way to tell what Vendor your G.Fast is connected to.
As they both appear to be Broadcom it will make much less difference which Vendor is on your cabinet.
-
As far as I know all UK stock shipped so far says firmware 4.0.5_BT on the box but actually has 4.1.1_BT installed.
I guess it was a last minute thing & they couldn't be bothered to change the sticker on the boxes.
As firmware 423RC1 is still in BETA testing it won't be installed on any production units yet.
-
Received my Vigor 166 Gen1 (V166-K) yesterday and connected it to my line, replacing my Vigor 130. With the 130 I was getting a stable connection of around 69Mbps with the 166 that dropped down to 64Mpbs initially but has since raised to 66Mps and remained connected for 16hrs+. As others have mentioned the box states firmware 4.0.5_BT but actually ships with 4.1.1, I reloaded the firmware for good measure.
The only thing not working for me is the CLI, if I try to enter any command or enter ? for help it just hangs, I've not tried resetting to factory defaults yet I'll give it a few days to see if the speeds increase and try a reset at the weekend.
I'll keep this installed on my line as I want to see how it performs over the 130 which I have deployed at a number of offices I maintain.
-
Someone was asking how the 166 fared against the MT992 on a G.Fast line so I managed to borrow a ZTLink MT992 to compare.
I tried several different speed-test sites, & on my line the Vigor came out on top on every test.
The overall results were that the MT992 was approx. 12% slower on download speed & 5% slower on the upload speed.
I did the test with each modem in turn & then repeated the process, all the sites gave pretty consistent readings so I think this is a fairly accurate result.
-
Thanks very much. That's really helpful to know. Can I ask if you did any particular config on the Vigor 166 or did you run with defaults?
-
Thanks very much. That's really helpful to know. Can I ask if you did any particular config on the Vigor 166 or did you run with defaults?
I ran it in it's default (Modem) mode, just as it came out of the box. Firmware was as shipped too (4.1.1_BT)
-
Just to note that I have not managed to update my EU purchased V166 to the latest BT firmware. Tried both methods but get a compatibility warning. No response from Draytek Support as yet.
-
Just to note that I have not managed to update my EU purchased V166 to the latest BT firmware. Tried both methods but get a compatibility warning. No response from Draytek Support as yet.
When I first got my device (the UK model), I did try to load the international firmware (v4.1.1_STD) and I recall ignoring some kind of warning and I simply pushed the installation of the firmware: the only difference with the UK firmware I remember is the max MTU value = 1500 + different modem codes.
Are you saying you have no way to force the upload of the UK/BT firmware onto your unit ?
-
Hi there
I've just purchased this modem, I've found it works great in bridge mode no set up, simple plugs and play on BT/Openreach G.Fast.
I am however having difficulties accessing the management page, I've followed all the advice in the book and the help page at Draytek but as yet have been unable to get a connection.
I did try and follow the fixed IP route, but could not establish what the default gateway was when connected to the modem alone via cable. I did the ipconfig command but it leaves the default gateway blank.
Anyone else have any tips I could follow ?
-
I did try and follow the fixed IP route, but could not establish what the default gateway was when connected to the modem alone via cable. I did the ipconfig command but it leaves the default gateway blank.
You don't use a gateway as both devices should have an IP address on the same network. You need to know the IP address of the device and manually set the IP on your client to be on the same network. Or more ideal is set the device to a spare IP address on your normal network then you can simply plug it into your network and access it any time.
-
Hi there
I've just purchased this modem, I've found it works great in bridge mode no set up, simple plugs and play on BT/Openreach G.Fast.
I am however having difficulties accessing the management page, I've followed all the advice in the book and the help page at Draytek but as yet have been unable to get a connection.
I did try and follow the fixed IP route, but could not establish what the default gateway was when connected to the modem alone via cable. I did the ipconfig command but it leaves the default gateway blank.
Anyone else have any tips I could follow ?
Did you follow my instructions on the previous page (p16-reply#237), it should work, the gateway is shown (192.168.2.1)
Leave 'obtain DNS' on auto
Plug your computer's network cable DIRECTLY into the modem as it won't work if you try to access it via the router.
-
Just to note that I have not managed to update my EU purchased V166 to the latest BT firmware. Tried both methods but get a compatibility warning. No response from Draytek Support as yet.
Have you tried the recovery method: https://www.draytek.co.uk/support/guides/kb-firmwarerecovery-drayos
-
Have you tried the recovery method: https://www.draytek.co.uk/support/guides/kb-firmwarerecovery-drayos
Tried the GUI and the TFTP method.
Being a Mac user I had to breakout the emergency windows machine for the TFTP thing. A nice reminder why I don't like Windows.
Draytek support asked me for a screenshot earlier today so will see where that takes us.
-
Just picked up one of these modems - using it in bridge mode it works flawlessly but I can't access its management GUI via its IP on P2 unless I unplug the router going into P1.
Is this normal?
I was hoping to monitor line stats via SNMP through P2 but not sure why when P2 is active P1 can't be pinged and vice versa.
-
Just picked up one of these modems - using it in bridge mode it works flawlessly but I can't access its management GUI via its IP on P2 unless I unplug the router going into P1.
Is this normal?
I was hoping to monitor line stats via SNMP through P2 but not sure why when P2 is active P1 can't be pinged and vice versa.
Leonroy, it worked fine for me but I did change the ip of P2 to match the subnet of router.
Great that it works for you. I ended up returning mine as I couldn't get it to work correctly. What kind of connection are you using it for (VDSL or G.Fast)? And do you know what your cabinet type is (Huawei or ECI)? Curious if it was something specific to my unit
-
What kind of connection are you using it for (VDSL or G.Fast)? And do you know what your cabinet type is (Huawei or ECI)? Curious if it was something specific to my unit
Using G.Fast, believe it's Huawei. Previously was using VDSL - swapped between the ECI and Huawei modems - zero difference that I noticed but I was getting pretty much 76/20. What was the issue you had with yours?
I don't see what the point of port 2 is since plugging into it seems to mess with port 1. I managed to log onto the Draytek eventually using pfSense to create an Outbound NAT route on a second WAN interface IP as per here (http://"https://blog.linuxserver.io/2019/11/10/modem-webui-pfsense/").
Stats:
DrayTek> vdsl status
--------------------------- ATU-R Info (hw: annex A, f/w: annex X) -----------
Running Mode : G.fast State : SHOWTIME
DS Actual Rate :329606000 bps US Actual Rate : 49916000 bps
DS Attainable Rate :425783000 bps US Attainable Rate : 87369000 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 0 US Interleave Depth : 0
NE Current Attenuation : 127 dB Cur SNR Margin : 8 dB
DS actual PSD : 0. 0 dB US actual PSD : -1.-7 dB
NE Rcvd Cells : 0 NE Xmitted Cells : 0
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
ADSL Firmware Version : 12-3-2-3-0-5
Power Management Mode : DSL_G997_PMS_L0
Test Mode : DISABLE
-------------------------------- ATU-C Info ---------------------------------
Far Current Attenuation : 127 dB Far SNR Margin : 13 dB
CO ITU Version[0] : 00b54442 CO ITU Version[1] : 4d4390c1
DSLAM CHIPSET VENDOR : < ----- >
Also managed to enable SNMP using this command via the CLI:
mngt snmp -e 1
mngt snmp -g supersecretread -s supersecretwrite
So now can get some snazzy graphs showing noise levels and negotiated rates. ;D
-
Leonroy, it worked fine for me but I did change the ip of P2 to match the subnet of router.
Great that it works for you. I ended up returning mine as I couldn't get it to work correctly. What kind of connection are you using it for (VDSL or G.Fast)? And do you know what your cabinet type is (Huawei or ECI)? Curious if it was something specific to my unit
Sadly I returned mine too. Support were great but the beta firmware did not solve to constant latency. I could see it on thinkbroadband monitor and PingPlotter showed constant spikes and packet loss.
Tried it with 3 routers too. Voice coms on playstation had a constant blip.
Stuck the old HG612 and it’s back to a smooth line. Hopefully at some point they will improve it but once support ran out of ideas it’s time to call it the day.
-
After two weeks my connection has gone from a stable 69Mbps on the Vigor 133 down to 52Mbps on the Vigor 166, as far as I can see I'm not getting any errors on the line and uptime on the physical connection is 194hrs. Stats are below;
> vdsl status
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
Running Mode : 17A State : SHOWTIME
DS Actual Rate : 52617000 bps US Actual Rate : 14376000 bps
DS Attainable Rate : 64990350 bps US Attainable Rate : 14377000 bps
DS Path Mode : Fast US Path Mode : Fast
DS Interleave Depth : 4 US Interleave Depth : 1
NE Current Attenuation : 17 dB Cur SNR Margin : 8 dB
DS actual PSD : 14. 2 dB US actual PSD : 7. 8 dB
NE CRC Count : 0 FE CRC Count : 0
NE ES Count : 0 FE ES Count : 0
Xdsl Reset Times : 0 Xdsl Link Times : 8
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 : 6 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 270 (symbols)
INTLVDelay : 100 0 (1/100 ms)
NFEC : 254 236
RFEC : 16 8
LSYMB : 3859 14319
INTLVBLOCK : 127 236
AELEM : 0 ----
>
-
Using G.Fast, believe it's Huawei. Previously was using VDSL - swapped between the ECI and Huawei modems - zero difference that I noticed but I was getting pretty much 76/20. What was the issue you had with yours?
Mine wouldn't hold a connection for any more than 10 mins before disconnecting/reconnecting. Seems it didnt like vdsl connections with Huawei cabs, and no G.Fast in my area. HG612 been solid now for 3 weeks. My concern and why I got the draytek is if the modem breaks I have no backup. Perhaps I should try the 133 since I don't need G.Fast...
-
as far as I can see I'm not getting any errors on the line
The error counters are broken and always show 0 errors.
Your high attainable/high SNRM and low sync is rather odd though. It suggests the modem is capable of syncing much higher and it doesn't look like DLM has banded/capped the sync.
I recommend resyncing the line and seeing if the sync increases. In theory it should.
-
The error counters are broken and always show 0 errors.
Your high attainable/high SNRM and low sync is rather odd though. It suggests the modem is capable of syncing much higher and it doesn't look like DLM has banded/capped the sync.
I recommend resyncing the line and seeing if the sync increases. In theory it should.
By resync, do you just mean turn the modem off/on, or do I need to leave it off for 30mins plus to reset?
-
By resync, do you just mean turn the modem off/on, or do I need to leave it off for 30mins plus to reset?
Either, but its generally safer to do the 30 minutes.
-
Thanks for the reply, I left it off for 40mins or so, turned it back on and no change in the initial sync I'll recheck in the morning.
-
Just thought that I'd mention that I've been running my 166 as a modem on a G.Fast line without major problems so far.
However when I turned on Hardware Acceleration (just to see what would happen) the connection became very unstable.
So Draytek have lots of problems to fix, although VDSL customers seem to be having more problems that G.Fast ones.
If anyone gets a link from Draytek to new BETA Firmware it would be nice if they could post it here.
-
If anyone gets a link from Draytek to new BETA Firmware it would be nice if they could post it here.
Have you already tested the 423RC1? https://forum.kitz.co.uk/index.php/topic,25203.msg429392.html#msg429392
-
I tried the Latest release candidate R23RC2 and that was more stable but still no increase in throughput, I put my old 2016 build ECI modem back on and my latency (QoS is off on the router) went from 200-300ms UL on the Draytec to 30ms on the ECI, download is about the same at 38ms Idle at 18ms and on TBB and I get a B down and b Up or a A down and B up on bufferbloat compared with A and F with the Draytec, with spikes up to 314ms and sometimes erroneous downloads of 1GB peaks which would be a miracle.
The new beta firmware gives some of the stats now but still no errors but does show the cab you are on, I am on a ECI. After a month of this modem I have decided to return the 166 (I have a week) its just not worth the effort to keep playing with it and watch my downloads actually become corrupt due to packet loss I imagine. Also I won't buy a Vigor 130 as I believe its the same chipset as in the last ECI v2 Openreach modems anyway and they run just fine on my cab.
My ECI modem runs cooler, syncs better and even though I am still interleaved I did gain back 3 Mbps straight away, so hopefully I will get the whole 10Mbps back in about a week or so. The 166 needs alot more work and I don't have the inclination to keep playing with it and messing my line up at this time.
Here is the link if anyone wants to try, I guess newer isn't always better, I think the 166 is a victim of the pandemic and issues with firmware and hardware and maybe Intel owning it now. Moreover it seems to really work for G.fast but not so well for VDSL, and my ECI modem is fine and I have a few spares for now. A lot of money paid for a device that wrecked my line gets very warm and as does the PSU compared with the ECI modem that gives off hardly any heat in comparison and the PSU is cold to the touch, and also less errors it appears and no packet loss. A shame but I dont want to be a beta tester at this price range, even though we all are with new tech really.
https://www.draytek.co.uk/download/support/files/v166_bt_423RC2.zip
-
Thanks for the link to RC2 beta.
I didn't bother with RC1 as others has already reported that it didn't change anything.
However, I'll give this one a try & see what happens on a G.Fast line.
-
I've also been in contact with Draytek and provided with the 423RC2 firmware, so far no change for me. Also the CLI still locks up.
-
I was asked to try tweaking the VDSL target SNR via the CLI by a friend who's running stock firmware on a VDSL line, as it killed P1 & P2 when he tried it.
He knew I'm using RC2 (but on G.Fast) so he thought he'd get me to try it before flashing his, but I got the same result, it bricks the modem!
It says command successful & reboots, but it crashes, a power cycle kills ports 1 & 2, no green lights on P1 & P2 & no connections available.
The reset button brings it back to life luckily.
-
For anyone thinking of buying the new V166-A GEN 2 (EU) version, Amazon in Germany have just got stock.
They're one of the few EU traders who will actually sell to the UK at the moment!
€122 + shipping to the UK & taxes = approx. €128 (as of 12:00hrs 18/02)
Update: A friend has just ordered one & it's due on Monday
He's going to loan it to me for a couple of days to look it over.
Update: It arrived early & I've given it the once over on my G.FAST line.
It comes with the same current firmware as EU GEN1 (4.1.1_STD)
Different IP address (192.168.1.1) to the UK model (192.168.2.1)
MTU max=1500 as per EU GEN1, needs VLAN=101 to be set manually for UK use.
The Q.S.Manual is in German only & no RJ11 - RJ11 cable supplied (as required for UK use).
Instead RJ11 to RJ45 & RJ11 to a large plastic plug of some kind are supplied.
Any attempt to upgrade firmware with UK version gets an incompatible hardware message & upgrade button greyed out
Same bugs as the EU GEN1 & UK models regarding the stats readouts, performance seems to be about the same too.
Last update: Tried tweaking the target SNR as per my previous post & again it doesn't work, bricks the unit & reset button required
Returned to the owner
-
Hi everyone,
I got this to swop out an Openreach modem for no reason really other than to see line stats etc.
I am still on the original firmware anybody had any other firmware apart form the RC1 and RC2.
Can anybody on the RC2 give any more info other than it hasn't made a difference. Like what is it showing now that it didn't before? Has it made any difference to line stats good or bad?
Unfortunately i have nothing to compare my stats with but i was getting 47 down and 15 up but me being me messed about with it a few times and have managed to knock it down to 32 down :D But leaving it in and trying to stop messing with it. Which for me is impossible. ::)
My power brick and modem don't actually get hot and is on par with me ECI Openreach modem.
So basically is it worth me putting RC2 or any other newer one that might be available.
Also what VDSL faceplate have people got i am still on the MK1 will i see improvement with a Mk3/ NTE5C/MK4. Would be interesting to see what other people have, well for me anyway.
Cheers
-
For anyone thinking of buying the new V166-A GEN 2 (EU) version, Amazon in Germany have just got stock.
They're one of the few EU traders who will actually sell to the UK at the moment!
€122 + shipping to the UK & taxes = approx. €128 (as of 12:00hrs 18/02)
Update: A friend has just ordered one & it's due on Monday
He's going to loan it to me for a couple of days to look it over.
We have someone who has an EU version of Gen1 above and can't install the UK firmware on it so I'll add that warning to anyone thinking of buying it.
Though I don't know if they will even release a UK version of Gen2 so might never come across that issue.
-
Hi everyone,
I got this to swop out an Openreach modem for no reason really other than to see line stats etc.
Aren't you disappointed
Can anybody on the RC2 give any more info other than it hasn't made a difference. Like what is it showing now that it didn't before? Has it made any difference to line stats good or bad?
Still no error counters. Retx still shows incorrectly, etc etc.
In my opinion the best socket and faceplate combo is the NTE5A and MK3.
The NTE5C is junk
-
Disappointed not really. It should in theory perform better, new tech and all that. In this day and age its company's getting lazy and cutting corners we could also blame the pandemic etc. I have seen it many times in the IT industry over 20 years. Unifi for me must be one of the worst at the moment as they release firmware that seems to fix one thing then break something else constant pain, people will swear by it but they are the ones that have probably invested heavily.
That's a shame but I will continue with it. The speed lost doesn't really bother me at the moment. I do think initially it was a better connection than the ECI modem but me being me i did a few too many reboots etc and got put on interleaving which is my fault rather than the modem at this point. Time will tell I suppose if I can leave it alone or leave it for over 30mins before turning it back on.
I did read/think the MK3 was better again you would think it would have some advantage of the MK1 or else it wouldn't get to MK4. But i have read about the build quality of the NTE5C MK4.
Thanks
-
I can't remember where I read it, but someone said Ubiquiti also use very cheap hardware compared to other manufacturers, even in a similar price bracket. With the likes of Zyxel (I think) adding a lot more filtering with just generally better build quality in their APs.
Sounds about right, as Ubiquiti seem to basically use consumer-grade hardware and graft their mod of OpenWRT on top of it.
The icing on the cake for me was the Unifi 6 Lite, WiFi 6 on 5Ghz but they seem to use WiFi 4 on 2.4Ghz. Its basically being sold as an upgrade form the nanoHD but its only 2x2 MIMO so in many ways is actually a downgrade. They just rushed it out so they could say they have a WiFi 6 AP on the market.
Its not even clear if it supports 160Mhz channel width, another thing they like to omit from their launch firmware and tack on later. The only reason I started using Unifi Controller was because they didn't let you enable 160Mhz on the nanoHD from the web UI. Seems they forgot that feature when they added 160Mhz support to the firmware.
-
It’s the same no matter what router you have, nothing is bug free nowadays or simply works but what some hate others love. Routers are ten to the dozen, they don’t qualify like a lovely valve amp or an old Musical Fidelity A370 where craftsmanship is involved with electronics so with routers it’s plastic technology that’s here today and gone tomorrow.
Mind you routers are a damn sight cheaper than the A370 I have and a lot cheaper to run :lol:
-
There's certainly a blurred line now with high-end consumer routers cost as much as the low-end Ubiquiti kit.
Honestly its all this ambiguity about the quality and speed of routers that pushed me to x86 in the first place. Its not without its problems, but I can be sure CPU power and RAM isn't one of them.
When it comes to WiFi though you're still at the mercy of the manufacturer as the good drivers are closed source, despite the main software components being open source. There's also all the regulation regarding WiFi certification that makes throwing together your own solution a none-starter. I've dabbled with hostapd before, its not worth the effort.
-
I was running one of those high end routers, a RAX120 when I had the vigor 166. I was suffering the increase latency and packet drops and hoped to combat it with some QoS but it’s broken on the 120 and was a true pain if you liked your online gaming. It’s been broken for a while sadly and has some rather interesting choices under its menu for services long gone.
I had the monitor up and running from Thinkbroadband and PingPlotter to see what was going on. There was a distinctive saw pattern from the vigor so if any one wants to check the monitors free to use.
If the pic works you can see the issue I was having. From around midnight shows the vigor saw pattern and you can see the dropped packets on the top left side during my daily use.
-
Just to compare with the HG612 I’ve included a pic but I’m using a different router to control those dropped packets and latency.
-
Hello all, good review, great thread, some very interesting posts and points of view.
Like many on the board I am having difficulty with the Vigor 166, more specifically the speed at which the modem syncs to the VDSL2 equipment within the cabinet we are hooked up to.
My connection loses 4-5 Mbps (17 down from 21/22Mbps) using the 166, as opposed to either my Openreach ECI modem (B-Focus model) or my ISP supplied FRITZ!Box 7530 Router / VDSL modem combo which sync at a rate up to 5Mbps higher. Our home is a decent way from the broadband cabinet (850M - 900M), typically we enjoy a "stable" but low speed FTTC connection in the 21 Mbps range for downloads and upload speeds of around 4-5 Mbps.
Historically I have used the ECI and more recently the 7530 and sync at around 21-22 Mbps download with a consistent 4.5Mbps upload and a typical 22ms - 28ms ping to UK servers.
This DL speed is instantly reduced when the 166 is connected to the line, upstream remains extant as does the "typical" ping but with large, intermittent latency spikes that can easily be recreated using DSL reports Speed-test where buffer-bloat is off the charts, this does not occur with the ECI modem when using QOS via a UniFi Dream Machine router.
The same router and QOS settings exhibit huge latency spikes when connected to the 166 leading me to believe that the 166 is most certainly the issue.
It's worth noting that the second VDSL Modem code (not default) on the 166 provides marginally higher sync speeds than the factory default setup. Changing the MTU setting for a lower value makes little difference in my case.
The cabinet is the ECI M41 type (FRITZ!box 7530 reports Infinium based hardware and the cabinet type when I checked on Google Maps is commensurate with this)
In addition, like many others I am unable monitor stats to even see if the modem is damaging my line profile as many here have reported, so in the interim I have switched back to the Openreach modem until Draytek fixes whatever is causing the issues or I return the product.
It's a shame as the hardware is clearly well made and has potential longevity that far outweighs my ageing ECI and ISP supplied 7530, but without the ability to monitor the line I simply cannot tell if the modem is performing as it should, couple this with a sync speed that’s 20-25% worse than the ancient hardware that I already use and the 166 is a hard purchase to justify :/
-
I see the EU version has another BETA firmware out - 423RC4
No idea what (if anything) they've fixed
Anyone know if there's a UK version?
-
I see the EU version has another BETA firmware out - 423RC4
Do you have a web link?
-
BETA 423RC4 (For EU GEN1/GEN2 models only) - I don't have a DrayTek link so I've put it on a cloud-share at:
https://c.gmx.com/@947635074856129735/nv_3yRDJRLSETI0veFoW1w
It would be nice if DrayTek could include a list of fixes with these releases!
Update: Apparently DrayTek (Germany) are collecting debug info to try & solve the VDSL syncing issues.
This firmware has the following feature to do this:
Our G.fast router Vigor166 supports collecting DSL debug logs since firmware version 4.2.3.
To help fix DSL synchronization problems, please create DSL debug log and send this to us for further analysis.
Below are the steps to collect the DSL debug logs.
1: Open the web console and enter the command "adsl idle dti_on" to enable debug mode, then enter the command "sys reboot" to restart.
2: After the Vigor166 has started, open the web console again and enter the command “adsl idle dti_on” again.
3: Connect the VDSL line to the Vigor166 and wait 3-5 minutes.
4: In the WebUI under Diagnostics >> DTI log download, click on Download. The log name is "_dti_training_0_0.bin".
-
Yeah I've gathered a few logs for them over the last week, hopefully they can work out what is going on.
**My connection is now down to 46Mbps from 69Mbps.
-
Yeah I've gathered a few logs for them over the last week, hopefully they can work out what is going on.
**My connection is now down to 46Mbps from 69Mbps.
Can i just ask if you are getting a lot of resyncs. I watch my xdsl link times go from 1 up to max of 6 I have had in a day. This is on the beta firmware r4786_792_63b4abf00_beta. Don't seem to be getting the 2am resync for the data logs update to BT servers at the moment either i am putting that down to the resyncs in the day.
I am also in the process of getting logs. Slow process but hopefully we will get somewhere..
-
Can i just ask if you are getting a lot of resyncs. I watch my xdsl link times go from 1 up to max of 6 I have had in a day. This is on the beta firmware r4786_792_63b4abf00_beta. Don't seem to be getting the 2am resync for the data logs update to BT servers at the moment either i am putting that down to the resyncs in the day.
I am also in the process of getting logs. Slow process but hopefully we will get somewhere..
No, my connection seems to be stable but I'm getting a massive drop in sync speeds. The firmware I've been provided is a debug version, I need to get some logs using the alternate modem codes which I will attempt at the weekend, I tried it last week and it was hit or miss if it would generate the required log codes.
-
Quick update on this buggy firmware: last few days due to repairing works at home, I had to switch off the mains electricity a few times, and once back up, each time the modedm re-synced at a slower speed (after last time it dispalys a sync speed of 14,156 Kb/s)... well, actually that's what is displayed on the GUI, but in reality the sync speed is still above 79Mb/s - I checked this morning on the Zen portal and it said 79,666 Kb/s and did several online speed tests which were all above 73 Mb/s :graduate:
I contacted DrayTek UK and they provided me with another beta firmware (https://www.draytek.co.uk/download/support/files/v166_0225_api5337_mdm1.zip) but problem is not solved, awaiting their reply ???
The saga continues :no:
-
Don't seem to be getting the 2am resync for the data logs update to BT servers at the moment either i am putting that down to the resyncs in the day.
Huh? There's no such thing.
Sounds like the DLM taking action on the line which should NOT be a daily occurrence.
-
With that firmware they should have asked you to run a command in the console for some logs. That also had resync issues and i asked if i could go back to the original which they said yes and told me it was only for getting the logs. So far none of the firmware i have been provided makes any difference. They have also not been in contact with me since. So we shall see.
They just asked me to run this: vdsl status lfsg
and that was the output:
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
DSL_UPSTREAM: bTrellisEnable=1 bBitswapEnable=0 bReTxEnable=0 bVirtualNoiseSupport=0
DSL_DOWNSTREAM: bTrellisEnable=1 bBitswapEnable=0 bReTxEnable=0 bVirtualNoiseSupport=0
-
I see Draytek have officially released a new firmware (v4.2.3) for the EU model V166-A.
As far as I can tell it should work for both the GEN1 & GEN2 versions.
See: https://fw.draytek.com.tw/Vigor166/Firmware/v4.2.3/
Nothing yet for the UK version.
-
It does look like the modem code has been updated, interesting to see how that affects people's connections. For the moment I'm going to stay on my Vigor 130, so far my connection won't resync faster than 48Mbps, I think I'm going to need an engineer out to reset the line.
-
I see Draytek have officially released a new firmware (v4.2.3) for the EU model V166-A.
As far as I can tell it should work for both the GEN1 & GEN2 versions.
See: https://fw.draytek.com.tw/Vigor166/Firmware/v4.2.3/
Nothing yet for the UK version.
The file "Vigor166_4.2.3_MDM1.zip" has got the same two AnnexA modem codes of the v4.1.1_BT firmware.
-
They just asked me to run this: vdsl status lfsg
and that was the output:
---------------------- ATU-R Info (hw: annex A, f/w: annex A/B/C) -----------
DSL_UPSTREAM: bTrellisEnable=1 bBitswapEnable=0 bReTxEnable=0 bVirtualNoiseSupport=0
DSL_DOWNSTREAM: bTrellisEnable=1 bBitswapEnable=0 bReTxEnable=0 bVirtualNoiseSupport=0
Other codes:
> acog, AutobootConfigOptionGet
> acos, AutobootConfigOptionSet
> acs, AutobootControlSet
> alf, AutobootLoadFirmware
> asecg, AutobootScriptExecuteConfigGet
> asecs, AutobootScriptExecuteConfigSet
> asg, AutobootStatusGet
> aufg, AutobootUsedFirmwareGet
> alig, AuxLineInventoryGet
> bbsg, BandBorderStatusGet
> bpstg, BandPlanSTatusGet
> bpsg, BandPlanSupportGet
> dbgmlg, DBG_ModuleLevelGet
> dbgmls, DBG_ModuleLevelSet
> dmms, DeviceMessageModifySend
> dms, DeviceMessageSend
> esmcg, EventStatusMaskConfigGet
> esmcs, EventStatusMaskConfigSet
> fddg, FilterDetectionDataGet
> fpsg, FramingParameterStatusGet
> g997amdpfcg, G997_AlarmMaskDataPathFailuresConfigGet
> g997amdpfcs, G997_AlarmMaskDataPathFailuresConfigSet
> g997amlfcg, G997_AlarmMaskLineFailuresConfigGet
> g997amlfcs, G997_AlarmMaskLineFailuresConfigSet
> g997bang, G997_BitAllocationNscGet
> g997bansg, G997_BitAllocationNscShortGet
> g997cdrtcg, G997_ChannelDataRateThresholdConfigGet
> g997cdrtcs, G997_ChannelDataRateThresholdConfigSet
> g997csg, G997_ChannelStatusGet
> g997dpfsg, G997_DataPathFailuresStatusGet
> g997dfr, G997_DeltFreeResources
> g997dhling, G997_DeltHLINGet
> g997dhlinsg, G997_DeltHLINScaleGet
> g997dhlogg, G997_DeltHLOGGet
> g997dqlng, G997_DeltQLNGet
> g997dsnrg, G997_DeltSNRGet
> g997fpsg, G997_FramingParameterStatusGet
> g997gang, G997_GainAllocationNscGet
> g997gansg, G997_GainAllocationNscShortGet
> g997lstg, G997_LastStateTransmittedGet
> g997lacg, G997_LineActivateConfigGet
> g997lacs, G997_LineActivateConfigSet
> g997lfsg, G997_LineFailureStatusGet
> g997lisg, G997_LineInitStatusGet
> g997lig, G997_LineInventoryGet
> g997listrg, G997_LineInventorySTRingGet
> g997lis, G997_LineInventorySet
> g997lsg, G997_LineStatusGet
> g997lspbg, G997_LineStatusPerBandGet
> g997ltsg, G997_LineTransmissionStatusGet
> g997pmsft, G997_PowerManagementStateForcedTrigger
> g997pmsg, G997_PowerManagementStatusGet
> g997racg, G997_RateAdaptationConfigGet
> g997racs, G997_RateAdaptationConfigSet
> g997smr, G997_SnmpMessageReceive
> g997sms, G997_SnmpMessageSend
> g997sang, G997_SnrAllocationNscGet
> g997sansg, G997_SnrAllocationNscShortGet
> g997xtusecg, G997_XTUSystemEnablingConfigGet
> g997xtusecs, G997_XTUSystemEnablingConfigSet
> g997xtusesg, G997_XTUSystemEnablingStatusGet
> help, Help
> hsdg, HybridSelectionDataGet
> ics, InstanceControlSet
> isg, InstanceStatusGet
> lecg, LastExceptionCodesGet
> lfcg, LineFeatureConfigGet
> lfcs, LineFeatureConfigSet
> lfsg, LineFeatureStatusGet
> locg, LineOptionsConfigGet
> locs, LineOptionsConfigSet
> lsg, LineStateGet
> llsg, LoopLengthStatusGet
> llcg, LowLevelConfigurationGet
> llcs, LowLevelConfigurationSet
> mlsg, MiscLineStatusGet
> mfcg, MultimodeFsmConfigGet
> mfcs, MultimodeFsmConfigSet
> mfsg, MultimodeFsmStatusGet
> nsecg, NotificationScriptExecuteConfigGet
> nsecs, NotificationScriptExecuteConfigSet
> pm15meet, PM_15MinElapsedExtTrigger
> pmbms, PM_BurninModeSet
> pmcc15mg, PM_ChannelCounters15MinGet
> pmcc1dg, PM_ChannelCounters1DayGet
> pmccsg, PM_ChannelCountersShowtimeGet
> pmcctg, PM_ChannelCountersTotalGet
> pmchs15mg, PM_ChannelHistoryStats15MinGet
> pmchs1dg, PM_ChannelHistoryStats1DayGet
> pmct15mg, PM_ChannelThresholds15MinGet
> pmct15ms, PM_ChannelThresholds15MinSet
> pmct1dg, PM_ChannelThresholds1DayGet
> pmct1ds, PM_ChannelThresholds1DaySet
> pmcg, PM_ConfigGet
> pmcs, PM_ConfigSet
> pmdpc15mg, PM_DataPathCounters15MinGet
> pmdpc1dg, PM_DataPathCounters1DayGet
> pmdpcsg, PM_DataPathCountersShowtimeGet
> pmdpctg, PM_DataPathCountersTotalGet
> pmdpfc15mg, PM_DataPathFailureCounters15MinGet
> pmdpfc1dg, PM_DataPathFailureCounters1DayGet
> pmdpfcsg, PM_DataPathFailureCountersShowtimeGet
> pmdpfctg, PM_DataPathFailureCountersTotalGet
> pmdpfhs15mg, PM_DataPathFailureHistoryStats15MinGet
> pmdpfhs1dg, PM_DataPathFailureHistoryStats1DayGet
> pmdphs15mg, PM_DataPathHistoryStats15MinGet
> pmdphs1dg, PM_DataPathHistoryStats1DayGet
> pmdpt15mg, PM_DataPathThresholds15MinGet
> pmdpt15ms, PM_DataPathThresholds15MinSet
> pmdpt1dg, PM_DataPathThresholds1DayGet
> pmdpt1ds, PM_DataPathThresholds1DaySet
> pmetr, PM_ElapsedTimeReset
> pmlesc15mg, PM_LineEventShowtimeCounters15MinGet
> pmlesc1dg, PM_LineEventShowtimeCounters1DayGet
> pmlescsg, PM_LineEventShowtimeCountersShowtimeGet
> pmlesctg, PM_LineEventShowtimeCountersTotalGet
> pmleshs15mg, PM_LineEventShowtimeHistoryStats15MinGet
> pmleshs1dg, PM_LineEventShowtimeHistoryStats1DayGet
> pmlfc15mg, PM_LineFailureCounters15MinGet
> pmlfc1dg, PM_LineFailureCounters1DayGet
> pmlfcsg, PM_LineFailureCountersShowtimeGet
> pmlfctg, PM_LineFailureCountersTotalGet
> pmlfhs15mg, PM_LineFailureHistoryStats15MinGet
> pmlfhs1dg, PM_LineFailureHistoryStats1DayGet
> pmlic15mg, PM_LineInitCounters15MinGet
> pmlic1dg, PM_LineInitCounters1DayGet
> pmlicsg, PM_LineInitCountersShowtimeGet
> pmlictg, PM_LineInitCountersTotalGet
> pmlihs15mg, PM_LineInitHistoryStats15MinGet
> pmlihs1dg, PM_LineInitHistoryStats1DayGet
> pmlit15mg, PM_LineInitThresholds15MinGet
> pmlit15ms, PM_LineInitThresholds15MinSet
> pmlit1dg, PM_LineInitThresholds1DayGet
> pmlit1ds, PM_LineInitThresholds1DaySet
> pmlsc15mg, PM_LineSecCounters15MinGet
> pmlsc1dg, PM_LineSecCounters1DayGet
> pmlscsg, PM_LineSecCountersShowtimeGet
> pmlsctg, PM_LineSecCountersTotalGet
> pmlshs15mg, PM_LineSecHistoryStats15MinGet
> pmlshs1dg, PM_LineSecHistoryStats1DayGet
> pmlst15mg, PM_LineSecThresholds15MinGet
> pmlst15ms, PM_LineSecThresholds15MinSet
> pmlst1dg, PM_LineSecThresholds1DayGet
> pmlst1ds, PM_LineSecThresholds1DaySet
> pmrtc15mg, PM_ReTxCounters15MinGet
> pmrtc1dg, PM_ReTxCounters1DayGet
> pmrtcsg, PM_ReTxCountersShowtimeGet
> pmrtctg, PM_ReTxCountersTotalGet
> pmrths15mg, PM_ReTxHistoryStats15MinGet
> pmrths1dg, PM_ReTxHistoryStats1DayGet
> pmrtt15mg, PM_ReTxThresholds15MinGet
> pmrtt15ms, PM_ReTxThresholds15MinSet
> pmrtt1dg, PM_ReTxThresholds1DayGet
> pmrtt1ds, PM_ReTxThresholds1DaySet
> pmr, PM_Reset
> pmsmg, PM_SyncModeGet
> pmsms, PM_SyncModeSet
> ptsg, PilotTonesStatusGet
> quit, Quit
> rccg, RebootCriteriaConfigGet
> rccs, RebootCriteriaConfigSet
> rusg, ResourceUsageStatisticsGet
> se, ScriptExecute
> sicg, SystemInterfaceConfigGet
> sics, SystemInterfaceConfigSet
> sisg, SystemInterfaceStatusGet
> tmcs, TestModeControlSet
> tmsg, TestModeStatusGet
> vig, VersionInformationGet
-
Is there any modem code that performs better than the others when connecting to the Openreach UK network?
-
Is there any modem code that performs better than the others when connecting to the Openreach UK network?
On my ECI line (Zen is currently my ISP), I tried both 123230_05 and 123210_14 and while with the former I was syncing at full speed (79,991 Kb/s) with the latter the sync was 73,693 Kb/s.
-
The UK version of the new firmware has now appeared (v4.2.3.BT)
https://www.draytek.co.uk/support/downloads/vigor-166
-
Eventually, my G.fast line went live, so far so good :fingers:
-
I finally got my g.fast service yesterday.
I upgraded the Vigor 166 to the latest UK firmware prior to using it on the line. Otherwise, it is left with all the default settings at the moment. This includes its IP which is 192.168.2.1. All good.
My question is though, previously I had a Vigor 130 in my setup and could connect to the modem directly from my browser (my main network is on different subnet 192.168.178.1/24) by using its IP address, which is the same as the Vigor 166. However I can no longer connect to the modem this way, although I can plug my laptop into the other LAN port on the modem and connect to it that way. Not as convenient. My entire network, router setup has not changed so am a little puzzled.
So - does anyone know what I should change in the modem config to allow a connection via my browser on my main network?
-
I finally got my g.fast service yesterday.
I upgraded the Vigor 166 to the latest UK firmware prior to using it on the line. Otherwise, it is left with all the default settings at the moment. This includes its IP which is 192.168.2.1. All good.
My question is though, previously I had a Vigor 130 in my setup and could connect to the modem directly from my browser (my main network is on different subnet 192.168.178.1/24) by using its IP address, which is the same as the Vigor 166. However I can no longer connect to the modem this way, although I can plug my laptop into the other LAN port on the modem and connect to it that way. Not as convenient. My entire network, router setup has not changed so am a little puzzled.
So - does anyone know what I should change in the modem config to allow a connection via my browser on my main network?
I don't have the Vigor 160 connected at the moment, but you should be able to connect the 2nd LAN port to your router on the internal network and configure it with an IP address in the same network as your PC, the 192.168.178.0/24 network.
-
I don't have the Vigor 160 connected at the moment, but you should be able to connect the 2nd LAN port to your router on the internal network and configure it with an IP address in the same network as your PC, the 192.168.178.0/24 network.
I can confirm that this works when running the V166-K in Bridge mode:
- On the V166, I set an IP (e.g. 192.168.178.X) in LAN > General Setup
- On my router (also Vigor), I used the LAN > Bind IP to Mac to do just that - set 192.168.178.X to always be assigned to the V166's MAC address
I'm upgrading from VDSL2 to G.fast soon, so I got the V166 in anticipation (due to helpful advice on this forum!). Have got it all working with my existing VDSL2 connection, so hopefully the transition over to G.fast will be smooth.
-
For anyone with an EU GEN1 or GEN2 model, DrayTek in Germany now has a dedicated BETA firmware page here:
http://draytek.com/download_de/Firmwares-Modem/Vigor160-Serie/Vigor166/BETA-TEST/
-
I see someone in the UK is auctioning off the latest GEN2 Version of the EU variant on eBay at the moment, a German import apparently.
-
I see someone in the UK is auctioning off the latest GEN2 Version of the EU variant on eBay at the moment, a German import apparently.
any chance of a link to the ebay auction?
-
I am also interested https://www.ebay.co.uk/itm/114847396131?hash=item1abd703123:g:JbkAAOSwpjxgw4pA
-
Apparently it didn't sell, no sign of a re-listing.
-
Has anyone managed to get the full 330mb download speed on G.Fast using the V166?
I ask as I have 2 friends who have these (one has the UK version, the other is a GEN1 EU model) & both get just shy of 321Mb.
However the max attainable speed is showing as being much higher, at 384mb & 395mb.
I used my XMG3927 (in bridge mode) to test their lines & got the full 330Mb on both without any trouble, also the max. speeds were slightly higher.
The SNR seems to be the key, the V166 settles at around 17-18db whereas the XMG3927 is in the 13-15db region.
Could it be a firmware issue or just poor hardware?
-
Could it be a firmware issue or just poor hardware?
. . . or both.
I think it will be rather difficult to determine. There are so few members with a G.Fast service and hardware that allows the circuit to be monitored. :-\
-
I think the firmware is not mature yet, still lots of work to do for Draytek...
They gave me a beta firmware (https://www.draytek.co.uk/download/support/files/v166_G86434_beta.zip) which is supposed to fix the issue of not displaying CRC errors: still too many '0' unfortunately.
-
Been a few weeks since upgrading to 4.2.3_BT but anecdotally there have been zero instances of 100% packet loss when maxing out the connection since the update:
Before:
(https://i.imgur.com/PN75Yz6.png)
After:
(https://i.imgur.com/ldxXlCt.png)
Using G.Fast w/ Zen.
-
Hello :)
Is there something on this model 166 that i can tweak or lower the dB value of INP through CLI on VDSL2 line (when G.INP disabled) like to make 0/0 dB "instead of 4/4 by G.INP setted by DLM"
what's the chipset on this model Vigor 166 ?
and is this brand >Draytek< the best i can get to tweak my xDSL line with CLI or theres better brand?!
-
I think the chipset is probably Lantiq / Intel.
Welcome to the forum!
-
Hello :)
Is there something on this model 166 that i can tweak or lower the dB value of INP through CLI on VDSL2 line (when G.INP disabled) like to make 0/0 dB "instead of 4/4 by G.INP setted by DLM"
what's the chipset on this model Vigor 166 ?
and is this brand >Draytek< the best i can get to tweak my xDSL line with CLI or theres better brand?!
AFAIK you have no control over INP, trying to do so would likely just make DLM raise INP even more to compensate and/or maybe your line unstable.
INP is a delay imposed by performing a form of error correction that interleaves the data. The numbers provided AFAIK refer to the level of complexity of the interleaving and the delay imposed from it, nothing to do with a dB value (which refer the characters of the line itself).