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

feature: it will be very cool if nfcapd switch '-n' allow specifying port to listen to. not globally single '-p' but per-configured exporter #500

Open
MrdUkk opened this issue Jan 15, 2024 · 3 comments
Labels
Feature request Feature request

Comments

@MrdUkk
Copy link

MrdUkk commented Jan 15, 2024

so single nfcapd process can listen at multiple ports with its-own configuration...
is will reduce administrative efforts and socket congestion when gathering data at single port is not possible (too large number of flows).

@phaag
Copy link
Owner

phaag commented Jan 20, 2024

Ok - I see the point. In order to be effective, these different listeners should go in their own threads. This take a bit more work, but I would keep it on my todo list.

@phaag phaag added the Feature request Feature request label Feb 14, 2024
@gabrielmocan
Copy link
Sponsor

@phaag please just keep the current behavior and add this functionality as an extra, as for most scenarios, single port is enough.

@phaag
Copy link
Owner

phaag commented Mar 8, 2024

@gabrielmocan - no worries - the default remains a single port. As I mentioned, this requires more work to implement. Meanwhile as a workaround, one can startup multiple collectors on multiple ports.

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

No branches or pull requests

3 participants