[Chilli] redir.c: 1990: Too much data in http request! -47

Lnx lnx.consultant at gmail.com
Thu Jul 25 08:05:44 UTC 2013


Hi list,

This might help someone in configuring chilli's dchp setting. 

I had a problem in setting up dhcp to give a range of /16 ip addresses. 

Please read below if you are also facing the same problems.




On Jul 25, 2013, at 3:18 PM, Russell Mike <radius.sir at gmail.com> wrote:

> Please never mind. Glad that it worked for you !!
> 
> Regards / --RM
> 
> 
> On Thu, Jul 25, 2013 at 5:18 AM, Lnx <lnx.consultant at gmail.com> wrote:
>> Hi sir, 
>> 
>> Thank you very much for your reply. 
>> Dhcp setting worked perfectly!
>> 
>> 
>> Regards,
>> 
>> 
>> On Jul 24, 2013, at 4:15 PM, Russell Mike <radius.sir at gmail.com> wrote:
>> 
>>> Hi Sir,
>>> 
>>> define "net" option in "chilli.conf" and define dhcp ip range in "local.conf". i remember, i wrote about it for list archives, for new implementations. i still found in my sent items. Kindly read following carefully. if any difficulty, please feel free to ask again. 
>>> 
>>> you need to configure two files. local.conf & chilli.conf
>>> 
>>> nano "/usr/local/etc/chilli.conf" 
>>> net=192.168.8.0/255.255.255.0
>>> 
>>> OR
>>> 
>>> net=192.168.8.0/24
>>> 
>>> nano "/usr/local/etc/chilli/local.conf"
>>> # Starting issue from 55 (first address) to 155 (last address)
>>> 
>>> dhcpstart=55
>>> 
>>> dhcpend=155
>>> 
>>> 
>>> 
>>> NOTE: it is different technique to manage classless ranges, understand the difference from below writing. 
>>>  
>>> 
>>> Thanks / Regards
>>> RM --
>>> Configuring CoovaChilli (I used v1.3.0) For DHCP Pool Range Classless & Class-full Ranges VLMS How To ??
>>> 
>>> Scenario: I have a network of 192.168.8.0 255.255.255.0 (24). i am using some static ip address for my server from the range 192.168.8.1 - 192.168.8.34. I do not want CoovaChilli to issue these ip address. Saying other way, i want to specify a dhcp pool range, therefore CoovaChilli can use a ip from the pool to issue the ip address for incoming dhcp requests. 
>>> 
>>> How do i do that? 
>>> 
>>> nano "/usr/local/etc/chilli.conf" (These are two different ways of writing the directive, use one only)
>>> 
>>> net=192.168.8.0/255.255.255.0
>>> 
>>> OR
>>> 
>>> net=192.168.8.0/24
>>> 
>>> nano "/usr/local/etc/chilli/local.conf"
>>> 
>>> dhcpstart=35
>>> 
>>> dhcpend=254
>>> 
>>> save the files and it is done. Coova will now issue the ip address from this range (192.168.8.35 - 192.168.8.254). make sure your entires are not in conflict with previous configuration otherwise it would just work. configured so many times. 
>>> BUT when it comes to variable length subnet mask (VLMS) - (sub-netting braking ip address, hosts & networks in small/big partitions as needed)  i found it bit tricky to configure and understand DHCP pool range directive when using VLMS, to help new comers and those may attempt in future, i wish to share my opinion that may helpful for them to understand easily. 
>>> 
>>> 
>>> My Network: 10.130.8.160
>>> 
>>> My Subnet Mask: 255.255.255.224
>>> 
>>> (- IP sub netting example copied from online subnet calculator)
>>> 
>>> Network:   10.130.8.160/27       00001010.10000010.00001000.101 00000 (Class A)
>>> 
>>> Broadcast: 10.130.8.191          00001010.10000010.00001000.101 11111
>>> 
>>> HostMin:   10.130.8.161          00001010.10000010.00001000.101 00001
>>> 
>>> HostMax:   10.130.8.190          00001010.10000010.00001000.101 11110
>>> Hosts/Net: 30
>>> Assuming that 10.130.8.161 is CoovaChilli Box. Coova dhcp must issue from 10.130.8.162 - 10.130.8.190.  What would you expect to write in to "local.conf" & "chilli.conf" when reading above example.
>>> dhcpstart=162
>>> 
>>> dhcpend=190
>>> 
>>> IT IS WRONG !!!! WOULD NOT WORK. HERE IT IS BIT TICKY
>>> 
>>> CORRECT VERSION:
>>> 
>>> nano "/usr/local/etc/chilli.conf" (These are two different ways of writing the directive, use one only)
>>> 
>>> net=10.130.8.160/255.255.255.224
>>> 
>>> OR
>>> 
>>> net=192.168.8.0/27
>>> 
>>> nano "/usr/local/etc/chilli/local.conf"
>>> 
>>> dhcpstart=2
>>> 
>>> dhcpend=29
>>> 
>>> The correct dhcpstart should be 2 and dhcpend should be 29
>>> 
>>> I hope this would helps someone..
>>> 
>>> Thanks / Regards 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Tue, Jul 23, 2013 at 3:25 AM, lnx consultant <lnx.consultant at gmail.com> wrote:
>>>> Hi Russel,
>>>> 
>>>> Thanks again for your reply.
>>>> 
>>>> Yes, it is a layer 2 setup with chilli acting as the dhcp server.
>>>> I'm trying to have chilli distribute a max of /16 ip addresses, I have the following defined in /etc/chilli/config. Is there a proper way
>>>> to set the dhcp range that chilli is distributing? or the config below will do? notice i set the subnet mask as 255.255.0.0 (/16) 
>>>> 
>>>> HS_LANIF=eth1              # Subscriber Interface for client devices
>>>> HS_NETWORK=10.1.0.0        # HotSpot Network (must include HS_UAMLISTEN)
>>>> HS_NETMASK=255.255.0.0   # HotSpot Network Netmask
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Mon, Jul 22, 2013 at 6:22 PM, Russell Mike <radius.sir at gmail.com> wrote:
>>>>> Okay, 
>>>>> 
>>>>> 1.) I trust it is layer 2 setup, because coovachilli internal DHCP do not work in layer3 mode when enable. 
>>>>> 2.) A client, to obtain IP address do not use http=80 rather udp=67. please ignore the error, not related with your problem. 
>>>>> 3.) This error (Too much data in http request!) is also logged by windows update. if a client is doing windows security upgrade. 
>>>>> 
>>>>> check tail -35f /var/log/message for Redhat/CentOS
>>>>> check tail -35f /var/log/syslog for Ubuntu / Debian
>>>>> 
>>>>> 
>>>>> i doubt you have run short of IPs in your pool. please let me know if any thing i can help further. 
>>>>> 
>>>>> Thanks / Regards
>>>>> 
>>>>> 
>>>>> 
>>>>> On Fri, Jul 19, 2013 at 9:05 PM, Lnx <lnx.consultant at gmail.com> wrote:
>>>>>> Hi Russel,
>>>>>> 
>>>>>> Thank you very much for you reply.
>>>>>> I'm not sure if it's related to this error but sometimes users are reporting that they are not getting any ip address.
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> On Jul 19, 2013, at 8:11 PM, Russell Mike <radius.sir at gmail.com> wrote:
>>>>>> 
>>>>>>> Hi
>>>>>>> 
>>>>>>> Are you experiencing problems or is it just the occasional log entry? Typically, this happens when the browser (or headless process) is doing something like a POST or GET with a large
>>>>>>> query string, not your typical first page in a browser. This warning is normal, do not modify if users are not reporting problem. i also have the same warning in log but no user one reports problem. 
>>>>>>> 
>>>>>>> you can increase limits here:  
>>>>>>> nano /usr/local/include/chilli/chilli_limits.h 
>>>>>>> 
>>>>>>> Look for this entry:
>>>>>>> #define REDIR_MAXBUFFER                 7125 /* DEFAULT WAS --> #define REDIR_MAXBUFFER 5125  */
>>>>>>> 
>>>>>>> Thanks / Regards
>>>>>>> RM --
>>>>>>> 
>>>>>>> 
>>>>>>> 
>>>>>>> On Fri, Jul 19, 2013 at 8:26 AM, lnx consultant <lnx.consultant at gmail.com> wrote:
>>>>>>>> Hi,
>>>>>>>> 
>>>>>>>> How can i fix the error redir.c: 1990: Too much data in http request! -47.
>>>>>>>> i already search the internet but i could not find a concrete answer as to why it is giving that error or how to fix it.
>>>>>>>> 
>>>>>>>> Thank you
>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> Chilli mailing list
>>>>>>>> Chilli at coova.org
>>>>>>>> http://lists.coova.org/cgi-bin/mailman/listinfo/chilli
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.coova.org/pipermail/chilli/attachments/20130725/3f1968b7/attachment-0001.html>


More information about the Chilli mailing list