Correct some network-related configuration variable names. All *_MTU defines were changes to *_PKTSIZE gut that was not reflected in apps/

This commit is contained in:
Gregory Nutt 2018-09-14 07:06:06 -06:00
parent c5edf40542
commit 42e99d59ce
4 changed files with 4 additions and 4 deletions

View File

@ -2176,7 +2176,7 @@ examples/webserver
(as well as various other UDP-related
configuration settings).
CONFIG_NET_BROADCAST=y - UDP broadcast support is needed.
CONFIG_NET_ETH_MTU=650 - Per RFC2131 (p. 9), the DHCP client must be
CONFIG_NET_ETH_PKTSIZE=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).

View File

@ -63,7 +63,7 @@
****************************************************************************/
#define MAX_DEVNAME 8
#define IPFWD_BUFSIZE CONFIG_NET_TUN_MTU
#define IPFWD_BUFSIZE CONFIG_NET_TUN_PKTSIZE
#define NBYTES_PER_LINE 32
#define IPFWD_NPACKETS 3

View File

@ -132,7 +132,7 @@ required. These include:
(as well as various other UDP-related
configuration settings).
CONFIG_NET_BROADCAST=y UDP broadcast support is needed.
CONFIG_NET_ETH_MTU=650 The client must be prepared to receive
CONFIG_NET_ETH_PKTSIZE=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

View File

@ -1758,7 +1758,7 @@ NSH-Specific Configuration Settings
* CONFIG_NET_BROADCAST=y
UDP broadcast support is needed.
* CONFIG_NET_ETH_MTU=650 (or larger)
* CONFIG_NET_ETH_PKTSIZE=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