rsyslog / rsyslog/librelp

Unable to configure RELP (imrelp) module to bind to single IP

Open
#7 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
32
Forks
39
Avg merge
2h 27m
Merged PRs (30d)
7

Description

Apologies in advance if this is a limitation of rsyslog not librelp.

Currently it appears that when you enable librelp (imrelp) in rsyslog that it listens on all available IPs and there is no way to restrict this to listening on a single IP.

Would it be possible to add a feature to librelp so an IP can be specified along with the port (currently implemented) to restrict where the server listens for incoming connections?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how the imrelp server currently configures its listening port and how librelp creates the listener. Determine where a bind IP could be specified alongside the port. Done means the server can be restricted to one configured IP instead of listening on all available IPs.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
networking
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.