uIP 1.0 教程：嵌入式TCP/IP堆栈参考手册 - CSDN文库

5星 · 超过95%的资源需积分: 35 128 浏览量更新于2024-07-26 1 收藏 1.36MB PDF 举报

"uip-1.0-refman" 《uIP 1.0参考手册》是针对uIP嵌入式TCP/IP栈的英文使用指南，由Adam Dunkels编写，发布于2006年6月。uIP是一个轻量级的TCP/IP协议栈，专为资源有限的嵌入式系统设计。手册内容涵盖了uIP的主要控制循环、架构特定功能、内存管理、应用编程接口(API)、示例、协议实现、性能评估等多个方面。 1. uIP TCP/IP栈 - 引言：这部分介绍了uIP的基本概念，强调了它在小型设备上的适用性。 - TCP/IP通信：解释了如何在uIP中进行网络通信，包括TCP和UDP等协议的使用。 - 主控制循环：描述了uIP如何处理网络事件和数据包的接收与发送。 - 架构特定函数：讨论了根据具体硬件平台定制uIP功能的方法。 - 内存管理：说明了uIP如何高效地管理和分配内存资源，以适应嵌入式系统的限制。 2. 应用程序接口(API) - API详细介绍了uIP提供的接口，开发者可以利用这些接口创建网络应用程序。 3. 示例 - 提供了一些实际应用示例，帮助读者理解如何使用uIP进行开发。 4. 协议实现 - 这部分详述了uIP栈中包含的各种网络协议，如TCP、UDP、ICMP等的实现细节。 5. 性能 - 分析了uIP在不同条件下的性能表现，包括处理速度、内存占用等。 6. 模块索引、层次结构、数据结构和文件索引 - 这些章节提供了uIP模块、类层次结构、数据结构和文件的详细索引，方便开发者查找和引用相关代码。 7. 模块文档 - 对uIP中的各个模块进行了详细的文档化，包括protothreads（轻量级线程库）、应用、配置函数、初始化函数、设备驱动函数、应用函数、转换函数、设备驱动变量以及TCP/IP栈本身。通过这份参考手册，开发者可以获得全面的uIP知识，以便在嵌入式系统中有效地实现和优化网络功能。无论是新手还是有经验的开发者，都能从中受益，提升对uIP的理解和应用能力。

10 The uIP TCP/IP stack

1.7.4 Utilizing TCP Flow Control

This example shows a simple application that connects to a host, sends an HTTP request for a ﬁle and

downloads it to a slow device such a disk drive. This shows how to use the ﬂow control functions of uIP.

void example4_init(void) {

uip_ipaddr_t ipaddr;

uip_ipaddr(ipaddr, 192,168,0,1);

uip_connect(ipaddr, HTONS(80));

}

void example4_app(void) {

if(uip_connected() || uip_rexmit()) {

uip_send("GET /file HTTP/1.0\r\nServer:192.186.0.1\r\n\r\n",

48);

return;

}

if(uip_newdata()) {

device_enqueue(uip_appdata, uip_datalen());

if(device_queue_full()) {

uip_stop();

}

}

if(uip_poll() && uip_stopped()) {

if(!device_queue_full()) {

uip_restart();

}

}

}

When the connection has been established, an HTTP request is sent to the server. Since this is the only

data that is sent, the application knows that if it needs to retransmit any data, it is that request that should

be retransmitted. It is therefore possible to combine these two events as is done in the example.

When the application receives new data from the remote host, it sends this data to the device by using

the function device_enqueue(). It is important to note that this example assumes that this function copies

the data into its own buffers. The data in the uip_appdata buffer will be overwritten by the next incoming

packet.

If the device’s queue is full, the application stops the data from the remote host by calling the uIP function

uip_stop(). The application can then be sure that it will not receive any new data until uip_restart() is called.

The application polling event is used to check if the device’s queue is no longer full and if so, the data ﬂow

is restarted with uip_restart().

1.7.5 A Simple Web Server

This example shows a very simple ﬁle server application that listens to two ports and uses the port number

to determine which ﬁle to send. If the ﬁles are properly formatted, this simple application can be used as a

