Sponsored Content
Full Discussion: TCP/IP troubleshooting
Special Forums IP Networking TCP/IP troubleshooting Post 302671851 by bakunin on Saturday 14th of July 2012 07:08:45 PM
Old 07-14-2012
There is a fantastic book about TCP/IP, which really covers everything up to a reference implementation of a TCP/IP-stack:

W. Richard Stevens: TCP/IP Illustrated (3 volumes)

I can wholeheartedly recommend this book.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Networking troubleshooting

How can i tell how long my network cards have been connected to the network for. (1 Reply)
Discussion started by: manwithaphone
1 Replies

2. Shell Programming and Scripting

Troubleshooting Script

I am fairly new to Unix (Sun OS) scripting with Ksh, and I could use a little help troubleshooting my script. When I run it, I get the error "if unexpected" on the function setYear. If I comment out the setYear function, I get the error "for unexpected" on the function sendEmails. This leads me... (8 Replies)
Discussion started by: mharley
8 Replies

3. UNIX for Dummies Questions & Answers

tftp troubleshooting

Hi I am trying to do a network install of Solaris 10 08_07 onto a Sunfire T2000. I have configured all my network-boot-arguments on the client server (named sundb1). I have installed my image of Solaris on my install server (sun1). But when I try to install using # boot net -s I get the... (0 Replies)
Discussion started by: Bobby76
0 Replies

4. Solaris

help troubleshooting

Hi. I have a Solaris 10 server that's taking about 20secs to respond to telnet or ftp commands. Has anyone ever seen something like that? Can you tell me where to start troubleshooting please? I logged in and did a prtstat, but nothing is jumping out as an issue. (8 Replies)
Discussion started by: bbbngowc
8 Replies

5. AIX

AIX troubleshooting

Hi guys, Is there a command in AIX similar to ps, but shows memory usage by application? I'm trying to track down a rogue application that's using up all 32GB of the available systems memory and causing the the system to page to disk. (4 Replies)
Discussion started by: bbbngowc
4 Replies

6. Ubuntu

Help with troubleshooting crontab

