[
https://issues.apache.org/jira/browse/DISPATCH-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109542#comment-16109542
]
Ganesh Murthy commented on DISPATCH-632:
----------------------------------------
The requested enhancement can be achieved by using multiple listeners which can
have different hosts
So, instead of
{noformat}
listener {
host: 172.16.2.8, 127.0.0.1
port: amqp
authenticatePeer: no
}
{noformat}
you could do two listeners like the following
{noformat}
listener {
host: 172.16.2.8
port: amqp
authenticatePeer: no
}
listener {
host: 127.0.0.1
port: amqp
authenticatePeer: no
}
{noformat}
> [RFE] Add multiple hosts listening capability
> ---------------------------------------------
>
> Key: DISPATCH-632
> URL: https://issues.apache.org/jira/browse/DISPATCH-632
> Project: Qpid Dispatch
> Issue Type: Improvement
> Components: Router Node
> Affects Versions: 0.6.1
> Environment: Centos 7.3 + qpid-dispatch-router-0.6.1-4.el7.x86_64
> Reporter: Michele Baldessari
> Priority: Minor
>
> Currently a single ip/hostname is allowed in the host directive to have a
> service listen to a specific address:
> See
> https://qpid.apache.org/releases/qpid-dispatch-0.6.1/man/qdrouterd.conf.html
> and listener/host.
> It would be nice to support multiple ip addresses/hostnames. So something
> like the following:
> listener {
> host: 172.16.2.8, 127.0.0.1
> port: 5672
> }
> The reason for this request is that sometimes on multi-homed hosts with a few
> interfaces it is quite useful to bind the service to a subset of the
> interfaces.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
