joshsagredo/syn-flood

sendmsg: invalid argument

c2h2 opened this issue · 5 comments

c2h2 commented

used brew install, but have problem with running example, please point me some directions.

➜  syn-flood git:(master) ✗ sudo ulimit -S -n 2048000
➜  syn-flood git:(master) ✗ sudo syn-flood --host asdf.com --port 443     
2022/05/15 17:02:30 maxprocs: Leaving GOMAXPROCS=8: CPU quota undefined
                                 __   _                       _
  ___   _   _   _ __            / _| | |   ___     ___     __| |
 / __| | | | | | '_ \   _____  | |_  | |  / _ \   / _ \   / _` |
 \__ \ | |_| | | | | | |_____| |  _| | | | (_) | | (_) | | (_| |
 |___/  \__, | |_| |_|         |_|   |_|  \___/   \___/   \__,_|
        |___/

GoVersion: go1.17.8
GOOS: darwin
GOARCH: amd64
NumCPU: 8
GOPATH: 
GOROOT: /opt/hostedtoolcache/go/1.17.8/x64
Compiler: gc
ENV: 
Now: Sunday, 15 May 2022
BannerGeneratedAt: https://devops.datenkollektiv.de/banner.txt/index.html

2022/05/15 17:02:30 asdf.com is a DNS record, making DNS lookup
2022/05/15 17:02:30 dns lookup succeeded, found 64.90.40.65 for asdf.com
2022/05/15 17:02:30 an error occured on flooding process: write ip 0.0.0.0->64.90.40.65: sendmsg: invalid argument
bilalcaliskan commented

hello @c2h2 , i'm not sure but i think i've come across that error while developing that tool but can you verify that you get the same error with the latest version?

github-actions commented

This bot triages issues and PRs according to the following rules: - After 60d of inactivity, lifecycle/stale is applied. - After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed. You can: - Make a comment to remove the stale label and show your support. The 60 days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interseted in reopening

github-actions commented

This bot triages issues and PRs according to the following rules: - After 60d of inactivity, lifecycle/stale is applied. - After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied and the issue is closed. You can: - Make a comment to remove the stale label and show your support. The 60 days reset. - If an issue has lifecycle/rotten and is closed, comment and ask maintainers if they'd be interseted in reopening

mrzxy commented

i got same error with 1.1.1 version

image

joshsagredo commented

actually, it is really hard to maintain these kind of attacks on non-linux machines. so i am removing the support for macos.

i am saying that because with the same command, i get no error.