IPnom Home • Manuals • FreeBSD

 FreeBSD Man Pages

Man Sections:Commands (1)System Calls (2)Library Functions (3)Device Drivers (4)File Formats (5)Miscellaneous (7)System Utilities (8)
Keyword Live Search (10 results max):
 Type in part of a command in the search box.
 
Index:
  a.out(5)
  acct(5)
  adduser.conf(5)
  aliases(5)
  amd.conf(5)
  auth.conf(5)
  big5(5)
  bluetooth.hosts(5)
  bluetooth.protocols(5)
  bootparams(5)
  bootptab(5)
  config(5)
  core(5)
  crontab(5)
  ctm(5)
  cvs(5)
  devd.conf(5)
  devfs(5)
  device.hints(5)
  dhclient.conf(5)
  dhclient.leases(5)
  dhcp-eval(5)
  dhcp-options(5)
  dir(5)
  dirent(5)
  disktab(5)
  editrc(5)
  elf(5)
  ethers(5)
  euc(5)
  eui64(5)
  exports(5)
  fbtab(5)
  fdescfs(5)
  finger.conf(5)
  forward(5)
  fs(5)
  fstab(5)
  ftpchroot(5)
  gb18030(5)
  gb2312(5)
  gbk(5)
  gettytab(5)
  groff_font(5)
  groff_out(5)
  groff_tmac(5)
  group(5)
  hcsecd.conf(5)
  hesiod.conf(5)
  hosts(5)
  hosts.equiv(5)
  hosts.lpd(5)
  hosts_access(5)
  hosts_options(5)
  inetd.conf(5)
  info(5)
  inode(5)
  intro(5)
  ipf(5)
  ipnat(5)
  ipnat.conf(5)
  ipsend(5)
  isdnd.acct(5)
  isdnd.rates(5)
  isdnd.rc(5)
  kbdmap(5)
  keycap(5)
  keymap(5)
  krb5.conf(5)
  lastlog(5)
  libarchive-formats(5)
  libmap.conf(5)
  link(5)
  linprocfs(5)
  loader.conf(5)
  login.access(5)
  login.conf(5)
  mac.conf(5)
  magic(5)
  mailer.conf(5)
  make.conf(5)
  malloc.conf(5)
  master.passwd(5)
  moduli(5)
  motd(5)
  msdos(5)
  msdosfs(5)
  mskanji(5)
  named.conf(5)
  netconfig(5)
  netgroup(5)
  netid(5)
  networks(5)
  newsyslog.conf(5)
  nologin(5)
  nsmb.conf(5)
  nsswitch.conf(5)
  ntp.conf(5)
  ntp.keys(5)
  opieaccess(5)
  opiekeys(5)
  passwd(5)
  pbm(5)
  pccard.conf(5)
  periodic.conf(5)
  pf.conf(5)
  pf.os(5)
  phones(5)
  printcap(5)
  procfs(5)
  protocols(5)
  publickey(5)
  pw.conf(5)
  quota.group(5)
  quota.user(5)
  radius.conf(5)
  rc.conf(5)
  rcsfile(5)
  remote(5)
  resolv.conf(5)
  resolver(5)
  rhosts(5)
  rndc.conf(5)
  rpc(5)
  rrenumd.conf(5)
  rtadvd.conf(5)
  services(5)
  shells(5)
  ssh_config(5)
  sshd_config(5)
  stab(5)
  style.Makefile(5)
  sysctl.conf(5)
  syslog.conf(5)
  tacplus.conf(5)
  tar(5)
  term(5)
  termcap(5)
  terminfo(5)
  texinfo(5)
  tmac(5)
  ttys(5)
  tzfile(5)
  usbd.conf(5)
  utf2(5)
  utf8(5)
  utmp(5)
  uuencode(5)
  uuencode.format(5)
  vgrindefs(5)
  wtmp(5)

pf.os(5)

NAME

     pf.os -- format of the operating system fingerprints file


DESCRIPTION

     The pf(4) firewall and the tcpdump(8) program can both fingerprint the
     operating system of hosts that originate an IPv4 TCP connection.  The
     file consists of newline-separated records, one per fingerprint, contain-
     ing 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 sys-
			tem, 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 win-
     dow 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 seg-
		ment 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 finger-
     print code will account for the volatility of the packet's TTL as it tra-
     verses 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 func-
     tion 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

     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 sev-
     enth 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 vender of the operating system.

     The version is the version of the operating system.  It is used to dis-
     tinguish 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 ver-
     sion.  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(8) output of

       # tcpdump -s128 -c1 -nv 'tcp[13] == 2'
       03:13:48.118526 10.0.0.1.3377 > 10.0.0.0.2: S [tcp sum ok] \
	   534596083:534596083(0) win 57344 <mss 1460> (DF) [tos 0x10] \
	   (ttl 64, id 11315)

     almost translates into the following fingerprint

       57344:64:1:44:M1460:  exampleOS:1.0::exampleOS 1.0

     tcpdump(8) does not explicitly give the packet length.  But it can usu-
     ally be derived by adding the size of the IPv4 header to the size of the
     TCP header to the size of the TCP options.  The size of both headers is
     typically twenty each and the usual sizes of the TCP options are:


SEE ALSO

     pf(4), pf.conf(5), pfctl(8), tcpdump(8)

FreeBSD 5.4			August 18, 2003 		   FreeBSD 5.4

SPONSORED LINKS




Man(1) output converted with man2html , sed , awk