Wireless Access

I have a Client who wants to connect AP directly to a DSL for public access in their store - I can't seem to get the AP to provide DHCP addresses for its wireless clients however. Normally, I understand, there would be a DHCP server to forward to but in this case there isn't. Any way to do this?

please read : http://cdn.procurve.com/training/Manuals/AP530-Install-Oct08-59925444.pdf

From this document :
>>> The ProCurve Wireless Access Point 530 WW (J8987A) has no preset country
code and must be configured before you can enable radio communications
for the access point. <<<

also from this document :
>>> Also verify that the
wireless station has been configured with an IP address compatible with
the attached network, either manually or via DHCP. <<<

So the AP acts as a dhcp-client to the fixed network. And I don't think the AP acts as DHCP-server, but it expects one allready present on the "local network".

Depending on the DSL provider, there may not be any dhcp-server in its "modem/router".
a solution can be to add an additional router that connects the DSL on the uplink and the AP at one of the local ports.

from document : http://cdn.procurve.com/training/Manuals/AP530-MgmtCfg-Dec2008-5991-2193.pdf

The AP-530 Web-Auth feature includes a limited-function DHCP server that
serves IP addresses from a pool of temporary addresses. To connect using
Web-Auth, users must first configure their stations to receive a dynamic IP
address from this server, and connect to the Web-Auth configured WLAN.

So basically there is a dhcp-server.
But then you also need a radiusserver to authenticate.

Maybe it can work without radius server if you configure the AP to allow unauthenticated users to access the network.
This is not how this AP is meant to be set up.

If you don't want too much fuss, then you better leave the 530 alone and use another WiFi device (WiFi router + built-in dsl modem ???) for this public access service.

Well thanks for attempts - I realize another device will work (FW, Router, etc) but Client is cheap! As for the WebAuth, not sure that will work based on this from same manual, after authentication - noting there is no network's DHCP server:

At this point, the userâ s station enters the Authenticated state, the station
receives a more permanent IP address from the networkâ s DHCP server, and
the user can access the network resources to which he or she has rights.