Add option to bind listening daemons to a specific IP

Description

Right now, listening daemons (trapd specificl is what we are looking at, but I
am assuming it is others as well) listen to all IP ona system. It would make
OpenNMS much more usable for small locations that want to run multiple NMs
packages on one server, for vendor specific features, or large locations to run
in a high availability environment, if the listeners could be bound to specific
IP addresses.

Environment

Operating System: All Platform: All

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Seth Leger September 19, 2014 at 1:50 PM

This bug doesn't specifically mention any daemons besides Trapd and the binding address feature for it was added in 1.9.90. Marking as fixed.

Benjamin Reed October 6, 2008 at 3:39 PM

I know DJ did at least some of this, DJ – are there interfaces that can't bind to specific IPs now?

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created April 4, 2007 at 1:50 PM
Updated January 27, 2017 at 4:31 PM
Resolved September 19, 2014 at 1:50 PM