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

IPTrk and XFF: Odd behavior when using same IP range as the system #145

Open
teward opened this issue Oct 15, 2018 · 0 comments
Open

IPTrk and XFF: Odd behavior when using same IP range as the system #145

teward opened this issue Oct 15, 2018 · 0 comments

Comments

@teward
Copy link

teward commented Oct 15, 2018

In a production environment, we have an IP range of, say, 1.2.3.0/24 at the 'corporate' environment. Of that, 1.2.3.162/29 is the IP range assigned use on the box itself.

When we set "xff_trusted_cidr" to [ "127.0.0.1/8", "1.2.3.0/24" ], IPTrk ends up ignoring the XFF header and setting the IP address in IPTrk to 127.0.0.1, but only for IPs fitting within the /24.

This is not expected behavior in which Trident would trust the headers from both the localhost and the IP address falling into the specified CIDR range that isn't local host.

This sounds a lot like a bug in how IPTrk parses XFF Trusted CIDR and handles the actual reading of XFF.

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

No branches or pull requests

1 participant