Bug 572456 - [Feature request] Provide the possibility to choose the network interface to bind qpidd.
Summary: [Feature request] Provide the possibility to choose the network interface to ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 1.2
Hardware: All
OS: All
medium
medium
Target Milestone: 3.0
: ---
Assignee: Andrew Stitcher
QA Contact: Ernie
URL:
Whiteboard:
: 671229 (view as bug list)
Depends On:
Blocks: 698367 957951
TreeView+ depends on / blocked
 
Reported: 2010-03-11 09:30 UTC by noel.rocher
Modified: 2014-09-24 15:01 UTC (History)
9 users (show)

Fixed In Version: qpid-cpp-0.22-1
Doc Type: Enhancement
Doc Text:
In MRG Messaging 3.0, it is now possible to select the network interface to bind qpidd to. This allows customers to restrict the networks to which qpidd is exposed. This may be used as part of the security policy of the installation. Customers can now use the qpidd --interface command to bind qpidd to a network interface, but not a specific port. This command is documented in the "General Broker Options" section of the Messaging Installation and Configuration Guide.
Clone Of:
: 957951 (view as bug list)
Environment:
Last Closed: 2014-09-24 15:01:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA QPID-3351 0 None None None 2012-10-22 18:58:38 UTC
Red Hat Product Errata RHEA-2014:1296 0 normal SHIPPED_LIVE Red Hat Enterprise MRG Messaging 3.0 Release 2014-09-24 19:00:06 UTC

Description noel.rocher 2010-03-11 09:30:48 UTC
Feature Request:
Provide the possibility to choose the network interface to bind qpidd. maybe with "--bind-address" new option

Comment 1 Gordon Sim 2011-01-24 08:52:44 UTC
*** Bug 671229 has been marked as a duplicate of this bug. ***

Comment 3 Andy Goldstein 2011-07-09 12:18:25 UTC
Created JIRA for this too: https://issues.apache.org/jira/browse/QPID-3351

Comment 7 Ernie 2013-08-23 15:53:38 UTC
I have a question on specifying the port along with the interface. According to the proposal 
http://qpid.2158936.n2.nabble.com/Proposal-qpidd-to-listen-on-multiple-network-interfaces-td7584581.html 
I should be able to specify a port with the interface:
--interface wlan0:5672 
--interface 127.0.0.1:465 
--interface [fe80::3e97:eff:fe14:bbc1%em1]:12002

However, the documentation for this feature does not mention the ability to specify a port. 
http://deathstar1.usersys.redhat.com:3000/builds/18173-Messaging_Installation_and_Configuration_Guide/#General_Broker_options

And indeed, when I attempt to specify a port, I get an error:
> qpidd --interface 10.16.44.233:5680 -d
Daemon startup failed: Cannot resolve 10.16.44.233:5680:5672: Name or service not known (/builddir/build/BUILD/qpid-0.22/cpp/src/qpid/sys/posix/SocketAddress.cpp:148)

This happens for ipv4 and ipv6 literal and named interfaces.
So my question is, is specifying a port along with the interface supposed to be supported?

Comment 8 Andrew Stitcher 2013-08-23 21:05:45 UTC
Not it is not supported. The documentation is correct. The proposal is not fully implemented.

Comment 9 Ernie 2013-08-29 15:15:47 UTC
Verified

