[5391] in SIPB bug reports
ytalk and icmp port unreachables
daemon@ATHENA.MIT.EDU (John Hawkinson)
Mon May 15 16:11:59 1995
Date: Mon, 15 May 1995 16:05:29 -0400
To: bug-sipb@MIT.EDU
From: John Hawkinson <jhawk@MIT.EDU>
Ytalk fails to notice ICMP port unreachables
from the machine you attempt to open a talk
connection on, meaning it just sits and hangs, when
it should tell you that the other end isn't running
a talkd.
You can see this (on a sun) by ping -sdv'ing the other
side:
[portnoy!jhawk] ~> /usr/sbin/ping -sdv titan.sprintlink.net
PING titan.sprintlink.net: 56 data bytes
64 bytes from titan.sprintlink.net (199.0.55.78): icmp_seq=0. time=32. ms
64 bytes from titan.sprintlink.net (199.0.55.78): icmp_seq=1. time=25. ms
64 bytes from titan.sprintlink.net (199.0.55.78): icmp_seq=2. time=24. ms
64 bytes from titan.sprintlink.net (199.0.55.78): icmp_seq=3. time=26. ms
64 bytes from titan.sprintlink.net (199.0.55.78): icmp_seq=4. time=28. ms
64 bytes from titan.sprintlink.net (199.0.55.78): icmp_seq=5. time=40. ms
64 bytes from titan.sprintlink.net (199.0.55.78): icmp_seq=6. time=28. ms
64 bytes from titan.sprintlink.net (199.0.55.78): icmp_seq=7. time=31. ms
ICMP Port Unreachable from gateway titan.sprintlink.net (199.0.55.78)
for udp from portnoy (18.70.0.218) to titan.sprintlink.net (199.0.55.78) port 518
This ought to be fixed, perhaps by connect()-ing the socket.
--jhawk
