I'm currently investigating setting up a wireless hotspot with multiple internal networks (routed through to chilli) all going through the same external connection. I've successfully managed to set up a test environment with a single internal network, with coova, freeradius, openldap and NAT. I'm running the FC5 rpm of 1.0.11, downloaded from coova.org.
On the coova machine, I've got 2 network interfaces. Eth0 is connected to the external connection, and eth1 is connected to the internal network on 192.168.0.1/24. There's another router at 192.168.0.2, behind which sits 192.168.2.0/24. This router isn't doing NAT or anything like that.
Before starting the coova daemon, after adding the route in I can ping from the other net to this box, and vice versa. However, after starting coova (and obviously putting the route back in), I can only ping to/from the network that's directly connected to the box. If I set a value for the dynamic addressing range that excludes 192.168.0.2, I can't ping to/from there. I've set the uamanyip option, but this hasn't had any effect.
I've been looking through documentation and I've done a quick search but I can't seem to find anyone who's tried anything similar.
So, I guess my question is: Is the above possible? And if it is possible? Any pointers on where I might be going wrong?
Re: Multiple Internal Networks
Chilli is pretty strict about the traffic it lets through. It is primarily designed to be on the edge servicing subscribers, not servers. But, others have done tricky solutions whereby they carefully create routing rules and give the chilli "dhcpif" an IP address (something that you usually do not do).