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

ARP storm #68

Closed
jordens opened this issue Nov 1, 2017 · 8 comments
Closed

ARP storm #68

jordens opened this issue Nov 1, 2017 · 8 comments
Assignees
Labels

Comments

@jordens
Copy link

jordens commented Nov 1, 2017

smoltcp seems to be generating a bit of an ARP storm, at least when interacting with some security scan appliance.

Might be related to #25

@whitequark has the dump.

@dlrobertson
Copy link
Collaborator

dlrobertson commented Nov 1, 2017

Might also be related to #50

Sorry, something went wrong.

@dnadlinger
Copy link
Contributor

We saw a similar issue in our network a couple of weeks ago (ARP requests for the same address more than once every millisecond, from a nominally idle KC705), but it was late at night trying to get some actual data, so we just restarted the core device and it was gone. Unfortunately, I can't seem to find the dump right now, but reproducing this might definitely be a bit non-straightforward, as the problem didn't occur again. No security scan appliances on the subnet that I'm aware of.

Sorry, something went wrong.

@whitequark
Copy link
Contributor

This is the exact same issue as #25.

@klickverbot It is not easily reproducible in practice but it's trivial to write tests for, so it's not a problem. Don't bother with the dumps, I am well aware of all causes of this one.

Sorry, something went wrong.

@dhslichter
Copy link

@whitequark what is the timeline for fixing this issue? This is a high priority for us because we can't use ARTIQ 3 on our network until it is addressed (the ARP storm breaks some other groups' stuff), and I think other labs may be in a similar position.

@whitequark
Copy link
Contributor

@dhslichter I plan to have it fixed in 2 days.

@dhslichter
Copy link

Thanks!

@sbourdeauducq
Copy link

@whitequark ping

@whitequark
Copy link
Contributor

Done

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

No branches or pull requests

6 participants