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

Harmonize flags between arping and iputils-arping #22

Closed
ZuZuD opened this issue Nov 20, 2016 · 2 comments
Closed

Harmonize flags between arping and iputils-arping #22

ZuZuD opened this issue Nov 20, 2016 · 2 comments
Assignees

Comments

@ZuZuD
Copy link

ZuZuD commented Nov 20, 2016

There is a conflict between these 2 packages options that can cause network trouble with ease.
iputils-arping use the option "-w" for timeout in second whereas arping use the same option for timeout in microseconds.

Installing a pgpool cluster (for example) from Ubuntu universe repository use by default the arping cmd for the gratuitous ARP Virtual IP.
arping_cmd = 'arping -U $IP$ -w 1'

Using by default the arping package instead of iputils-arping can cause serious trouble to you network (tremendous layer2 broadcast).

A quick fix could be switching the -W (second) and -w flag (microsecond) on arping package.
Seems to be a good idea to harmonize the flags for those 2 similar packages ?

@ThomasHabets
Copy link
Owner

Actually -w is a deadline in ping/iputils-arping, not a timeout.

I think I did it in microseconds in the past because the ping I was looking at did that. But that was over 16 years ago so I could be wrong or it could have changed.

I'll fix this.

@ZuZuD
Copy link
Author

ZuZuD commented Nov 24, 2016

Thank you for your commit.
I should now return to scappy to test my network against crafted L2 fast broadcast ;)

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

No branches or pull requests

2 participants