> ## Documentation Index
> Fetch the complete documentation index at: https://docs.futurex.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Appendix A: Frequently asked questions

> Frequently asked questions about syslog export in VIP, covering network reachability, transport, blocked ranges, and certificates.

This section answers common questions about configuring syslog exports in VIP.

#### Can a private network, such as a VPN or VAP, receive syslog traffic?

No. VIP delivers logs only to a public ingress. A syslog server that is reachable only through a private network is not supported.

#### Does the syslog connection use TCP or UDP?

The syslog connection uses TCP, not UDP.

#### Which destinations does VIP block?

By default, VIP blocks private and reserved IP ranges, so only publicly reachable syslog endpoints receive messages. Before sending a log, VIP resolves the configured hostname to an IP address and checks it against this default block list. If the destination falls within a blocked range and is not whitelisted, VIP skips it and does not attempt a connection. To deliver logs to an address that would otherwise be blocked, whitelist it. See [Whitelist IP addresses](./Whitelist_IP_addresses).

#### For the certificate, does VIP expect a server or a client private key?

Neither. VIP does not expect a private key of any kind. Provide the CA certificate or CA bundle that issued the syslog server's certificate.

#### Why are there separate fields for cert files and cert content?

The **Select cert files** field opens an upload dialog so you can upload the target certificate file. The **Cert Content (Read Only)** field is a read-only view that displays the content of the uploaded certificate.