Print

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

[FlopShot]

So I've decided to use a different router to resolve some VPN issues, and want to use my DIR-655 as a pure wireless access point.  I need the access point to use the same range of IP addresses as the rest of the network (maintain access to networked printers, file shares, etc).  However, I can't establish a wireless connection to the access point.  Here is what I've done:

- Defined a IP address for the DIR-655 within the DHCP range of the primary router
- Defined the proper subnet
- Disabled the DHCP server on the DIR-655
- Connect a LAN port of the DIR-655 to a LAN port on a switch (note that it's not connected directly to a router).

When I connect a device WIRED to a LAN port on the DIR-655, everything works fine.  The device gets assigned a DHCP address (which I know is being assigned by the main router since the DIR-655 DHCP server is disabled), and I can connect to the LAN and I can access the internet with no problem.  So I know the DIR-655 is acting correctly to pass thru traffic.  Also, I can access the DIR-655 web configuration page from any LAN device (even a device not directly connected to the DIR-655), so I know the DIR-655 is on that LAN correctly.

But when I try to connect WIRELESS to the DIR-655, it doesn't work at all.  Although the wireless NIC is connecting to the DIR-655 (e.g. it asks me for the WPA key), it can't pull an IP address, so there is no connection to the LAN or internet.

Any suggestions?  Why would wired work, but wireless would not?

[FurryNutz]

Review the Turning a router into an AP over on the FAQ Library forum.

Let us know if that helps.

[FlopShot]

Review the Turning a router into and AP over on the DGL-4500 forum.

Let us know if that helps.

Thanks, but I already had done everything in that writeup.  It's definitely acting correctly as a switch, since any wired connection is fine.  It's just the wireless, so I don't understand why that would be any different than wired connections in terms of grabbing a DHCP address.

[HoustonREF]

FlopShot - I'd look at your DHCP setup.  I use a DIR-655 as an access point.  Works great, and I can pull the IP easily.  However, back when I was using a Windows 2008 R2 server, sometimes it would take minutes to get the IP.  Now, I'm using a Zyxel USW20 as the gateway, and the DHCP from the Zyxel.  Whole system is working better...  Also, for speed on the DIR-655, suggest using WPA-2 only, and "AES ONLY".  Under router settings, click "DNS Relay".  (Not original ideas - These appeared in earlier posts.)

[markem_sd]

I've got a slightly different problem in setting up the DIR-655 as an access-point.  The primary wireless network works fine, but the guest network will not provide traffic.  It broadcasts and I can connect to it, but I can't do LAN or internet traffic.  I've tried two different routers (Rev B1) with same results.  I would have assumed that since the primary network provides connectivity that the guest network would also.  Can someone confirm that in AP mode only the primary wireless works?  Any suggestions?

[Makdaddy]

Do you name the SSID the same as other SSID on your network?