<!-- 
RSS generated by JIRA (9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c) at Sat Feb 10 03:34:59 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>Whamcloud Community JIRA</title>
    <link>https://jira.whamcloud.com</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.4.14</version>
        <build-number>940014</build-number>
        <build-date>05-12-2023</build-date>
    </build-info>


<item>
            <title>[LU-17382] LNet: allow dynamic setting of &quot;accept&quot; parameter</title>
                <link>https://jira.whamcloud.com/browse/LU-17382</link>
                <project id="10000" key="LU">Lustre</project>
                    <description>&lt;p&gt;By default, LNet is accepting connections only from &quot;secure&quot; (&amp;lt;1024) ports. If there are clients connecting using a wider range of ports, e.g. via NAT, the server is expected to have set lnet module parameter &quot;accept&quot; to &quot;all&quot;, otherwise out-of-range connections are rejected with an error similar to the following:&lt;/p&gt;
&lt;div class=&quot;code panel&quot; style=&quot;border-width: 1px;&quot;&gt;&lt;div class=&quot;codeContent panelContent&quot;&gt;
&lt;pre class=&quot;code-java&quot;&gt;
LNetError: 6508:0:(acceptor.c:430:lnet_acceptor()) Refusing connection from 10.49.76.116: insecure port 60694
&lt;/pre&gt;
&lt;/div&gt;&lt;/div&gt;
&lt;p&gt;Currently to change the value of the &quot;accept&quot; parameter it is required to modify the &lt;tt&gt;/etc/modprobe.d/lustre.conf&lt;/tt&gt; file and reload the module. It is proposed to allow setting &quot;accept&quot; parameter dynamically - it is less disruptive to do so compared to having to reload LNet just because a few clients using NAT got added.&lt;/p&gt;</description>
                <environment></environment>
        <key id="79702">LU-17382</key>
            <summary>LNet: allow dynamic setting of &quot;accept&quot; parameter</summary>
                <type id="4" iconUrl="https://jira.whamcloud.com/secure/viewavatar?size=xsmall&amp;avatarId=11310&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="4" iconUrl="https://jira.whamcloud.com/images/icons/priorities/minor.svg">Minor</priority>
                        <status id="1" iconUrl="https://jira.whamcloud.com/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="wc-triage">WC Triage</assignee>
                                    <reporter username="ssmirnov">Serguei Smirnov</reporter>
                        <labels>
                            <label>lnet</label>
                            <label>security</label>
                    </labels>
                <created>Thu, 21 Dec 2023 19:45:01 +0000</created>
                <updated>Fri, 22 Dec 2023 18:32:33 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                            <comments>
                            <comment id="397830" author="adilger" created="Thu, 21 Dec 2023 20:47:02 +0000"  >&lt;p&gt;Sebastien, it is probably not (easily) possible to accept connections from insecure ports based on a nodemap?  That is probably a chicken-and-egg issue where we can&apos;t check the nodemap until after the connection is established?  I guess for a more secure environment, it is better to have strong authentication (SSK, Kerberos) and then accepting connections from insecure ports is not really a concern...&lt;/p&gt;</comment>
                            <comment id="397919" author="sebastien" created="Fri, 22 Dec 2023 16:57:22 +0000"  >&lt;p&gt;Yes exactly, nodemap operates way above LNet, so I am not even sure we could have access to the LNet port? I do not really know why the ports below 1024 are called secure actually. Maybe it is more that those ports can be assigned to &quot;services&quot;, so there is no risk of having the port used by someone else?&lt;/p&gt;</comment>
                            <comment id="397923" author="adilger" created="Fri, 22 Dec 2023 18:32:33 +0000"  >&lt;p&gt;Ports below 1024 cannot be opened by non-root processes, so in environments where the nodes are secure/trusted this means that services using those ports are also more secure.&#160; With modern systems where any user can install the client and/or run as root this is less useful.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Related</name>
                                            <outwardlinks description="is related to ">
                                                        </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                            <customfield id="customfield_10890" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10390" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|i045nb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10090" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10060" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Severity</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10022"><![CDATA[3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>