Sorry for the delay, but this sounds like expected behavior. Ncat is generally using the socket API rather than raw packets and so the host receives the ICMP response and translates that into a more generic error code that Ncat sees. You can use our Nping tool if you need raw packet sending and sniffing instead.
-Gordon On Sat, Jan 21, 2023 at 8:30 AM Marco Moock <m...@posteo.de> wrote: > Package: ncat > Version: 7.93+dfsg1-1 > Severity: minor > Tags: upstream > X-Debbugs-Cc: m...@posteo.de > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate > *** > > * What led up to the situation? > ncat <IPv4 addr> <port> and reply is ICMPv4 Type 3 Code 13, wrong error > message > "Ncat: No route to host.". > * What outcome did you expect instead? > Correct message, like "Connection to <IPv4 addr> <Port> administratively > prohibited". > https://datatracker.ietf.org/doc/html/rfc1812#section-5.2.7.1 > > *** End of the template - remove these template lines *** > > > -- System Information: > Debian Release: bookworm/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 6.1.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE > not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > > Versions of packages ncat depends on: > ii libc6 2.36-8 > ii liblua5.3-0 5.3.6-2 > ii libpcap0.8 1.10.3-1 > ii libssl3 3.0.7-1 > > ncat recommends no packages. > > ncat suggests no packages. > > -- no debconf information > >
