summaryrefslogtreecommitdiff
path: root/digital/avr/modules/usb/lufa/Demos/RNDISEthernet/RNDISEthernet.txt
blob: bd4ff69e810933e8318a46fd6b8206f751e7f831 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
/** \file
 *
 *  This file contains special DoxyGen information for the generation of the main page and other special
 *  documentation pages. It is not a project source file.
 */
 
/** \mainpage RNDIS Class Ethernet Demo (with Webserver/Telnet)
 *  
 *  Remote Network Driver Interface demonstration application.
 *  This gives a simple reference application for implementing
 *  a CDC RNDIS device acting as a simple network interface for
 *  ethernet packet exchange. RNDIS is a proprietary Microsoft
 *  standard; this demo will only work on Windows 2000 (manually
 *  patched with the Microsoft RNDIS hotfix) and above (with no
 *  manual patches), or on the latest Linux kernels.
 *  
 *  Before running, you will need to install the INF file that
 *  is located in the RNDISEthernet project directory. This will
 *  enable Windows to use its inbuilt RNDIS drivers, negating the
 *  need for special Windows drivers for the device. To install,
 *  right-click the .INF file and choose the Install option. If
 *  Windows 2000 is used, the Microsoft INF file in the hotfix
 *  will need to be altered to use the VID/PID of the demo and
 *  then chosen instead of the LUFA RNDIS INF file when prompted.
 *  
 *  When enumerated, this demo will install as a new network
 *  adapter which ethernet packets can be sent to and received
 *  from. Running on top of the adapter is a very simple TCP/IP
 *  stack with a HTTP webserver and TELNET host which can be
 *  accessed through a web browser at IP address 10.0.0.2:80 or
 *  through a TELNET client at 10.0.0.2:25. This device also supports
 *  ping echos via the ICMP protocol.
 *  
 *  \note The TCP/IP stack in this demo has a number of limitations
 *  and should serve as an example only - it is not fully featured nor
 *  compliant to the TCP/IP specification. For complete projects, it is 
 *  recommended that it be replaced with an external open source TCP/IP
 *  stack that is feature complete, such as the uIP stack.
 *
 *  <table>
 *   <tr>
 *    <td><b>USB Mode:</b></td>
 *    <td>Device</td>
 *   </tr>
 *   <tr>
 *    <td><b>USB Class:</b></td>
 *    <td>Communications Device Class (CDC)</td>
 *   </tr>
 *   <tr> 
 *    <td><b>USB Subclass:</b></td>
 *    <td>Remote NDIS (Microsoft Proprietary CDC Class Networking Standard)</td>
 *   </tr>
 *   <tr>
 *    <td><b>Relevant Standards:</b></td>
 *    <td>Microsoft RNDIS Specification</td>
 *   </tr>
 *   <tr>
 *    <td><b>Usable Speeds:</b></td>
 *    <td>Full Speed Mode</td>
 *   </tr>
 *  </table>
 */