DHCP Auto-Auth
udhcpd/DHCP Auto-Auth is very basic, there is little to do.
Configuring udhcpd/DHCP Auto-Auth
Configuration
In the StarOS configuration menu system, go to:
interfaces --> {interface you want to run DHCP services on} --> dhcp auto-auth configuration --> configuration
In this configuration dialog you will find:
- Default gateway
- Subnet mask
- Primary DNS
- Secondary DNS
- Lease Duration (see Caveats)
- IP Address Range
You need to set these options as appropriate for the IP addresses you are handing out via DHCP on this interface. The default gateway would almost always be the IP of your interface (your StarV3 system is very likely meant to be the default gateway).
Subnet mask, Primary DNS, Secondary DNS are basic IP configuration settings needed for clients to use The Internet. IP Address Range would be the first and last IP addresses of the pool of IPs you will hand out via DHCP.
Enabling udhcpd/DHCP Auto-Auth
Once you've configured everything in the configuration dialog, go to:
interfaces --> {interface you want to run DHCP services on} --> interface features --> enable dhcp auto-auth
This will turn udhcpd on and if you hit F9 (or advanced --> display system log) you should see a log entry that indicates udhcpd has started.
Caveats
WinXP Known Problem with udhcpd
If you are running udhcpd/DHCP Auto-Auth as your DHCP service directly for WinXP clients, they may fail to renew their DHCP lease once it expires, which will result in a short interruption in their connectivity as they unbind their IP address and start the DHCP process over from the beginning.
I recommend setting the lease duration to at least one day (86400 seconds) to minimize the impact of this hassle.