01.06.2013 Views

IPC@CHIP Documentation - SC12 @CHIP-RTOS V1.10

IPC@CHIP Documentation - SC12 @CHIP-RTOS V1.10

IPC@CHIP Documentation - SC12 @CHIP-RTOS V1.10

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Comments<br />

unsigned long ipReasmOKs; // number of fragments reassembled<br />

unsigned long ipReasmFails; // number of failures in IP reassembly<br />

unsigned long ipFragOKs; // number of datagrams fragmented here<br />

unsigned long ipFragFails; // no. pkts unable to be fragmented here<br />

unsigned long ipFragCreates; // number of IP fragments created here<br />

unsigned long ipRoutingDiscards;<br />

} IpMib;<br />

These structures are only available in <strong>@CHIP</strong>-<strong>RTOS</strong> versions which contain the SNMP option. A SNMP agent is not part of<br />

the <strong>@CHIP</strong>-<strong>RTOS</strong>. But if a user is able to implement an agent based on the TCP/IP API, they need access to these internal<br />

TCP/IP variables.<br />

Related Topics<br />

Top of list<br />

Index page<br />

API function API_SNMP_GET - Get internal TCP/IP SNMP variables<br />

IpUserCallbackInfo<br />

Comments<br />

A structure of this type is passed as an input parameter to an IP user callback handler.<br />

struct IpUserCallbackInfo<br />

{<br />

int size; // Size of this struct<br />

unsigned long srcAddr; // Source IP Address (in network byte order)<br />

unsigned long destAddr; // Destination IP Address (in network byte order))<br />

unsigned int srcPort; // Source Port (in network byte order)<br />

unsigned int destPort; // Destination Port (in network byte order)<br />

unsigned char protocol; // Protocol (see list below)<br />

int fragmented; // 0: it is an unfragmented package, 1: it is a fragment<br />

unsigned int dataLength; // Length of the data in the IP package<br />

// (only available if package is not fragmented!)<br />

void far * dataPtr; // Pointer to the IP data<br />

// (only available if package is not fragmented!)<br />

} IpCallbackUserInfo_t;<br />

Protocol types enumerated by the protocol member are coded as follows:<br />

1 ICMP (Internet Control Management Protocol)<br />

2 IGMP (Internet Group Management Protocol)<br />

6 TCP (Transmission Control Protocol)<br />

17 UDP (User Datagram Protocol)<br />

Note: The IP callback function will be called before defragmenting fragmented IP packages. So if we receive a fragmented<br />

package, the IP callback will be called for every received fragment.<br />

Related Topics<br />

Top of list<br />

Index page<br />

API function IP_USER_CB - Install IP callback function<br />

Packet_Count<br />

Page 169 / 400

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!