rhel 6.4 x86_64
cyrus-sasl-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-devel-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-gssapi-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-lib-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-md5-2.1.23-13.el6_3.1.x86_64
cyrus-sasl-plain-2.1.23-13.el6_3.1.x86_64
perl-qpid-0.22-5.el6.x86_64
python-qpid-0.22-4.el6.noarch
python-qpid-qmf-0.22-9.el6.x86_64
python-saslwrapper-0.22-3.el6.x86_64
qpid-cpp-client-0.22-11.el6.x86_64
qpid-cpp-client-devel-0.22-11.el6.x86_64
qpid-cpp-client-devel-docs-0.22-11.el6.noarch
qpid-cpp-client-rdma-0.22-11.el6.x86_64
qpid-cpp-client-ssl-0.22-11.el6.x86_64
qpid-cpp-debuginfo-0.22-11.el6.x86_64
qpid-cpp-server-0.22-11.el6.x86_64
qpid-cpp-server-devel-0.22-11.el6.x86_64
qpid-cpp-server-ha-0.22-11.el6.x86_64
qpid-cpp-server-rdma-0.22-11.el6.x86_64
qpid-cpp-server-ssl-0.22-11.el6.x86_64
qpid-cpp-server-store-0.22-11.el6.x86_64
qpid-cpp-server-xml-0.22-11.el6.x86_64
qpid-cpp-tar-0.22-11.el6.noarch
qpid-java-client-0.22-5.el6.noarch
qpid-java-common-0.22-5.el6.noarch
qpid-java-example-0.22-5.el6.noarch
qpid-proton-c-0.4-2.2.el6.x86_64
qpid-proton-c-devel-0.4-2.2.el6.x86_64
qpid-proton-debuginfo-0.4-2.2.el6.x86_64
qpid-qmf-0.22-9.el6.x86_64
qpid-qmf-debuginfo-0.22-9.el6.x86_64
qpid-qmf-devel-0.22-9.el6.x86_64
qpid-snmpd-1.0.0-12.el6.x86_64
qpid-snmpd-debuginfo-1.0.0-12.el6.x86_64
qpid-tests-0.22-4.el6.noarch
qpid-tools-0.22-3.el6.noarch
rh-qpid-cpp-tests-0.22-11.el6.x86_64
ruby-qpid-0.7.946106-2.el6.x86_64
saslwrapper-0.22-3.el6.x86_64
saslwrapper-devel-0.22-3.el6.x86_64

rhel 6.4 i686
cyrus-sasl-2.1.23-13.el6_3.1.i686
cyrus-sasl-devel-2.1.23-13.el6_3.1.i686
cyrus-sasl-gssapi-2.1.23-13.el6_3.1.i686
cyrus-sasl-lib-2.1.23-13.el6_3.1.i686
cyrus-sasl-md5-2.1.23-13.el6_3.1.i686
cyrus-sasl-plain-2.1.23-13.el6_3.1.i686
perl-qpid-0.22-5.el6.i686
python-qpid-0.22-4.el6.noarch
python-qpid-qmf-0.22-9.el6.i686
python-saslwrapper-0.22-3.el6.i686
qpid-cpp-client-0.22-11.el6.i686
qpid-cpp-client-devel-0.22-11.el6.i686
qpid-cpp-client-devel-docs-0.22-11.el6.noarch
qpid-cpp-client-rdma-0.22-11.el6.i686
qpid-cpp-client-ssl-0.22-11.el6.i686
qpid-cpp-debuginfo-0.22-11.el6.i686
qpid-cpp-server-0.22-11.el6.i686
qpid-cpp-server-devel-0.22-11.el6.i686
qpid-cpp-server-ha-0.22-11.el6.i686
qpid-cpp-server-rdma-0.22-11.el6.i686
qpid-cpp-server-ssl-0.22-11.el6.i686
qpid-cpp-server-store-0.22-11.el6.i686
qpid-cpp-server-xml-0.22-11.el6.i686
qpid-cpp-tar-0.22-11.el6.noarch
qpid-java-client-0.22-5.el6.noarch
qpid-java-common-0.22-5.el6.noarch
qpid-java-example-0.22-5.el6.noarch
qpid-proton-c-0.4-2.2.el6.i686
qpid-proton-c-devel-0.4-2.2.el6.i686
qpid-proton-debuginfo-0.4-2.2.el6.i686
qpid-qmf-0.22-9.el6.i686
qpid-qmf-debuginfo-0.22-9.el6.i686
qpid-qmf-devel-0.22-9.el6.i686
qpid-snmpd-1.0.0-12.el6.i686
qpid-snmpd-debuginfo-1.0.0-12.el6.i686
qpid-tests-0.22-4.el6.noarch
qpid-tools-0.22-3.el6.noarch
rh-qpid-cpp-tests-0.22-11.el6.i686
ruby-qpid-qmf-0.22-9.el6.i686
saslwrapper-0.22-3.el6.i686

Comment 10 Jared MORGAN 2014-09-17 01:24:30 UTC
Can I please get a Release Note review on this ticket. There is NEEDINFO specifically for the "reason" part of the CCFR text.

Comment 12 errata-xmlrpc 2014-09-24 15:01:41 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2014-1296.html


Note You need to log in before you can comment on or make changes to this bug.