Erik Auerswald <auers...@unix-ag.uni-kl.de> writes: > Hi, > > On Sat, Jan 21, 2023 at 04:16:59PM +0000, Marco wrote: >> >> inetutils-telnet doesn't seem to implement ICMPv4 correctly. > > The telnet client does not use ICMP directly. > >> It doesn't print a proper message when ICMPv4 Type 3 Code 13 is being >> received, only "no route to destination". > > When telnet cannot connect to a remote server, it uses perror(3) to > print the error message associated with the failed connect(2) syscall. > The telnet client does not control the contents of that error message.
I agree -- although maybe there is a way for telnet to find out the low-level error reason, does someone know what APIs to use? If it is easy to call some other function to get a human readable string explaining the ICMPv4 Type 3 Code 13 reason (when that situation occured) we could print it. /Simon
signature.asc
Description: PGP signature
