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.

Sign up for GitHub

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

Jump to bottom

furious -s connect example.com always return Host is down #12

Open
ghost opened this issue Aug 28, 2020 · 3 comments
Open

furious -s connect example.com always return Host is down #12

ghost opened this issue Aug 28, 2020 · 3 comments

Comments

@ghost
Copy link

ghost commented Aug 28, 2020 •
edited by ghost
Loading

Exactly as mentioned in the title the command always returns Host is down output.

❯ furious -s connect github.com

Starting scan at 2020-08-29 01:04:42.530665 +0300 +03 m=+0.019277855

Scan results for host 140.82.121.4
	Host is down

Scan complete in 2.110237526s.

Environment Information

❯ go version
go version go1.15 darwin/amd64
❯ brew info libpcap
libpcap: stable 1.9.1 (bottled), HEAD [keg-only]

Added Homebrew libpcap to path

❯ furious --version
furious development version
@httpnotonly
Copy link

+1
my Dockerfile

FROM golang:latest
RUN apt-get update && apt-get install libpcap-dev -y
RUN go get -u github.com/liamg/furious
ENTRYPOINT ["furious"]

docker run -it --rm whitespots/furious -s connect whitespots.io
docker run -it --rm whitespots/furious -s syn whitespots.io

everything is the same..

@003random
Copy link

same here. you guys ever found the solution? @httpnotonly @metebyte

@ghost
Copy link
Author

ghost commented Dec 20, 2020

same here. you guys ever found the solution? @httpnotonly @metebyte

Unfortunately, no. Probably won't be maintained anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@003random @httpnotonly