The Network Dual-Stack Component contains services, protocol sockets, and physical communication interfaces for creating IPv4 and IPv6 networking applications.
Network Overview
The various services provide program templates for common networking tasks.
- The HTTP Server supports static and dynamic page content using scripting, AJAX and SOAP technologies. Web resource files are accessed either via the File System (for component Web Server) or are directly stored in ROM (for component Compact Web Server).
- FTP server/client and TFTP server/client are used for file transfer. TFTP supports only file upload and download and is typically used for boot-loading remote devices in a closed LAN. It has very low memory requirements. FTP provides full file access including sub-directories, log-in and a set of manipulation commands.
- The Telnet Server realizes a simple Command Line Interface (CLI) over an IP network.
- Devices are often monitored using the Simple Network Management Protocol (SNMP). The SNMP Agent helps to report vital information of a device to the network manager.
- The DNS Client resolves domain names like www.arm.com to the respective IP address. It makes use of a freely configurable name server.
- The SNTP Client synchronizes clocks and enables a device to get an accurate time signal over the data network.
- The SMTP Client helps you to send out for example status updates or alerts via e-mail to freely configurable e-mail addresses.
All services rely on a network socket for communication. The Network Component supports these sockets:
- TCP is a connection-oriented, reliable full-duplex protocol. This means that packets delivered using TCP are error-checked and delivered in the right order.
- UDP is a transaction-oriented and stateless protocol. Data streaming or time-critical applications commonly use UDP. With UDP you can multicast a datagram to a group of devices.
- The BSD Socket API is a programming interface, which implements a standard Berkeley Socket communication interface (using TCP and UDP sockets for communication).
The physical interface can be either Ethernet or a serial connection.
- Ethernet Interface is widely used for connecting local area networks (LAN). It can utilize different media as means of transmission.
- The serial connection supports two different protocols:
- The SLIP Interface implements the Internet Protocol over a serial connection.
- The PPP Interface connects two network devices directly and provides authentication.
A driver provides provides the interface to the microcontroller peripherals or external components (for example an external PHY chip).
- For Ethernet an Ethernet MAC and an Ethernet PHY is required.
- PPP or SLIP interfaces use either a UART or a Modem.
The Network CORE is available in a Debug variant with extensive diagnostic messages. The Release variant omits this diagnostic information.
A list of RFCs that are currently implemented in the dual-stack version of the Network DS Component is also available.
Documentation
This user's guide contains the following chapters:
Revision History
Version | Description |
V7.0.0 (beta 2) |
- added Stateless Address Auto Configuration (SLAAC)
- added IPv6 FTP extensions in FTP server and FTP client
- added MIME type ".pdf" in HTTP server supported file types
- added netCGI_ContentType() function for custom MIME types
- added system configuration check in netInitialize(), signal NET_ERROR_CONFIG on error
- added system created network Core and interface threads in a library
- added mutex protection to network API functions, these functions are now thread-safe
- added adaptive time polling in ETH thread when ETH driver is used in polling mode
- updated dynamic port range in TCP and UDP sockets to use IANA recommendation (49152 - 65535)
- updated to provide full path for FTP server user access control
- corrected "frame too short" error in HTTP server when processing fragmented POST requests
- corrected application build problem when using PPP interface
- corrected bug in processing router advertisement message
- corrected vulnerability to Spank Attack and Spoofed RST packets
- corrected IPv6 receive address for loop-back interface
|
V7.0.0 (beta) |
- Initial release of dual-stack (IPv4 and IPv6) version of Network Component
- Incompatible API to version 6.x (refer to Migration)
- Added RFC_list
- This Pack contains example projects for development boards: MCB1800, MCBSTM32F200, MCBSTM32F400
|