Request for Enhancement: If you want to use luci in a server-infrastructure with more than one network you want access luci only from internal network. The easiest way is to configure the stunnel-component to listen only on one ip. This is possible with LUCI_HTTPS_PORT=10.10.10.10:8084 in /etc/sysconfig/luci It would be better to adopt a own variable and use it in the init-script and correct $LUCI_URL for correct output.
Changing component to documentation component "Cluster_Administration" since this is a procedural issue.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
Ryan: I'm looking at a bunch of the Cluster documentation bugs, and I have a couple of questions about this one: 1) This is technically a RHEL 5 bug, but does it apply to RHEL 6 as well? 2) It looks to me as if I can just add this procedure to this section: http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Cluster_Administration/s2-iptables-conga-CA.html Does that makes sense, simply to add this information to that existing subsection? 3) I'm not sure what this is saying -- there seems to be a typo of sorts: It would be better to adopt a own variable and use it in the init-script and correct $LUCI_URL for correct output. "a own variable"? What does that refer to? Thanks, -Steven Levine
Marking as needinfo from Ryan McCabe as per Comment 6.
I imagine "own variable" was a typo for environment variable, which is a feature that has not been implemented. The way to configure this is to change the LUCI_HTTPS_PORT parameter in the /etc/sysconfig/luci file as described in comment #1