On Thu, Feb 10, 2011 at 10:12 AM, Tor Arntsen <tor_at_spacetec.no> wrote:
> On Wed, Feb 9, 2011 at 19:51, Tolas Anon <tolas777_at_gmail.com> wrote:
>> curl_exec() to localhost : works like a charm, for a 1hr request.
>>
>> curl_exec() to internet domain name of localhost (port forwarding from
>> adsl modem to localhost enabled) : still running, does appear as
>> frozen as in the original request for help.
>
> That sounds like you're behind a NAT'ed firewall. Quiet connections
> will often go dead (by the firewall) in an hour or less (I've seen 30
> minutes on some).  My ssh tunnel connections always use a 'ping -i
> localhost 600' on the tunnel-setup ssh to keep the connections up.
>
> You may instead try to set the TCP option SO_KEEPALIVE (see 'man
> socket') to see if it helps.
>
Thanks for the info, it is indeed a NAT setup.

But on one of those low-featured ADSL routers, with a webpage that
gives you only the most basic options.
I consider myself lucky it has NAT capabilities at all ;)
I'd have seen no options for tcp keep-alive on that thing, i seriously
doubt it can do it at all.

My localhost is win7, and as far as i know it doesn't get involved in
the NATing.

Plus: i wanna use these import routines from continent to continent
one day, there might be more equipment on the internets that has this
problem..

So i'm running another simple test atm, whereby i echo a byte every 25
seconds, and an ob_flush() each time, during the run. I've set it for
1.5hrs this time. Results should be in within the hour.
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2011-02-10