<div class="content"><p>The <b>RRouterInterfaceGetCustomInfoEx</b> method<a id="Appendix_A_Target_328"></a><a aria-label="Product behavior note 328" href="3bb906f0-b077-47ab-ad11-d8d807afde26#Appendix_A_328" data-linktype="relative-path">&lt;328&gt;</a> is used to get the
tunnel-specific custom configuration for an interface.</p><dl>
<dd>
<div><pre> DWORD RRouterInterfaceGetCustomInfoEx(
   [in] DIM_HANDLE hDimServer,
   [in] DWORD hInterface,
   [in, out] PMPR_IF_CUSTOMINFOEX_IDL pIfCustomConfig
 );
</pre></div>
</dd></dl><p><b>hDimServer: </b>A handle to the RRASM server where
the call is to be executed; see section <a href="1f8cdbcc-9791-4a35-ad78-878b8d110e15" data-linktype="relative-path">3.1.3</a>.</p><p><b>hInterface: </b>The unique identifier of an
interface. This can be obtained from <a href="72bead5c-821f-4e98-bacd-0de279552379" data-linktype="relative-path"><b>RRouterInterfaceCreate (section 3.1.4.13)</b></a>
or <a href="b4cc4f8f-e2bc-4e8f-a521-08a0558d3e44" data-linktype="relative-path"><b>RRouterInterfaceGetHandle (section 3.1.4.12)</b></a>.
Because the RRASM server does not maintain the interface handles, the RRAS
server SHOULD check to ensure that this handle represents a valid interface
handle. </p><p><b>pIfCustomConfig: </b>A valid pointer to an <a href="89cbdcda-d307-4445-861f-d411107a8bbe" data-linktype="relative-path"><b>MPR_IF_CUSTOMINFOEX_IDL (section 2.2.1.2.245)</b></a>
structure. This MUST NOT be NULL. On successful return, this parameter contains
tunnel-specific custom configuration for the interface whose handle is
specified in the <i>hInterface</i> parameter.  </p><p><b>Return Values: </b>A 32-bit unsigned integer value
that indicates return status. A return value of ERROR_SUCCESS (0x00000000)
indicates that the operation was completed successfully; otherwise, it contains
an error code, as specified in <a href="../ms-erref/1bc92ddf-b79e-413c-bbaa-99a5281a6c90" data-linktype="relative-path">[MS-ERREF]</a>
or in section <a href="5c0c991a-0d3d-4fe5-9503-5128d0d49fe1" data-linktype="relative-path">2.2.4</a>.
All values that are not in the table that follows MUST be treated the same by
the RRASM client.</p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Return value/code</p>
   </th>
   <th>
   <p>Description</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>
  <p>ERROR_SUCCESS</p>
  <p>0x00000000</p>
  </td>
  <td>
  <p>The call was successful.</p>
  </td>
 </tr><tr>
  <td>
  <p>ERROR_ACCESS_DENIED</p>
  <p>0x00000005</p>
  </td>
  <td>
  <p>The calling application does not have sufficient privileges.</p>
  </td>
 </tr></tbody></table>
</dd></dl><p>When processing this call, the RRASM server MUST do the
following:</p><ul><li><p><span><span> 
</span></span>Validate, as specified in section <a href="9373431f-ed29-4639-9f8b-743267c9f9b6" data-linktype="relative-path">2.1.1.1</a>, whether this
method was called by a client that has access to the method. If the client does
not have access, return the error ERROR_ACCESS_DENIED (0x00000005).</p>
</li><li><p><span><span> 
</span></span>Call the abstract interface <b>Invoke DIMSVC</b> method,
specifying the operation and the parameters, to enable the RRAS server to
perform the required management task.</p>
</li><li><p><span><span> 
</span></span>Return any error status that the RRAS server returns. Otherwise,
return ERROR_SUCCESS (0x00000000).</p>
</li></ul><p>No exceptions are thrown beyond those thrown by the
underlying RPC protocol <a href="../ms-rpce/290c38b1-92fe-4229-91e6-4fc376610c15" data-linktype="relative-path">[MS-RPCE]</a>.</p></div>