2011-03-19 22:04:13 +01:00
|
|
|
netutils
|
|
|
|
|
^^^^^^^^
|
|
|
|
|
|
|
|
|
|
This directory contains most of the network applications contained
|
|
|
|
|
under the uIP-1.0 apps directory. As the uIP apps/README says,
|
|
|
|
|
these applications "are not all heavily tested." These uIP apps
|
|
|
|
|
include:
|
|
|
|
|
|
|
|
|
|
dhcpc - Dynamic Host Configuration Protocol (DHCP) client
|
|
|
|
|
resolv - uIP DNS resolver
|
|
|
|
|
smtp - Simple Mail Transfer Protocol (SMTP) client
|
|
|
|
|
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:
|
|
|
|
|
|
|
|
|
|
dhcpd - Dynamic Host Configuration Protocol (DHCP) server
|
|
|
|
|
tftpc - TFTP client
|
2012-01-30 22:29:59 +01:00
|
|
|
telnetd - TELNET server. This is the Telnet logic adapted from
|
|
|
|
|
uIP and generalized for use as the front end to any
|
|
|
|
|
shell. The telnet daemon creates sessions that are
|
|
|
|
|
"wrapped" as character devices and mapped to stdin,
|
|
|
|
|
stdout, and stderr. Now the telnet session can be
|
|
|
|
|
inherited by spawned tasks.
|
2011-06-02 01:09:29 +02:00
|
|
|
ftpc - FTP client
|
2011-03-19 22:04:13 +01:00
|
|
|
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).
|
