Results 1 to 5 of 5

Thread: Dodgy looking info on netstat

  1. #1

    Dodgy looking info on netstat

    Hi all, I've been having some connection issues lately and so just decided to do a netstat to have a look what's going on, and I saw this:

    TCP 192.168.0.2:51440 lhr08s01-in-f8:http TIME_WAIT
    TCP 192.168.0.2:51442 we-in-f139:http TIME_WAIT
    Looks very dodgy with that timer, especially the "we-in" address that has me nervous.

    Is there anyone that could shed some light on this?

  2. #2
    Junior Member
    Join Date
    Apr 2012
    Location
    Chicago suburbs
    Posts
    44
    This forum must be slow. More than 6 months, and no response.

    In any case, that "netstat" output is quite normal. You recently had http connections to the two sites. The connections were closed. It is standard procedure to put the connection into TIME_WAIT state for a while (typically 1-3 minutes, depending on the operating system).

    The intended purpose is that there might be some stray packets for the connection that were delayed. Because the system is temporarily retaining information about this connection, it can recognize those stray packets as related, and drop them (i.e. silently ignore them).

  3. #3
    A+, Security+, Mobility+ Shinobi's Avatar
    Join Date
    Jan 2001
    Location
    South Carolina
    Posts
    4,432
    Blog Entries
    1
    Quote Originally Posted by nwrickert View Post
    This forum must be slow. More than 6 months, and no response.
    Welcome to Speedguide


    I'm glad there are new members like yourself to pick up the slack. Glad your here.
    _______________________________________________
    Vendor neutral certified in IT Project Management, IT Security, Cisco Networking, Cisco Security, Wide Area Networks, IPv6, IT Hardware, Unix, Linux, and Windows server administration

  4. #4
    Junior Member
    Join Date
    Aug 2016
    Posts
    2
    SpeedGuide.net TCP Analyzer Results
    Tested on: 2016.08.04 02:55
    IP address: 141.134.xxx.xx
    Client OS/browser: Android (Chrome 51.0.2704.81)

    TCP options string: 0204058c0402080a00532a120000000001030307
    MSS: 1420
    MTU: 1460
    TCP Window: 87680 (NOT multiple of MSS)
    RWIN Scaling: 7 bits (2^7=128)
    Unscaled RWIN : 685
    Recommended RWINs: 65320, 130640, 261280, 522560, 1045120
    BDP limit (200ms): 3507kbps (438KBytes/s)
    BDP limit (500ms): 1403kbps (175KBytes/s)
    MTU Discovery: ON
    TTL: 50
    Timestamps: ON
    SACKs: ON
    IP ToS: 00000000 (0)


    I don't know what the do

  5. #5
    Junior Member
    Join Date
    Aug 2016
    Posts
    2
    SpeedGuide.net TCP Analyzer Results
    Tested on: 2016.08.04 02:55
    IP address: 141.134.xxx.xx
    Client OS/browser: Android (Chrome 51.0.2704.81)

    TCP options string: 0204058c0402080a00532a120000000001030307
    MSS: 1420
    MTU: 1460
    TCP Window: 87680 (NOT multiple of MSS)
    RWIN Scaling: 7 bits (2^7=128)
    Unscaled RWIN : 685
    Recommended RWINs: 65320, 130640, 261280, 522560, 1045120
    BDP limit (200ms): 3507kbps (438KBytes/s)
    BDP limit (500ms): 1403kbps (175KBytes/s)
    MTU Discovery: ON
    TTL: 50
    Timestamps: ON
    SACKs: ON
    IP ToS: 00000000 (0)

Similar Threads

  1. +12 and +5 Volt Dodgy
    By wazbishop in forum Hardware & Overclocking
    Replies: 1
    Last Post: 12-16-05, 06:45 PM
  2. netstat -s
    By wangnan in forum Broadband Tweaks Help
    Replies: 0
    Last Post: 08-30-02, 08:23 PM
  3. netstat
    By hubby105 in forum Network Security
    Replies: 1
    Last Post: 04-16-01, 07:36 AM
  4. Netstat
    By Prey521 in forum Network Security
    Replies: 6
    Last Post: 11-02-00, 11:35 PM
  5. Netstat questions
    By dmsmed in forum Network Security
    Replies: 1
    Last Post: 10-23-00, 07:14 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •