[Chilli] Installation question

[Steffen Dettmer]

Hi,

I'm in a hurry, sorry, but without difficult tricky stuff you need one device for coova client net (wlan0 or eth1.10 or whatever) and Coova is DHCP server on that interface (because coova checks MAC address etc). You must not have another DHCP server on that device, it will be a race with undefined results I guess. Also notice that Coova rewrites firewalling (and has to).
I don't understand what you mean with "DHCP of the lan", you mean outside HS_NETWORK?

Steffen



Von: Stephen Davies [mailto:steve at base-it.co.uk]
Gesendet: Dienstag, 20. Mai 2014 20:38
An: Steffen Dettmer
Betreff: Re: [Chilli] Installation question

Thanks again Steffen,

I have Chilli working great on an Ubuntu PC with the same running RadiusDesk. I now need a Chilli hotspot 'device' rather than a PC and that is where the problems have started. i've tried to keep the minimal config initially to make things easier to get running. i just cant work out for the life of me why an IP as set is given to the client and a DHCP off the lan is given instead. i'm thinking Chilli will just not wok on certain types of router although OpenWRT is installed fine.

Thanks
Steve

On 20/05/2014 19:13, Steffen Dettmer wrote:
Hi,

Normally you copy /etc/chilli defaults to /etc/chilli/config and edit it e.g. to include
HS_WANIF="eth0" # Give interface of default route or omit (=auto).
HS_LANIF="wlan0"      # Your WiFi interface.


There is a *very* brief note http://coova.org/CoovaChilli/Configuration
Looking at the init.d script and the function file it uses may help,
Google should point you to some configuration HOWTOs,
Setting up backends (RADIUS) can be challenging.

Steffen

Von: Charles Chambers [mailto:cchamb2 at gmail.com]
Gesendet: Dienstag, 20. Mai 2014 15:24
An: Steffen Dettmer
Betreff: Re: AW: [Chilli] Installation question


Sure.

I'm installing on an Ubuntu server (14. 04) with basic system files,  with RadiusDesk already configured.  I'm at the step of starting CoovaChilli,  and the daemon is looking to bind to eth0 and eth1 (WAN and LAN interface... assuming that eth1 connects to an access point).

There is no eth1.   ifconfig shows eth0 and wlan0 for the network adapters,  along with lo.

I'm asking how/where/what to change so that the daemon accepts wlan0 instead of eth0.
On May 20, 2014 1:12 AM, "Steffen Dettmer" <steffen.dettmer at nomadrail.com<mailto:steffen.dettmer at nomadrail.com>> wrote:
* Charles Chambers
> Chilli doesn't want to deal with wlan0, it wants both network
> connections to be ethernet (eth0 and eth1).

Could you describe a bit more in detail, please?
Coova works fine with wlan0, a standard config for me.

> Any way to configure Chilli so that eth1 can be wlan0?

Sure, should be straight-forward:

HS_WANIF="uplink-tun" # Give interface of default route or omit (=auto).
HS_LANIF="wlan0"      # Your WiFi interface.
HS_TUNDEV="wlan0-tun" # Name of the tun dev.
...

Steffen




_______________________________________________

Chilli mailing list

Chilli at coova.org<mailto:Chilli at coova.org>

http://lists.coova.org/cgi-bin/mailman/listinfo/chilli

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.coova.org/pipermail/chilli/attachments/20140521/2ef06354/attachment-0001.html>