DHCP client problem when no default route

[Derek C]

Hi all,

I've noticed a problem for a while now - its not major but it can be
bothersome: -

When an OpenWRT AP doesn't have a default route Coova Chilli doesn't
appear to hand out an IP through its internal DHCP server.

I'm able to get Coova Chilli running without a default route by having the
UAMserver and radius server(s) in /etc/hosts (otherwise Coova Chilli exits
at startup) - I do this anyway in case the default route hasn't come up
with the AP boots.

So currently, if an AP doesn't have a default route the notebooks trying
to connect just fail with no DHCP assigned IP and it's kind of hard to
diagnose.

Has anyone else come across this?  I'm running Coova Chilli 1.0.13

thanks!

Derek


-- 
Derek C
In Ireland