[ previous ] [ next ] [ threads ]
 From:  Adam Gibson <agibson at ptm dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Re: [m0n0wall] Upgrading to 1.3b3 over slow link issue
 Date:  Thu, 09 Aug 2007 12:22:53 -0400
According to Michael's information if it takes more time than the mini 
httpd hard time limit I would expect you would get a disconnect 
connection regardless if the connection is https only, over PPTP, or 
even over IPSEC.  PPTP would not be exempt from the mini httpd time 
limit.  It is the web server that m0n0wall uses that has the limit.

Lonnie Abelbeck wrote:
> On Aug 9, 2007, at 9:33 AM, Adam Gibson wrote:
>> Michael Iedema wrote:
>>> Adam,
>>>> I was upgrading from 1.231.  It appears that after about 5 minutes 
>>>> or so
>>>> the monowall system ends the transmission with a FIN packet.  The 
>>>> upload
>>>> speed was around 12 to 15KBytes/sec.  I tried messing with the timeouts
>>>> in PHP but I still did not get it to work.  I uploaded it over the LAN
>>>> and it worked.  The filesystem was not full either so that was not it.
>> --- CUT ---
>>> I ran into this same thing. It's a hard timeout in the webserver, mini
>>> httpd. It can be changed but you would need to recompile mini httpd
>>> and create a new m0n0wall image with that binary.
>> Thanks for the information.  Unfortunately it is too late at this 
>> point for currently deployed systems.
>> Does anyone know if this is something that might be changed in the 
>> future?  It is a shame needing to go to a remote site to upgrade the 
>> firmware because of the mini httpd hard timeout setting.
> Are you remotely connecting via HTTP/SSL or via PPTP?
> I have updated many m0n0walls remotely, but always using PPTP.  Possibly 
> this would make a difference?
> Lonnie