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

Devices with full path RTT sometimes have packet parsing errors #6

Open
jkilpatr opened this issue Jan 30, 2018 · 0 comments
Open

Devices with full path RTT sometimes have packet parsing errors #6

jkilpatr opened this issue Jan 30, 2018 · 0 comments
Assignees
Labels

Comments

@jkilpatr
Copy link
Member

About to enter subtlv parsting loop if 0 < 4
About to enter subtlv parsting loop if 0 < 4
About to enter subtlv parsting loop if 0 < 4
About to enter subtlv parsting loop if 0 < 4
About to enter subtlv parsting loop if 0 < 4
About to enter subtlv parsting loop if 0 < 4
About to enter subtlv parsting loop if 0 < 4
About to enter subtlv parsting loop if 0 < 4
About to enter subtlv parsting loop if 0 < -2
About to enter subtlv parsting loop if 0 < -2
About to enter subtlv parsting loop if 0 < -2
About to enter subtlv parsting loop if 0 < -2
About to enter subtlv parsting loop if 0 < -2
Couldn't parse packet (13, 23) from fe80::8eae:4cff:fef4:2201 on eth1.
Couldn't parse packet (13, 23) from fe80::8eae:4cff:fef4:2201 on eth1.
Couldn't parse packet (13, 31) from fe80::8eae:4cff:fef4:2201 on eth1.
Couldn't parse packet (13, 22) from fe80::8eae:4cff:fef4:2201 on eth1.
Couldn't parse packet (13, 22) from fe80::8eae:4cff:fef4:2201 on eth1.

Everything seems to work but I'm still concerned by these messages and potentially hard to find errors.

@jkilpatr jkilpatr added the bug label Jan 30, 2018
@jkilpatr jkilpatr self-assigned this Jan 30, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant