diff --git a/Documentation/NuttShell.html b/Documentation/NuttShell.html index 4cc4c41255e..74170efee38 100644 --- a/Documentation/NuttShell.html +++ b/Documentation/NuttShell.html @@ -8,7 +8,7 @@

NuttShell (NSH)

-

Last Updated: June 08, 2009

+

Last Updated: July 06, 2010

@@ -2099,6 +2099,23 @@ nsh> Description + CONFIG_NET=y + + Of course, networking must be enabled. + + + + CONFIG_NSOCKET_DESCRIPTORS + + And, of course, you must allocate some socket descriptors. + + + + CONFIG_NET_TCP=y + + TCP/IP support is required for telnet (as well as various other TCP-related configuration settings). + + CONFIG_EXAMPLES_NSH_IOBUFFER_SIZE Determines the size of the I/O buffer to use for sending/ @@ -2139,6 +2156,49 @@ nsh> +

+ If you use DHCPC, then some special configuration network options are + required. These include: +

+ +
+ + + + + + + + + + + + + + + + + + + + + + + + +
ConfigurationDescription
CONFIG_NET=y + Of course, networking must be enabled. +
CONFIG_NSOCKET_DESCRIPTORS + And, of course, you must allocate some socket descriptors. +
CONFIG_NET_UDP=y + UDP support is required for DHCP (as well as various other UDP-related configuration settings). +
CONFIG_NET_BROADCAST=y + UDP broadcast support is needed. +
CONFIG_NET_BUFSIZE=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). +
+

If CONFIG_EXAMPLES_NSH_ROMFSETC is selected, then the following additional configuration setting apply: diff --git a/examples/README.txt b/examples/README.txt index 9b61d77b05b..ad301dbab20 100644 --- a/examples/README.txt +++ b/examples/README.txt @@ -22,6 +22,14 @@ examples/dhcpd make -f Makefile.host NuttX configuration settings: + + CONFIG_NET=y - Of course + CONFIG_NSOCKET_DESCRIPTORS - And, of course, you must allocate some + socket descriptors. + CONFIG_NET_UDP=y - UDP support is required for DHCP + (as well as various other UDP-related + configuration settings) + CONFIG_NET_BROADCAST=y - UDP broadcast support is needed. CONFIG_EXAMPLE_DHCPD_NOMAC - (May be defined to use software assigned MAC) CONFIG_EXAMPLE_DHCPD_IPADDR - Target IP address @@ -353,6 +361,21 @@ examples/uip CONFIG_EXAMPLE_UIP_NETMASK - Network mask CONFIG_EXAMPLE_UIP_DHCPC - Select to get IP address via DHCP + If you use DHCPC, then some special configuration network options are + required. These include: + + CONFIG_NET=y - Of course + CONFIG_NSOCKET_DESCRIPTORS - And, of course, you must allocate some + socket descriptors. + CONFIG_NET_UDP=y - UDP support is required for DHCP + (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 + (or larger) prepared to receive DHCP messages of up to + 576 bytes (excluding Ethernet, IP, or UDP + headers and FCS). + Other configuration items apply also to the selected webserver net utility. Additional relevant settings for the uIP webserver net utility are: diff --git a/examples/nsh/README.txt b/examples/nsh/README.txt index e663071fcaf..f4e1da9aea1 100644 --- a/examples/nsh/README.txt +++ b/examples/nsh/README.txt @@ -893,6 +893,16 @@ NSH-Specific Configuration Settings must be defined. If CONFIG_EXAMPLES_NSH_TELNET is selected, then there some other configuration settings that apply: + * CONFIG_NET=y + Of course, networking must be enabled + + * CONFIG_NSOCKET_DESCRIPTORS + And, of course, you must allocate some socket descriptors. + + * CONFIG_NET_TCP=y + TCP/IP support is required for telnet (as well as various other TCP-related + configuration settings). + * CONFIG_EXAMPLES_NSH_IOBUFFER_SIZE Determines the size of the I/O buffer to use for sending/ receiving TELNET commands/reponses @@ -914,6 +924,26 @@ NSH-Specific Configuration Settings Set if your ethernet hardware has no built-in MAC address. If set, a bogus MAC will be assigned. + If you use DHCPC, then some special configuration network options are + required. These include: + + * CONFIG_NET=y + Of course, networking must be enabled + + * CONFIG_NSOCKET_DESCRIPTORS + And, of course, you must allocate some socket descriptors. + + * CONFIG_NET_UDP=y + UDP support is required for DHCP (as well as various other UDP-related + configuration settings) + + * CONFIG_NET_BROADCAST=y + UDP broadcast support is needed. + + * CONFIG_NET_BUFSIZE=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). + If CONFIG_EXAMPLES_NSH_ROMFSETC is selected, then the following additional configuration setting apply: diff --git a/examples/nsh/nsh_telnetd.c b/examples/nsh/nsh_telnetd.c index 546b88ce77d..d9a5902171b 100644 --- a/examples/nsh/nsh_telnetd.c +++ b/examples/nsh/nsh_telnetd.c @@ -60,6 +60,7 @@ #include #include #if defined(CONFIG_EXAMPLES_NSH_DHCPC) +# include # include #endif diff --git a/netutils/README b/netutils/README index a28270715ea..e4b05eb2138 100644 --- a/netutils/README +++ b/netutils/README @@ -13,6 +13,9 @@ include: webclient - HTTP web client webserver - HTTP web server +You may find additional information on these apps in the uIP forum +accessible through: http://www.sics.se/~adam/uip/index.php/Main_Page + Additional applications that were not part of uIP (but which are highly influenced by uIP) include: @@ -21,4 +24,16 @@ highly influenced by uIP) include: thttpd - This is a port of Jef Poskanzer's THTTPD HTPPD server. See http://acme.com/software/thttpd/. +If you use DHCPC/D, then some special configuration network options are +required. These include: + CONFIG_NET=y Of course + CONFIG_NSOCKET_DESCRIPTORS And, of course, you must allocate some + socket descriptors. + CONFIG_NET_UDP=y UDP support is required for DHCP + (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 + (or larger) DHCP messages of up to 576 bytes (excluding + Ethernet, IP, or UDP headers and FCS).