larryllix Posted March 19, 2021 Posted March 19, 2021 My ASUS routers handles my 75 LAN devices just fine. Only the master node router provides DHCP. However my older ASUS router caused really obscure havoc at about 51 devices. Drove me around the bend for about two years. Why are you not using the range of .0 to .254? My guess is that is causing confusion. Also using 8.8.8.8 IMHO may be causing you probems. How can an ISY without an IP address talk to a cloud based DNS server via a router that can't recognise the ISY? Again. Try the full subnet range and use the router address for it's DNS handler. Keep things standard and simple until you get it working.
larryllix Posted March 20, 2021 Posted March 20, 2021 11 hours ago, n4bos said: Not quite sure what you mean... If I set the ISY to not use DHCP, then set the IP address to 192.168.0.50 for example, then the subnet mask to the router's 255.255.255.0, then the gateway to the router's IP of 192.168.0.1, are you saying to leave the DNS blank? You can't expect your ISY to talk to anything on the router's subnet when you have excluded IS from that allowed range of IP addresses. You have restricted your router to a tight range of IP addresses and made all other devices blind to your ISY. Unless you set your router to "ad-hoc" LAN (not likely) it controls all traffic on your LAN and all traffic must be handled by your router. Being outside of the IP address range tells the router to ignore your ISY.
n4bos Posted March 20, 2021 Author Posted March 20, 2021 The default range was .100-.199 and i don't have nearly that many devices so I just left it at that range. In addition, I have a number of reserved address for cameras and such that are outside the DHCP range. I have not activated all of them in this router while I chased this problem. I have tried using my router address as the DNS and it works for a short time and then disconnects from the portal again. I'm really weary of trying to make this tplink router work. I've about decided it's going back. I may give Dd-wrt a try on my dlink and see how that goes. Lots of people seem to have great luck with that. It's very frustrating because the dlink just works! No hassles. MrBill had very similar results with a tplink router and I have a friend who has an IT support company and he has not had good luck with tplink. Won't use them in fact. Thanks for the suggestions nut I think this thing is flawed.
n4bos Posted March 20, 2021 Author Posted March 20, 2021 I have tried using DHCP which puts it INSIDE the DHCP range and tried a reserved address outside the DHCP range. Both will sometimes work for a short time and then stop. With the dlink, the ISY has ALWAYS had a reserved address outisde the DHCP range and it has (and does) work fine. With this tplink router, it doesn't seem to care if the address is DHCP assigned or not.... it only works for a short time and then stops. BTW, I have tried 192.168.0.1 for the DNS as well as 1.1.1.1, 8.8.4.4 and 8.8.8.8. None work for very long and some, not at all. I think I mentioned that I have another device that "normally" works fine with UPNP on the dlink. It will NOT work with UPNP on the tplink and requires manually setting port forwarding to work. I really think tplink has a bug in their UPNP protocol and perhaps other parts of the software as well.
n4bos Posted March 20, 2021 Author Posted March 20, 2021 Just to be sure and as a test, I opened up the DHCP range all the way from .1 to .254. No difference. Still won't connect.
larryllix Posted March 20, 2021 Posted March 20, 2021 (edited) 3 hours ago, n4bos said: Just to be sure and as a test, I opened up the DHCP range all the way from .1 to .254. No difference. Still won't connect. Ever try a different cable or another Ethernet location in your house, a different port on your router? Kind'o sounds like an intermittent connection. How about factory resetting the router? Edited March 20, 2021 by larryllix
n4bos Posted March 20, 2021 Author Posted March 20, 2021 6 hours ago, larryllix said: Ever try a different cable or another Ethernet location in your house, a different port on your router? Kind'o sounds like an intermittent connection. How about factory resetting the router? Oh yah, as a matter of fact, I replaced the network cable from the router to the switch yesterday just to clean things up as bit but it made no difference. I'm putting back the old dlink this morning. I'm tired of messing with the tplink. BTW, I did a search last night and there are quite a few reports of tplink problems with UPNP. I'll report back after putting the dlink back but I bet it's back up and running 100%. Stand by... Steve 1
n4bos Posted March 20, 2021 Author Posted March 20, 2021 Well, as a wrap up to this story, I reinstalled the dlink DIR-880L router and instantly, the ISY is back on line with all functions alive and well. If anyone reads this in the future, be very wary of tpink routers. At least two of us are done with them! Steve
MrBill Posted March 20, 2021 Posted March 20, 2021 2 hours ago, n4bos said: At least two of us are done with them! yep... I use an ubiquiti ER-12 currently. I started with an ER-X but needed an upgrade when I switched the primary connection to 1gig. As I mentioned above Re: the tp-link I was needing a dual wan router, I use a second LTE modem as backup. The edgerouter line is solid, the DHCP and Routing tables with both take whatever you can throw at them (unlike consumer routers that have limited size in for both tables). Much like a certain automation controller we all love they have V1 firmware and V2 firmware... v2 was beta and had issues for years. I stuck with v1 which they may have now stopped updating (last v1 firmware was 1 year ago), I'm still resistant to moving to V2 tho. There is a learning curve. It's not exactly plug and play like consumer all-in-one units. Your wireless AP's are separate entities. There is a GUI, but several things are left out of it, or harder to configure, so you will likely learn to use the CLI. It's basically a dedicated version of debian linux with router software built-in. I added a couple of scripts so that the ISY could keep track of minutes per month that the primary WAN was down, and set it up to send me Pushover notifications when it switches between the primary WAN and Failover WAN. I haven't rebooted the router in 323 days.... It's rock solid. Quote bill@ubnt:~$ uptime 08:22:25 up 323 days, 22:35, 1 user, load average: 0.21, 0.17, 0.11
larryllix Posted March 20, 2021 Posted March 20, 2021 (edited) 7 hours ago, n4bos said: Oh yah, as a matter of fact, I replaced the network cable from the router to the switch yesterday just to clean things up as bit but it made no difference. I'm putting back the old dlink this morning. I'm tired of messing with the tplink. BTW, I did a search last night and there are quite a few reports of tplink problems with UPNP. I'll report back after putting the dlink back but I bet it's back up and running 100%. Stand by... Steve So tplink doesn't threaten legal action against the people to remove comments that libel them on forums? It's just like linux. It was rock solid (like MSDos and all the rest ) until they started trying to come up to MS standards with a GUI. Now it crashes like the best of them. My older ASUS router handled all the DHCP table I could throw at it until it actually got used. The DHCP table was fine but the rest wasn't. The third party (super bug fixing) firmware made it worse. Now I stick with the manufacturer's firmware that understands the hardware inside. These WiFi repeating systems have made it worse too. I haven't seen one yet that functions properly or doesn't grind the speeds down to a crawl. WTF are you using uPnP for with ISY? I don't even know why ISY has it as an option. Edited March 20, 2021 by larryllix
Geddy Posted March 20, 2021 Posted March 20, 2021 9 hours ago, n4bos said: If anyone reads this in the future, be very wary of tpink routers. At least two of us are done with them! I'll keep an eye out on this in the future, but I've had 2 different tplink routers and no issues with the ISY. I forget my old model number, but currently been on the Deco 9+ for about 18 months and didn't have any issues going from one to the other and don't have issues accessing the ISY remotely. I know at one point their DDNS service was having issues and don't have the option to use another DDNS service directly in the router so it was a little tricky, but thankfully not having to reboot router or modem my IP has said steady for quite a while. Just my experience wasn't as bad as yours.
n4bos Posted March 20, 2021 Author Posted March 20, 2021 (edited) Hi Geddy, Lots of people use the TP-Link routers and have no issues but I'm convinced there are issues with the A20. I'm not unfamiliar with networks but I've never had issues like this. I think I'm going to try dd-wrt on my dlink if for no other reason than the learning exercise but MrBill has me thinking seriously about a Ubiquiti prosumer router. I'm studying those now and it looks like a LOT of power to play with. Thanks for your reply. Steve Edited March 21, 2021 by n4bos
n4bos Posted March 27, 2021 Author Posted March 27, 2021 As kind of a final update, I ordered a Ubiquiti ER-4 router as recommended my MrBill. While not a "drop in" router in that it takes some level of network understanding to program, it is a SMOKING router. the ISY worked with NO modifications to the settings I used with the old dlink and unlike the TP-Link, there were NO issues with it connecting to the portal. Thanks to all who offered suggestions and assistance and especially to MrBill who helped me make the decision to go with the ER-4.
Recommended Posts