Re: dev Digest, Vol 217, Issue 1

[Subhra Das <subhradas () gmail com>]

Hi Jack,

Thanks for the reply!

Yes, Default is ICMP echo. But I am using the below command where I use TCP
mode. Moreover, I have the firewall set up on the source node to block ICMP
requests and replies. In this case, which user/ kernel process on the
target node, Node 2, is replying to the below nping TCP packets

*nping -c 1 --tcp -p 13567 <IP Address on Node 2>*

Thanks & Regards,
Subhra

On Thu, Aug 3, 2023 at 12:30 AM <dev-request () nmap org> wrote:

> Send dev mailing list submissions to
>         dev () nmap org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://nmap.org/mailman/listinfo/dev
> or, via email, send a message with subject or body 'help' to
>         dev-request () nmap org
>
> You can reach the person managing the list at
>         dev-owner () nmap org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of dev digest..."
>
>
> Today's Topics:
>
>    1. How Nping works at the OS/ kernel level (Subhra Das)
>    2. Re: How Nping works at the OS/ kernel level (Jack Dangler)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 2 Aug 2023 18:25:32 +0530
> From: Subhra Das <subhradas () gmail com>
> To: dev () nmap org
> Subject: How Nping works at the OS/ kernel level
> Message-ID:
>         <CAMvXMz+DKSKAW6KmCFGGSeaj8pa8Xh=
> EMGZMEviF7j3Z9FtO-w () mail gmail com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi,
>
> I carried out the below experiment. Could anyone help me to find out which
> process (at user/ kernel level) on the remote node is responding to nping
> TCP packets. Is there any flow diagram to understand the same
>
> a) On Node 1 installed nping tool
>
> b) On Node 2 removed nping tool
>
> c) Executed the *below* command on Node 1. It still works. Could you please
> let us know how should we go about finding which process is responding to
> nping tcp packets on Node 2, which doesn?t have the nping module installed
>
> *nping -c 1 --tcp -p 13567 <IP Address on Node 2>*
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://nmap.org/mailman/private/dev/attachments/20230802/28bfd1e1/attachment.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Wed, 2 Aug 2023 11:12:37 -0400
> From: Jack Dangler <tdldev () gmail com>
> To: dev () nmap org
> Subject: Re: How Nping works at the OS/ kernel level
> Message-ID: <96c6bb5f-88c1-c9b4-e108-66c33f3b3d4d () gmail com>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
>
>
> On 8/2/23 08:55, Subhra Das wrote:
> > Hi,
> >
> > I carried out the below experiment. Could anyone help me to find out
> > which process (at user/ kernel level) on the remote node is responding
> > to nping TCP packets. Is there any flow diagram to understand the same
> >
> > a) On Node 1 installed nping tool
> >
> > b) On Node 2 removed nping tool
> >
> > c) Executed the *below* command on Node 1. It still works. Could you
> > please let us know how should we go about finding which process is
> > responding to nping tcp packets on Node 2, which doesn?t have the
> > nping module installed
> >
> > *nping -c 1 --tcp -p 13567 <IP Address on Node 2>*
> >
> >
> > _______________________________________________
> > Sent through the dev mailing list
> > https://nmap.org/mailman/listinfo/dev
> > Archived athttps://seclists.org/nmap-dev/
>
> Unless I am mistaken, nping doesn't need to be installed at both ends.
> nping is issuing a ping request to the other node. When ping runs, it
> sends an ICMP "Echo" request to the interface and waits to get a
> response. Once the target receives the request, it (should) respond by
> sending a "Reply" packet.
>
>
> Jack
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> https://nmap.org/mailman/private/dev/attachments/20230802/d587dfdd/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> dev mailing list
> dev () nmap org
> https://nmap.org/mailman/listinfo/dev
>
>
> ------------------------------
>
> End of dev Digest, Vol 217, Issue 1
> ***********************************
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at https://seclists.org/nmap-dev/