owtap − Packet sniffer for the owserver protocol
owtap −p owtap-tcp-port −s owserver-tcp-port
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,...)
All the 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 (1) is interposed between 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.
TCP port or
IPaddress:port for owtap
Other OWFS programs will access owtap via this address.
(e.g. owdir −s IP:port /)
TCP port or
IPaddress:port for owserver
The tcp port (IP:port) for the "upstream"
owserver.
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.
owtap (1) is a pure Tcl/TK program and will run wherever Tcl/TK is available (Windows, Macintosh, Linux, Unix)
http://www.owfs.org/index.php?page=owserver-protocol
http://www.tcl.tk
http://www.owfs.org
Paul Alfille ([email protected])