Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mixing UDP and TCP ports #35

Closed
cweb opened this issue Nov 5, 2013 · 3 comments
Closed

Mixing UDP and TCP ports #35

cweb opened this issue Nov 5, 2013 · 3 comments

Comments

@cweb
Copy link

cweb commented Nov 5, 2013

On Windows, setting a flag like:

-p T:22,53,139,445,U:53,137,161

I'm only seeing results for UDP port 53 but expecting results for UDP 137 and 161. However in the following I get results for UDP 53, 137, and 161 as expected:

-p T:22,53,139,445,U:53,U:137,U:161

@robertdavidgraham
Copy link
Owner

Is that how nmap does it? I've tried to replicate the syntax, but I don't know all the exact details. I'll change it to make this work.


On Tue, 11/5/13, Chris Weber notifications@github.com wrote:

Subject: [masscan] Mixing UDP and TCP ports (#35)
To: "robertdavidgraham/masscan" masscan@noreply.github.com
Date: Tuesday, November 5, 2013, 12:53 PM

On Windows, setting a flag like:

-p T:22,53,139,445,U:53,137,161

I'm only seeing results for UDP port 53 but expecting
results for UDP 137 and 161. However in the following I get
results for UDP 53, 137, and 161 as expected:

-p T:22,53,139,445,U:53,U:137,U:161


Reply to this email directly or view
it on GitHub.

@cweb
Copy link
Author

cweb commented Nov 5, 2013

Ya, nmap will scan 4 TCP ports and 3 UDP ports with -p T:22,53,139,445,U:53,137,161

@robertdavidgraham
Copy link
Owner

I've checked in the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants