diff options
| -rw-r--r-- | apps/examples/README.txt | 5 | ||||
| -rw-r--r-- | apps/netutils/README.txt | 5 | ||||
| -rw-r--r-- | apps/nshlib/README.txt | 10 | ||||
| -rw-r--r-- | nuttx/Documentation/NuttShell.html | 8 |
4 files changed, 19 insertions, 9 deletions
diff --git a/apps/examples/README.txt b/apps/examples/README.txt index caac77e4a..c9b637439 100644 --- a/apps/examples/README.txt +++ b/apps/examples/README.txt @@ -1914,10 +1914,13 @@ examples/webserver (as well as various other UDP-related configuration settings). CONFIG_NET_BROADCAST=y - UDP broadcast support is needed. - CONFIG_NET_BUFSIZE=650 - Per RFC2131 (p. 9), the DHCP client must be + CONFIG_NET_ETH_MTU=650 - Per RFC2131 (p. 9), the DHCP client must be (or larger) prepared to receive DHCP messages of up to 576 bytes (excluding Ethernet, IP, or UDP headers and FCS). + NOTE: Note that the actual MTU setting will + depend upon the specific link protocol. + Here Ethernet is indicated. Other configuration items apply also to the selected webserver net utility. Additional relevant settings for the uIP webserver net utility are: diff --git a/apps/netutils/README.txt b/apps/netutils/README.txt index 818f6a784..394be98dc 100644 --- a/apps/netutils/README.txt +++ b/apps/netutils/README.txt @@ -116,7 +116,10 @@ required. These include: (as well as various other UDP-related configuration settings). CONFIG_NET_BROADCAST=y UDP broadcast support is needed. - CONFIG_NET_BUFSIZE=650 The client must be prepared to receive + CONFIG_NET_ETH_MTU=650 The client must be prepared to receive (or larger) DHCP messages of up to 576 bytes (excluding Ethernet, IP, or UDP headers and FCS). + NOTE: Note that the actual MTU setting will + depend upon the specific link protocol. + Here Ethernet is indicated. diff --git a/apps/nshlib/README.txt b/apps/nshlib/README.txt index 821e40027..b49daf2a0 100644 --- a/apps/nshlib/README.txt +++ b/apps/nshlib/README.txt @@ -961,7 +961,7 @@ Command Dependencies on Configuration Settings exec -- exit -- free -- - get CONFIG_NET && CONFIG_NET_UDP && CONFIG_NFILE_DESCRIPTORS > 0 && CONFIG_NET_BUFSIZE >= 558 (see note 1) + get CONFIG_NET && CONFIG_NET_UDP && CONFIG_NFILE_DESCRIPTORS > 0 && MTU >= 558 (see note 1) help -- hexdump CONFIG_NFILE_DESCRIPTORS > 0 ifconfig CONFIG_NET @@ -981,7 +981,7 @@ Command Dependencies on Configuration Settings nfsmount !CONFIG_DISABLE_MOUNTPOINT && CONFIG_NFILE_DESCRIPTORS > 0 && CONFIG_NET && CONFIG_NFS ping CONFIG_NET && CONFIG_NET_ICMP && CONFIG_NET_ICMP_PING && !CONFIG_DISABLE_SIGNALS ps -- - put CONFIG_NET && CONFIG_NET_UDP && CONFIG_NFILE_DESCRIPTORS > 0 && CONFIG_NET_BUFSIZE >= 558 (see note 1,2) + put CONFIG_NET && CONFIG_NET_UDP && CONFIG_NFILE_DESCRIPTORS > 0 && MTU >= 558 (see note 1,2) pwd !CONFIG_DISABLE_ENVIRON && CONFIG_NFILE_DESCRIPTORS > 0 rm (((!CONFIG_DISABLE_MOUNTPOINT && CONFIG_FS_WRITABLE) || !CONFIG_DISABLE_PSEUDOFS_OPERATIONS) && CONFIG_NFILE_DESCRIPTORS > 0) rmdir (((!CONFIG_DISABLE_MOUNTPOINT && CONFIG_FS_WRITABLE) || !CONFIG_DISABLE_PSEUDOFS_OPERATIONS) && CONFIG_NFILE_DESCRIPTORS > 0) @@ -998,7 +998,7 @@ Command Dependencies on Configuration Settings xd --- * NOTES: - 1. Because of hardware padding, the actual buffersize required for put and get + 1. Because of hardware padding, the actual MTU required for put and get operations size may be larger. 2. Special TFTP server start-up options will probably be required to permit creation of file for the correct operation of the put command. @@ -1331,9 +1331,11 @@ NSH-Specific Configuration Settings * CONFIG_NET_BROADCAST=y UDP broadcast support is needed. - * CONFIG_NET_BUFSIZE=650 (or larger) + * CONFIG_NET_ETH_MTU=650 (or larger) Per RFC2131 (p. 9), the DHCP client must be prepared to receive DHCP messages of up to 576 bytes (excluding Ethernet, IP, or UDP headers and FCS). + NOTE: Note that the actual MTU setting will depend upon the specific + link protocol. Here Ethernet is indicated. If CONFIG_NSH_ROMFSETC is selected, then the following additional configuration setting apply: diff --git a/nuttx/Documentation/NuttShell.html b/nuttx/Documentation/NuttShell.html index 886ae053c..939e7373c 100644 --- a/nuttx/Documentation/NuttShell.html +++ b/nuttx/Documentation/NuttShell.html @@ -2605,7 +2605,7 @@ nsh> <tr> <td><b><code>get</code></b></td> <td><code>CONFIG_NET</code> && <code>CONFIG_NET_UDP</code> && - <code>CONFIG_NFILE_DESCRIPTORS</code> > 0 && <code>CONFIG_NET_BUFSIZE</code> >= 558<sup>1</sup></td> + <code>CONFIG_NFILE_DESCRIPTORS</code> > 0 && <i>MTU</i> >= 558<sup>1</sup></td> <td><code>CONFIG_NSH_DISABLE_GET</code></td> </tr> <tr> @@ -2711,7 +2711,7 @@ nsh> <tr> <td><b><code>put</code></b></td> <td><code>CONFIG_NET</code> && <code>CONFIG_NET_UDP</code> && - <code>CONFIG_NFILE_DESCRIPTORS</code> > 0 && <code>CONFIG_NET_BUFSIZE</code> >= 558<sup>1,2</sup></td> + <code>CONFIG_NFILE_DESCRIPTORS</code> > 0 && <i>MTU</i> >= 558<sup>1,2</sup></td> <td><code>CONFIG_NSH_DISABLE_PUT</code></td> </tr> <tr> @@ -3254,10 +3254,12 @@ set FOOBAR ABC_${FOO}_${BAR} </td> </tr> <tr> - <td valign="top"><b><code>CONFIG_NET_BUFSIZE=650</code></b> (or larger)</td> + <td valign="top"><b><code>CONFIG_NET_ETH_MTU=650</code></b> (or larger)</td> <td> Per RFC2131 (p. 9), the DHCP client must be prepared to receive DHCP messages of up to 576 bytes (excluding Ethernet, IP, or UDP headers and FCS). + NOTE: Note that the actual MTU setting will depend upon the specific link protocol. + Here Ethernet is indicated. </td> </tr> </table></center> |