-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
fix: Allow use of valid Port 0 #40259
Conversation
💚 CLA has been signed |
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
Port 0 is a normal but reserved port. See: https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml or RFC6335 Section 6
efde01f
to
3705d1e
Compare
This pull request is now in conflicts. Could you fix it? 🙏
|
/test |
@MarcWort the test does not pass, could you please fix it?
|
Head branch was pushed to by a user without write access
@rdner Of course, and sorry for the late reply, I was on vacation. |
This pull request is now in conflicts. Could you fix it? 🙏
|
Could someone please run the remaining tests to get this done? |
/test |
run docs-build |
Proposed commit message
Port 0 is a normal but reserved port.
See: https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml or RFC6335 Section 6
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Use cases
Our internet facing server with Shorewall sometimes logs packets with SPT=0.
These trigger an alarm because of many dropped messages in our monitoring.
Logs