dhcp relay

Oguzhan Kayhan oguzhank at bilkent.edu.tr
Tue Oct 13 09:34:52 UTC 2009


Hi,
Yes easiest way is to set manual ip addresses for such devices but!!!!
To make static ip addresses work, i need to enable uamanyip. Otherwise
static ip's does not work.
And when i enable uamanyip, for example a client connected to another
accesspoint switches to this coova, and second coova gets the old ip
address of the client so, it can not work.
There should be a way to allow only static-ip subnet on coova.

The other solution.
There is only one dhcp server (except coova) running on the network.
And it is configured to answer to requests coming from coova's ip only.

What i notice is, i set one of my clients macid to get 192.168.1.50 ip add
on dhcp server.And also on dhcp server it waas set to release ip addresses
starting from 192.168.1.10.
Anyway, on coova when a client tries to connect. coova tries to distribute
ip address from its own configuration even if i enabled dhcpgateway and
dhcprelayagent parameters on it and the ip address that coova gives (for
ex 192.168.1.2) and the clients ip address taken from dhcp server itself
192.169.1.10. so it makes impossible to work with.



> It's not possible to use two or more DHCP servers reliably on a single
> network segment, as you may never know which server gives a lease to a
> particular client. It's because of the way DHCP works. A DHCP client sends
> its request to the broadcast address and whichever server receives it
> first
> will create a lease for that client.
> The best solution, I think, is to use static (manually set) addresses to
> printers, servers and other permanent equipments on your network.
> DHCP relaying may work, if you know how to configure it, but I cannot help
> with that as I never used relaying with Chilli.
> Probably other users can tell you more about this.
>
> 2009/10/13 Oguzhan Kayhan <oguzhank at bilkent.edu.tr>
>
>> Anybody??? :)
>>
>> I made a few tests more..
>> I installed dhcp server to another server.
>> And i also installed coova.
>> Lets assume DHCP server is on 192.168.1.10
>> and coova wan ip is 192.168.1.11
>> So what i need to enter on coova config i guess is,
>>
>> But when i enter dhcpgateway 192.168.1.10
>>
>> the msg i got on syslog is
>>
>> Oct 13 11:00:04 gw coova-chilli[11812]: dhcp.c: 2262: received DHCP
>> response from host other than our gateway
>> Oct 13 11:00:04 gw coova-chilli[11812]: chilli.c: 4164:
>> dhcp_relay_decaps() failed!
>>
>> if i enter dhcprelayagent 192.168.1.10
>>
>> nothing happens..it still gives the ip addresses from coova.
>>
>> Anybody experienced about that????
>>
>>
>>
>>
>> > Hello,
>> > I wonder am i thinking wrong about dhcprelay..
>> >
>> > I am planning to run a dhcpserver on same server with coova.
>> > And i want to disable coova's own dhcp server, so i can give static
>> ip's
>> > to some of MACID's (like printers etc)
>> > I dont wanna use anyip and and dynamic-static ip masks.
>> > Because it creates other problems too.
>> >
>> >
>> > As i see it seems possible  via freeradius+jradius.
>> > What i wonder how (or can I) can i set coova to use local dhcp server
>> > instead of its own or freeradius..
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: chilli-unsubscribe at coova.org
>> > For additional commands, e-mail: chilli-help at coova.org
>> > http://www.coova.org/CoovaChilli
>> >
>> >
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: chilli-unsubscribe at coova.org
>> For additional commands, e-mail: chilli-help at coova.org
>> http://www.coova.org/CoovaChilli
>>
>>
>





More information about the Chilli mailing list