Lines Matching refs:to
6 to use for communication with the TCP/IP code:
12 to use the lwIP stack. It is quite similar to the BSD socket API. The
19 currently it is built on top of the sequential API. It is meant to
20 provide all functions needed to run socket API applications running
21 on other platforms (e.g. unix / windows etc.). However, due to limitations
49 Only since 1.3.0, if SYS_LIGHTWEIGHT_PROT is set to 1
50 and LWIP_ALLOW_MEM_FREE_FROM_OTHER_CONTEXT is set to 1,
59 The raw TCP/IP interface allows the application program to integrate
70 the raw TCP/IP interface are more difficult to understand. Still, this
83 argument. Also, in order to be able to keep program specific state,
91 Specifies the program specific state that should be passed to all
94 that will be passed to the callbacks.
99 The functions used for setting up connections is similar to that of
102 tcp_new() function. This PCB can then be either set to listen for new
103 incoming connections or be explicitly connected to another host.
113 Binds the pcb to a local IP address and port number. The IP address
114 can be specified as IP_ADDR_ANY in order to bind the connection to
117 If another connection is bound to the same port, the function will
122 Commands a pcb to start listening for incoming connections. When an
124 tcp_accept() function will be called. The pcb will have to be bound
125 to a local port with the tcp_bind() function.
128 the one passed as an argument to the function will be
136 passed as an argument to tcp_listen() will not be deallocated.
141 in the listen queue to the value specified by the backlog argument.
142 To use it, your need to set TCP_LISTEN_BACKLOG=1 in your lwipopts.h.
147 usually be called from the accept callback. This allows lwIP to perform
148 housekeeping tasks, such as allowing further incoming connections to be
165 Sets up the pcb to connect to the remote host and sends the
169 the connection to be properly setup. Instead, it will call the
184 TCP data is sent by enqueueing the data with a call to
185 tcp_write(). When the data is successfully transmitted to the remote
186 host, the application will be notified with a call to a specified
192 Enqueues the data pointed to by the argument dataptr. The length of
195 for the data to be copied into. If this flag is not given, no new memory
200 the PSH flag is set in the last segment created by this call to tcp_write.
209 The proper way to use this function is to call the function with at
220 host. The len argument passed to the callback function gives the
228 application has taken the data, it has to call the tcp_recved()
229 function to indicate that TCP can advertise increase the receive
237 arrives. The callback function will be passed a NULL pbuf to
239 there are no errors and the callback function is to return
255 as a method of waiting for memory to become available. For instance,
256 if a call to tcp_write() has failed because memory wasn't available,
257 the application may use the polling functionality to call tcp_write()
265 be called to poll the application. The interval is specified in
281 The pcb is deallocated by the TCP code after a call to tcp_close().
285 Aborts the connection by sending a RST (reset) segment to the remote
296 function to be called is set using the tcp_err() function.
301 The error callback function does not get the pcb passed to it as a
307 TCP provides a simple interface to the lower layers of the
309 to be called before any other TCP function is called. When the system
318 The UDP interface is similar to that of TCP, but due to the lower
324 pcb is not active until it has either been bound to a local address
325 or connected to a remote address.
334 Binds the pcb to a local address. The IP-address argument "ipaddr"
335 can be IP_ADDR_ANY to indicate that it should listen to any local IP
370 We can give you some idea on how to proceed when using the raw API.
383 to be called for easy configuration changes.
405 Doesn't do much, it should be called to handle future changes.
422 Adds your network interface to the netif_list. Allocate a struct
423 netif and pass a pointer to this structure as the first argument.
424 Give pointers to cleared ip_addr structures when using DHCP,
427 The init function pointer must point to a initialization function for
439 For ethernet drivers, the input function pointer must point to the lwip
462 The first thing you want to optimize is the lwip_standard_checksum()
466 There are C examples given in inet.c or you might want to
468 introduction to this subject.
480 buffer overflows are likely to occur.
486 to match your application and network.
488 For a production release it is recommended to set LWIP_STATS to 0.
490 high values to the memory options.
496 To achieve zero-copy on transmit, the data passed to the raw API must
501 This implies that PBUF_RAM/PBUF_POOL pbufs passed to raw-API send functions
506 PBUF_ROM-pbufs are just enqueued (as ROM-data is expected to never change).
508 Also, data passed to tcp_write without the copy-flag must not be changed!