1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 <2015> 2016 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 <2015> 2016 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: asyn timeout |
From: | Pedro Gigoux <[email protected]> |
To: | Mark Rivers <[email protected]> |
Cc: | "[email protected]" <[email protected]> |
Date: | Mon, 19 Oct 2015 18:24:12 -0300 |
Hi Pedro,
It seems like it might be a good idea to add optional keepalive support to the asyn socket driver. If I were to create a branch on github that implemented this would you be able to test it?
Mark
From: [email protected] [mailto:[email protected]] On Behalf Of Pedro Gigoux
Sent: Monday, October 19, 2015 1:46 PM
To: Torsten bögershaus
Cc: [email protected]
Subject: Re: asyn timeout
Hi Torsten,
The instrument is located in a remote institution so I don't have much details about their network setup. On our side, the machine where the software runs goes through a couple of switches and the firewall before connecting to the remote host. Our IP is registered on their firewall to accept connections to the instrument. According to our IT department we don't have timeouts for outgoing traffic so we suspect the remote network equipment is the one dropping the connection (I don't have hard evidence to support this yet, though). A workaround that has been proposed is to modify the software to send a ping-like packet every minute to prevent the link from going down.
Thank you,
Pedro.
On 19 October 2015 at 12:27, Torsten bögershaus <[email protected]> wrote:
Not with asyn in special, but with all kind of TCP/IP related devices.
TCP/IP has a „Keepalive“, but this is typically 2 hours.
Could you share more information about that "component in the communication chain“ ?
And what happens if the communication is broken ?
Is there a clean FIN on the TCP-layer ?
Is it just dropped ?
Can you run Wireshark on the IOC ?
On the instrument ?
More info is appreciated
Am 19.10.2015 um 16:38 schrieb Pedro Gigoux <[email protected]>:
> Hi,
>
> We are using asynDriver to talk to an instrument connected to a socket port on a remote site using an ASCII based protocol. The communication works well except that the connection consistently drops when the exposure time is longer than 30 minutes. While the instrument is exposing there's no traffic in the socket; this points to a component in the communication chain that times out if it doesn't see any traffic for more than a certain time. I did not find timeouts in the asynDriver code so I suspect that the problem is in a network switch/firewall. Has anyone seen a similar problem with asyn before?
>
> Thank you,
> Pedro Gigoux
> Gemini Observatory
>