web server with static pages. The implementation follows.

struct example5_state {

char

*

dataptr;

unsigned int dataleft;

};

void example5_init(void) {

uip_listen(HTONS(80));

uip_listen(HTONS(81));

Generated on Mon Jun 12 11:56:02 2006 for uIP 1.0 by Doxygen

1.7 Examples 11

}

void example5_app(void) {

struct example5_state

*

s;

s = (struct example5_state)uip_conn->appstate;

if(uip_connected()) {

switch(uip_conn->lport) {

case HTONS(80):

s->dataptr = data_port_80;

s->dataleft = datalen_port_80;

break;

case HTONS(81):

s->dataptr = data_port_81;

s->dataleft = datalen_port_81;

break;

}

uip_send(s->dataptr, s->dataleft);

return;

}

if(uip_acked()) {

if(s->dataleft < uip_mss()) {

uip_close();

return;

}

s->dataptr += uip_conn->len;

s->dataleft -= uip_conn->len;

uip_send(s->dataptr, s->dataleft);

}

}

The application state consists of a pointer to the data that should be sent and the size of the data that is left

to send. When a remote host connects to the application, the local port number is used to determine which

ﬁle to send. The ﬁrst chunk of data is sent using

uip_send(). uIP makes sure that no more than MSS bytes

of data is actually sent, even though s->dataleft may be larger than the MSS.

The application is driven by incoming acknowledgments. When data has been acknowledged, new data

can be sent. If there is no more data to send, the connection is closed using uip_close().

1.7.6 Structured Application Program Design

When writing larger programs using uIP it is useful to be able to utilize the uIP API in a structured way.

The following example provides a structured design that has showed itself to be useful for writing larger

protocol implementations than the previous examples showed here. The program is divided into an uIP

event handler function that calls seven application handler functions that process new data, act on acknowl-

edged data, send new data, deal with connection establishment or closure events and handle errors. The

functions are called newdata(), acked(), senddata(), connected(), closed(), aborted(), and timedout(), and

needs to be written speciﬁcally for the protocol that is being implemented.

The uIP event handler function is shown below.

void example6_app(void) {

if(uip_aborted()) {

aborted();

}

if(uip_timedout()) {

timedout();

}

if(uip_closed()) {

closed();

}

Generated on Mon Jun 12 11:56:02 2006 for uIP 1.0 by Doxygen

1.7 Examples 13

s->textlen -= uip_conn->len;

s->textptr += uip_conn->len;

if(s->textlen == 0) {

switch(s->state) {

case STATE_HELLO:

s->state = STATE_WORLD;

s->textptr = "world!\n";

s->textlen = 7;

break;

case STATE_WORLD:

uip_close();

break;

}

}

}

static void senddata(void) {

struct example6_state

*

s = (struct example6_state

*

)uip_conn->appstate;

if(s->textlen > 0) {

uip_send(s->textptr, s->textlen);

}

}

The application state consists of a "state" variable, a "textptr" pointer to a text message and the "textlen"

length of the text message. The "state" variable can be either "STATE_WAITING", meaning that the

application is waiting for data to arrive from the network, "STATE_HELLO", in which the application is

sending the "Hello" part of the message, or "STATE_WORLD", in which the application is sending the

"world!" message.

The application does not handle errors or connection closing events, and therefore the aborted(), timedout()

and closed() functions are implemented as empty functions.

The connected() function will be called when a connection has been established, and in this case sets the

"state" variable to be "STATE_WAITING" and the "textlen" variable to be zero, indicating that there is no

message to be sent out.

When new data arrives from the network, the newdata() function will be called by the event handler func-

tion. The newdata() function will check if the connection is in the "STATE_WAITING" state, and if so

switches to the "STATE_HELLO" state and registers a 6 byte long "Hello " message with the connection.

This message will later be sent out by the senddata() function.

The acked() function is called whenever data that previously was sent has been acknowleged by the receiv-

ing host. This acked() function ﬁrst reduces the amount of data that is left to send, by subtracting the length

of the previously sent data (obtained from "uip_conn → len") from the "textlen" variable, and also adjusts

