D-Link Forums

The Graveyard - Products No Longer Supported => Routers / COVR => DIR-615 => Topic started by: Kitzul on October 13, 2010, 04:12:42 PM

Title: Run DIR-615 as AP
Post by: Kitzul on October 13, 2010, 04:12:42 PM

I am trying to configure this router to be strickly an access point. I already have another router and i need my wireless devices to be on the same subnet as my wired devices.

Is this even possible, i dont see the option anywhere, but online I read that it was possible.

Thanks,
-Kyle

Title: Re: Run DIR-615 as AP
Post by: carbonic on October 17, 2010, 04:05:25 PM

You might want to look at the unofficial firmware DD-WRT (see elsewhere in the forum). It has way more features and options than the stock firmware.

Title: Re: Run DIR-615 as AP
Post by: Kitzul on October 20, 2010, 01:44:15 PM

Unfortunately i have hardware version B which is not listed as supported for this router.

Title: Re: Run DIR-615 as AP
Post by: Skello on October 21, 2010, 10:23:21 PM

From the manual:

If you are connecting the D-Link router to another router to use as a wireless access point and/or switch, you will have to do the following before connecting the router to your network:
• Disable UPnP™
• Disable DHCP
• Change the LAN IP address to an available address on your network. The LAN ports on the router cannot accept a DHCP address from your other router.

http://static.highspeedbackbone.net/pdf/D-Link-DIR-615-Manual.pdf Read the "Connect to Another Router" section.

Title: Re: Run DIR-615 as AP
Post by: Trikein on October 22, 2010, 05:23:20 PM

Do you need the router to act as a Access point or a repeater?I know you said Access point, but since so many have been calling repeaters access points, I thought I would clairify. Access point is one thing, +1 to Skello. As for a repeater(as in only a power cord connected to the DIR-615) thats a horse of a different color, and not a function supported by the factory firmware.

Title: Re: Run DIR-615 as AP
Post by: Kitzul on October 25, 2010, 06:55:37 AM

Skellos suggestion was what i needed.

Thanks,
I had plugged my Ethernet cable into the wan instead of LAN...Oops.

Thanks again