[Chilli] interacting with Coovachilli

Jose toboganfing at googlegroups.com
Sat Apr 17 18:55:21 UTC 2010

Hi list,

The network is already built and we can't change the architecture. You can
see an example in the image attached.
When a laptop wants to get connected through an AP doing outdoor coverage,
it broadcast a DHCP discover packet that arrive to both servers because they
are in the same broadcast domain (bridged network). So, as both servers are
running Coovachilli, Coovachilli's DHCP services would respond to that with
a DHCP offer packet. Actually the first server that respond with an offer is
the one that finally configure and authenticate the host.
We have to develop a software that must run in every server, monitor its
state and the state of  the network. By a three hand shake exchange between
the servers each one decide if is optimum or not. The optimum server must be
the one that configure and authenticate the host.
Then our application must listen on port 67 to be able to control the IP
assignation. The problem is that we don't know hot to change the
Coovachilli's dhcp listening port.
Thank you in advance!

2010/4/16 David Bird <david at coova.com>

> Hi José,
> Do you have any diagram of the network you are building? I don't
> understand how you plan to have DHCP services...
> Also, you might ask your question to the chilli at coova.org mailing list
> (after signing up for the list) as I think a few people there might be
> doing similar things.
> David
> On Thu, 2010-04-15 at 02:24 -0300, Jose wrote:
> > Dear David,
> >
> >
> > I am part of a group of students from Uruguay that is working on their
> > graduate thesis for the Plan Ceibal (implementation of the OLPC
> > project in Uruguay). We are trying to balance connections in a bridged
> > network that has several possible gateways to internet, every server
> > has Coovachilli running to grant access control. For that purpose, we
> > have to develop an application that must run in each server and
> > intercept the DHCP packets before they get to the coova dhcp server,
> > and then depending on the state of the server, give or not to give an
> > IP to the host. Meaning, if the server is the optimal one it will
> > forward the packet to Coova DHCP server, otherwise it will discard the
> > packet. To be able to do that we would need to change the port where
> > Coovachilli is listening for DHCP packets and some firewall rules I
> > imagine, but we don't have any idea on how to do that. Would you be
> > able to gibe us some guidance?
> > I'm sorry for my english and hope you understand.
> >
> >
> > Yours sincerely.
> >
> >
> > José Luis Horta
> >
> >
> >
> >
> >
> >
> >
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.coova.org/pipermail/chilli/attachments/20100417/82181adf/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: DIAGRAMA.jpg
Type: image/jpeg
Size: 77814 bytes
Desc: not available
URL: <http://lists.coova.org/pipermail/chilli/attachments/20100417/82181adf/attachment-0001.jpg>

More information about the Chilli mailing list