[5.8-2]TCP KeepAlive? - VMS

This is a discussion on [5.8-2]TCP KeepAlive? - VMS ; Hello! I see very strange problem: $ netcu sho conn /loc=*.995 TCPware(R) for OpenVMS Active Internet Connections (including servers): ID RecvQ SendQ Local Address Foreign Address State -- ----- ----- ------------- --------------- ----- BG58558 0 0 172.16.0.45.pop3s 89.253.10.243.52656 ESTABLISHED BG0 ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: [5.8-2]TCP KeepAlive?

  1. [5.8-2]TCP KeepAlive?

    Hello!

    I see very strange problem:

    $ netcu sho conn /loc=*.995
    TCPware(R) for OpenVMS Active Internet Connections (including servers):

    ID RecvQ SendQ Local Address Foreign Address State
    -- ----- ----- ------------- --------------- -----
    BG58558 0 0 172.16.0.45.pop3s 89.253.10.243.52656 ESTABLISHED
    BG0 96 0 172.16.0.45.pop3s 217.66.145.101.22504 ESTABLISHED
    BG0 102 0 172.16.0.45.pop3s 172.16.1.9.2796 CLOSE-WAIT
    BG0 78 0 172.16.0.45.pop3s 172.16.1.9.2798 CLOSE-WAIT
    BG0 69 0 172.16.0.45.pop3s 195.74.84.191.6222 CLOSE-WAIT
    BG0 0 0 172.16.0.45.pop3s 195.74.84.191.6232 CLOSE-WAIT
    BG63789 0 0 *.pop3s *.* LISTEN


    $ netcu debug /tcp /lpn=995 /ria=217.66.145.101
    DTV5::LAISHEV 11:21:35 NETCU CPU=00:02:11.53 PF=11239 IO=112080 MEM=344
    DTV5::LAISHEV 11:21:57 NETCU CPU=00:02:11.53 PF=11240 IO=112081 MEM=345
    DTV5::LAISHEV 11:22:08 NETCU CPU=00:02:11.53 PF=11240 IO=112082 MEM=345
    DTV5::LAISHEV 11:22:31 NETCU CPU=00:02:11.53 PF=11240 IO=112083 MEM=345


    $ netcu sho bg_tcp drop
    Parameter BG_TCP DROP_TIMER's current value is 60
    $ netcu sho bg_tcp prob
    Parameter BG_TCP PROBE_TIMER's current value is 15
    $


    As I understand the SO_KeepAlivE don't work at all.




    --
    + WBR, OpenVMS [Sys|Net] HardWorker ................ ICQ# 319518233 +
    Delta Telecom JSC, IMT-MC-450(CDMA2000) cellular operator
    Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 716-3222
    +http://starlet.deltatelecom.ru ............. Frying on OpenVMS only +

  2. Re: [5.8-2]TCP KeepAlive?

    Hi!


    Sorry ladies and guys, it's a bug/feature in the HP SSL, I suspect so ...



    Ruslan R. Laishev wrote:
    > Hello!
    >
    > I see very strange problem:
    >
    > $ netcu sho conn /loc=*.995
    > TCPware(R) for OpenVMS Active Internet Connections (including servers):
    >
    > ID RecvQ SendQ Local Address Foreign Address State
    > -- ----- ----- ------------- --------------- -----
    > BG58558 0 0 172.16.0.45.pop3s 89.253.10.243.52656 ESTABLISHED
    > BG0 96 0 172.16.0.45.pop3s 217.66.145.101.22504 ESTABLISHED
    > BG0 102 0 172.16.0.45.pop3s 172.16.1.9.2796 CLOSE-WAIT
    > BG0 78 0 172.16.0.45.pop3s 172.16.1.9.2798 CLOSE-WAIT
    > BG0 69 0 172.16.0.45.pop3s 195.74.84.191.6222 CLOSE-WAIT
    > BG0 0 0 172.16.0.45.pop3s 195.74.84.191.6232 CLOSE-WAIT
    > BG63789 0 0 *.pop3s *.* LISTEN
    >
    >
    > $ netcu debug /tcp /lpn=995 /ria=217.66.145.101
    > DTV5::LAISHEV 11:21:35 NETCU CPU=00:02:11.53 PF=11239 IO=112080 MEM=344
    > DTV5::LAISHEV 11:21:57 NETCU CPU=00:02:11.53 PF=11240 IO=112081 MEM=345
    > DTV5::LAISHEV 11:22:08 NETCU CPU=00:02:11.53 PF=11240 IO=112082 MEM=345
    > DTV5::LAISHEV 11:22:31 NETCU CPU=00:02:11.53 PF=11240 IO=112083 MEM=345
    >
    >
    > $ netcu sho bg_tcp drop
    > Parameter BG_TCP DROP_TIMER's current value is 60
    > $ netcu sho bg_tcp prob
    > Parameter BG_TCP PROBE_TIMER's current value is 15
    > $
    >
    >
    > As I understand the SO_KeepAlivE don't work at all.
    >
    >
    >
    >


    --
    + WBR, OpenVMS [Sys|Net] HardWorker ................ ICQ# 319518233 +
    Delta Telecom JSC, IMT-MC-450(CDMA2000) cellular operator
    Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 716-3222
    +http://starlet.deltatelecom.ru ............. Frying on OpenVMS only +

  3. Re: [5.8-2]TCP KeepAlive?

    Hi There! It's me again....

    Thanks to Richard for TW SDA... So, now I see that KeepAlive options is set for
    the socket, but actualy KeepAlive does not checking.


    SDA> tw sho sock 906ACAC0
    scb at 906ACAC0 BG8623 lia 172.16.0.45 fia 172.16.0.4 lpn 995 fpn
    11490
    options REUSEADDR KEEPALIVE
    state SOCKET CONNECTED PRIV tcp flags IDLE WSCALE tcp state ESTABLISHED cdb
    88E2A100
    Receive Queue 90826700 90826700, byte count 0
    Transmit Queue 906ACB4C 906ACB4C, byte count 0
    Transmit data buffer 00000000, Byte count 0
    Hash table entry 88E2AC88, Hash Link 00000000
    Allocated RTE address 88E273C0 Send Unack 2190122137, Send Max 2190122137 Send
    next 2190122137 Send High water 32676
    send window size 4096, maximum 4096 congestion window 4380
    offered receive window size 61440
    probe idle 15 Drop idle 60
    maximum segment size 1460, original MSS 1460, MTU 8134

    SDA> Exit
    $ netcu debug /tcp /lpn=995 /ria=dtv4
    DTV5::LAISHEV 14:38:32 NETCU CPU=00:02:41.96 PF=15746 IO=138792 MEM=314
    DTV5::LAISHEV 14:38:53 NETCU CPU=00:02:41.96 PF=15748 IO=138793 MEM=316
    DTV5::LAISHEV 14:39:53 NETCU CPU=00:02:41.96 PF=15748 IO=138794 MEM=316
    DTV5::LAISHEV 14:39:53 NETCU CPU=00:02:41.96 PF=15748 IO=138795 MEM=316







    Ruslan R. Laishev wrote:
    > Hi!
    >
    >
    > Sorry ladies and guys, it's a bug/feature in the HP SSL, I suspect so ...
    >
    >
    >
    > Ruslan R. Laishev wrote:
    >> Hello!
    >>
    >> I see very strange problem:
    >>
    >> $ netcu sho conn /loc=*.995
    >> TCPware(R) for OpenVMS Active Internet Connections (including servers):
    >>
    >> ID RecvQ SendQ Local Address Foreign Address State
    >> -- ----- ----- ------------- --------------- -----
    >> BG58558 0 0 172.16.0.45.pop3s 89.253.10.243.52656 ESTABLISHED
    >> BG0 96 0 172.16.0.45.pop3s 217.66.145.101.22504 ESTABLISHED
    >> BG0 102 0 172.16.0.45.pop3s 172.16.1.9.2796 CLOSE-WAIT
    >> BG0 78 0 172.16.0.45.pop3s 172.16.1.9.2798 CLOSE-WAIT
    >> BG0 69 0 172.16.0.45.pop3s 195.74.84.191.6222 CLOSE-WAIT
    >> BG0 0 0 172.16.0.45.pop3s 195.74.84.191.6232 CLOSE-WAIT
    >> BG63789 0 0 *.pop3s *.* LISTEN
    >>
    >>
    >> $ netcu debug /tcp /lpn=995 /ria=217.66.145.101
    >> DTV5::LAISHEV 11:21:35 NETCU CPU=00:02:11.53 PF=11239 IO=112080 MEM=344
    >> DTV5::LAISHEV 11:21:57 NETCU CPU=00:02:11.53 PF=11240 IO=112081 MEM=345
    >> DTV5::LAISHEV 11:22:08 NETCU CPU=00:02:11.53 PF=11240 IO=112082 MEM=345
    >> DTV5::LAISHEV 11:22:31 NETCU CPU=00:02:11.53 PF=11240 IO=112083 MEM=345
    >>
    >>
    >> $ netcu sho bg_tcp drop
    >> Parameter BG_TCP DROP_TIMER's current value is 60
    >> $ netcu sho bg_tcp prob
    >> Parameter BG_TCP PROBE_TIMER's current value is 15
    >> $
    >>
    >>
    >> As I understand the SO_KeepAlivE don't work at all.
    >>
    >>
    >>
    >>

    >


    --
    + WBR, OpenVMS [Sys|Net] HardWorker ................ ICQ# 319518233 +
    Delta Telecom JSC, IMT-MC-450(CDMA2000) cellular operator
    Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 716-3222
    +http://starlet.deltatelecom.ru ............. Frying on OpenVMS only +

  4. Re: [5.8-2]TCP KeepAlive?

    Ruslan,

    Unfortunately the SDA callouts don't show the actual information used in
    figuring out when to send a keepalive packet. The default value for when to
    send a keepalive packet would be the drop idle time * 5 seconds, so you have
    to wait at least 5 minutes to see if a keepalive is sent.


    "Ruslan R. Laishev" wrote in message
    news:491429C5.5080108@SMTP.DeltaTel.RU...
    > Hi There! It's me again....
    >
    > Thanks to Richard for TW SDA... So, now I see that KeepAlive options is
    > set for
    > the socket, but actualy KeepAlive does not checking.
    >
    >
    > SDA> tw sho sock 906ACAC0
    > scb at 906ACAC0 BG8623 lia 172.16.0.45 fia 172.16.0.4 lpn
    > 995 fpn
    > 11490
    > options REUSEADDR KEEPALIVE
    > state SOCKET CONNECTED PRIV tcp flags IDLE WSCALE tcp state ESTABLISHED
    > cdb
    > 88E2A100
    > Receive Queue 90826700 90826700, byte count 0
    > Transmit Queue 906ACB4C 906ACB4C, byte count 0
    > Transmit data buffer 00000000, Byte count 0
    > Hash table entry 88E2AC88, Hash Link 00000000
    > Allocated RTE address 88E273C0 Send Unack 2190122137, Send Max 2190122137
    > Send
    > next 2190122137 Send High water 32676
    > send window size 4096, maximum 4096 congestion window 4380
    > offered receive window size 61440
    > probe idle 15 Drop idle 60
    > maximum segment size 1460, original MSS 1460, MTU 8134
    >
    > SDA> Exit
    > $ netcu debug /tcp /lpn=995 /ria=dtv4
    > DTV5::LAISHEV 14:38:32 NETCU CPU=00:02:41.96 PF=15746 IO=138792
    > MEM=314
    > DTV5::LAISHEV 14:38:53 NETCU CPU=00:02:41.96 PF=15748 IO=138793
    > MEM=316
    > DTV5::LAISHEV 14:39:53 NETCU CPU=00:02:41.96 PF=15748 IO=138794
    > MEM=316
    > DTV5::LAISHEV 14:39:53 NETCU CPU=00:02:41.96 PF=15748 IO=138795
    > MEM=316
    >
    >
    >
    >
    >
    >
    >
    > Ruslan R. Laishev wrote:
    >> Hi!
    >>
    >>
    >> Sorry ladies and guys, it's a bug/feature in the HP SSL, I suspect so ...
    >>
    >>
    >>
    >> Ruslan R. Laishev wrote:
    >>> Hello!
    >>>
    >>> I see very strange problem:
    >>>
    >>> $ netcu sho conn /loc=*.995
    >>> TCPware(R) for OpenVMS Active Internet Connections (including servers):
    >>>
    >>> ID RecvQ SendQ Local Address Foreign Address
    >>> State
    >>> -- ----- ----- ------------- --------------- -----
    >>> BG58558 0 0 172.16.0.45.pop3s 89.253.10.243.52656
    >>> ESTABLISHED
    >>> BG0 96 0 172.16.0.45.pop3s 217.66.145.101.22504
    >>> ESTABLISHED
    >>> BG0 102 0 172.16.0.45.pop3s 172.16.1.9.2796
    >>> CLOSE-WAIT
    >>> BG0 78 0 172.16.0.45.pop3s 172.16.1.9.2798
    >>> CLOSE-WAIT
    >>> BG0 69 0 172.16.0.45.pop3s 195.74.84.191.6222
    >>> CLOSE-WAIT
    >>> BG0 0 0 172.16.0.45.pop3s 195.74.84.191.6232
    >>> CLOSE-WAIT
    >>> BG63789 0 0 *.pop3s *.*
    >>> LISTEN
    >>>
    >>>
    >>> $ netcu debug /tcp /lpn=995 /ria=217.66.145.101
    >>> DTV5::LAISHEV 11:21:35 NETCU CPU=00:02:11.53 PF=11239 IO=112080
    >>> MEM=344
    >>> DTV5::LAISHEV 11:21:57 NETCU CPU=00:02:11.53 PF=11240 IO=112081
    >>> MEM=345
    >>> DTV5::LAISHEV 11:22:08 NETCU CPU=00:02:11.53 PF=11240 IO=112082
    >>> MEM=345
    >>> DTV5::LAISHEV 11:22:31 NETCU CPU=00:02:11.53 PF=11240 IO=112083
    >>> MEM=345
    >>>
    >>>
    >>> $ netcu sho bg_tcp drop
    >>> Parameter BG_TCP DROP_TIMER's current value is 60
    >>> $ netcu sho bg_tcp prob
    >>> Parameter BG_TCP PROBE_TIMER's current value is 15
    >>> $
    >>>
    >>>
    >>> As I understand the SO_KeepAlivE don't work at all.
    >>>
    >>>
    >>>
    >>>

    >>

    >
    > --
    > + WBR, OpenVMS [Sys|Net] HardWorker ................ ICQ# 319518233 +
    > Delta Telecom JSC, IMT-MC-450(CDMA2000) cellular operator
    > Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 716-3222
    > +http://starlet.deltatelecom.ru ............. Frying on OpenVMS only +




  5. Re: [5.8-2]TCP KeepAlive?

    Hi, Richard!

    From the docs:

    BG_TCP Parameters and Values
    BG_TCP DROP_TIMER seconds
    Maximum number of *seconds* to probe for idle TCP connections before a
    TCP connection close
    times out.
    BG_TCP PROBE_TIMER seconds
    Number of *seconds* between probes for idle TCP connections. Also
    indicates the maximum number
    of seconds before a TCP connection request times out.


    >> probe idle 15 Drop idle 60








    Richard Whalen wrote:
    > Ruslan,
    >
    > Unfortunately the SDA callouts don't show the actual information used in
    > figuring out when to send a keepalive packet. The default value for when to
    > send a keepalive packet would be the drop idle time * 5 seconds, so you have
    > to wait at least 5 minutes to see if a keepalive is sent.
    >
    >
    > "Ruslan R. Laishev" wrote in message
    > news:491429C5.5080108@SMTP.DeltaTel.RU...
    >> Hi There! It's me again....
    >>
    >> Thanks to Richard for TW SDA... So, now I see that KeepAlive options is
    >> set for
    >> the socket, but actualy KeepAlive does not checking.
    >>
    >>
    >> SDA> tw sho sock 906ACAC0
    >> scb at 906ACAC0 BG8623 lia 172.16.0.45 fia 172.16.0.4 lpn
    >> 995 fpn
    >> 11490
    >> options REUSEADDR KEEPALIVE
    >> state SOCKET CONNECTED PRIV tcp flags IDLE WSCALE tcp state ESTABLISHED
    >> cdb
    >> 88E2A100
    >> Receive Queue 90826700 90826700, byte count 0
    >> Transmit Queue 906ACB4C 906ACB4C, byte count 0
    >> Transmit data buffer 00000000, Byte count 0
    >> Hash table entry 88E2AC88, Hash Link 00000000
    >> Allocated RTE address 88E273C0 Send Unack 2190122137, Send Max 2190122137
    >> Send
    >> next 2190122137 Send High water 32676
    >> send window size 4096, maximum 4096 congestion window 4380
    >> offered receive window size 61440
    >> probe idle 15 Drop idle 60
    >> maximum segment size 1460, original MSS 1460, MTU 8134
    >>
    >> SDA> Exit
    >> $ netcu debug /tcp /lpn=995 /ria=dtv4
    >> DTV5::LAISHEV 14:38:32 NETCU CPU=00:02:41.96 PF=15746 IO=138792
    >> MEM=314
    >> DTV5::LAISHEV 14:38:53 NETCU CPU=00:02:41.96 PF=15748 IO=138793
    >> MEM=316
    >> DTV5::LAISHEV 14:39:53 NETCU CPU=00:02:41.96 PF=15748 IO=138794
    >> MEM=316
    >> DTV5::LAISHEV 14:39:53 NETCU CPU=00:02:41.96 PF=15748 IO=138795
    >> MEM=316
    >>
    >>
    >>
    >>
    >>
    >>
    >>
    >> Ruslan R. Laishev wrote:
    >>> Hi!
    >>>
    >>>
    >>> Sorry ladies and guys, it's a bug/feature in the HP SSL, I suspect so ...
    >>>
    >>>
    >>>
    >>> Ruslan R. Laishev wrote:
    >>>> Hello!
    >>>>
    >>>> I see very strange problem:
    >>>>
    >>>> $ netcu sho conn /loc=*.995
    >>>> TCPware(R) for OpenVMS Active Internet Connections (including servers):
    >>>>
    >>>> ID RecvQ SendQ Local Address Foreign Address
    >>>> State
    >>>> -- ----- ----- ------------- --------------- -----
    >>>> BG58558 0 0 172.16.0.45.pop3s 89.253.10.243.52656
    >>>> ESTABLISHED
    >>>> BG0 96 0 172.16.0.45.pop3s 217.66.145.101.22504
    >>>> ESTABLISHED
    >>>> BG0 102 0 172.16.0.45.pop3s 172.16.1.9.2796
    >>>> CLOSE-WAIT
    >>>> BG0 78 0 172.16.0.45.pop3s 172.16.1.9.2798
    >>>> CLOSE-WAIT
    >>>> BG0 69 0 172.16.0.45.pop3s 195.74.84.191.6222
    >>>> CLOSE-WAIT
    >>>> BG0 0 0 172.16.0.45.pop3s 195.74.84.191.6232
    >>>> CLOSE-WAIT
    >>>> BG63789 0 0 *.pop3s *.*
    >>>> LISTEN
    >>>>
    >>>>
    >>>> $ netcu debug /tcp /lpn=995 /ria=217.66.145.101
    >>>> DTV5::LAISHEV 11:21:35 NETCU CPU=00:02:11.53 PF=11239 IO=112080
    >>>> MEM=344
    >>>> DTV5::LAISHEV 11:21:57 NETCU CPU=00:02:11.53 PF=11240 IO=112081
    >>>> MEM=345
    >>>> DTV5::LAISHEV 11:22:08 NETCU CPU=00:02:11.53 PF=11240 IO=112082
    >>>> MEM=345
    >>>> DTV5::LAISHEV 11:22:31 NETCU CPU=00:02:11.53 PF=11240 IO=112083
    >>>> MEM=345
    >>>>
    >>>>
    >>>> $ netcu sho bg_tcp drop
    >>>> Parameter BG_TCP DROP_TIMER's current value is 60
    >>>> $ netcu sho bg_tcp prob
    >>>> Parameter BG_TCP PROBE_TIMER's current value is 15
    >>>> $
    >>>>
    >>>>
    >>>> As I understand the SO_KeepAlivE don't work at all.
    >>>>
    >>>>
    >>>>
    >>>>

    >> --
    >> + WBR, OpenVMS [Sys|Net] HardWorker ................ ICQ# 319518233 +
    >> Delta Telecom JSC, IMT-MC-450(CDMA2000) cellular operator
    >> Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 716-3222
    >> +http://starlet.deltatelecom.ru ............. Frying on OpenVMS only +

    >
    >
    >
    > .
    >


  6. Re: [5.8-2]TCP KeepAlive?

    Hi, Richard!

    From the docs:

    BG_TCP Parameters and Values
    BG_TCP DROP_TIMER seconds
    Maximum number of *seconds* to probe for idle TCP connections before a
    TCP connection close
    times out.
    BG_TCP PROBE_TIMER seconds
    Number of *seconds* between probes for idle TCP connections. Also
    indicates the maximum number
    of seconds before a TCP connection request times out.


    >> probe idle 15 Drop idle 60








    Richard Whalen wrote:
    > Ruslan,
    >
    > Unfortunately the SDA callouts don't show the actual information used in
    > figuring out when to send a keepalive packet. The default value for when to
    > send a keepalive packet would be the drop idle time * 5 seconds, so you have
    > to wait at least 5 minutes to see if a keepalive is sent.
    >
    >
    > "Ruslan R. Laishev" wrote in message
    > news:491429C5.5080108@SMTP.DeltaTel.RU...
    >> Hi There! It's me again....
    >>
    >> Thanks to Richard for TW SDA... So, now I see that KeepAlive options is
    >> set for
    >> the socket, but actualy KeepAlive does not checking.
    >>
    >>
    >> SDA> tw sho sock 906ACAC0
    >> scb at 906ACAC0 BG8623 lia 172.16.0.45 fia 172.16.0.4 lpn
    >> 995 fpn
    >> 11490
    >> options REUSEADDR KEEPALIVE
    >> state SOCKET CONNECTED PRIV tcp flags IDLE WSCALE tcp state ESTABLISHED
    >> cdb
    >> 88E2A100
    >> Receive Queue 90826700 90826700, byte count 0
    >> Transmit Queue 906ACB4C 906ACB4C, byte count 0
    >> Transmit data buffer 00000000, Byte count 0
    >> Hash table entry 88E2AC88, Hash Link 00000000
    >> Allocated RTE address 88E273C0 Send Unack 2190122137, Send Max 2190122137
    >> Send
    >> next 2190122137 Send High water 32676
    >> send window size 4096, maximum 4096 congestion window 4380
    >> offered receive window size 61440
    >> probe idle 15 Drop idle 60
    >> maximum segment size 1460, original MSS 1460, MTU 8134
    >>
    >> SDA> Exit
    >> $ netcu debug /tcp /lpn=995 /ria=dtv4
    >> DTV5::LAISHEV 14:38:32 NETCU CPU=00:02:41.96 PF=15746 IO=138792
    >> MEM=314
    >> DTV5::LAISHEV 14:38:53 NETCU CPU=00:02:41.96 PF=15748 IO=138793
    >> MEM=316
    >> DTV5::LAISHEV 14:39:53 NETCU CPU=00:02:41.96 PF=15748 IO=138794
    >> MEM=316
    >> DTV5::LAISHEV 14:39:53 NETCU CPU=00:02:41.96 PF=15748 IO=138795
    >> MEM=316
    >>
    >>
    >>
    >>
    >>
    >>
    >>
    >> Ruslan R. Laishev wrote:
    >>> Hi!
    >>>
    >>>
    >>> Sorry ladies and guys, it's a bug/feature in the HP SSL, I suspect so ...
    >>>
    >>>
    >>>
    >>> Ruslan R. Laishev wrote:
    >>>> Hello!
    >>>>
    >>>> I see very strange problem:
    >>>>
    >>>> $ netcu sho conn /loc=*.995
    >>>> TCPware(R) for OpenVMS Active Internet Connections (including servers):
    >>>>
    >>>> ID RecvQ SendQ Local Address Foreign Address
    >>>> State
    >>>> -- ----- ----- ------------- --------------- -----
    >>>> BG58558 0 0 172.16.0.45.pop3s 89.253.10.243.52656
    >>>> ESTABLISHED
    >>>> BG0 96 0 172.16.0.45.pop3s 217.66.145.101.22504
    >>>> ESTABLISHED
    >>>> BG0 102 0 172.16.0.45.pop3s 172.16.1.9.2796
    >>>> CLOSE-WAIT
    >>>> BG0 78 0 172.16.0.45.pop3s 172.16.1.9.2798
    >>>> CLOSE-WAIT
    >>>> BG0 69 0 172.16.0.45.pop3s 195.74.84.191.6222
    >>>> CLOSE-WAIT
    >>>> BG0 0 0 172.16.0.45.pop3s 195.74.84.191.6232
    >>>> CLOSE-WAIT
    >>>> BG63789 0 0 *.pop3s *.*
    >>>> LISTEN
    >>>>
    >>>>
    >>>> $ netcu debug /tcp /lpn=995 /ria=217.66.145.101
    >>>> DTV5::LAISHEV 11:21:35 NETCU CPU=00:02:11.53 PF=11239 IO=112080
    >>>> MEM=344
    >>>> DTV5::LAISHEV 11:21:57 NETCU CPU=00:02:11.53 PF=11240 IO=112081
    >>>> MEM=345
    >>>> DTV5::LAISHEV 11:22:08 NETCU CPU=00:02:11.53 PF=11240 IO=112082
    >>>> MEM=345
    >>>> DTV5::LAISHEV 11:22:31 NETCU CPU=00:02:11.53 PF=11240 IO=112083
    >>>> MEM=345
    >>>>
    >>>>
    >>>> $ netcu sho bg_tcp drop
    >>>> Parameter BG_TCP DROP_TIMER's current value is 60
    >>>> $ netcu sho bg_tcp prob
    >>>> Parameter BG_TCP PROBE_TIMER's current value is 15
    >>>> $
    >>>>
    >>>>
    >>>> As I understand the SO_KeepAlivE don't work at all.
    >>>>
    >>>>
    >>>>
    >>>>

    >> --
    >> + WBR, OpenVMS [Sys|Net] HardWorker ................ ICQ# 319518233 +
    >> Delta Telecom JSC, IMT-MC-450(CDMA2000) cellular operator
    >> Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 716-3222
    >> +http://starlet.deltatelecom.ru ............. Frying on OpenVMS only +

    >
    >
    >
    > .
    >



  7. Re: [5.8-2]TCP KeepAlive?

    Hi, Richard!

    I spend 10+ minutes in hope that will catch keepalive checking.


    $ netcu sho conn /loc=*.995
    TCPware(R) for OpenVMS Active Internet Connections (including servers ) :

    ID RecvQ SendQ Local Address Foreign Address State
    -- ----- ----- ------------- --------------- -----
    BG50578 0 0 172.16.0.8.pop3s 83.149.3.47.5518
    ESTABLISHED
    BG0 171 0 172.16.0.8.pop3s 172.16.1.24.20735
    CLOSE-WAIT
    BG0 96 0 172.16.0.8.pop3s 89.223.96.210.12175
    CLOSE-WAIT
    BG0 102 0 172.16.0.8.pop3s 172.16.1.9.4001
    CLOSE-WAIT
    BG0 78 0 172.16.0.8.pop3s 172.16.1.9.4007
    CLOSE-WAIT
    BG0 96 0 172.16.0.8.pop3s 83.149.3.86.53202
    CLOSE-WAIT
    BG44749 0 0 *.pop3s *.* LISTEN


    $ netcu debug /tcp /ria=83.149.3.47 /rpn=5518
    DTV1::SSHD 0843A PTD 11:35:03 NETCU CPU=00:00:00.18 PF=608 IO=610
    MEM=296
    New mail on node DTV5 from MX%"jcagey@mail2doctor.com"
    "=?koi8-r?B?7NXexdrB0iDlxtLFzQ==?=" (11:35:49)
    DTV1::SSHD 0843A PTD 11:36:34 NETCU CPU=00:00:00.18 PF=608 IO=611
    MEM=296
    DTV1::SSHD 0843A PTD 11:38:46 NETCU CPU=00:00:00.18 PF=608 IO=612
    MEM=296
    DTV1::SSHD 0843A PTD 11:40:15 NETCU CPU=00:00:00.18 PF=608 IO=613
    MEM=296
    DTV1::SSHD 0843A PTD 11:40:15 NETCU CPU=00:00:00.18 PF=608 IO=614
    MEM=296
    DTV1::SSHD 0843A PTD 11:41:25 NETCU CPU=00:00:00.18 PF=608 IO=615
    MEM=296
    DTV1::SSHD 0843A PTD 11:42:59 NETCU CPU=00:00:00.18 PF=608 IO=616
    MEM=296
    DTV1::SSHD 0843A PTD 11:42:59 NETCU CPU=00:00:00.18 PF=608 IO=617
    MEM=296
    DTV1::SSHD 0843A PTD 11:45:31 NETCU CPU=00:00:00.18 PF=608 IO=618
    MEM=296
    DTV1::SSHD 0843A PTD 11:47:13 NETCU CPU=00:00:00.18 PF=608 IO=619
    MEM=296
    DTV1::SSHD 0843A PTD 11:47:41 NETCU CPU=00:00:00.18 PF=608 IO=620
    MEM=296
    Cancel

    $ netcu sho conn /loc=*.995
    TCPware(R) for OpenVMS Active Internet Connections (including servers ) :

    ID RecvQ SendQ Local Address Foreign Address State
    -- ----- ----- ------------- --------------- -----
    BG50578 0 0 172.16.0.8.pop3s 83.149.3.47.5518
    ESTABLISHED
    BG0 171 0 172.16.0.8.pop3s 172.16.1.24.20735
    CLOSE-WAIT
    BG0 96 0 172.16.0.8.pop3s 89.223.96.210.12175
    CLOSE-WAIT
    BG0 102 0 172.16.0.8.pop3s 172.16.1.9.4001
    CLOSE-WAIT
    BG0 78 0 172.16.0.8.pop3s 172.16.1.9.4007
    CLOSE-WAIT
    BG0 96 0 172.16.0.8.pop3s 83.149.3.86.53202
    CLOSE-WAIT
    BG44749 0 0 *.pop3s *.* LISTEN
    $


    SDA> tw sho sock 8A8BDDC0
    scb at 8A8BDDC0 BG50578 lia 172.16.0.8 fia 83.149.3.47 lpn
    995 fpn 5518
    options REUSEADDR KEEPALIVE
    state SOCKET CONNECTED PRIV tcp flags IDLE WSCALE tcp state
    ESTABLISHED cdb 89A9E000
    Receive Queue 89C783C0 89C783C0, byte count 0
    Transmit Queue 8A8BDE4C 8A8BDE4C, byte count 0
    Transmit data buffer 00000000, Byte count 0
    Hash table entry 89A9E47C, Hash Link 00000000
    Allocated RTE address 89849C80 Send Unack 1063292057, Send Max
    1063292057 Send next 1063292057 Send High water 32676
    send window size 66240, maximum 66240 congestion window 4140
    offered receive window size 61440
    probe idle 15 Drop idle 60
    maximum segment size 1380, original MSS 1380, MTU 1460

    SDA>
    DTV1::SSHD 0843A PTD 11:52:37 (DCL) CPU=00:00:00.30 PF=972 IO=960
    MEM=165
    $ netcu sho conn /loc=*.995
    TCPware(R) for OpenVMS Active Internet Connections (including servers):

    ID RecvQ SendQ Local Address Foreign Address State
    -- ----- ----- ------------- --------------- -----
    BG50578 0 0 172.16.0.8.pop3s 83.149.3.47.5518
    ESTABLISHED
    BG0 171 0 172.16.0.8.pop3s 172.16.1.24.20735
    CLOSE-WAIT
    BG0 96 0 172.16.0.8.pop3s 89.223.96.210.12175
    CLOSE-WAIT
    BG0 102 0 172.16.0.8.pop3s 172.16.1.9.4001
    CLOSE-WAIT
    BG0 78 0 172.16.0.8.pop3s 172.16.1.9.4007
    CLOSE-WAIT
    BG0 96 0 172.16.0.8.pop3s 83.149.3.86.53202
    CLOSE-WAIT
    BG44749 0 0 *.pop3s *.* LISTEN
    $


    Ruslan R. Laishev wrote:
    > Hi, Richard!
    >
    > From the docs:
    >
    > BG_TCP Parameters and Values
    > BG_TCP DROP_TIMER seconds
    > Maximum number of *seconds* to probe for idle TCP connections before a
    > TCP connection close
    > times out.
    > BG_TCP PROBE_TIMER seconds
    > Number of *seconds* between probes for idle TCP connections. Also
    > indicates the maximum number
    > of seconds before a TCP connection request times out.
    >
    >
    >>> probe idle 15 Drop idle 60

    >
    >
    >
    >
    >
    >
    >
    > Richard Whalen wrote:
    >> Ruslan,
    >>
    >> Unfortunately the SDA callouts don't show the actual information used
    >> in figuring out when to send a keepalive packet. The default value
    >> for when to send a keepalive packet would be the drop idle time * 5
    >> seconds, so you have to wait at least 5 minutes to see if a keepalive
    >> is sent.
    >>
    >>
    >> "Ruslan R. Laishev" wrote in message
    >> news:491429C5.5080108@SMTP.DeltaTel.RU...
    >>> Hi There! It's me again....
    >>>
    >>> Thanks to Richard for TW SDA... So, now I see that KeepAlive options
    >>> is set for
    >>> the socket, but actualy KeepAlive does not checking.
    >>>
    >>>
    >>> SDA> tw sho sock 906ACAC0
    >>> scb at 906ACAC0 BG8623 lia 172.16.0.45 fia 172.16.0.4
    >>> lpn 995 fpn
    >>> 11490
    >>> options REUSEADDR KEEPALIVE
    >>> state SOCKET CONNECTED PRIV tcp flags IDLE WSCALE tcp state
    >>> ESTABLISHED cdb
    >>> 88E2A100
    >>> Receive Queue 90826700 90826700, byte count 0
    >>> Transmit Queue 906ACB4C 906ACB4C, byte count 0
    >>> Transmit data buffer 00000000, Byte count 0
    >>> Hash table entry 88E2AC88, Hash Link 00000000
    >>> Allocated RTE address 88E273C0 Send Unack 2190122137, Send Max
    >>> 2190122137 Send
    >>> next 2190122137 Send High water 32676
    >>> send window size 4096, maximum 4096 congestion window 4380
    >>> offered receive window size 61440
    >>> probe idle 15 Drop idle 60
    >>> maximum segment size 1460, original MSS 1460, MTU 8134
    >>>
    >>> SDA> Exit
    >>> $ netcu debug /tcp /lpn=995 /ria=dtv4
    >>> DTV5::LAISHEV 14:38:32 NETCU CPU=00:02:41.96 PF=15746 IO=138792
    >>> MEM=314
    >>> DTV5::LAISHEV 14:38:53 NETCU CPU=00:02:41.96 PF=15748 IO=138793
    >>> MEM=316
    >>> DTV5::LAISHEV 14:39:53 NETCU CPU=00:02:41.96 PF=15748 IO=138794
    >>> MEM=316
    >>> DTV5::LAISHEV 14:39:53 NETCU CPU=00:02:41.96 PF=15748 IO=138795
    >>> MEM=316
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>
    >>> Ruslan R. Laishev wrote:
    >>>> Hi!
    >>>>
    >>>>
    >>>> Sorry ladies and guys, it's a bug/feature in the HP SSL, I suspect
    >>>> so ...
    >>>>
    >>>>
    >>>>
    >>>> Ruslan R. Laishev wrote:
    >>>>> Hello!
    >>>>>
    >>>>> I see very strange problem:
    >>>>>
    >>>>> $ netcu sho conn /loc=*.995
    >>>>> TCPware(R) for OpenVMS Active Internet Connections (including
    >>>>> servers):
    >>>>>
    >>>>> ID RecvQ SendQ Local Address Foreign Address State
    >>>>> -- ----- ----- -------------
    >>>>> --------------- -----
    >>>>> BG58558 0 0 172.16.0.45.pop3s 89.253.10.243.52656
    >>>>> ESTABLISHED
    >>>>> BG0 96 0 172.16.0.45.pop3s 217.66.145.101.22504
    >>>>> ESTABLISHED
    >>>>> BG0 102 0 172.16.0.45.pop3s 172.16.1.9.2796
    >>>>> CLOSE-WAIT
    >>>>> BG0 78 0 172.16.0.45.pop3s 172.16.1.9.2798
    >>>>> CLOSE-WAIT
    >>>>> BG0 69 0 172.16.0.45.pop3s 195.74.84.191.6222
    >>>>> CLOSE-WAIT
    >>>>> BG0 0 0 172.16.0.45.pop3s 195.74.84.191.6232
    >>>>> CLOSE-WAIT
    >>>>> BG63789 0 0 *.pop3s *.* LISTEN
    >>>>>
    >>>>>
    >>>>> $ netcu debug /tcp /lpn=995 /ria=217.66.145.101
    >>>>> DTV5::LAISHEV 11:21:35 NETCU CPU=00:02:11.53 PF=11239 IO=112080
    >>>>> MEM=344
    >>>>> DTV5::LAISHEV 11:21:57 NETCU CPU=00:02:11.53 PF=11240 IO=112081
    >>>>> MEM=345
    >>>>> DTV5::LAISHEV 11:22:08 NETCU CPU=00:02:11.53 PF=11240 IO=112082
    >>>>> MEM=345
    >>>>> DTV5::LAISHEV 11:22:31 NETCU CPU=00:02:11.53 PF=11240 IO=112083
    >>>>> MEM=345
    >>>>>
    >>>>>
    >>>>> $ netcu sho bg_tcp drop
    >>>>> Parameter BG_TCP DROP_TIMER's current value is 60
    >>>>> $ netcu sho bg_tcp prob
    >>>>> Parameter BG_TCP PROBE_TIMER's current value is 15
    >>>>> $
    >>>>>
    >>>>>
    >>>>> As I understand the SO_KeepAlivE don't work at all.
    >>>>>
    >>>>>
    >>>>>
    >>>>>
    >>> --
    >>> + WBR, OpenVMS [Sys|Net] HardWorker ................ ICQ# 319518233 +
    >>> Delta Telecom JSC, IMT-MC-450(CDMA2000) cellular operator
    >>> Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 716-3222
    >>> +http://starlet.deltatelecom.ru ............. Frying on OpenVMS only +

    >>
    >>
    >>
    >> .
    >>

    >
    >
    > .
    >


  8. Re: [5.8-2]TCP KeepAlive?

    Hi, Richard!

    I spend 10+ minutes in hope that will catch keepalive checking.


    $ netcu sho conn /loc=*.995
    TCPware(R) for OpenVMS Active Internet Connections (including servers ) :

    ID RecvQ SendQ Local Address Foreign Address State
    -- ----- ----- ------------- --------------- -----
    BG50578 0 0 172.16.0.8.pop3s 83.149.3.47.5518
    ESTABLISHED
    BG0 171 0 172.16.0.8.pop3s 172.16.1.24.20735
    CLOSE-WAIT
    BG0 96 0 172.16.0.8.pop3s 89.223.96.210.12175
    CLOSE-WAIT
    BG0 102 0 172.16.0.8.pop3s 172.16.1.9.4001
    CLOSE-WAIT
    BG0 78 0 172.16.0.8.pop3s 172.16.1.9.4007
    CLOSE-WAIT
    BG0 96 0 172.16.0.8.pop3s 83.149.3.86.53202
    CLOSE-WAIT
    BG44749 0 0 *.pop3s *.* LISTEN


    $ netcu debug /tcp /ria=83.149.3.47 /rpn=5518
    DTV1::SSHD 0843A PTD 11:35:03 NETCU CPU=00:00:00.18 PF=608 IO=610
    MEM=296
    New mail on node DTV5 from MX%"jcagey@mail2doctor.com"
    "=?koi8-r?B?7NXexdrB0iDlxtLFzQ==?=" (11:35:49)
    DTV1::SSHD 0843A PTD 11:36:34 NETCU CPU=00:00:00.18 PF=608 IO=611
    MEM=296
    DTV1::SSHD 0843A PTD 11:38:46 NETCU CPU=00:00:00.18 PF=608 IO=612
    MEM=296
    DTV1::SSHD 0843A PTD 11:40:15 NETCU CPU=00:00:00.18 PF=608 IO=613
    MEM=296
    DTV1::SSHD 0843A PTD 11:40:15 NETCU CPU=00:00:00.18 PF=608 IO=614
    MEM=296
    DTV1::SSHD 0843A PTD 11:41:25 NETCU CPU=00:00:00.18 PF=608 IO=615
    MEM=296
    DTV1::SSHD 0843A PTD 11:42:59 NETCU CPU=00:00:00.18 PF=608 IO=616
    MEM=296
    DTV1::SSHD 0843A PTD 11:42:59 NETCU CPU=00:00:00.18 PF=608 IO=617
    MEM=296
    DTV1::SSHD 0843A PTD 11:45:31 NETCU CPU=00:00:00.18 PF=608 IO=618
    MEM=296
    DTV1::SSHD 0843A PTD 11:47:13 NETCU CPU=00:00:00.18 PF=608 IO=619
    MEM=296
    DTV1::SSHD 0843A PTD 11:47:41 NETCU CPU=00:00:00.18 PF=608 IO=620
    MEM=296
    Cancel

    $ netcu sho conn /loc=*.995
    TCPware(R) for OpenVMS Active Internet Connections (including servers ) :

    ID RecvQ SendQ Local Address Foreign Address State
    -- ----- ----- ------------- --------------- -----
    BG50578 0 0 172.16.0.8.pop3s 83.149.3.47.5518
    ESTABLISHED
    BG0 171 0 172.16.0.8.pop3s 172.16.1.24.20735
    CLOSE-WAIT
    BG0 96 0 172.16.0.8.pop3s 89.223.96.210.12175
    CLOSE-WAIT
    BG0 102 0 172.16.0.8.pop3s 172.16.1.9.4001
    CLOSE-WAIT
    BG0 78 0 172.16.0.8.pop3s 172.16.1.9.4007
    CLOSE-WAIT
    BG0 96 0 172.16.0.8.pop3s 83.149.3.86.53202
    CLOSE-WAIT
    BG44749 0 0 *.pop3s *.* LISTEN
    $


    SDA> tw sho sock 8A8BDDC0
    scb at 8A8BDDC0 BG50578 lia 172.16.0.8 fia 83.149.3.47 lpn
    995 fpn 5518
    options REUSEADDR KEEPALIVE
    state SOCKET CONNECTED PRIV tcp flags IDLE WSCALE tcp state
    ESTABLISHED cdb 89A9E000
    Receive Queue 89C783C0 89C783C0, byte count 0
    Transmit Queue 8A8BDE4C 8A8BDE4C, byte count 0
    Transmit data buffer 00000000, Byte count 0
    Hash table entry 89A9E47C, Hash Link 00000000
    Allocated RTE address 89849C80 Send Unack 1063292057, Send Max
    1063292057 Send next 1063292057 Send High water 32676
    send window size 66240, maximum 66240 congestion window 4140
    offered receive window size 61440
    probe idle 15 Drop idle 60
    maximum segment size 1380, original MSS 1380, MTU 1460

    SDA>
    DTV1::SSHD 0843A PTD 11:52:37 (DCL) CPU=00:00:00.30 PF=972 IO=960
    MEM=165
    $ netcu sho conn /loc=*.995
    TCPware(R) for OpenVMS Active Internet Connections (including servers):

    ID RecvQ SendQ Local Address Foreign Address State
    -- ----- ----- ------------- --------------- -----
    BG50578 0 0 172.16.0.8.pop3s 83.149.3.47.5518
    ESTABLISHED
    BG0 171 0 172.16.0.8.pop3s 172.16.1.24.20735
    CLOSE-WAIT
    BG0 96 0 172.16.0.8.pop3s 89.223.96.210.12175
    CLOSE-WAIT
    BG0 102 0 172.16.0.8.pop3s 172.16.1.9.4001
    CLOSE-WAIT
    BG0 78 0 172.16.0.8.pop3s 172.16.1.9.4007
    CLOSE-WAIT
    BG0 96 0 172.16.0.8.pop3s 83.149.3.86.53202
    CLOSE-WAIT
    BG44749 0 0 *.pop3s *.* LISTEN
    $


    Ruslan R. Laishev wrote:
    > Hi, Richard!
    >
    > From the docs:
    >
    > BG_TCP Parameters and Values
    > BG_TCP DROP_TIMER seconds
    > Maximum number of *seconds* to probe for idle TCP connections before a
    > TCP connection close
    > times out.
    > BG_TCP PROBE_TIMER seconds
    > Number of *seconds* between probes for idle TCP connections. Also
    > indicates the maximum number
    > of seconds before a TCP connection request times out.
    >
    >
    >>> probe idle 15 Drop idle 60

    >
    >
    >
    >
    >
    >
    >
    > Richard Whalen wrote:
    >> Ruslan,
    >>
    >> Unfortunately the SDA callouts don't show the actual information used
    >> in figuring out when to send a keepalive packet. The default value
    >> for when to send a keepalive packet would be the drop idle time * 5
    >> seconds, so you have to wait at least 5 minutes to see if a keepalive
    >> is sent.
    >>
    >>
    >> "Ruslan R. Laishev" wrote in message
    >> news:491429C5.5080108@SMTP.DeltaTel.RU...
    >>> Hi There! It's me again....
    >>>
    >>> Thanks to Richard for TW SDA... So, now I see that KeepAlive options
    >>> is set for
    >>> the socket, but actualy KeepAlive does not checking.
    >>>
    >>>
    >>> SDA> tw sho sock 906ACAC0
    >>> scb at 906ACAC0 BG8623 lia 172.16.0.45 fia 172.16.0.4
    >>> lpn 995 fpn
    >>> 11490
    >>> options REUSEADDR KEEPALIVE
    >>> state SOCKET CONNECTED PRIV tcp flags IDLE WSCALE tcp state
    >>> ESTABLISHED cdb
    >>> 88E2A100
    >>> Receive Queue 90826700 90826700, byte count 0
    >>> Transmit Queue 906ACB4C 906ACB4C, byte count 0
    >>> Transmit data buffer 00000000, Byte count 0
    >>> Hash table entry 88E2AC88, Hash Link 00000000
    >>> Allocated RTE address 88E273C0 Send Unack 2190122137, Send Max
    >>> 2190122137 Send
    >>> next 2190122137 Send High water 32676
    >>> send window size 4096, maximum 4096 congestion window 4380
    >>> offered receive window size 61440
    >>> probe idle 15 Drop idle 60
    >>> maximum segment size 1460, original MSS 1460, MTU 8134
    >>>
    >>> SDA> Exit
    >>> $ netcu debug /tcp /lpn=995 /ria=dtv4
    >>> DTV5::LAISHEV 14:38:32 NETCU CPU=00:02:41.96 PF=15746 IO=138792
    >>> MEM=314
    >>> DTV5::LAISHEV 14:38:53 NETCU CPU=00:02:41.96 PF=15748 IO=138793
    >>> MEM=316
    >>> DTV5::LAISHEV 14:39:53 NETCU CPU=00:02:41.96 PF=15748 IO=138794
    >>> MEM=316
    >>> DTV5::LAISHEV 14:39:53 NETCU CPU=00:02:41.96 PF=15748 IO=138795
    >>> MEM=316
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>
    >>>
    >>> Ruslan R. Laishev wrote:
    >>>> Hi!
    >>>>
    >>>>
    >>>> Sorry ladies and guys, it's a bug/feature in the HP SSL, I suspect
    >>>> so ...
    >>>>
    >>>>
    >>>>
    >>>> Ruslan R. Laishev wrote:
    >>>>> Hello!
    >>>>>
    >>>>> I see very strange problem:
    >>>>>
    >>>>> $ netcu sho conn /loc=*.995
    >>>>> TCPware(R) for OpenVMS Active Internet Connections (including
    >>>>> servers):
    >>>>>
    >>>>> ID RecvQ SendQ Local Address Foreign Address State
    >>>>> -- ----- ----- -------------
    >>>>> --------------- -----
    >>>>> BG58558 0 0 172.16.0.45.pop3s 89.253.10.243.52656
    >>>>> ESTABLISHED
    >>>>> BG0 96 0 172.16.0.45.pop3s 217.66.145.101.22504
    >>>>> ESTABLISHED
    >>>>> BG0 102 0 172.16.0.45.pop3s 172.16.1.9.2796
    >>>>> CLOSE-WAIT
    >>>>> BG0 78 0 172.16.0.45.pop3s 172.16.1.9.2798
    >>>>> CLOSE-WAIT
    >>>>> BG0 69 0 172.16.0.45.pop3s 195.74.84.191.6222
    >>>>> CLOSE-WAIT
    >>>>> BG0 0 0 172.16.0.45.pop3s 195.74.84.191.6232
    >>>>> CLOSE-WAIT
    >>>>> BG63789 0 0 *.pop3s *.* LISTEN
    >>>>>
    >>>>>
    >>>>> $ netcu debug /tcp /lpn=995 /ria=217.66.145.101
    >>>>> DTV5::LAISHEV 11:21:35 NETCU CPU=00:02:11.53 PF=11239 IO=112080
    >>>>> MEM=344
    >>>>> DTV5::LAISHEV 11:21:57 NETCU CPU=00:02:11.53 PF=11240 IO=112081
    >>>>> MEM=345
    >>>>> DTV5::LAISHEV 11:22:08 NETCU CPU=00:02:11.53 PF=11240 IO=112082
    >>>>> MEM=345
    >>>>> DTV5::LAISHEV 11:22:31 NETCU CPU=00:02:11.53 PF=11240 IO=112083
    >>>>> MEM=345
    >>>>>
    >>>>>
    >>>>> $ netcu sho bg_tcp drop
    >>>>> Parameter BG_TCP DROP_TIMER's current value is 60
    >>>>> $ netcu sho bg_tcp prob
    >>>>> Parameter BG_TCP PROBE_TIMER's current value is 15
    >>>>> $
    >>>>>
    >>>>>
    >>>>> As I understand the SO_KeepAlivE don't work at all.
    >>>>>
    >>>>>
    >>>>>
    >>>>>
    >>> --
    >>> + WBR, OpenVMS [Sys|Net] HardWorker ................ ICQ# 319518233 +
    >>> Delta Telecom JSC, IMT-MC-450(CDMA2000) cellular operator
    >>> Russia,191119,St.Petersburg,Transportny per. 3 Cel: +7 (812) 716-3222
    >>> +http://starlet.deltatelecom.ru ............. Frying on OpenVMS only +

    >>
    >>
    >>
    >> .
    >>

    >
    >
    > .
    >



+ Reply to Thread