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

# [NAME](#NAME)

**owtap** - Packet sniffer for the owserver protocol

# [SYNOPSIS](#SYNOPSIS)

**owtap** *-p* owtap-tcp-port *-s* owserver-tcp-port

# [DESCRIPTION](#DESCRIPTION)

See the file man1/description.1so.

## [owserver](#owserver)

[**owserver (1)**](/man/os/owfs/owserver.1) is the backend component of the OWFS 1-wire bus control system. [**owserver (1)**](/man/os/owfs/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)**](/man/os/owfs/owserver.1) over network sockets (tcp port).

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

There are also many light-weight clients that can only talk to [**owserver (1)**](/man/os/owfs/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)**](/man/os/owfs/owserver.1) clients use the **owserver protocol** for communication. The **owserver protocol** is a well documented tcp/ip client/server protocol. Assigned the "well known port" default of 4304.

## [owtap](#owtap)

[**owtap (1)**](/man/os/owfs/owtap.1) is interposed between [**owserver (1)**](/man/os/owfs/owserver.1) and clients, to display and help resolve communication problems. Network communication is forwarded in both directions, but a visual display is also created, with statistics and "drill-down" of individual packets.

# [SPECIFIC OPTIONS](#SPECIFIC_OPTIONS)

## [-p](#p)

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

## [-s](#s)

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

# [EXAMPLE](#EXAMPLE)

If [**owserver (1)**](/man/os/owfs/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)**](/man/os/owfs/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)**](/man/os/owfs/owtap.1) is connecting to [**owserver (1)**](/man/os/owfs/owserver.1) on the original port (4304) and offering a new port (3000) for clients.

# [PLATFOMS](#PLATFOMS)

[**owtap (1)**](/man/os/owfs/owtap.1) is a pure *Tcl/TK* program and will run wherever *Tcl/TK* is available (Windows, Macintosh, Linux, Unix)

# [LINKS](#LINKS)

## owserver protocol

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

## [Tcl/TK](#Tcl/TK)

http://www.tcl.tk

# [SEE ALSO](#SEE_ALSO)

See the file man1/seealso.1so.

# [AVAILABILITY](#AVAILABILITY)

http://www.owfs.org

# [AUTHOR](#AUTHOR)

Paul Alfille (paul.alfille@gmail.com)

2007 OWTAP Manpage

---

Document: owtap(1) from owfs 3.2.4-r9 (Chainguard OS)
Source: https://github.com/owfs/owfs