CompuLab SBC-FITPC2 Manual do Utilizador descarregar pdf (Página 14)

rad_recv: Access-Accept packet from host 127.0.0.1 port 1812, id=39, length=20

STEP 6: Download and build Coova-Chilli

There are two ways to run Coova Chilli in our Village Telco setup:

b) L3 (Layer 3 /CC3): In this scenario our meshed clients can be behind a L3 super

node or router and have IP addresses from other IP networks that the one present

in the Captive portal's incoming interface. In a L3 setup Coova-Chilli does not run

a DHCP server and does not need to hijack ARP messages. Coova-Chilli in Layer 3

is suitable when B.A.T.M.A.N runs in L3 in the super node. If you are advertising

your gateway network via a supernode, it seems that you run the mesh network

in a different network that the gateway/server network.

a) L2 (Layer 2 /CC2): In this scenario our clients (the potatoes) need to be able to

be in the same link layer of the Coova-Chilli. Authentication in Layer 2, requires

the wireless clients to be in the same network segment that the Captive Portal as

authentication uses the IP and MAC address of the clients. ARP messages need to

be exchanged directly between the wireless clients and the access controller. This

means in practice that no router, NAT servers can be placed in the middle. In the

context of a B.A.T.M.A.N. Network, it implies that the protocol needs to run in L2

(Link Layer Routing) and not L3 (IP routing)

The following section covers how to download and install Coova Chilli in both

scenarios CC2 and CC3:

cd /usr/local/src;

wget http://dev.villagetelco.org/coova-chilli/coova-chilli_1.2.9_i386.deb

dpkg -i coova-chilli_1.2.9_i386.deb

STEP 7: Configure Coova-Chilli

This user is defined in the default chilli config file

1 2 ... 9 10 11 12 13 14 15 16 17 18

Sem comentários

CompuLab SBC-FITPC2 Manual do Utilizador Página 14