SNX

[biskit]

Hi everyone 🙂

A customer is reporting problems with SNX.  It keeps disconnecting.  They were doing some testing yesterday and found repeats of the following stuff in the log from the SNX SSL VPN Network Extender during drops:

[ 3864 4568]@IT[8 May 10:04:35][] fwasync_connbuf_realloc: reallocating 1350b80 from 1208 to 2292

[ 3864 4568]@IT[8 May  9:01:33][] fwasync_mux_in: 2348: read: Connection Reset by peer
[ 3864 4568]@IT[8 May  9:01:35][] SkSetTCP_NODELAY: fd=1428: Invalid Argument
[ 3864 4568]@IT[8 May  9:01:35][] fwasync_conn_params: ->
[ 3864 4568]@IT[8 May  9:01:35][] fwasync_connbuf_realloc: reallocating 0 from 0 to 1208
[ 3864 4568]@IT[8 May  9:01:35][] fwasync_connbuf_realloc: reallocating 0 from 0 to 66560
[ 3864 4568]@IT[8 May  9:01:37][] kmsg_handle_local: 2 records handled
[ 3864 4568]@IT[8 May  9:01:37][] fwasync_connbuf_realloc: reallocating 134e078 from 1208 to 2292

[ 3864 4568]@IT[8 May  8:52:52][] fwasync_mux_in: 2348: read: Connection Reset by peer
[ 3864 4568]@IT[8 May  8:52:54][] SkSetTCP_NODELAY: fd=2348: Invalid Argument
[ 3864 4568]@IT[8 May  8:52:54][] fwasync_conn_params: ->
[ 3864 4568]@IT[8 May  8:52:54][] fwasync_connbuf_realloc: reallocating 0 from 0 to 1208
[ 3864 4568]@IT[8 May  8:52:54][] fwasync_connbuf_realloc: reallocating 0 from 0 to 66560

[ 3864 4568]@IT[8 May  8:51:04][] fwasync_mux_in: 1748: read: Connection Reset by peer
[ 3864 4568]@IT[8 May  8:51:06][] SkSetTCP_NODELAY: fd=2316: Invalid Argument
[ 3864 4568]@IT[8 May  8:51:06][] fwasync_conn_params: ->
[ 3864 4568]@IT[8 May  8:51:06][] fwasync_connbuf_realloc: reallocating 0 from 0 to 1208
[ 3864 4568]@IT[8 May  8:51:06][] fwasync_connbuf_realloc: reallocating 0 from 0 to 66560
[ 3864 4568]@IT[8 May  8:51:14][] kmsg_handle_local: 2 records handled
[ 3864 4568]@IT[8 May  8:51:15][] fwasync_connbuf_realloc: reallocating 139eac0 from 1208 to 2292

This was recorded for each of the drops they experienced over an hour window. 

The first thing I notice is the date.  Yesterday was 5 May.  The logs show 8 May.  I presume as it does connect and work for a while each time, the incorrect date isn't the root cause of this problem?

Anyone got any ideas?

It's R80.10 Take 42.

Thanks,

Matt

[G_W_Albrecht]

May ? May ? It is currently June, i would assume 😊...

[G_W_Albrecht]

May ? May ? Brexit ? It currently is June, i assume 😊...

[biskit]

Good spot.  I need more caffeine!  It is indeed June 🙂  I must have been hoping we weren't getting this close to Christmas, although the way things are going Christmas will come and go before Brexit happens 😂