426cc840d8
nsh> ping 192.168.31.162 PING 192.168.31.162 56 bytes of data 56 bytes from 192.168.31.162: icmp_seq=0 time=8 ms 56 bytes from 192.168.31.162: icmp_seq=1 time=27 ms 56 bytes from 192.168.31.162: icmp_seq=2 time=17 ms 56 bytes from 192.168.31.162: icmp_seq=3 time=14 ms 56 bytes from 192.168.31.162: icmp_seq=4 time=16 ms 56 bytes from 192.168.31.162: icmp_seq=5 time=14 ms 56 bytes from 192.168.31.162: icmp_seq=6 time=8 ms 56 bytes from 192.168.31.162: icmp_seq=7 time=87 ms WARNING: Received after timeout 56 bytes from 192.168.31.162: icmp_seq=8 time=1003 ms 56 bytes from 192.168.31.162: icmp_seq=8 time=6 ms 56 bytes from 192.168.31.162: icmp_seq=9 time=5 ms 10 packets transmitted, 11 received, 4294967287% packet loss, time 10011 ms Signed-off-by: zhouliang3 <zhouliang3@xiaomi.com> |
||
|---|---|---|
| .. | ||
| chat | ||
| cjson | ||
| codecs | ||
| dhcp6c | ||
| dhcpc | ||
| dhcpd | ||
| discover | ||
| esp8266 | ||
| ftpc | ||
| ftpd | ||
| iperf | ||
| libcurl4nx | ||
| mqttc | ||
| netcat | ||
| netinit | ||
| netlib | ||
| ntpclient | ||
| ping | ||
| pppd | ||
| rexec | ||
| rexecd | ||
| smtp | ||
| telnetc | ||
| telnetd | ||
| tftpc | ||
| thttpd | ||
| usrsock_rpmsg | ||
| wakeonlan | ||
| webclient | ||
| webserver | ||
| xmlrpc | ||
| .gitignore | ||
| Make.defs | ||
| Makefile | ||
| README.md | ||
Network Utilities
Contents
- uIP Applications
- Other Network Applications
- Tips for Using Telnetd
- Tips for Using DHCPC
uIP Applications
This directory contains most of the network applications contained under the
uIP-1.0 apps directory. As the uIP apps/README.md says, these applications
are not all heavily tested. These uIP-based apps include:
-
dhcpc– Dynamic Host Configuration Protocol (DHCP) client. Seeapps/include/netutils/dhcpc.hfor interface information. -
smtp– Simple Mail Transfer Protocol (SMTP) client. Seeapps/include/netutils/smtp.hfor interface information. -
webclient– HTTP web client. Seeapps/include/netutils/webclient.hfor interface information. -
webserver– HTTP web server. Seeapps/include/netutils/httpd.hfor interface information.
You may find additional information on these apps in the uIP forum accessible through: http://www.sics.se/~adam/uip/index.php/Main_Page. Some of these (such as the uIP web server) have grown some additional functionality due primarily to NuttX user contributions.
Other Network Applications
Additional applications that were not part of uIP (but which are highly influenced by uIP) include:
-
dhcpd– Dynamic Host Configuration Protocol (DHCP) server. Seeapps/include/netutils/dhcpd.hfor interface information. -
discover– This daemon is useful for discovering devices in local networks, especially with DHCP configured devices. It listens for UDP broadcasts which also can include a device class so that groups of devices can be discovered. It is also possible to address all classes with a kind of broadcast discover. (Contributed by Max Holtzberg). -
esp8266– An ESP8266 networking layer contributed by Pierre-Noel Bouteville. -
json– cJSON is an ultra-lightweight, portable, single-file, simple-as-can-be ANSI-C compliant JSON parser, under MIT license. Embeddable Lightweight XML-RPC Server discussed at http://www.drdobbs.com/web-development/an-embeddable-lightweight-xml-rpc-server/184405364.This code was taken from http://sourceforge.net/projects/cjson/ and adapted for NuttX by Darcy Gong.
-
tftpc– TFTP client. Seeapps/include/netutils/tftp.hfor interface information. -
telnetc– This is a port of libtelnet to NuttX. This is a public domain Telnet client library available from https://github.com/seanmiddleditch/libtelnet modified for use with NuttX. Original Authors: Sean Middleditch sean@sourcemud.org, Jack Kelly endgame.dos@gmail.com and Katherine Flavel kate@elide.org -
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 tostdin,stdoutandstderr. Now the telnet session can be inherited by spawned tasks. -
ftpc– FTP client. Seeapps/include/netutils/ftpc.hfor interface information. -
ftpd– FTP server. Seeapps/include/netutils/ftpd.hfor interface information. -
ntpclient– This is a fragmentary NTP client. It neither well-tested nor mature nor complete at this point in time. -
thttpd– This is a port of Jef Poskanzer's THTTPD HTPPD server. See http://acme.com/software/thttpd/ for general THTTPD information. Seeapps/include/netutils/thttpd.hfor interface information. Applications using thisthttpdwill need to provide the following definitions in thedefconfigfile to select the appropriatenetutilslibraries:CONFIG_NETUTILS_NETLIB=y CONFIG_NETUTILS_THTTPD=y -
xmlrpc– The Embeddable Lightweight XML-RPC Server discussed at http://www.drdobbs.com/web-development/an-embeddable-lightweight-xml-rpc-server/184405364 -
ping– This is an unfinished implementation of ping and ping6 using raw sockets. It is not yet hooked into the configuration or build systems.Current
ping/ping6logic in NSH makes illegal calls into the OS in order to implementping/ping6. One correct implementation would be to use raw sockets to implementping/ping6as a user application. This is a first cut at such an implementation.
Tips for Using Telnetd
Telnetd is set up to be the front end for a shell. The primary use of Telnetd in
NuttX is to support the NuttShell (NSH) Telnet front end. See
apps/include/netutils/telnetd.h for information about how to incorporate
Telnetd into your custom applications.
To enable and link the Telnetd daemon, you need to include the following in in your defconfig file:
CONFIG_NETUTILS_NETLIB=y
CONFIG_NETUTILS_TELNETD=y
Also if the Telnet console is enabled, make sure that you have the following set in the NuttX configuration file or else the performance will be very bad (because there will be only one character per TCP transfer):
CONFIG_STDIO_BUFFER_SIZE– Some value>= 64.CONFIG_STDIO_LINEBUFFER=y– Since Telnetd is line oriented, line buffering is optimal.
Tips for Using DHCPC
If you use DHCPC/D, then some special configuration network options are required. These include:
CONFIG_NET=yCONFIG_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_ETH_PKTSIZE=650or larger. The client must be prepared to receive DHCP messages of up to576bytes (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.