Man page or keyword search:   man All Sections 1 - General Commands 2 - System Calls 3 - Subroutines, Functions 4 - Special Files 5 - File Formats 6 - Games and Screensavers 7 - Macros and Conventions 8 - Maintenence Commands 9 - Kernel Interface New Commands Server 4.4BSD AIX Alpinelinux Archlinux Aros BSDOS BSDi Bifrost CentOS Cygwin Darwin Debian DigitalUNIX DragonFly ElementaryOS Fedora FreeBSD Gentoo GhostBSD HP-UX Haiku Hurd IRIX Inferno JazzOS Kali Knoppix LinuxMint MacOSX Mageia Mandriva Manjaro Minix MirBSD NeXTSTEP NetBSD OPENSTEP OSF1 OpenBSD OpenDarwin OpenIndiana OpenMandriva OpenServer OpenSuSE OpenVMS Oracle PC-BSD Peanut Pidora Plan9 QNX Raspbian RedHat Scientific Slackware SmartOS Solaris SuSE SunOS Syllable Tru64 UNIXv7 Ubuntu Ultrix UnixWare Xenix YellowDog aLinux   44335 pages apropos Keyword Search (all sections) Output format html ascii pdf view pdf save postscript

OWTAP(1)		     One-Wire File System		      OWTAP(1)

NAME
       owtap - Packet sniffer for the owserver protocol

SYNOPSIS
       owtap -p owtap-tcp-port -s owserver-tcp-port

DESCRIPTION
   owserver
       owserver	 (1)  is  the backend component of the OWFS 1-wire bus control
       system.	owserver (1) arbitrates access to the bus from multiple client
       processes.  The	physical  bus  is usually connected to a serial or USB
       port, and other processes connect to owserver (1) over network  sockets
       (tcp port).

       Frontend	 clients include a filesystem representation: owfs (1) , and a
       webserver: owhttpd (1).	Direct language bindings are  also  available,
       e.g: owperl (3).

       There are also many light-weight clients that can only talk to owserver
       (1) and not to the 1-Wire bus directly. They include shell and multiple
       language modules (perl, Visual Basic, python,...)

   owserver protocol
       All  the	 owserver (1) clients use the owserver protocol for communica‐
       tion. The owserver protocol is a well documented	 tcp/ip	 client/server
       protocol. Assigned the "well known port" default of 4304.

   owtap
       owtap  (1)  is  interposed between owserver (1) and clients, to display
       and help resolve communication problems. Network communication is  for‐
       warded  in  both directions, but a visual display is also created, with
       statistics and "drill-down" of individual packets.

SPECIFIC OPTIONS
   -p
       TCP port or IPaddress:port for owtap
       Other OWFS programs will access owtap via this address. (e.g. owdir  -s
       IP:port /)

   -s
       TCP port or IPaddress:port for owserver
       The tcp port (IP:port) for the "upstream" owserver.

EXAMPLE
       If owserver (1) is started:
       owserver -p 4304 -d /dev/ttyS0
       owserver	 on  tcp  port 4304 and connects to a physical 1-wire bus on a
       serial port.

       You can directly query owserver (1) with
       owdir -s 4304 /

       To see the protocol in action:
       owtap -s 4304 -p 3000
       owdir -p 3000 /

       In this case owtap (1) is connecting to owserver (1)  on	 the  original
       port (4304) and offering a new port (3000) for clients.

PLATFOMS
       owtap  (1)  is  a  pure Tcl/TK program and will run whereever Tcl/TK is
       available (Windows, Macintosh, Linux, Unix)

LINKS
   owserver protocol
       http://www.owfs.org/index.php?page=owserver-protocol

   Tcl/TK
       http://www.tcl.tk

SEE ALSO
AVAILABILITY
       http://www.owfs.org

AUTHOR
       Paul Alfille (paul.alfille@gmail.com)

OWTAP Manpage			     2007			      OWTAP(1)

Vote for polarhome