Network settings

Use the global network configuration to modify the connection timeout variables between Corelight-update and the sensors, a Fleet Manager instance, or a data source to be downloaded. The sensor_timeout_settings are used to manage communication between Corelight-update and a sensor or Fleet Manager instance. The download_timeout_settings are used to manage communication between Corelight-update and a data source to download.

Updating the Global network config

Changes can be made to the global network configuration using the Corelight-update CLI command with the --network-settings flag.

The Corelight-update CLI command supports updating the Global Network Configuration directly using the --network-settings flag.

  • Multiple settings can be updated using a single command.

  • Update nested settings by using a “.”. For example, sensor_timeout_settings.tls_handshake_seconds=10.

  • Any setting can be updated using a key=value pair.

For example:

corelight-update update --network-settings sensor_timeout_settings.tls_handshake_seconds=10 sensor_timeout_settings.upload_wait_seconds=60

See the next section for a list of fields that can be updated directly.

After updating a configuration, verify the global network configuration using the console. For example:

 corelight-update show -network

Complete global network settings

sensor_timeout_settings:
    transport_dialer_seconds: 5  # The amount of time the dialer should wait before abandoning an attempt to connect to a remote address.
    tls_handshake_seconds: 10    # The amount of time allowed for the TLS handshake to complete when establishing a TLS-secured HTTP connection.
    idle_conn_seconds: 90        # The amount of time that an idle (keep-alive) connection will remain open before being closed by the HTTP client.
    expect_continue_seconds: 1   # The amount of time that the client will wait for a server's first response to an HTTP request that includes an Expect: 100-continue header, before sending the request body.
    http_seconds: 60             # The amount of time a client will wait for an HTTP request to complete, from the time the request is made until the response is fully read.
    upload_wait_seconds: 60      # The amount of time to wait for the status of an upload to Fleet Manager or a sensor.  In general, errors return within a few seconds.
download_timeout_settings:
    transport_dialer_seconds: 5  # The amount of time the dialer should wait before abandoning an attempt to connect to a remote address.
    tls_handshake_seconds: 10    # The amount of time allowed for the TLS handshake to complete when establishing a TLS-secured HTTP connection.
    idle_conn_seconds: 90        # The amount of time that an idle (keep-alive) connection will remain open before being closed by the HTTP client.
    expect_continue_seconds: 1   # The amount of time that the client will wait for a server's first response to an HTTP request that includes an Expect: 100-continue header, before sending the request body.
    http_seconds: 60             # The amount of time a client will wait for an HTTP request to complete, from the time the request is made until the response is fully read.