Hello all, When I configured cron jobs that execute bash scripts a while back on my box they worked and the other day I tried to enable cron jobs that execute a bash script to run with no success. cron text file: test.sh file The script has execution rights (e.g. if I use bash... (2 Replies)
Discussion started by: LAVco
2 Replies

7. AIX

How to Troubleshooting IO in AIX 6.xx

I am running Oracle databases and recently have been facing slow IO response. I know in 11g one can run calibrate_IO from within DB and it would have given me some data for IO, but DB is 10g. Is there any tool available which can give me max MBPS, max IO requests per second system can handle and... (1 Reply)
Discussion started by: clifford
1 Replies

8. Solaris

prtdiag -v troubleshooting

selected lines from the output of the "prtdiag -v" command on a T5240 SUN server running Solaris 10. Are the following known as FRU names and what do they mean? MB/CMP0/BR0/CH0/D0 MB/CMP0/BR0/CH1/D0 SYS/FANBD0/FM0/F0 SYS/FANBD0/FM0/F1 SYS/MB/CMP0/BR1/CH0/D1 ... (1 Reply)
Discussion started by: snoman1
1 Replies

9. Solaris

Too much TCP retransmitted and TCP duplicate on server Oracle Solaris 10

I have problem with oracle solaris 10 running on oracle sparc T4-2 server. Os information: 5.10 Generic_150400-03 sun4v sparc sun4v Output from tcpstat.d script TCP bytes: out outRetrans in inDup inUnorder 6833763 7300 98884 0... (2 Replies)
Discussion started by: insatiable1610
2 Replies

10. Shell Programming and Scripting

Troubleshooting whiptail

Here is a code snippet using whiptail , it fails to complete giving me long list of options available for whiptail . That is great, but how do I determine which of the current opinions is wrong? I did tried inserting comment (#) into options and it just did not work. Deleting the option... (9 Replies)
Discussion started by: annacreek
9 Replies
PF.OS(5)						      BSD File Formats Manual							  PF.OS(5)

NAME
pf.os -- format of the operating system fingerprints file DESCRIPTION
The packet filter firewall and the tcpdump(1) program can both fingerprint the operating system of hosts that originate an IPv4 TCP connec- tion. The file consists of newline-separated records, one per fingerprint, containing nine colon (':') separated fields. These fields are as follows: window The TCP window size. TTL The IP time to live. df The presence of the IPv4 don't fragment bit. packet size The size of the initial TCP packet. TCP options An ordered list of the TCP options. class The class of operating system. version The version of the operating system. subtype The subtype of patchlevel of the operating system. description The overall textual description of the operating system, version and subtype. The window field corresponds to the th->th_win field in the TCP header and is the source host's advertised TCP window size. It may be between zero and 65,535 inclusive. The window size may be given as a multiple of a constant by prepending the size with a percent sign '%' and the value will be used as a modulus. Three special values may be used for the window size: * An asterisk will wildcard the value so any window size will match. S Allow any window size which is a multiple of the maximum segment size (MSS). T Allow any window size which is a multiple of the maximum transmission unit (MTU). The ttl value is the initial time to live in the IP header. The fingerprint code will account for the volatility of the packet's TTL as it traverses a network. The df bit corresponds to the Don't Fragment bit in an IPv4 header. It tells intermediate routers not to fragment the packet and is used for path MTU discovery. It may be either a zero or a one. The packet size is the literal size of the full IP packet and is a function of all of the IP and TCP options. The TCP options field is an ordered list of the individual TCP options that appear in the SYN packet. Each option is described by a single character separated by a comma and certain ones may include a value. The options are: Mnnn maximum segment size (MSS) option. The value is the maximum packet size of the network link which may include the '%' modulus or match all MSSes with the '*' value. N the NOP option (NO Operation). T[0] the timestamp option. Certain operating systems always start with a zero timestamp in which case a zero value is added to the option; otherwise no value is appended. S the Selective ACKnowledgement OK (SACKOK) option. Wnnn window scaling option. The value is the size of the window scaling which may include the '%' modulus or match all window scalings with the '*' value. No TCP options in the fingerprint may be given with a single dot '.'. An example of OpenBSD's TCP options are: M*,N,N,S,N,W0,N,N,T The first option M* is the MSS option and will match all values. The second and third options N will match two NOPs. The fourth option S will match the SACKOK option. The fifth N will match another NOP. The sixth W0 will match a window scaling option with a zero scaling size. The seventh and eighth N options will match two NOPs. And the ninth and final option T will match the timestamp option with any time value. The TCP options in a fingerprint will only match packets with the exact same TCP options in the same order. The class field is the class, genre or vendor of the operating system. The version is the version of the operating system. It is used to distinguish between different fingerprints of operating systems of the same class but different versions. The subtype is the subtype or patch level of the operating system version. It is used to distinguish between different fingerprints of oper- ating systems of the same class and same version but slightly different patches or tweaking. The description is a general description of the operating system, its version, patchlevel and any further useful details. EXAMPLES
The fingerprint of a plain OpenBSD 3.3 host is: 16384:64:1:64:M*,N,N,S,N,W0,N,N,T:OpenBSD:3.3::OpenBSD 3.3 The fingerprint of an OpenBSD 3.3 host behind a PF scrubbing firewall with a no-df rule would be: 16384:64:0:64:M*,N,N,S,N,W0,N,N,T:OpenBSD:3.3:!df:OpenBSD 3.3 scrub no-df An absolutely braindead embedded operating system fingerprint could be: 65535:255:0:40:.:DUMMY:1.1:p3:Dummy embedded OS v1.1p3 The tcpdump(1) output of # tcpdump -s128 -c1 -nv 'tcp[13] == 2' 03:13:48.118526 10.0.0.1.3377 > 10.0.0.2.80: S [tcp sum ok] 534596083:534596083(0) win 57344 <mss 1460> (DF) [tos 0x10] (ttl 64, id 11315, len 44) almost translates into the following fingerprint 57344:64:1:44:M1460: exampleOS:1.0::exampleOS 1.0 SEE ALSO
pf.conf(5), pfctl(8), tcpdump(1) BSD
May 31, 2007 BSD
All times are GMT -4. The time now is 06:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy