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

Ping command could fail #1

Open
karasz opened this issue Jul 28, 2016 · 1 comment
Open

Ping command could fail #1

karasz opened this issue Jul 28, 2016 · 1 comment
Assignees
@karasz
Labels
enhancement

Comments

@karasz
Copy link
Owner

karasz commented Jul 28, 2016

We inherit this issue from https://github.com/tatsushid/go-fastping, ping command using raw sockets needs either root user or setcap cap_net_raw+ep genet. Genet should check for uid=0 or maybe for the capability.
@karasz
Copy link
Owner Author

karasz commented Jul 29, 2016 •
edited
Loading

Another issue is that recent kernels restrict the capability to use raw ping,

sudo sysctl net.ipv4.ping_group_range
net.ipv4.ping_group_range = 1 0
practically disables this feature, one needs to use a better range like:
sudo sysctl -w net.ipv4.ping_group_range="0 65535"
WARNING! The previous command will enable the capability to all users

@karasz karasz self-assigned this Aug 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@karasz karasz

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@karasz