ytalk

wizy · Tux's lil' helper Joined: 26 May 2002 Posts: 133

I want to get ytalk up and going. I merged in ytalk and netkit-talk.

I know I need to do something with in.talkd to get a talk daemon up before ytalk will work. Anyone want to tell me what to do?

wizy · Tux's lil' helper Joined: 26 May 2002 Posts: 133

Guess im on my own with this one? Seems no one has tried or wants to. Oh well.

Ondrej · n00b Joined: 28 Apr 2002 Posts: 15

I'm trying to set it up as well. I was going to have xinetd run the talk deamon when a connection was established. The xinetd.d file I made looked something like this:

yold · n00b Joined: 02 Jul 2002 Posts: 1

i am having the same pb

ela

I hate to say this, but I've got the same problem, too... Just to keep this thread "alive"...

Ela.

fmalabre · Guru Joined: 19 Jun 2002 Posts: 376 Location: Chicago

Me too I have this issue...
I would like to know how I could fix that...
Please help...

meyerm · Posted: Sat Sep 07, 2002 11:17 am Post subject:

Hi,

did anybody finally achieved in getting a talkd to run?

Thanks

ela · Posted: Sat Sep 07, 2002 12:15 pm Post subject: No Succes...

Not me.

_________________
Jabber: ela_AT_jabber_DOT_org

fmalabre · Guru Joined: 19 Jun 2002 Posts: 376 Location: Chicago

GotTLoS · n00b Joined: 15 Sep 2002 Posts: 35

hi

this is not the same as use the talkd but i' m able to use talk command use as demon kotalkd started with xinetd. hope it helps.
hasta

Uranus · Posted: Sun Sep 22, 2002 10:37 pm Post subject:

whenever I try to start ktalkd I get:

Naan Yaar · Bodhisattva Joined: 27 Jun 2002 Posts: 1549

This error occurs if a server that is meant to start from inetd is started outside of it (e.g., from a console). You may need to emerge xinetd, e.g., and set it up to start talkd.

GotTLoS · n00b Joined: 15 Sep 2002 Posts: 35

My /etc/xinetd.d/talk file looks like this:

yottabit · Posted: Mon Nov 18, 2002 11:06 pm Post subject:

I hate to reopen a can of worms here, but it doesn't seem like we have any resolution.

I have merged xinetd, netkit-base, and netkit-talk. I know xinetd is working properly since I have uw-pop3d running successfully. I created /etc/xinetd.d/talk:

nrosier · n00b Joined: 06 Jul 2002 Posts: 43 Location: Belgium

create a file /etc/inetd.conf with this line:

talk dgram udp wait root /usr/sbin/talkd talkd

and launch /usr/sbin/inetd

Uranus · Posted: Tue Dec 17, 2002 4:44 pm Post subject:

wooooooooooot that worked

yottabit · Posted: Wed Dec 18, 2002 8:40 pm Post subject:

yottabit · Posted: Fri Dec 20, 2002 12:47 am Post subject:

Hi Folks,

I finally figured out my problem. Not 100% sure how/why this is happening, but talk/ytalk is resolving my computer's hostname to my external FQDN instead of using the local hostname or address, and therefore the request packets get sent to my router, which then firewalls them from coming into the network (it's too stupid to realize the packets came from the internal port, not the external port).

Just to explain more clearly, here's my setup:

hostname: hal
FQDN: hal.jacobmcdonald.net
Internal IP: 192.168.0.10

I'm using NAT on my router... and I'm using dynamic DNS for my domain name. So therefore, the proper FQDN for my external IP address (and domain), at the moment, is rrcs-central-24-123-148-131.biz.rr.com.

For some reason, talk/ytalk acquires the EXTERNAL (rr.com) IP address instead of using the internally defined IP address. So it tries to contact that FQDN, which routes the packets to the router of course, and then the router firewall drops the packet since I don't allow the talk port inbound.

So I had two solutions:

1. Simply open the talk port on the firewall. This is fine for some, but I really didn't want to do that in the interest of security (plaintext you know).

2. Define a global alias for the talk command to use, which will automagically fill in "localhost" for the server name instead of letting the client figure it out by itself. This is accomplished by sticking

thequbemaster · n00b Joined: 03 Jun 2003 Posts: 4

i was able to get talk working with inetd but i really wanted to get it working with xinetd. yottabit's instructions were very helpful, but i was still having some trouble. having searched google i finally got talk working and have one thing to add to yottabit's guide:

slartibartfasz · Posted: Mon Jul 14, 2003 1:08 pm Post subject:

is it possible to run a talkd without inetd?
_________________
To an engineer the glass is neither half full, nor half empty - it is just twice as big as it needs to be.

ProtectR · n00b Joined: 22 Nov 2002 Posts: 3

Ok, had the same problem, now it works

I think I figured out how it works. I don't have a lot of knowledge about how communications work under linux, but here's what I found:

IMPORTANT: The next lines suppose interface eth0 has 192.168.1.1 assigned to, and the hostname is 'einstein'

I found in my logs that if I try to talk to a user using

meyerm · Posted: Mon Oct 27, 2003 9:10 am Post subject:

Hi,

I won't test it now, but I just wanted to say thank you. I really appreciate people who also try to answer quite old articles :-)

Marcel

zrajm · Posted: Wed Jun 30, 2004 10:09 am Post subject:

Ytalk worked right out of the box for me.

However when I'm running X and somebody tries to ytalk/talk me I get a notification message in a (more or less) random (x)terminal -- which very seldom the terminal I'm actually using at the moment...

Is there a way to set up some other means of notification. E.g. running a script which beeps, plays a sample pops up a requester, or uses xosd to alert me to the fact that someone wishes to ytalk to me?

That would make ytalk sooo much more usable (to me).
_________________
ta' Hol DajatlhlaH'a' je?

seank · l33t Joined: 08 Jul 2004 Posts: 686

In my /etc/hosts files my "localhost" entry was as follows:

Truckle · n00b Joined: 16 Oct 2003 Posts: 5

Hi,

To get talkd working, just add the line

disable = no

to /etc/xinitd.d/talk, and restart xinitd

Cheers,

Truckle.