Identifying remote client ip #326

Closed
opened 2025-12-29 01:27:04 +01:00 by adam · 1 comment
Owner

Originally created by @mhameed on GitHub (Sep 14, 2022).

Feature request

Hi,

Thanks for a great project.

I see log entries from headscale like the following:

Sep 14 09:43:50 headscale headscale[574]: 2022-09-14T09:43:50+01:00 WRN Ignoring request, cannot find machine with key mkey:6c161593e3f3e03e48aca6724ed3cb67b7d8eb27d06f317c9bd86204b4fdff28 handler=PollNetMap

This is with v0.17.0-alpha2

Any chance the remote ip can be included, so that the peer can be identified?

Thanks.

Originally created by @mhameed on GitHub (Sep 14, 2022). <!-- Headscale is a multinational community across the globe. Our common language is English. Please consider raising the feature request in this language. --> **Feature request** <!-- A clear and precise description of what new or changed feature you want. --> <!-- Please include the reason, why you would need the feature. E.g. what problem does it solve? Or which workflow is currently frustrating and will be improved by this? --> Hi, Thanks for a great project. I see log entries from headscale like the following: Sep 14 09:43:50 headscale headscale[574]: 2022-09-14T09:43:50+01:00 WRN Ignoring request, cannot find machine with key mkey:6c161593e3f3e03e48aca6724ed3cb67b7d8eb27d06f317c9bd86204b4fdff28 handler=PollNetMap This is with v0.17.0-alpha2 Any chance the remote ip can be included, so that the peer can be identified? Thanks.
adam added the enhancement label 2025-12-29 01:27:04 +01:00
adam closed this issue 2025-12-29 01:27:04 +01:00
Author
Owner

@juanfont commented on GitHub (May 10, 2023):

Should already be fixed.

@juanfont commented on GitHub (May 10, 2023): Should already be fixed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#326