the "textptr" pointer accordingly. It then checks if the "textlen" variable now is zero, which indicates that all

data now has been successfully received, and if so changes application state. If the application was in the

"STATE_HELLO" state, it switches state to "STATE_WORLD" and sets up a 7 byte "world!\n" message

to be sent. If the application was in the "STATE_WORLD" state, it closes the connection.

Finally, the senddata() function takes care of actually sending the data that is to be sent. It is called by

the event handler function when new data has been received, when data has been acknowledged, when

a new connection has been established, when the connection is polled because of inactivity, or when a

retransmission should be made. The purpose of the senddata() function is to optionally format the data that

is to be sent, and to call the

uip_send() function to actually send out the data. In this particular example,

the function simply calls

uip_send() with the appropriate arguments if data is to be sent, after checking if

data should be sent out or not as indicated by the "textlen" variable.

It is important to note that the senddata() function never should affect the application state; this should only

be done in the acked() and newdata() functions.

Generated on Mon Jun 12 11:56:02 2006 for uIP 1.0 by Doxygen

14 The uIP TCP/IP stack

1.8 Protocol Implementations

The protocols in the TCP/IP protocol suite are designed in a layered fashion where each protocol performs

a speciﬁc function and the interactions between the protocol layers are strictly deﬁned. While the layered

approach is a good way to design protocols, it is not always the best way to implement them. In uIP, the

protocol implementations are tightly coupled in order to save code space.

This section gives detailed information on the speciﬁc protocol implementations in uIP.

1.8.1 IP — Internet Protocol

When incoming packets are processed by uIP, the IP layer is the ﬁrst protocol that examines the packet.

The IP layer does a few simple checks such as if the destination IP address of the incoming packet matches

any of the local IP address and veriﬁes the IP header checksum. Since there are no IP options that are

strictly required and because they are very uncommon, any IP options in received packets are dropped.

1.8.1.1 IP Fragment Reassembly

IP fragment reassembly is implemented using a separate buffer that holds the packet to be reassembled. An

incoming fragment is copied into the right place in the buffer and a bit map is used to keep track of which

fragments have been received. Because the ﬁrst byte of an IP fragment is aligned on an 8-byte boundary,

the bit map requires a small amount of memory. When all fragments have been reassembled, the resulting

IP packet is passed to the transport layer. If all fragments have not been received within a speciﬁed time

frame, the packet is dropped.

The current implementation only has a single buffer for holding packets to be reassembled, and therefore

does not support simultaneous reassembly of more than one packet. Since fragmented packets are uncom-

mon, this ought to be a reasonable decision. Extending the implementation to support multiple buffers

would be straightforward, however.

1.8.1.2 Broadcasts and Multicasts

IP has the ability to broadcast and multicast packets on the local network. Such packets are addressed

to special broadcast and multicast addresses. Broadcast is used heavily in many UDP based protocols

such as the Microsoft Windows ﬁle-sharing SMB protocol. Multicast is primarily used in protocols used

for multimedia distribution such as RTP. TCP is a point-to-point protocol and does not use broadcast or

multicast packets. uIP current supports broadcast packets as well as sending multicast packets. Joining

multicast groups (IGMP) and receiving non-local multicast packets is not currently supported.

1.8.2 ICMP — Internet Control Message Protocol

The ICMP protocol is used for reporting soft error conditions and for querying host parameters. Its main

use is, however, the echo mechanism which is used by the "ping" program.

The ICMP implementation in uIP is very simple as itis restricted to only implement ICMP echo messages.

Replies to echo messages are constructed by simply swapping the source and destination IP addresses of

incoming echo requests and rewriting the ICMP header with the Echo-Reply message type. The ICMP

checksum is adjusted using standard techniques (see RFC1624).

Since only the ICMP echo message is implemented, there is no support for Path MTU discovery or ICMP

redirect messages. Neither of these is strictly required for interoperability; they are performance enhance-

ment mechanisms.

Generated on Mon Jun 12 11:56:02 2006 for uIP 1.0 by Doxygen

剩余260页未读，继续阅读

dyyy4

粉丝: 29
资源: 19

最新资源