[Chilli] Router

[Steffen Dettmer]

Hi!

> I understand that turning off NAT turns the router into a switch.

Not sure if this is right, normally you can route with or without
NAT, on OSI layer 3,
or alternatively switch (bridge) on OSI layer 2.

> Connecting the router WAN port and turning off NAT works, but how do I
> continue to access the router for maintenance purposes (changing WPA
> password, for instance)?

Maybe via secure shell (SSH)?
It might be needed to add your SSH port to HS_TCP_PORTS in
/etc/chilli/config, e.g.:
HS_TCP_PORTS="22 80"

> Could someone  please enlighten me on why eth1 on the CoovaChilli server does
> not appear to have an IP address?

Coova sets an IP on the appropriate tun device. Coova captures
all traffic on the interface (bypassing kernel's routing and
firewalling), so no IP needed here, similarly for sending.
Sending to client network is done using the tun dev, and this has
an IP.

> What is the opening page for the walled_garden found on the CoovaChilli
> server?

By default, Coova is configured to use:
  HS_UAMFORMAT=http://\$HS_UAMLISTEN:\$HS_UAMUIPORT/www/login.chi
a script generated from miniportal/ login.chi.in and installed as /etc/chilli/www/login.chi.

> Is self-registration for basic (minimal) access to the Internet
> possible yet?

For testing, you also could create /etc/chilli/localusers files
with <username>:<cleartextpw>, e.g.
  user:secret
this works with the built-in mini portal.
and in /etc/chilli/config, add:
  HS_USELOCALUSERS=on
after restart it should work.

> Is there a URL for configuring CoovaChilli, for example
> http://192.168.0.6:1447?

You would need a portal or website supporting this, but I don't
think anything like this is part of Coova Chilli distribution.
Typically you configure the backend (DB) the RADIUS server is using.
When you like to support updating the contents of your local
portal or such, things can get more and more complicated of course.

Steffen