Re: Reg: Clarification of my question

[Daniel Miller <bonsaiviking () gmail com>]

Akash,

Nmap already has options to choose TCP or UDP transport. These are the scan
type options: -sS, -sU, and similar. A user of Nmap doesn't want to choose
what is "best" for the network, but what is available. The target offers
services which use one of these transports, and to discover them the user
must scan the appropriate transport. In most targets, both are in use and
offering different services.

Dan

On Wed, Jan 11, 2017 at 10:04 AM, Akash Das <akash210197 () gmail com> wrote:

> Dear dario,
>
> I think you got the question wrong. I just wanted to ask that a new
> feature can also be added which will choose which connection to use TCP or
> UDP . I am not at all talking about IPv4 and IPv6 here.
> I was just suggesting that instead of specifying everytime which type of
> connection to use I just wanted to say on the basis of the network
> architecture can there be an option which chooses the best type of
> connection either UDP or TCP.
> We can introduce ML into this concept also.
> I think you got my question wrong.
>
> Thanks for replying,
>
> With Regards,
> --
>
> *Akash Das*
>
> *Student Systems admin*
>
> *Indian Institute Of Information Technology*
> *Sricity*
>
> _______________________________________________
> Sent through the dev mailing list
> https://nmap.org/mailman/listinfo/dev
> Archived at http://seclists.org/nmap-dev/
_______________________________________________
Sent through the dev mailing list
https://nmap.org/mailman/listinfo/dev
Archived at http://seclists.org/nmap-dev/