XRP isn't a gateway so shouldn't tell DHCP clients that it's the default gateway #52
Description
This is an enhancement request.
It would be nice if it was possible to connect from a PC to the Wi-Fi AP provided by the XRP while using a second network adapter on the PC (Ethernet or secondary Wi-Fi) to connect to the Internet. This would allow browsing documentation, etc. while also controlling the XRP via WiFi.
Currently, the XRP DHCP server returns the XRP's address as the default gateway in response to a DHCP request. In many situations, this results in all outbound traffic from the PC to be routed to the XRP by default, even though the XRP has no ability to act as a gateway (router) for that traffic. From a networking perspective, a better response to a DHCP request to the XRP would be to return only an IP address and netmask, not a default gateway address. This would not prevent packets addressed to IP addresses on the XRP's private subnet from reaching those addresses, but it would avoid traffic addressed for other IP addresses being sent to the XRP.
FWIW, I took a quick look at the Arduino WiFi library, and it looks like this might not be easy to implement, but just putting this out there in case there was something I missed.