New VDSL line issues

[Joel]

Hi all

I would really appreciate some help with an issue with my new VDSL connection. It was installed yesterday and all went OK, I plugged in the router (a TP Link W9970) and configured it as per usual, using the wizard actually. I let it try to find the connection however it failed. So on the ISP drop down there is an entry for VDSL_IDnet. So I picked this, I was quite surprised to see it there, but it basically just configures the VLAN so it's not a big deal anyway. After letting it do it's thing, it by default leaves the DSL on auto discover mode, and I notice on the status page that it's showing an ADSL connection as live on the bridge? It is in sync and has a download and upload speed extremely similar to my old ADSL2+ connection that was ceased yesterday.... strange.

Anyway so if I manually select VDSL as the DSL type, it doesn't connect, or even try, it doesn't see the line there at all. I've done a fair few routers installs and generally it's pretty straightforward but this has just got me confused. I don't understand how it would see the adsl in sync when the line has been converted?

Can anyone offer some advice. I'll attach some pictures for some idea. Picture 1 is the correct set up, showing no connection or line. Picture 2 is after a factory reboot, no settings configured whatsoever, it shows an ADSL line in sync?

Any ideas?

thanks in advance

[Glenn]

Joel, did you get a BT modem with the install, if so fit that but do not connect the router, instead connect your PC/laptop to the router to see whether it's the line or the router. This guide is for XP but it will be similar for other versions http://community.plus.net/library/broadband/fibre-help-setting-up-a-pppoe-dialler-for-windows-xp/

[MisterW]

I would suggest that your upgrade to VDSL hasn't happened yet...

[Steve]

Does look like you've not been switched over.

[Joel]

Thanks for the replies. It was a self install so no modem was supplied. I understand that from next year this will be the only service BT offer. The upgrade has definitely been completed (at least in terms of technicality) however I agree that it looks like something hasn't happened. I spoke with Idnet support yesterday afternoon and they've not seen this before. I turned the router off, a line check went through and reported the router was in sync and authenticating at 80/20 up/down... Looks like something has gone badly wrong! Either way my adsl is no longer working so I'm stuck with 4g for the minute.

Further evidence to support a mess up is bt recorded the work being complete at 11:30. My vpn connection in didn't drop until about 3pm and I was using it until that time. I don't think that's how it works...

Will keep you updated, idnet are arranging an SFI engineer. Hopefully soon!

Thanks.

[Joel]

to follow up, SFI engineer was out today, and in his words 'the guy before made a right hash of this'. Apparently the numbers were reversed in the fibre cab so when they'd be run through they were the wrong way around. My line was connected to the ADSL filter hence I saw an adsl connection, and someone else was patched in to my VDSL service. Apparently there were 5 lines affected including the secondary school down the road. 

I always struggle to think of another company so quick to blame their 'colleagues' as BT. I'm happy the issue is resolved but their engineers are far from consistent, it really depends which way the wind blows!

IDnet were faultless throughout, taking the call Saturday afternoon to calling me Sunday morning, then again in the afternoon to arrange the engineer. Definitely makes life easier.

[Steve]

It's not the first time someone's cocked up the cabinet configuration, good news that it's sorted.

BTW completely irrelevant, but possibly more relevant with self installs being the future of FTTC. I'm now using a Vigor 130 on an ECI cabinet, seems to be performing very well ,at least it allows me to have a router of my choosing. The OpenReach ECI modem has given pretty faultless service for probably 4 years but I guess won't last forever.

[Gary]

The OpenReach ECI modem has given pretty faultless service for probably 4 years but I guess won't last forever.

Luckily I was given a 2015 ECI modem (ECI Cab) I have a spare ECI and a HG612 as well so that should keep me ok for some time to come. 

[Steve]

The unlocked HG612 I have doesn't work as well on my line as the locked ECI (early version) presumably due to the cabinet mismatch. I could have got a later ECI modem I guess much cheaper than the Vigor 130 I now have, however I wanted to see the line stats.

I realised it's not easy to see the line stats on the Vigor 130 whilst connected to the internet, but using Asuswrt-merlin, my very limited knowledge of Linux, a search of the snbforum ,I now have managed to write and copy over a couple of start up scripts -i.e  wan-start & nat-start which allow me to access via telnet or via a browser the modem GUI on it's own subnet.

So far on my ECI cabinet the Vigor 130 is performing as well as the ECI modem - early days though.

Lastly RFC 4638 is supported by the modem and the router which permits me an MTU/MTR of >1492 via PPPoE i.e. router MTU/MTR 1500

Scripts: These are copied to the /jffs/scripts writeable section of the flash memory which is enabled by default on later asuswrt-merlin firmwares

wan-start

#!/bin/sh
ifconfig `nvram get wan0_ifname`:0 192.168.2.2 netmask 255.255.255.0


(The default Vigor IP is set i.e 192.168.2.1, now idea why the above address has to be one higher but it works, the GUI is accessible at 192.168.2.1, router lan address 192.168.1.1)


nat-start

#!/bin/sh
iptables -t nat -I POSTROUTING -o `nvram get wan0_ifname` -j MASQUERADE