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

Proc monitoring with Packetbeat on tcp6 #4443

Closed

tomaszrichert opened this issue Jun 2, 2017 · 1 comment

Labels

Contributor

tomaszrichert commented Jun 2, 2017 •

edited

Loading

There is a simple bug in proc monitoring feature of packetbeat, that tcp6 ports are not being scanned.
I've described it here:
https://discuss.elastic.co/t/packetbeat-support-for-tcp6/87894

I believe i've found the issue in code, I've corrected it and made a pull request: #4442

With this change its working and scanning also tcp6 file, however it's not able to parse some entries due to next error:

Error parsing IP and port: strconv.ParseInt: parsing "0000000000000000FFFF00000100007F": value out of range

Edit:
fixed parse bug for ipv6 - included in pull request.

andrewkroh added Packetbeat bug labels

Member

andrewkroh commented Sep 17, 2018

Fixed in #4442.

andrewkroh closed this as completed

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