Kitz Forum
Broadband Related => Broadband Hardware => Topic started by: DaleLamar on September 14, 2017, 06:46:04 PM
-
Hello everyone,
I have just bought a used TP-Link TD-W8980 modem router and I can't get it to sync with my ISP - idnet. Any help/feedback you can offer will be gratefully received.
This is what I've tried so far:
I did a factory reset and used the Quick Setup. I copied the VPI/VCI settings from my old router interface: 0 and 38, chose PPPoA, entered my connection username and password and then Save. Setup status then reports all configuring as success, no errors. Then I click Finish and see a basic status page showing line stats, WAN and LAN status etc. WAN status shows the correct VPI/VCI, but nothing in the IP/Mask, Gateway or DNS sections. The Status box in the WAN section alternates between initialising/disconnected. The ADSL light on the front of the router occasionally flashes twice.
I click on Network in the left hand menu which takes me into WAN Settings. In the WAN Service Setup section it shows the Connection Type: PPPoA, my PPP username and password, Connection Mode: Always on, and Authentication Type: AUTO_AUTH (I have tried CHAP too). I click on Advance and uncheck IGMP Proxy, check Use IP address specified by ISP and enter it, and also manually enter some DNS servers, 8.8.4.4 and 8.8.8.8. Click Save. Back to the Basic Status page, still no connection.
I've tried deleting the connection details and entering the connection details manually in the WAN Service Setup section, choosing IPoA (I know this doesn't give me the opportunity to enter my username and password but I just wanted to try it to see what the result was) and something odd happened: I enter my static IP address, Subnet Mask, Gateway IP and DNS servers and click Save, then a window pops up which says:
'The IP address does not match the subnet mask: illegal host number.'
It doesn't allow me to save so I can't go any further with that. The thing that is odd is that it is the correct IP address and subnet mask so I don't know why it would say that.
Anyway, I've re-flashed the firmware and tried again but things are no different, it still won't sync to the ISP.
If anyone has any idea what the problem might be I would be very grateful as I don't know what to try next. I have contacted the person I bought the router from and he says that it was working fine for him (as an ADSL modem/router) and the only reason he sold it was because he needed a VDSL router for his new connection, so I have to take this at face value and assume that the router is not faulty.
Cheers.
Dale
-
Welcome to the Kitz forum. :)
Having read through your description, there is just one point that is not clear. Do you have a static IPv4 address? Or is it dynamically allocated by your ISP?
-
Welcome to the Kitz forum. :)
Having read through your description, there is just one point that is not clear. Do you have a static IPv4 address? Or is it dynamically allocated by your ISP?
Thanks for the welcome, burakkucat. :)
Yes, I have a static IPv4 address given to me by my ISP when I joined them years ago. In my old netgear DG834G, I could enter the IP address manually or let the ISP set it. Either way, it is the same.
-
I have no experience with the TP-Link TD-W8980, so these are just my general suggestions --
- Power down and completely disconnect the device from everything other than its PSU.
- Power up the device and leave it for a few minutes to stabilise.
- Perform a factory reset by pressing the relevant recessed button with your favourite straightened out paper-clip. (I keep an old DMM probe specifically for such purposes.) Leave the device alone for a few minutes, allowing it to stabilise, once again.
- Configure an Ethernet port appropriately on the computer that you will use to enter the device's GUI configuration screen.
- Call up a web-browser. Enter the GUI configuration screen. Do not use the "wizard", as I suspect it will fail as the device is not connected to the incoming line.
- Manually set the static IPv4 address as specified by your ISP and all the other required parameters that have been provided.
- Save the configuration and then power down the device.
- Reconnect the incoming line, etc.
- Power up the device, wait for it to stabilise and then test.
If that fails, perhaps other members -- with experience of the device -- will try to assist.
-
I will try that tomorrow. Thanks vey much.
-
Can you test on a friends line. I have the W9970 which I assume is similar and in the quick setup you should select ADSL and input the other settings there.
-
Maybe a silly question but what is the product/service you're subscribed to at idnet?
The details you provide sound like it is an ADSL service. However, if you're on a VDSL/FTTC service those settings are incorrect - that needs PTM mode using PPPoE (no VPI/VCI) and a username and password.
The device also needs to be in the Wireless Router Operation mode
-
Well I've tried the procedure suggested by burakkucat, but no change, the router still wouldn't sync to the ISP.
The router is upstairs on the end of an extension cable so I though I'd take it down to the room that has the BT socket and try it there, plugged directly into the BT ADSL socket. I did this using the RJ11 cable that came with the router as it looked unused. The only difference was that the router tried more to sync, ie. the ADSL light on the front of the router flashed a few times, then stopped, the flashed a few times again and kept doing this. Previously, upstairs, and with the old RJ11 cable, it would just flash a couple of times every now and then. I don't know why this would happen or what it means but I'm taking notice of anything different that occurs in case it triggers anything for me or anyone else. Anyway, still no sync; I gave it a good five minutes of trying.
When I went back upstairs and fired up the old router to get a connection, I thought I would use the new RJ11 cable, but bizarrely, the old router would not sync whilst using the new cable. I swapped back to the old RJ11 cable and got sync as usual. I swapped the cables back and forth a couple of time because I couldn't believe what was happening. Yep, old router with new cable - no sync, old router with old cable - sync. Poltergeist activity?
Anyway, I can't think of anything else to try, (I'm going to test the router on a different line when I can, as suggested by banger) I'm putting the correct VPI/VCI, PPoA and all the other bits in all the right places but it won't sync with the ISP. I have already written to my ISP and asked if there was anything in their logs that would give me a clue, but although they replied and offered to go through the settings with me if I gave them a ring, they didn't offer up any log details.
Here's some entries from the TP-Link router log (see attachment) though, if anyone knows can pinpoint a particular problem from the log entries I would love to know.
-
Can you test on a friends line. I have the W9970 which I assume is similar and in the quick setup you should select ADSL and input the other settings there.
Good idea, I'll test it on a different line as soon as I can, probably next week sometime.
Thanks.
-
Maybe a silly question but what is the product/service you're subscribed to at idnet?
The details you provide sound like it is an ADSL service. However, if you're on a VDSL/FTTC service those settings are incorrect - that needs PTM mode using PPPoE (no VPI/VCI) and a username and password.
The device also needs to be in the Wireless Router Operation mode
Yes, I'm subscribed to idnet's ADSL service, so the settings are correct.
Cheers.
-
Since I last posted I bought another TP-Link router, an 8970 this time. This one would not sync to idnet, either. I spoke to Nick at idnet to see if their logs would show any useful details from my connection attempts, but apparently not.
So I've just tried both routers on another line today and they both sync to that ISP with no problem at all.
I will get back to idnet to see if they can shed any light on the situation, but does anyone here have any idea what the possible problem may be?
-
Very puzzling. :o
Your physical circuit, a broadband connection to the Internet provided by iDNET and usage of either a TP-Link TD-W8980 or a TP-Link 8970 results in failure.
A different physical circuit, a broadband connection to the Internet provided by "A.N.Other ISP" and usage of either a TP-Link TD-W8980 or a TP-Link 8970 results in success.
Upon analysis of the above two statements we can confirm two definite facts . . . that both TP-Link modem/routers that you have purchased are not defective.
The inner scientist now would like to perform a further series of experiments -- both TP-Link devices on a different physical circuit, with a broadband connection to the Internet provided by iDNET and then both TP-Link devices on your circuit, with a broadband connection to the Internet provided by "A.N.Other ISP".
Quite honestly I think you need to explain the results of your experiments to iDNET and request that they assist. :-\
-
Which version of the 8970 was it? The 8970v1 is essentially the same hardware as the 8980 apart from the wifi, while the 8970v3 is a completely different Broadcom chipset device. The 8980 and 8970v1 have the Lantiq VRX-268 chip.
-
Very puzzling. :o
Your physical circuit, a broadband connection to the Internet provided by iDNET and usage of either a TP-Link TD-W8980 or a TP-Link 8970 results in failure.
A different physical circuit, a broadband connection to the Internet provided by "A.N.Other ISP" and usage of either a TP-Link TD-W8980 or a TP-Link 8970 results in success.
Upon analysis of the above two statements we can confirm two definite facts . . . that both TP-Link modem/routers that you have purchased are not defective.
The inner scientist now would like to perform a further series of experiments -- both TP-Link devices on a different physical circuit, with a broadband connection to the Internet provided by iDNET and then both TP-Link devices on your circuit, with a broadband connection to the Internet provided by "A.N.Other ISP".
Quite honestly I think you need to explain the results of your experiments to iDNET and request that they assist. :-\
Yes, puzzling indeed!
Unfortunately, I don't know anyone else who uses idnet, and of course I'm not about to change my ISP just to try the devices on my circuit with another ISP. So that's as far as I can go with the experiment.
I'll share what idnet say about it when I hear back from them.
-
Which version of the 8970 was it? The 8970v1 is essentially the same hardware as the 8980 apart from the wifi, while the 8970v3 is a completely different Broadcom chipset device. The 8980 and 8970v1 have the Lantiq VRX-268 chip.
My 8970 is v1.2, and the 8980 is v1.
Thanks for the information.
-
I wrote to idnet and told them that my two TP-Link routers work OK on a different line and asked for assistance. What they have said is:
Check the settings.
They have lots of customer's who use TP Link routers with no problems.
The network team are not aware of any compatibility issues with TP Link kit or any specific chip sets.
Maybe the best bet it to get a different make and model of router to test with.
So that doesn't help me a great deal I'm afraid. I don't really want to buy various makes of router to try; whether they worked or not, it wouldn't tell me what the existing problem is, only that a different router worked, or didn't. Not, why.
They have some test routers (Billion 8800nl) and have agreed to lend me one when it becomes available. They are 'pretty sure it will work, so it may not prove much'. Which it won't. But it will allow me to see if a different router will work on my line without me having to buy one. And I don't know how they can be pretty sure it will work when we don't know what the existing problem is. I would have said I was pretty sure that the TP-Link routers would work on my line. But they don't.
-
If that is their idea of customer support, then I will recommend that they as an ISP/CP should be avoided. :(
Wait for the loan of their Billion 8800NL, try it and report back. If you still get evasive nonsense from their "customer support", request a deadlock letter and then take it to the regulator.
-
If that is their idea of customer support, then I will recommend that they as an ISP/CP should be avoided. :(
Wait for the loan of their Billion 8800NL, try it and report back. If you still get evasive nonsense from their "customer support", request a deadlock letter and then take it to the regulator.
Yea, I'm pretty disappointed, I must say. I have been with idnet for ten years now and have in general been reasonably happy with the level of customer support when I've needed it, which is not very often. But in this instance I was hoping to maybe interact with an actual techy whilst my TP-Link was trying to sync. Surely the logs or some other data they have access to could indicate where the problem might lie? Maybe my assumption is way off, though, I'm just guessing. I have asked whether their logs show anything that might help, but apparently not. And they 'have no visibility for historic logs of devices trying to sync up', which is why a live session with someone who knows what they're looking at might be useful.
They are not trying very hard to help me though, in my opinion.
-
They are not trying very hard to help me though, in my opinion.
Yes, that I can see from your posts. :o :(
-
Yes, that I can see from your posts. :o :(
I am currently perusing A&A's website... ;)
-
Interesting. Please update this thread, as things develop.
-
It might be worth "crossflashing" the 8980 with the 9980 firmware - the hardware is the same, and I think the 9980 firmware contains more recent Lantiq DSL code. And also unlock it to give proper telnet access - the TP-Link interface is quite limited and provides very little diagnostic information.
My 8970v1 running 9980 firmware, not connected to any line, logs alternating messages of "xDSL Ready!!" and "xDSL Leave Showtime!!". DaleLamar's logs indicated it got slightly further than that.
@DaleLamar - how long is your line and what speed are you expecting? If you have an extremely long line, it might be possible that one device can just manage to establish a connection, while another can't, with nothing being faulty or incorrectly configured.
-
It might be worth "crossflashing" the 8980 with the 9980 firmware - the hardware is the same, and I think the 9980 firmware contains more recent Lantiq DSL code. And also unlock it to give proper telnet access - the TP-Link interface is quite limited and provides very little diagnostic information.
My 8970v1 running 9980 firmware, not connected to any line, logs alternating messages of "xDSL Ready!!" and "xDSL Leave Showtime!!". DaleLamar's logs indicated it got slightly further than that.
@DaleLamar - how long is your line and what speed are you expecting? If you have an extremely long line, it might be possible that one device can just manage to establish a connection, while another can't, with nothing being faulty or incorrectly configured.
I'm 2.3 km from the exchange so I don't think there are any issues with line length. I also have no problems with connection speed; my Netgear router is currently synced at 8133 kbps down and 1325 kbps up.
With regard to crossflashing the firmware: I did consider doing that, but decided to leave it as it is for the time being, in case anything went wrong. Having said that, since I have two TP-Link routers to play with, I may well try it with one of them.
Cheers.
-
This afternoon I wrote to A&A and explained about my TP-Link router being able to connect to an ISP on a different line to mine, and not being able to connect to my own ISP on my line. I asked if they had a test account that I could use to see if my TP-Link router would connect to their ADSL service. (I had made an enquiry the previous evening about some aspect of their service, so it wasn't completely out of the blue.) A chap from their sales team replied and gave me some logon details, then spent quite a bit of time going back and forth with me via email as I tried to connect with the TP-Link router and we tried to figure out what the problem could be.
The TP-Link router could not connect and we didn't manage to solve the problem, but I was very impressed by his attitude and willingness to try to help me.
I made the same connection with my Netgear router, which connected just fine...
-
Have you tried explicitly setting the DSL mode to ADSL2 or even ADSL1?
-
I click on Advance and uncheck IGMP Proxy, check Use IP address specified by ISP and enter it, and also manually enter some DNS servers, 8.8.4.4 and 8.8.8.8. Click Save. Back to the Basic Status page, still no connection.
Try setting it up as if you had a dynamic IP - eg Obtain IP Address Automatically. IDnets RADIUS should still allocate the correct IP (even though you have a static IP) based on your login details. Same with other BTw based ISP's such as Plusnet - there's no need to enter your static IP. I never do.
-
Have you tried explicitly setting the DSL mode to ADSL2 or even ADSL1?
I hadn't tried that, but just did. I tried all the settings available, but still no connection.
-
Try setting it up as if you had a dynamic IP - eg Obtain IP Address Automatically. IDnets RADIUS should still allocate the correct IP (even though you have a static IP) based on your login details. Same with other BTw based ISP's such as Plusnet - there's no need to enter your static IP. I never do.
Yep, tried it that way too. Using the Quick Setup and just setting the VPI/VCI, username and password.
Thanks.
-
Are you actually syncing to the DSLAM? You mentioned in the 1st post that the ADSL light is flashing twice. I've no idea how that particular model works or shows sync, but without a successful sync you won't get any WAN connection.
-
It does look like it's the DSL link that's not being established. I think the logs indicate it detects the DSLAM, but fails at some stage before fully establishing the DSL link.
-
Then it's pointless trying all the different WAN settings as none will work without sync.
Try getting sync 1st.
Have you specified the ADSL modulation type? What options are available on the DSL settings page?
-
Are you actually syncing to the DSLAM? You mentioned in the 1st post that the ADSL light is flashing twice. I've no idea how that particular model works or shows sync, but without a successful sync you won't get any WAN connection.
No, it's not syncing to the DSLAM; that's the problem.
It does look like it's the DSL link that's not being established. I think the logs indicate it detects the DSLAM, but fails at some stage before fully establishing the DSL link.
That's right: the link is not being established. Hence, no sync to the DSLAM.
Yesterday, the A&A chap was monitoring as I was trying to connect to their test account. Afterwards, he said: "NO PPP attempts to us, odd."
-
Yes changing any the WAN settings will make absolutely no difference till you get sync. Concentrate on the DSL settings.
What DSL modulation does your other modem use? ADSL/ADSL2/ADSL2+?
Try specifically setting this rather than choosing automatic. What other DSL settings are on that same page?
edit: it's under Network > DSL settings.
Try a specific modulation rather than Auto sync up.
Try unchecking SRA also.
-
Yes changing any the WAN settings will make absolutely no difference till you get sync. Concentrate on the DSL settings.
What DSL modulation does your other modem use? ADSL/ADSL2/ADSL2+?
Try specifically setting this rather than choosing automatic. What other DSL settings are on that same page?
My other (Netgear DG834G v4) modem has the DSL modulation settings you mentioned; it is set to Auto.
I've tried all the DSL settings in the TP-Link router.
-
When synced the Netgear should show you which modulation you are using on the Status/log page.
I edited my post above with more to try.
-
Hi
I could be wrong sorry, as I’ve read this thread but getting slightly confused
If I read it correct, the rj11 for both cables work on netgear but not on tp, where both rj11 used does not allow the tp to sync
If this is correct, it will be the rj11 cable (probably a single pair), which are on the wrong pins
Try a full twin pair rj11, or change the pins wired to those that are not. Some use inner and some use outer (ie 14, 23)
As I say, could be wrong but have seen this over the years
Many thanks
John
-
It can't be the rj11 or the Netgear wouldn't sync with the cable. Only 1 pair in the rj11 cable is actually used. If they were on the wrong pins then the Netgear would not sync. They both use the same pins.
-
Hi
I could be wrong sorry, as I’ve read this thread but getting slightly confused
If I read it correct, the rj11 for both cables work on netgear but not on tp, where both rj11 used does not allow the tp to sync
If this is correct, it will be the rj11 cable (probably a single pair), which are on the wrong pins
Try a full twin pair rj11, or change the pins wired to those that are not. Some use inner and some use outer (ie 14, 23)
As I say, could be wrong but have seen this over the years
Many thanks
John
Hi John,
I wrote that the Negear router would not sync using the new cable.
And the TP-Link router would not sync using either the old or new cable.
Just now, looking at the cables that run upstairs, I see that I made a mistake.
I have two cables running upstairs from the downstairs BT faceplate: one is a good quality data cable, and the other is the phone cable which plugs into an RJ11 socket on a four-gang power strip. A phone or answer machine can then be plugged into the other RJ11 socket on the power strip.
When I said that I tried the new cable with the Negear router, I did. But the way I tried it was to plug it into the phone connection on the power strip. No wonder the Netgear router wouldn't sync with the new cable!
So, no poltergeist activity, just user error! :o
Cheers.
-
I've just noticed you appended a log file in one of your later posts. The log file is a bit odd, but it appears to be looping through training ok and the furthest its getting is PPP0 LCP confReq which is with the BTw RAS. Its at this point things are failing and it appears to be having difficultly setting up PPP.
You should after that get a CHAP challenge so the BTw RADIUS can set up the L2TP tunnel to the ISP.
Definitely make sure that you are not putting in a static IP info as this can and often does confuse the BTw RADIUS... as its the ISP RADIUS which verifies the PPP login and at this point dishes out the IP. I think you said in one of your posts that idNet said they could see no trace of you attempting to connect to their RADIUS.
In theory if the BTw RAS can't connect you to your ISP, it should at this point allocate one of its own [internal] dynamic IPs which will just give you access as far as the BTw backhaul for performing certain diagnostics.
Do you get anything at all on this page from the web GUI
http://wiki.kitz.co.uk/index.php/TD-W9980_Status
-
When the WAN connection is configured as "always on", the TP-Link will keep trying to bring up the PPP connection regardless of the status of the DSL link. The PPP messages in the log are a red herring. The TP-Link log would contain "xDSL Enter SHOWTIME!!" if it had succeeded in establishing the DSL link.
-
Ah right cheers. When I said odd, I wondered why it was leaving showtime, without it showing in the log and thought perhaps it was a logging issue... and why I wanted to know what showed on the status page, so we knew for certain if it was getting any sync.
Incidentally I notice there is a post on the PN forums of what appears to be similar issue on ADSL. The EU never got to the bottom of it and RMA'd the modem.
https://community.plus.net/t5/Broadband/Problems-with-TP-Link-TD-W9980-on-ADSL/td-p/1290022
-
I've just noticed you appended a log file in one of your later posts. The log file is a bit odd, but it appears to be looping through training ok and the furthest its getting is PPP0 LCP confReq which is with the BTw RAS. Its at this point things are failing and it appears to be having difficultly setting up PPP.
You should after that get a CHAP challenge so the BTw RADIUS can set up the L2TP tunnel to the ISP.
Definitely make sure that you are not putting in a static IP info as this can and often does confuse the BTw RADIUS... as its the ISP RADIUS which verifies the PPP login and at this point dishes out the IP. I think you said in one of your posts that idNet said they could see no trace of you attempting to connect to their RADIUS.
In theory if the BTw RAS can't connect you to your ISP, it should at this point allocate one of its own [internal] dynamic IPs which will just give you access as far as the BTw backhaul for performing certain diagnostics.
Do you get anything at all on this page from the web GUI
http://wiki.kitz.co.uk/index.php/TD-W9980_Status
Thanks for the information and advice.
It was A&A, using their test account. But yes, their chap said he couldn't see any PPP attempts.
The status page never shows any connection information, just 'initialising', then 'disconnected'.
Cheers.
-
As ejs explained the references to PPP in the log are a red herring.
You need to try get sync 1st. Try each of the DSL modulation available, with SRA unchecked. I believe it's Annex A although happy to be corrected there.