08-30-2001
You can put IP addresses in the hosts.deny/allow. Same format as you would use for hostnames. tcpd will try to do a reverse lookup on any IP that connects. Ensure that your dns is functioning properly.
9 More Discussions You Might Find Interesting
1. IP Networking
/* Linux Slackware */
looking in my logs I see tons of entries similar to below. Does anyone know what these mean, and should I be concerned. I looked up a few of the IP's at Arin.net and saw that many of them belong to isp's (not good).. Any information is helpful..
Body of Messages log... (1 Reply)
Discussion started by: LowOrderBit
1 Replies
2. UNIX for Dummies Questions & Answers
I want to be able to get telnetd to start a program of my choice or one that I have written . . . or . . . write a daemon of my own to listen on a port other than 23 and when a connection arrives it should create a controlling tty/pty and then launch my program on the client side of the pty.
A... (2 Replies)
Discussion started by: pdenaro
2 Replies
3. UNIX for Dummies Questions & Answers
Hi
I'm using linux slackware 8.0 with the 2.2.19 kernel
I have some problems..
First problem:
I cannot get kernel 2.4.* to work.. it hangs when I boot and displays someting like: configuring 100mbps tbase 100x full duplex
what can cause this? and what can I do about it?
Second... (4 Replies)
Discussion started by: Maestin
4 Replies
4. UNIX for Dummies Questions & Answers
I hope someone can enlighten me on this. A few weeks ago, the root file system my UnixWare 7.1.1 server became corrupt so I ended up doing a full restore of the OS from tape backup.
Since then, after I get about 270 users on the system, the message "telnetd: all network ports in use" is... (1 Reply)
Discussion started by: davekox
1 Replies
5. Cybersecurity
Hi folks. I have a quick question on using "telnetd" vs. "telnetd -a".
OS: AIX 5.x (5.1 through 5.3 ML3)
Some engineers at work want to stop using "telnetd -a" and use "telnetd".
(and of course, if I could get a cogent answer from them, I wouldn't be posting this question...) :mad:
The... (0 Replies)
Discussion started by: davidl9999
0 Replies
6. Solaris
hi mates,
a very important info for all solaris admins, there is a bug in telnetd on nearly every solaris version:
pressy@mp-wst01 # id
uid=100(pressy) gid=1(other)
pressy@mp-wst01 # telnet -l "-froot" 192.168.40.1
Trying 192.168.40.1...
Connected to 192.168.40.1.
Escape character is... (3 Replies)
Discussion started by: pressy
3 Replies
7. Solaris
Hello all,
I've got a problem on a V240 running Solaris 9, the telnet daemon won't start. The error message I get is "telnetd: stdin is not a socket file descriptor." I've never seen this message before and I'm not exactly sure what it means. I know generally what stdin, sockets, and file... (4 Replies)
Discussion started by: ONEX
4 Replies
8. SCO
Ok, here i am in 2008 trying to figure out how to edit the port of Telnetd in sco openserver 4.2.
I googled my butt off and cant seem to find any info. Does anyone have some specific howto's or good documentation on this? (2 Replies)
Discussion started by: j0ntar
2 Replies
9. AIX
Hi,
When a client connected to AIX server by telnet is killed/crashes, is there a way for telnetd to recognize that and close/kill the application linked/started by that telnet session?
We have a situation where clients disconnect because of frequent network outages, this leaves the... (2 Replies)
Discussion started by: mreyaz
2 Replies
TCPDMATCH(8) System Manager's Manual TCPDMATCH(8)
NAME
tcpdmatch - tcp wrapper oracle
SYNOPSIS
tcpdmatch [-d] [-i inet_conf] daemon client
tcpdmatch [-d] [-i inet_conf] daemon[@server] [user@]client
DESCRIPTION
tcpdmatch predicts how the tcp wrapper would handle a specific request for service. Examples are given below.
The program examines the tcpd access control tables (default /etc/hosts.allow and /etc/hosts.deny) and prints its conclusion. For maximal
accuracy, it extracts additional information from your inetd network configuration file.
When tcpdmatch finds a match in the access control tables, it identifies the matched rule. In addition, it displays the optional shell com-
mands or options in a pretty-printed format; this makes it easier for you to spot any discrepancies between what you want and what the pro-
gram understands.
ARGUMENTS
The following two arguments are always required:
daemon A daemon process name. Typically, the last component of a daemon executable pathname.
client A host name or network address, or one of the `unknown' or `paranoid' wildcard patterns.
When a client host name is specified, tcpdmatch gives a prediction for each address listed for that client.
When a client address is specified, tcpdmatch predicts what tcpd would do when client name lookup fails.
Optional information specified with the daemon@server form:
server A host name or network address, or one of the `unknown' or `paranoid' wildcard patterns. The default server name is `unknown'.
Optional information specified with the user@client form:
user A client user identifier. Typically, a login name or a numeric userid. The default user name is `unknown'.
OPTIONS
-d Examine hosts.allow and hosts.deny files in the current directory instead of the default ones.
-i inet_conf
Specify this option when tcpdmatch is unable to find your inetd.conf network configuration file, or when you suspect that the pro-
gram uses the wrong one.
EXAMPLES
To predict how tcpd would handle a telnet request from the local system:
tcpdmatch in.telnetd localhost
The same request, pretending that hostname lookup failed:
tcpdmatch in.telnetd 127.0.0.1
To predict what tcpd would do when the client name does not match the client address:
tcpdmatch in.telnetd paranoid
On some systems, daemon names have no `in.' prefix, or tcpdmatch may need some help to locate the inetd configuration file.
FILES
The default locations of the tcpd access control tables are:
/etc/hosts.allow
/etc/hosts.deny
SEE ALSO
tcpdchk(8), tcpd configuration checker
hosts_access(5), format of the tcpd access control tables.
hosts_options(5), format of the language extensions.
inetd.conf(5), format of the inetd control file.
AUTHORS
Wietse Venema (wietse@wzv.win.tue.nl),
Department of Mathematics and Computing Science,
Eindhoven University of Technology
Den Dolech 2, P.O. Box 513,
5600 MB Eindhoven, The Netherlands
TCPDMATCH(8)