Print

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

[RogerSC]

I followed this simple procedure to turn my DIR-655 into an access point:

http://blogs.oracle.com/simonthorpe/entry/configuring_a_dlink_dir_655_as

and it all worked except when I go to http://192.168.0.1 (which is where I left the router's IP address set) I don't get the DIR-655's admin login GUI, just a timeout.  Since my main Linksys router is on 192.168.1.1, and my cable modem is at 192.168.100.1, and the DHCP addresses handed out by the Linksys router is from 192.168.1.100 to 192.168.1.149, getting to 192.168.0.1 should not be a problem.

Any ideas on what setting that I might have wrong?  Functionally, the DIR-655 makes a great access point, wired and wireless are working very well, and I don't see any reason why I can't get to the web GUI admin page.

I should be able to get to the DIR-655 router via the WAN port, as suggested in the procedure above, but I'd really really like to be able to get to it without having to connect a cable to the DIR-655 WAN port.

[RogerSC]

I'm now wondering if the DIR-655 AP router IP address should be something like 192.168.1.250 instead of 192.168.0.1, since my dhcp addresses are 192.168.1.x also.

Just a thought...

Any comments?

Thanks.

[FurryNutz]

You won't be able to use the 0.1 due to the fact that the scheme of the routers platform has changed and no longer uses that address any more. Upon initial set up of the 655 as an AP, you do have the ability to set up a specific IP address for the AP using one you can remember. Once this is in place, you can use that IP address to connect to the APs web page. Mine's set for .12 and access the web page just find. And you won't be using the WAN port at all when using the router in this mode. Lan ports only.

[RogerSC]

You know, I was playing with this last night, and found that I couldn't change the router's IP address even when I was directly connected to it (not in AP mode).  I tried to change the router IP address from the default 192.168.0.1 to 192.168.1.250, and I couldn't get in touch with the router again, had to reset it back to defaults.  I also tried 192.168.1.200 for the router IP, no luck there either, could not get login prompt, and had to reset the router to get back into it.

I'm going to try 192.168.2.1 for the router IP, and see if that works, but it is a bit disturbing that I haven't been able to change the router IP yet, I've never had a problem with that with a router before.

I'm also wondering what you mean by "won't be able to use the 0.1"?  Do you mean I can't use the 192.168.0.1?  That's surprising, since it is the default router IP.  Do you mean that I can't use 192.168.0.1 in AP operation?  And you're using 192.168.1.2?  If that's what you mean, I can try that, too.  Although I don't see why that would be different than 192.168.1.250.

I have the "B1" hardware platform, relatively new model of the DIR-655.  This one is a replacement for my original DIR-655 router that I gave to my daughter to use in her apartment, that one was an A4.  

[RogerSC]

Okay, all working now.  I set the router IP to 192.168.1.2, and that apparently didn't work.  So this time, I power-cycled it, still failed to login, so just walked away for about 10 minutes.  When I came back, I could log into the router at 192.168.1.2.  I've never seen anything like this, where a change in router IP took so long to take effect.

But then I went through and set everything up the way I wanted it again for AP use, and everything is fine now, I can get into the router for admin.

What a hassle.  I could have saved myself a LOT of time if I'd waited long enough after changing the router IP before before giving up.  I'm used to holding in reset buttons for 30 seconds, power-cycling for a minute, and so on, but a matter of minutes is new to me.  But now I know, and I'm not likely to forget that *smile*.

[FurryNutz]

Glad you go it working. Enjoy.