Print

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

[mdog3000]

Hi guys,

Im trying to use my DIR 655 as an access point from my new router, which is a TP-Link TL-R860. I've read about every post and blog I can find about this and still cant get it to work. Currently I have a cable running from the TP main router to LAN port 1 on the 655. I then plugged my computer in to LAN port 2 to configure the router.

Here is the LAN IP for my TP router



I then set the LAN IP on my 655 as something in the same format but outside of the DHCP range (which is listed in TP as 192.168.1.100-192.168.1.199)



After I save the router settings and reboot it, the only way I can access the 655 settings is by creating a static IP for the computer, but I still get no internet (see below).



Can someone please tell me what I am doing wrong? I have spent hours trying to get this to work.
Thanks!

[FurryNutz]

Please find the "Turning a Router into an AP" located in the FAQ Library/FAQ. It will help you and works.

[mdog3000]

I tried that previously and again reset my values to match those in the FAQ and it still will not connect. I dont know if there is some setting on my TP router that I need to change to get it to work.

[FurryNutz]

something is not configured correctly then...
I would maybe to a factory reset.
Use one wired PC connected to the 655 router. Don't connect the 655 to the main host router. Just configure the 655 with the PC only. Configure it using the sticky post in the FAQ. Once it's all set up. Power OFF the 655 and connect it LAN to LAN to the main host router. Should work after that.

[mdog3000]

Ok I tried starting fresh this morning. I did what you suggested and did a factory reset and only had my computer attached via LAN to the AP. My computer was set under IPv4 to automatically pull IP and DNS. I then deactivated DHCP, UPnP and everything else listed. I then changed my network IP to 192.168.0.50, hit save, rebooted the router, unplugged it and connected it via LAN to the main router and turned it back on. Alas I still have no connection and when I check my IP address in command prompt it reports as 169.254.17.25, which doesnt make sense to me as it is seemingly a random number unrelated to either routers. I also cannot access the DLink setup page anymore unless I put the computer on a static IP. I feel like I've done everything the same way as everyone else but it still wont work. HELP

[davevt31]

The 169.254.x.x IP is a default address generated when there is no connection to the DHCP server.

[mdog3000]

So I presume that means the AP is not successfully connecting to the router    Do I need to create a static route from the router to the AP?

[FurryNutz]

To access the 655 if it's in AP mode and you've set the 192.168.0.50 for the 655 IP address, you'll need to enter in that specific IP address in the browser.

What is the IP address pool if your host router? 192.168.0.1-255? or 192.168.1.# ?
If it's .0.# then everything should work. If it's .1.#, then change the 655's router IP address from .0.50 to what ever the 3rd octet number is on the host router, so if it's 1.# then use 192.168.1.50. All should work. Make sure when you set up the SSID on the 655 that if you use the same SSID as on the the host router, that you use a manual channel that is DIFFERENT from the other WiFi. Can't be the same. The SSID name and password cane be. Turn off ALL other options, even disable SPI and any filtering as it won't be needed.

[mdog3000]

The other router (TP-Link) was the 192.168.1.1 subset but I changed it to 192.168.0.1 to match the Dlink. Is that not allowed? I will try again.

[FurryNutz]

If the Default router IP address on the TP is .1.1, I would keep it there and adjust the 655 to the host router. So use 192.168.1.50.

[mdog3000]

Ok so I restored to factory settings and changed the IPs on both sides (restored router and changed AP to .1.#) and still nothing. I decided to look at the lights on my dlink (AP) and noticed that the port light wont light up where the cable from the router is plugged in. Does that mean that it is not registering that signal properly? Also why do I have to keep setting my computer to a static IP to access the dlink page once I change the AP IP to 192.168.1.50? Im not sure what else to try besides throwing the dlink out and buying a TP-link access point.

[mdog3000]

I just thought to check my firmware and it states that it is 1.35NA, which appears to be outdated since I see there is 2.10NA. Would updating this possibly fix my issues?

[FurryNutz]

There should be a link light on the LED that you've connected. If its not then try swapping cables and try a different LAN port, can be any of the LAN ports. If your PC is connecting to the 655 on the same LAN port your trying to connect from the Main host router, I don't think the LAN ports are bad, either the cable between the main host router is bad or something on the main host router isn't working right.

Reason why you have to set a static IP address on the PC is due to the fact that the 655 doe not provide the IP addresses any more when the DHCP services are turned off. Now once the 655 is properly configured and the 655 does get a proper connection and data flow from the main host router, then the 655 will pass thru DHCP services from the main host router and the PC can revert back to Automatic IP addressing.

You could use the 655 has the main host router and maybe configure the TP as an AP. Not sure if it can do that or not, it might. As a last suggestion.

You have the last and latest version for your Rev A. v2.10 is for Rev B routers.

[coxhaus]

There are many way to configure your setup. The problem people run into using 2 routers is you are only allowed one DHCP server per network. Using the second router whichever one, you need to turn off DHCP so the first router will pass the correct DHCP addresses to the LAN side of the second router.

[FurryNutz]

Any status on this?