No peer protocol defined
Oguzhan Kayhan
oguzhank at bilkent.edu.tr
Tue Aug 11 07:42:04 UTC 2009
> The client device probably just needs to do DHCP again. You'll see this
> sometimes when chilli was restarted, it sees traffic from a device, but
> the device hasn't DHCP'ed yet (as far as that chilli knows). You can try
> out anyip features, or you can have your client renew the lease.
>
>
Client configuration was static only. No dhcp configs..
And its ip was given on the static subnet of coova config.
I tried both anyip enabled and disabled..but got no results so far.
> On Fri, 2009-08-07 at 09:13 +0300, Oguzhan Kayhan wrote:
>> Hi,
>>
>> I have a static-dynamic configuration with my chilli
>> as 192.168.1.1-128 static
>> 129-255 as dynamic.
>>
>> And i got a client with static ip.
>> That client was working till yesteday but starting this morning, i got
>> the
>> following error msg on chilli logs
>>
>> chilli.c: 1427: No peer protocol defined for 192.168.1.19
>>
>> What does this error means.. I restarted chilli, but no effect..still
>> getting same msg.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: chilli-unsubscribe at coova.org
>> For additional commands, e-mail: chilli-help at coova.org
>> Wiki: http://coova.org/wiki/index.php/CoovaChilli
>> Forum: http://coova.org/phpBB3/viewforum.php?f=4
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: chilli-unsubscribe at coova.org
> For additional commands, e-mail: chilli-help at coova.org
> Wiki: http://coova.org/wiki/index.php/CoovaChilli
> Forum: http://coova.org/phpBB3/viewforum.php?f=4
>
>
More information about the Chilli
mailing list