In case you haven't noticed, ytalk (and ntalk) doesn't behave nicely when there are multiple network interfaces. The connection request packet has to contain the IP address to reply to, and ytalk guess this by looking at the hostname. This doesn't always work -- for example, if the hostname is bound to a loopback device or to, say, the ethernet device and you want to talk over ppp. The most convienant thing would be for ytalk to check how the packets get routed to the destination machine to figure out the right source address to use, but this appears to be tricky to do in a portable fashion. So, I did the simplest thing and added a new -I option (just like the -i option for traceroute) which takes a net interface name as the argument. You can also set this in the ytalkrc. This patch should be applied against the source in ytalk-3.0.3-2.src.rpm in the redhat 5.0 distribution after applying both patches included in that rpm. I haven't gotten around to doing the same to ntalk. -- Brady Montz [EMAIL PROTECTED] -- PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES! http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
