[wplug] talk and xinetd?
Poyner, Brandon
bpoyner at ccac.edu
Wed Aug 4 09:01:39 EDT 2004
I believe the Linux talk client prefers to use ntalk. You should have
an ntalk file in xinetd.d, enable that one as well.
# chkconfig --list talk
talk on
# chkconfig --list ntalk
ntalk on
# netstat -a | grep talk
udp 0 0 *:talk *:*
udp 0 0 *:ntalk *:*
udp 0 0 localhost.localdo:32867 localhost.localdo:ntalk
ESTABLISHED
udp 0 0 localhost:32868 localhost:ntalk
ESTABLISHED
Brandon Poyner
Network Engineer II
CCAC - College Office
412-237-3086
-----Original Message-----
From: Brandon Kuczenski [mailto:brandon at 301south.net]
Sent: Tuesday, August 03, 2004 6:05 PM
To: WPLUG
Subject: [wplug] talk and xinetd?
I thought this would be simple, but it seems complex. I am trying to
get
talk to work on my server running Redhat 9 with xinetd. I modified the
'talk' file in the /etc/xinetd.d directory to include "disable = no" and
restarted xinetd. 'talk' now shows up in chkconfig:
$ chkconfig --list talk
talk on
$
.. and in netstat:
$ netstat -a | grep talk
udp 0 0 *:talk *:*
udp 0 0 *:talk *:*
udp 0 0 *:talk *:*
$
... yes, three times (is THAT a problem?)
But when I say 'talk user' where "user" is an online person other than
me,
the talk window tells me, "Error reading from talk daemon: connection
refused".
I put a line in my iptables firewall (the very first line in the INPUT
chain) which LOGs any udp packets on port 'talk', and it's not showing
anything. Is there somewhere upstream of the firewall that this could
be
getting stopped? The user is logged in on the same machine, so it
shoudl
be going through the loopback interface (right?) which I have wide open.
I'm just a little puzzled. Any ideas?
-Brandon
_______________________________________________
wplug mailing list
wplug at wplug.org
http://www.wplug.org/mailman/listinfo/wplug
More information about the wplug
mailing list