<div class="content"><p>The <b>RRouterInterfaceTransportGetInfo</b> method<a id="Appendix_A_Target_273"></a><a aria-label="Product behavior note 273" href="3bb906f0-b077-47ab-ad11-d8d807afde26#Appendix_A_273" data-linktype="relative-path">&lt;273&gt;</a> retrieves information about a
transport running on a specified interface. The information retrieved is of the
type <a href="402d2cc2-dd94-487a-9bb1-fab6728c3e7d" data-linktype="relative-path"><b>RTR_INFO_BLOCK_HEADER (section 2.2.1.2.3)</b></a>,
encapsulated within a <a href="61dfdb82-d5dd-4589-86ec-3aeb6b64ea20" data-linktype="relative-path"><b>DIM_INTERFACE_CONTAINER (section 2.2.1.2.2)</b></a>.  
</p><dl>
<dd>
<div><pre> DWORD RRouterInterfaceTransportGetInfo(
   [in] DIM_HANDLE hDimServer,
   [in] DWORD hInterface,
   [in] DWORD dwTransportId,
   [in, out] PDIM_INTERFACE_CONTAINER pInfoStruct
 );
</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>.
Since the RRASM server does not maintain the interface handles, the RRAS server
SHOULD check and ensure that this handle is a valid interface handle.   </p><p><b>dwTransportId: </b>Specifies the transport for
which the information is retrieved (IPX, IPv4, or IPv6). It MUST be one of the
following values.<a id="Appendix_A_Target_274"></a><a aria-label="Product behavior note 274" href="3bb906f0-b077-47ab-ad11-d8d807afde26#Appendix_A_274" data-linktype="relative-path">&lt;274&gt;</a> Otherwise an error other than
those in the return values table is returned.</p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Value</p>
   </th>
   <th>
   <p>Meaning</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>
  <p>PID_IPX</p>
  <p>0x0000002B</p>
  </td>
  <td>
  <p>IPX<span> </span>protocol</p>
  </td>
 </tr><tr>
  <td>
  <p>PID_IP</p>
  <p>0x00000021</p>
  </td>
  <td>
  <p>IPv4 protocol</p>
  </td>
 </tr><tr>
  <td>
  <p>PID_IPV6</p>
  <p>0x00000057</p>
  </td>
  <td>
  <p>IPv6 protocol<a id="Appendix_A_Target_275"></a><a aria-label="Product behavior note 275" href="3bb906f0-b077-47ab-ad11-d8d807afde26#Appendix_A_275" data-linktype="relative-path">&lt;275&gt;</a></p>
  </td>
 </tr></tbody></table>
</dd></dl><p><b>pInfoStruct: </b>This is a pointer of type <b>DIM_INTERFACE_CONTAINER</b>.
It MUST NOT be NULL.</p><p><b>fGetInterfaceInfo</b> of <b>DIM_INTERFACE_CONTAINER</b>
MUST be set to 1.</p><dl>
<dd>
<p>On completion of the method, <b>pInterfaceInfo</b>
and <b>dwInterfaceInfoSize</b> of the <i>pInfoStruct</i> fields are set. <b>pInterfaceInfo</b>
points to a valid <b>RTR_INFO_BLOCK_HEADER</b> (section 2.2.1.2.3) and <a href="c99955ec-6d18-4665-8d5b-e124de63a368" data-linktype="relative-path"><b>RTR_TOC_ENTRY (section 2.2.1.2.4)</b></a>
on return.  </p>
</dd></dl><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, as specified in section <a href="9373431f-ed29-4639-9f8b-743267c9f9b6" data-linktype="relative-path">2.1.1.1</a>.</p>
  </td>
 </tr></tbody></table>
</dd></dl><p>The opnum field value for this method is 18.</p><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 2.1.1.1, whether this method
was called by a client that has access to the method. If the client does not
have access, then return error ERROR_ACCESS_DENIED (0x00000005).</p>
</li><li><p><span><span> 
</span></span>If <i>pInfoStruct</i> is NULL, return an error other than those
in the preceding table.</p>
</li><li><p><span><span> 
</span></span>If <i>dwTransportId</i> is not specified in the <b>SupportedTransportsList</b>,
return an error other than those specified in the preceding table.</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 RRAS server to perform
the required management task.</p>
</li><li><p><span><span> 
</span></span>If the RRAS server processing returns successfully, populate the
interface information returned by RRAS server in <i>pInfoStruct</i> and return
ERROR_SUCCESS (0x00000000).</p>
</li><li><p><span><span> 
</span></span>Otherwise return the error result provided by RRAS server.</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>