# ICMP Component

The ICMP component is used to facilitate ICMP communications. It can act both as a client and a server and can communicate with any number of hosts simultaneously. It also can generate and receive broadcast packets.

## Syntax

```text
nsoftware.IPWorks.ICMP
```

## Remarks

The interface of the component is similar to the interface of TCPClient, only it is much simpler. The component is activated/deactivated by using the [Active](#active-property-icmp-component) property. This property enables or disables the sending or receiving of data. Data can be sent in the same way as TCPClient, using the [Send](#send-method-icmp-component) method and *Text* parameter. The destination is specified using the [RemoteHost](#remotehost-property-icmp-component) property. The component automatically creates an ICMP header containing [MessageType](#messagetype-property-icmp-component), [MessageSubType](#messagesubtype-property-icmp-component), and a checksum for the message.

If the [UseConnection](#UseConnection) configuration setting is set to True, then a local association is created with the remote host. Otherwise, the component can receive datagrams (packets) from any host and can send datagrams to any host. Packets can be broadcast on the local net by setting the destination to 255.255.255.255.

Inbound data is received through the [DataIn](#datain-event-icmp-component) event.

The operation of the component is almost completely asynchronous. All the calls, except the ones that deal with domain name resolution, operate through Windows messages (no blocking calls). The gain in performance is considerable when compared with using blocking calls.

## Property List

*The following is the full list of the properties of the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [AcceptData](#acceptdata-property-icmp-component) | This property indicates whether data reception is currently enabled. |
| [Active](#active-property-icmp-component) | This property indicates whether the component is active. |
| [DontRoute](#dontroute-property-icmp-component) | If this property is set to True, it forces the socket to send data directly to the interface (no routing). |
| [LocalHost](#localhost-property-icmp-component) | The name of the local host or user-assigned IP interface through which connections are initiated or accepted. |
| [MessageSubType](#messagesubtype-property-icmp-component) | This property is the subtype of the ICMP message (part of the ICMP header). |
| [MessageType](#messagetype-property-icmp-component) | This property includes the type of the ICMP message (part of the ICMP header). |
| [RemoteHost](#remotehost-property-icmp-component) | This property includes the address of the RemoteHost. Domain names are resolved to IP addresses. |
| [Timeout](#timeout-property-icmp-component) | This property specifies the timeout for the component. |
| [TimeToLive](#timetolive-property-icmp-component) | This property includes the time-to-live (TTL) value for the ICMP packets sent by the component. |

## Method List

*The following is the full list of the methods of the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [Activate](#activate-method-icmp-component) | This method enables sending and receiving of data. |
| [Config](#config-method-icmp-component) | Sets or retrieves a configuration setting. |
| [Deactivate](#deactivate-method-icmp-component) | This method disables sending and receiving of data. |
| [DoEvents](#doevents-method-icmp-component) | This method processes events from the internal message queue. |
| [PauseData](#pausedata-method-icmp-component) | This method pauses data reception. |
| [ProcessData](#processdata-method-icmp-component) | This method reenables data reception after a call to [PauseData](#pausedata-method-icmp-component) . |
| [Reset](#reset-method-icmp-component) | This method will reset the component. |
| [ResolveRemoteHost](#resolveremotehost-method-icmp-component) | This method resolves the hostname in [RemoteHost](#remotehost-property-icmp-component) to an IP address. |
| [Send](#send-method-icmp-component) | This method sends data to the remote host. |
| [SendBytes](#sendbytes-method-icmp-component) | This method sends data to the remote host. |
| [SendText](#sendtext-method-icmp-component) | This method sends data to the remote host. |

## Event List

*The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [DataIn](#datain-event-icmp-component) | This event is fired when a new ICMP messages come in. |
| [Error](#error-event-icmp-component) | Fired when information is available about errors during data delivery. |
| [ReadyToSend](#readytosend-event-icmp-component) | This event is fired when the component is ready to send data. |

## Config Settings

*The following is a list of config settings for the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [DelayHostResolution](#DelayHostResolution) | Whether the hostname is resolved when RemoteHost is set. |
| [DontFragment](#DontFragment) | Whether the DontFragment control flag is set. |
| [IcmpDllTimeout](#IcmpDllTimeout) | The timeout for the component when using the icmp.dll. |
| [MaxMessageSize](#MaxMessageSize) | The maximum length of the messages that can be received. |
| [MulticastTTL](#MulticastTTL) | The time to live (TTL) value for multicast ICMP packets sent by the component. |
| [ReceiveAllMode](#ReceiveAllMode) | Enables a socket to receive all IPv4 or IPv6 packets on the network. |
| [TimeoutInMilliseconds](#TimeoutInMilliseconds) | The timeout is treated as milliseconds. |
| [UseConnection](#UseConnection) | Determines whether to use a connected socket. |
| [UseICMPDLL](#UseICMPDLL) | Use the icmp.dll included on Windows Systems. |
| [UseIPHLPDLL](#UseIPHLPDLL) | Use the iphlpapi.dll included on Windows Systems. |
| [UseIPv6](#UseIPv6) | Whether to use IPv6. |
| [AbsoluteTimeout](#AbsoluteTimeout) | Determines whether timeouts are inactivity timeouts or absolute timeouts. |
| [FirewallData](#FirewallData) | Used to send extra data to the firewall. |
| [InBufferSize](#InBufferSize) | The size in bytes of the incoming queue of the socket. |
| [OutBufferSize](#OutBufferSize) | The size in bytes of the outgoing queue of the socket. |
| [BuildInfo](#BuildInfo) | Information about the product's build. |
| [GUIAvailable](#GUIAvailable) | Whether or not a message loop is available for processing events. |
| [LicenseInfo](#LicenseInfo) | Information about the current license. |
| [MaskSensitiveData](#MaskSensitiveData) | Whether sensitive data is masked in log messages. |
| [UseInternalSecurityAPI](#UseInternalSecurityAPI) | Whether or not to use the system security libraries or an internal implementation. |

# AcceptData Property ([ICMP](#icmp-component) Component)

This property indicates whether data reception is currently enabled.

## Syntax

```text
public bool AcceptData { get; }
```

## Default Value

True

## Remarks

This property indicates whether data reception is currently enabled. When *false*, data reception is disabled and the [DataIn](#datain-event-icmp-component) event will not fire. Use the [PauseData](#pausedata-method-icmp-component) and [ProcessData](#processdata-method-icmp-component) methods to pause and resume data reception.

This property is read-only and not available at design time.

# Active Property ([ICMP](#icmp-component) Component)

This property indicates whether the component is active.

## Syntax

```text
public bool Active { get; }
```

## Default Value

False

## Remarks

This property indicates whether the component is currently active and can send or receive data.

If the [UseConnection](#UseConnection) configuration setting is set to *true*, then a local association (connection) to the remote host also is created. Use the [Activate](#activate-method-icmp-component) and [Deactivate](#deactivate-method-icmp-component) methods to control whether the component is active.

This property is read-only and not available at design time.

# DontRoute Property ([ICMP](#icmp-component) Component)

If this property is set to True, it forces the socket to send data directly to the interface (no routing).

## Syntax

```text
public bool DontRoute { get; set; }
```

## Default Value

False

## Remarks

If this property is set to True, it forces the socket to send data directly to the interface (no routing). Normally, IP sockets send packets of data through routers and gateways until they reach the final destination. If this property is set to True, then data will be delivered on the local subnet only.

This property is not available at design time.

# LocalHost Property ([ICMP](#icmp-component) Component)

The name of the local host or user-assigned IP interface through which connections are initiated or accepted.

## Syntax

```text
public string LocalHost { get; set; }
```

## Default Value

""

## Remarks

This property contains the name of the local host as obtained by the *gethostname()* system call, or if the user has assigned an IP address, the value of that address.

In multihomed hosts (machines with more than one IP interface) setting LocalHost to the IP address of an interface will make the component initiate connections (or accept in the case of server components) only through that interface. It is recommended to provide an IP address rather than a hostname when setting this property to ensure the desired interface is used.

If the component is connected, the LocalHost property shows the IP address of the interface through which the connection is made in internet dotted format (aaa.bbb.ccc.ddd). In most cases, this is the address of the local host, except for multihomed hosts (machines with more than one IP interface).

NOTE: LocalHost is not persistent. You must always set it in code, and never in the property window.

# MessageSubType Property ([ICMP](#icmp-component) Component)

This property is the subtype of the ICMP message (part of the ICMP header).

## Syntax

```text
public int MessageSubType { get; set; }
```

## Default Value

0

## Remarks

This property contains the subtype of the ICMP message (part of the ICMP header). The ICMP message subtype (also referred to as "code") is a byte value representing the message subclass. Its meaning is associated with the [MessageType](#messagetype-property-icmp-component).

Types and subtypes of ICMP messages are defined in the various internet RFCs and other documentation associated with Transmission Control Protocol (TCP)/IP.

# MessageType Property ([ICMP](#icmp-component) Component)

This property includes the type of the ICMP message (part of the ICMP header).

## Syntax

```text
public int MessageType { get; set; }
```

## Default Value

0

## Remarks

This property contains the type of the ICMP message (part of the ICMP header). The ICMP message type is a byte value representing the message class. The message type defines the structure and meaning of the message data assigned to *Text* parameter of the [Send](#send-method-icmp-component) method.

Types for ICMP messages are defined in the various internet RFCs and other documentation associated with Transmission Control Protocol (TCP/IP). The following are a few examples of ICMP message types:

|  |  |
| --- | --- |
| 0 | Echo reply ("ping" reply). |
| 3 | Destination unreachable. |
| 4 | Source quench. |
| 5 | Redirect (change a route). |
| 8 | Echo request ("ping" request). |
| 11 | Time exceeded for datagram. |
| 12 | Parameter problem on datagram. |
| 13 | Timestamp request. |
| 14 | Timestamp reply. |
| 17 | Address mask request. |
| 18 | Address mask reply. |

# RemoteHost Property ([ICMP](#icmp-component) Component)

This property includes the address of the RemoteHost. Domain names are resolved to IP addresses.

## Syntax

```text
public string RemoteHost { get; set; }
```

## Default Value

""

## Remarks

This property specifies the IP address (IP number in dotted internet format) or the domain name of the remote host.

If this property is set to 255.255.255.255, the component broadcasts data on the local subnet.

If this property is set to a domain name, a DNS request is initiated. Upon successful termination of the request, the property is set to the corresponding address. If the search is not successful, the component throws an exception.

If [UseConnection](#UseConnection) is True, this property must be set before the component is activated ([Active](#active-property-icmp-component) is set to True).

# Timeout Property ([ICMP](#icmp-component) Component)

This property specifies the timeout for the component.

## Syntax

```text
public int Timeout { get; set; }
```

## Default Value

0

## Remarks

If the Timeout property is set to 0, all operations return immediately, potentially failing with an *WOULDBLOCK* error if data cannot be sent or received immediately.

If Timeout is set to a positive value, the component will automatically retry each operation that otherwise would result in a *WOULDBLOCK* error for a maximum of Timeout seconds.

The component will use [DoEvents](#doevents-method-icmp-component) to enter an efficient wait loop during any potential waiting period, making sure that all system events are processed immediately as they arrive. This ensures that the host application does not freeze and remains responsive.

If Timeout expires, and the operation is not yet complete, the component throws an exception.

NOTE: By default, all timeouts are *inactivity timeouts*, that is, the timeout period is extended by Timeout seconds when any amount of data is successfully sent or received.

The default value for the Timeout property is 0 (asynchronous operation).

NOTE: When a communication component behaves asynchronously in .NET, some events can fire from the background threads used to process socket IO. This can cause problems in GUI applications in which the logic inside an asynchronous event interacts with the GUI. In .NET, most GUI controls will not allow themselves to be accessed from any thread other than the one that created them because of potential deadlocking issues. To ensure that the user can do this, the .NET GUI API supplies a **BeginInvoke** method that can be used to access GUI controls from other threads, such as the ones that fire events. You can also set the **InvokeThrough** property of the communication component to any control on the GUI form to direct the component to forward all events through that control.

# TimeToLive Property ([ICMP](#icmp-component) Component)

This property includes the time-to-live (TTL) value for the ICMP packets sent by the component.

## Syntax

```text
public int TimeToLive { get; set; }
```

## Default Value

0

## Remarks

This method contains the time-to-live (TTL) value for the ICMP packets sent by the component. The TTL field of the ICMP packet is a counter limiting the lifetime of a packet.

Each router (or other module) that handles a packet decrements the TTL field by one or more if it holds the packet for more than one second. Thus, the TTL value is effectively a hop count limit on how far a datagram can propagate through the internet. When the TTL value is reduced to zero (or less), the packet is discarded.

If the value of the property is set to zero, then the default TTL value of the underlying Transmission Control Protocol (TCP)/IP subsystem will be used.

This property is not available at design time.

# Activate Method ([ICMP](#icmp-component) Component)

This method enables sending and receiving of data.

## Syntax

```text
public void Activate();

Async Version
public async Task Activate();
public async Task Activate(CancellationToken cancellationToken);
```

## Remarks

This method enables sending and receiving of data. When called, the component will create a communication endpoint (socket) that can be used for sending and receiving ICMP messages. This method must be called before using the component to send and receive data.

If the [UseConnection](#UseConnection) configuration setting is set to *true*, then a local association (connection) to the remote host also is created.

# Config Method ([ICMP](#icmp-component) Component)

Sets or retrieves a configuration setting.

## Syntax

```text
public string Config(string configurationString);

Async Version
public async Task<string> Config(string configurationString);
public async Task<string> Config(string configurationString, CancellationToken cancellationToken);
```

## Remarks

Config is a generic method available in every component. It is used to set and retrieve [configuration settings](#config-settings-icmp-component) for the component.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these *internal properties* is provided through the Config method.

To set a configuration setting named *PROPERTY*, you must call *Config("PROPERTY=VALUE")*, where *VALUE* is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a [configuration setting](#config-settings-icmp-component), you must call *Config("PROPERTY")*. The value will be returned as a string.

# Deactivate Method ([ICMP](#icmp-component) Component)

This method disables sending and receiving of data.

## Syntax

```text
public void Deactivate();

Async Version
public async Task Deactivate();
public async Task Deactivate(CancellationToken cancellationToken);
```

## Remarks

This method disables sending and receiving of data. When called, the component will destroy the existing socket and disable data communications.

# DoEvents Method ([ICMP](#icmp-component) Component)

This method processes events from the internal message queue.

## Syntax

```text
public void DoEvents();

Async Version
public async Task DoEvents();
public async Task DoEvents(CancellationToken cancellationToken);
```

## Remarks

When DoEvents is called, the component processes any available events. If no events are available, it waits for a preset period of time, and then returns.

# PauseData Method ([ICMP](#icmp-component) Component)

This method pauses data reception.

## Syntax

```text
public void PauseData();

Async Version
public async Task PauseData();
public async Task PauseData(CancellationToken cancellationToken);
```

## Remarks

This method pauses data reception when called. While data reception is paused, the [DataIn](#datain-event-icmp-component) event will not fire. Call [ProcessData](#processdata-method-icmp-component) to reenable data reception.

# ProcessData Method ([ICMP](#icmp-component) Component)

This method reenables data reception after a call to [PauseData](#pausedata-method-icmp-component) .

## Syntax

```text
public void ProcessData();

Async Version
public async Task ProcessData();
public async Task ProcessData(CancellationToken cancellationToken);
```

## Remarks

This method reenables data reception after a previous call to [PauseData](#pausedata-method-icmp-component). When [PauseData](#pausedata-method-icmp-component) is called, the [DataIn](#datain-event-icmp-component) event will not fire. To reenable data reception and allow [DataIn](#datain-event-icmp-component) to fire, call this method.

NOTE: This method is used only after previously calling [PauseData](#pausedata-method-icmp-component). It does not need to be called to process incoming data by default.

# Reset Method ([ICMP](#icmp-component) Component)

This method will reset the component.

## Syntax

```text
public void Reset();

Async Version
public async Task Reset();
public async Task Reset(CancellationToken cancellationToken);
```

## Remarks

This method will reset the component's properties to their default values.

# ResolveRemoteHost Method ([ICMP](#icmp-component) Component)

This method resolves the hostname in [RemoteHost](#remotehost-property-icmp-component) to an IP address.

## Syntax

```text
public void ResolveRemoteHost();

Async Version
public async Task ResolveRemoteHost();
public async Task ResolveRemoteHost(CancellationToken cancellationToken);
```

## Remarks

This method resolves the hostname specified by [RemoteHost](#remotehost-property-icmp-component) to an IP address. The resolved value is available in the [RemoteHost](#remotehost-property-icmp-component) property after this method returns.

In most cases, calling this method is not necessary; the component will resolve the hostname automatically when needed. If [DelayHostResolution](#DelayHostResolution) is *true*, this method may be called to manually resolve [RemoteHost](#remotehost-property-icmp-component), if desired.

# Send Method ([ICMP](#icmp-component) Component)

This method sends data to the remote host.

## Syntax

```text
public void Send(byte[] text);

Async Version
public async Task Send(byte[] text);
public async Task Send(byte[] text, CancellationToken cancellationToken);
```

## Remarks

This method sends data to the remote host.

# SendBytes Method ([ICMP](#icmp-component) Component)

This method sends data to the remote host.

## Syntax

```text
public void SendBytes(byte[] data);

Async Version
public async Task SendBytes(byte[] data);
public async Task SendBytes(byte[] data, CancellationToken cancellationToken);
```

## Remarks

This method sends data to the remote host. Calling this method is equivalent to calling the SendBytes/[SendText](#sendtext-method-icmp-component) method.

# SendText Method ([ICMP](#icmp-component) Component)

This method sends data to the remote host.

## Syntax

```text
public void SendText(string text);

Async Version
public async Task SendText(string text);
public async Task SendText(string text, CancellationToken cancellationToken);
```

## Remarks

This method sends data to the remote host. Calling this method is equivalent to calling the [SendBytes](#sendbytes-method-icmp-component)/SendText method.

# DataIn Event ([ICMP](#icmp-component) Component)

This event is fired when a new ICMP messages come in.

## Syntax

```text
public event OnDataInHandler OnDataIn;

public delegate void OnDataInHandler(object sender, ICMPDataInEventArgs e);

public class ICMPDataInEventArgs : EventArgs {
  public int MessageType { get; }
  public int MessageSubType { get; }
  public string MessageData { get; }  public byte[] MessageDataB { get; }
  public int Checksum { get; }
  public string SourceAddress { get; }
}
```

## Remarks

The *MessageType* parameter shows the type of the ICMP messages and the *MessageSubType* parameter shows its subtype.

The *MessageData* parameter contains the message data.

The *Checksum* parameter is True or False depending on the ICMP checksum validation on the message.

NOTE: Events are not re-entrant. Performing time-consuming operations within this event will prevent it from firing again in a timely manner and may affect overall performance.

# Error Event ([ICMP](#icmp-component) Component)

Fired when information is available about errors during data delivery.

## Syntax

```text
public event OnErrorHandler OnError;

public delegate void OnErrorHandler(object sender, ICMPErrorEventArgs e);

public class ICMPErrorEventArgs : EventArgs {
  public int ErrorCode { get; }
  public string Description { get; }
}
```

## Remarks

The Error event is fired in case of exceptional conditions during message processing. Normally the component throws an exception.

The *ErrorCode* parameter contains an error code, and the *Description* parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the [Error Codes](#trappable-errors-icmp-component) section.

# ReadyToSend Event ([ICMP](#icmp-component) Component)

This event is fired when the component is ready to send data.

## Syntax

```text
public event OnReadyToSendHandler OnReadyToSend;

public delegate void OnReadyToSendHandler(object sender, ICMPReadyToSendEventArgs e);

public class ICMPReadyToSendEventArgs : EventArgs {
}
```

## Remarks

The ReadyToSend event indicates that the underlying Transmission Control Protocol (TCP)/IP subsystem is ready to accept data after a failed [Send](#send-method-icmp-component).

# Config Settings ([ICMP](#icmp-component) Component)

 The component accepts one or more of the following *configuration settings*. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these *internal properties* is provided through the [Config](#config-method-icmp-component) method.

### ICMP Config Settings

**DelayHostResolution**: Whether the hostname is resolved when RemoteHost is set.This configuration setting specifies whether a hostname is resolved immediately when [RemoteHost](#remotehost-property-icmp-component) is set. If *true* the component will resolve the hostname and the IP address will be present in the [RemoteHost](#remotehost-property-icmp-component) property. If *false*, the hostname is not resolved until needed by the component when a method to connect or send data is called. If desired, [ResolveRemoteHost](#resolveremotehost-method-icmp-component) may be called to manually resolve the value in [RemoteHost](#remotehost-property-icmp-component) at any time.

The default value is *false* for the default library and *true* for the async library.

**DontFragment**: Whether the DontFragment control flag is set.When set to True, the DontFragment control flag in the IP header will be set.

The default value is False.

**IcmpDllTimeout**: The timeout for the component when using the icmp.dll.The component will wait for the operation to complete before returning control. If [IcmpDllTimeout](#IcmpDllTimeout) expires, and the operation is not yet complete, the component throws an exception. [IcmpDllTimeout](#IcmpDllTimeout) must be set to a positive value.

The default value for [IcmpDllTimeout](#IcmpDllTimeout) is 60 seconds.

NOTE: This configuration setting is valid only when [UseICMPDLL](#UseICMPDLL) is set to True.

**MaxMessageSize**: The maximum length of the messages that can be received.This setting specifies the maximum size of the datagrams that the component will accept without truncation.

**MulticastTTL**: The time to live (TTL) value for multicast ICMP packets sent by the component.When sending multicast packets, the setting specifies the time-to-live (TTL) field. The TTL field of the ICMP packet is a counter limiting the lifetime of a packet.

Each router (or other module) that handles a packet decrements the TTL field by one or more if it holds the packet for more than one second. Thus, the TTL is effectively a hop count limit on how far a datagram can propagate through the internet. When the TTL is reduced to zero (or less), the packet is discarded.

By default, the default TTL value of the underlying Transmission Control Protocol (TCP)/IP subsystem will be used.

**ReceiveAllMode**: Enables a socket to receive all IPv4 or IPv6 packets on the network.This setting specifies the ReceiveAll mode for the socket. The following modes are available:

|  |  |
| --- | --- |
| Value | Description |
| -1 (default) | The socket option is left unspecified. |
| 0 | Do not receive all network traffic. |
| 1 | Receive all network traffic. This enables the promiscuous mode on the network interface card (NIC). On a LAN segment with a network hub, a NIC that supports the promiscuous mode will capture all IPv4 or IPv6 traffic on the LAN, including traffic between other computers on the same LAN segment. |
| 2 | Receive only socket-level network traffic (this feature may not be implemented by your Windows installation). |
| 3 | Receive only IP-level network traffic. This option does not enable the promiscuous mode on the NIC. This option affects packet processing only at the IP level. The NIC still receives only those packets directed to its configured unicast and multicast addresses. A socket with this option enabled, however, not only will receive packets directed to specific IP addresses, but also will receive all the IPv4 or IPv6 packets the NIC receives. |

**TimeoutInMilliseconds**: The timeout is treated as milliseconds.Setting [TimeoutInMilliseconds](#TimeoutInMilliseconds) to True causes the component to use the value in the [IcmpDllTimeout](#IcmpDllTimeout) configuration setting as milliseconds instead of seconds, which is the default.

NOTE: This setting is valid only when [UseICMPDLL](#UseICMPDLL) is set to True.

**UseConnection**: Determines whether to use a connected socket.[UseConnection](#UseConnection) specifies whether or not the component should use a connected socket. The connection is defined as an association in between the local address/port and the remote address/port. As such, this is not a connection in the traditional Transmission Control Protocol (TCP) sense. It means only that the component will send and receive data to and from the specified destination.

The default value for this setting is False.

**UseICMPDLL**: Use the icmp.dll included on Windows Systems.Setting [UseICMPDLL](#UseICMPDLL) to True causes the component to use the icmp.dll on Windows 9x or on later machines. This sometimes enables access to raw sockets when permissions for standard operations are prohibited.

**UseIPHLPDLL**: Use the iphlpapi.dll included on Windows Systems.Setting [UseIPHLPDLL](#UseIPHLPDLL) to True causes the component to use the iphlpapi.dll on Windows XP or on later machines. This sometimes enables access to raw sockets when permissions for standard operations are prohibited.

NOTE: If both this and UseICMPDLL are enabled, the iphlpapi.dll will take precedence.

**UseIPv6**: Whether to use IPv6.When set to *0* (default), the component will use IPv4 exclusively. When set to *1*, the component will use IPv6 exclusively. To instruct the component to prefer IPv6 addresses, but use IPv4 if IPv6 is not supported on the system, this setting should be set to *2*. The default value is *0*. Possible values are as follows:

|  |  |
| --- | --- |
| 0 | IPv4 only |
| 1 | IPv6 only |
| 2 | IPv6 with IPv4 fallback |

### Socket Config Settings

**AbsoluteTimeout**: Determines whether timeouts are inactivity timeouts or absolute timeouts.If [AbsoluteTimeout](#AbsoluteTimeout) is set to True, any method that does not complete within [Timeout](#timeout-property-icmp-component) seconds will be aborted. By default, *AbsoluteTimeout* is False, and the timeout is an inactivity timeout.

NOTE: This option is not valid for User Datagram Protocol (UDP) ports.

**FirewallData**: Used to send extra data to the firewall.When the firewall is a tunneling proxy, use this property to send custom (additional) headers to the firewall (e.g., headers for custom authentication schemes).

**InBufferSize**: The size in bytes of the incoming queue of the socket.This is the size of an internal queue in the Transmission Control Protocol (TCP)/IP stack. You can increase or decrease its size depending on the amount of data that you will be receiving. In some cases, increasing the value of the *InBufferSize* setting can provide significant improvements in performance.

Some TCP/IP implementations do not support variable buffer sizes. If that is the case, when the component is activated the *InBufferSize* reverts to its defined size. The same happens if you attempt to make it too large or too small.

**OutBufferSize**: The size in bytes of the outgoing queue of the socket.This is the size of an internal queue in the TCP/IP stack. You can increase or decrease its size depending on the amount of data that you will be sending. In some cases, increasing the value of the *OutBufferSize* setting can provide significant improvements in performance.

Some TCP/IP implementations do not support variable buffer sizes. If that is the case, when the component is activated the *OutBufferSize* reverts to its defined size. The same happens if you attempt to make it too large or too small.

### Base Config Settings

**BuildInfo**: Information about the product's build.When queried, this setting will return a string containing information about the product's build.

**GUIAvailable**: Whether or not a message loop is available for processing events.In a GUI-based application, long-running blocking operations may cause the application to stop responding to input until the operation returns. The component will attempt to discover whether or not the application has a message loop and, if one is discovered, it will process events in that message loop during any such blocking operation.

In some non-GUI applications, an invalid message loop may be discovered that will result in errant behavior. In these cases, setting [GUIAvailable](#GUIAvailable) to *false* will ensure that the component does not attempt to process external events.

**LicenseInfo**: Information about the current license.When queried, this setting will return a string containing information about the license this instance of a component is using. It will return the following information:

- Product: The product the license is for.
- Product Key: The key the license was generated from.
- License Source: Where the license was found (e.g., RuntimeLicense, License File).
- License Type: The type of license installed (e.g., Royalty Free, Single Server).
- Last Valid Build: The last valid build number for which the license will work.

**MaskSensitiveData**: Whether sensitive data is masked in log messages.In certain circumstances it may be beneficial to mask sensitive data, like passwords, in log messages. Set this to *true* to mask sensitive data. The default is *true*.

**UseInternalSecurityAPI**: Whether or not to use the system security libraries or an internal implementation. When set to *false*, the component will use the system security libraries by default to perform cryptographic functions where applicable. In this case, calls to unmanaged code will be made. In certain environments, this is not desirable. To use a completely managed security implementation, set this setting to *true*.

Setting this configuration setting to *true* tells the component to use the internal implementation instead of using the system security libraries.

 On Windows, this setting is set to *false* by default. On Linux/macOS, this setting is set to *true* by default.

NOTE: This setting is static. The value set is applicable to all components used in the application.

When this value is set, the product's system dynamic link library (DLL) is no longer required as a reference, as all unmanaged code is stored in that file.

# Trappable Errors ([ICMP](#icmp-component) Component)

### ICMP Errors

|  |  |
| --- | --- |
| 104 | The component is already [Active](#active-property-icmp-component). |
| 107 | Cannot change the LocalHost at this time. A connection is in progress. |
| 109 | The component must be [Active](#active-property-icmp-component) for this operation. |
| 112 | Cannot change [MaxMessageSize](#MaxMessageSize) while ICMP is [Active](#active-property-icmp-component). |
| 114 | Cannot change [RemoteHost](#remotehost-property-icmp-component) when [UseConnection](#UseConnection) is set and the component is [Active](#active-property-icmp-component). |
| 117 | Cannot change [UseConnection](#UseConnection) while the component is [Active](#active-property-icmp-component). |
| 118 | The message cannot be longer than [MaxMessageSize](#MaxMessageSize). |
| 119 | The message is too short. |
| 120 | Cannot create ICMP handle. |

### SSL Errors

|  |  |
| --- | --- |
| 270 | Cannot load specified security library. |
| 271 | Cannot open certificate store. |
| 272 | Cannot find specified certificate. |
| 273 | Cannot acquire security credentials. |
| 274 | Cannot find certificate chain. |
| 275 | Cannot verify certificate chain. |
| 276 | Error during handshake. |
| 280 | Error verifying certificate. |
| 281 | Could not find client certificate. |
| 282 | Could not find server certificate. |
| 283 | Error encrypting data. |
| 284 | Error decrypting data. |

### TCP/IP Errors

|  |  |
| --- | --- |
| 10004 | [10004] Interrupted system call. |
| 10009 | [10009] Bad file number. |
| 10013 | [10013] Access denied. |
| 10014 | [10014] Bad address. |
| 10022 | [10022] Invalid argument. |
| 10024 | [10024] Too many open files. |
| 10035 | [10035] Operation would block. |
| 10036 | [10036] Operation now in progress. |
| 10037 | [10037] Operation already in progress. |
| 10038 | [10038] Socket operation on nonsocket. |
| 10039 | [10039] Destination address required. |
| 10040 | [10040] Message is too long. |
| 10041 | [10041] Protocol wrong type for socket. |
| 10042 | [10042] Bad protocol option. |
| 10043 | [10043] Protocol is not supported. |
| 10044 | [10044] Socket type is not supported. |
| 10045 | [10045] Operation is not supported on socket. |
| 10046 | [10046] Protocol family is not supported. |
| 10047 | [10047] Address family is not supported by protocol family. |
| 10048 | [10048] Address already in use. |
| 10049 | [10049] Cannot assign requested address. |
| 10050 | [10050] Network is down. |
| 10051 | [10051] Network is unreachable. |
| 10052 | [10052] Net dropped connection or reset. |
| 10053 | [10053] Software caused connection abort. |
| 10054 | [10054] Connection reset by peer. |
| 10055 | [10055] No buffer space available. |
| 10056 | [10056] Socket is already connected. |
| 10057 | [10057] Socket is not connected. |
| 10058 | [10058] Cannot send after socket shutdown. |
| 10059 | [10059] Too many references, cannot splice. |
| 10060 | [10060] Connection timed out. |
| 10061 | [10061] Connection refused. |
| 10062 | [10062] Too many levels of symbolic links. |
| 10063 | [10063] File name is too long. |
| 10064 | [10064] Host is down. |
| 10065 | [10065] No route to host. |
| 10066 | [10066] Directory is not empty |
| 10067 | [10067] Too many processes. |
| 10068 | [10068] Too many users. |
| 10069 | [10069] Disc Quota Exceeded. |
| 10070 | [10070] Stale NFS file handle. |
| 10071 | [10071] Too many levels of remote in path. |
| 10091 | [10091] Network subsystem is unavailable. |
| 10092 | [10092] WINSOCK DLL Version out of range. |
| 10093 | [10093] Winsock is not loaded yet. |
| 11001 | [11001] Host not found. |
| 11002 | [11002] Nonauthoritative 'Host not found' (try again or check DNS setup). |
| 11003 | [11003] Nonrecoverable errors: FORMERR, REFUSED, NOTIMP. |
| 11004 | [11004] Valid name, no data record (check DNS setup). |