Date: Fri, 10 May 2002 08:46:53 -0700 From: Nathan Kinkade <nkinkade@dsl-only.com> To: Sam Drinkard <sam@wa4phy.net> Cc: security@freebsd.org Subject: Re: Second request Talk ports/sockets Message-ID: <20020510084653.51d1ba8e.nkinkade@dsl-only.com> In-Reply-To: <3CDBCDFC.75062339@vortex.wa4phy.net> References: <3CDBCDFC.75062339@vortex.wa4phy.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 10 May 2002 09:41:16 -0400 Sam Drinkard <sam@wa4phy.net> wrote: > Since tightening up the firewall, my talk (from internal, not network) > is broken. I can't seem to figure out what ucp/tcp port(s) to open to > allow the talk utility to work. Looking at the source code didn't > help much either, but reference to sockets was mentioned. Once a user > logs in, does the talk utility not use the localhost address for > connections? The port for talk is 517. The port for ntalk is 518. I first found this out by launching ethereal (a network protocol analyzer that's in the ports collection). Then I attempted to launch a talk session with a non-existent host just to see some traffic. A quick review of the captured packets showed that my machine was attempting to communicate using ntalk on UDP port 518. I then did a quick search on Google for 'ntalk tcp port number'. The very first returned hit revealed the following. talk 517/tcp like tenex link, but across # machine - unfortunately, doesn't # use link protocol (this is actually # just a rendezvous port from which a # tcp connection is established) talk 517/udp like tenex link, but across # machine - unfortunately, doesn't # use link protocol (this is actually # just a rendezvous port from which a # tcp connection is established) ntalk 518/tcp ntalk 518/udp Further, a quick browse through /etc/services revealed exactly the same text as above. Presumably that's where the site got the information in the first place. There are plenty of ways to figure out information like this....it just requires that you think about it for a minute. The Google search engine is invaluable...and then again, as demonstrated above, often the info lies right on your own computer. Hope this helps. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020510084653.51d1ba8e.nkinkade>