1 .\" $NetBSD: tcpdmatch.8,v 1.5 2000/10/07 23:31:18 itojun Exp $
5 tcpdmatch \- tcp wrapper oracle
7 tcpdmatch [-d] [-i inet_conf] daemon client
9 tcpdmatch [-d] [-i inet_conf] daemon[@server] [user@]client
12 \fItcpdmatch\fR predicts how the tcp wrapper would handle a specific
13 request for service. Examples are given below.
15 The program examines the \fItcpd\fR access control tables (default
16 \fI/etc/hosts.allow\fR and \fI/etc/hosts.deny\fR) and prints its
17 conclusion. For maximal accuracy, it extracts additional information
18 from your \fIinetd\fR or \fItlid\fR network configuration file.
20 When \fItcpdmatch\fR finds a match in the access control tables, it
21 identifies the matched rule. In addition, it displays the optional
22 shell commands or options in a pretty-printed format; this makes it
23 easier for you to spot any discrepancies between what you want and what
24 the program understands.
26 The following two arguments are always required:
28 A daemon process name. Typically, the last component of a daemon
31 A host name or network address, or one of the `unknown' or `paranoid'
34 When a client host name is specified, \fItcpdmatch\fR gives a
35 prediction for each address listed for that client.
37 When a client address is specified, \fItcpdmatch\fR predicts what
38 \fItcpd\fR would do when client name lookup fails.
40 Optional information specified with the \fIdaemon@server\fR form:
42 A host name or network address, or one of the `unknown' or `paranoid'
43 wildcard patterns. The default server name is `unknown'.
45 Optional information specified with the \fIuser@client\fR form:
47 A client user identifier. Typically, a login name or a numeric userid.
48 The default user name is `unknown'.
51 Examine \fIhosts.allow\fR and \fIhosts.deny\fR files in the current
52 directory instead of the default ones.
54 Specify this option when \fItcpdmatch\fR is unable to find your
55 \fIinetd.conf\fR or \fItlid.conf\fR network configuration file, or when
56 you suspect that the program uses the wrong one.
58 To predict how \fItcpd\fR would handle a telnet request from the local
62 tcpdmatch in.telnetd localhost
64 The same request, pretending that hostname lookup failed:
67 tcpdmatch in.telnetd 127.0.0.1
69 To predict what tcpd would do when the client name does not match the
73 tcpdmatch in.telnetd paranoid
75 On some systems, daemon names have no `in.' prefix, or \fItcpdmatch\fR
76 may need some help to locate the inetd configuration file.
79 The default locations of the \fItcpd\fR access control tables are:
87 tcpdchk(8), tcpd configuration checker
88 hosts_access(5), format of the tcpd access control tables.
89 hosts_options(5), format of the language extensions.
90 inetd.conf(5), format of the inetd control file.
91 .\" tlid.conf(5), format of the tlid control file.
95 Wietse Venema (wietse@wzv.win.tue.nl),
96 Department of Mathematics and Computing Science,
97 Eindhoven University of Technology
98 Den Dolech 2, P.O. Box 513,
99 5600 MB Eindhoven, The Netherlands
100 \" @(#) tcpdmatch.8 1.5 96/02/11 17:01:35
102 If you specify FQDN hostname as client,
103 they will be recognized only as IPv4 or IPv6 address,
104 which should be recognized as both.