# Gateway Startup Arguments

### **Available regions:**

Use these for `ofr-host` argument. Select the one which is the closest to your region.

| Region    | Address                           | Cloud Provider                        |
| --------- | --------------------------------- | ------------------------------------- |
| Frankfurt | `frankfurt.solana-v2.blxrbdn.com` | [Latitude](https://www.latitude.sh/)  |
| New York  | `ny.solana-v2.blxrbdn.com`        | [Latitude](https://www.latitude.sh/)  |
| Tokyo     | `tokyo.solana-v2.blxrbdn.com`     | [Latitude](https://www.latitude.sh/)  |
| Amsterdam | `amsterdam.solana-v2.blxrbdn.com` | [Teraswitch](https://teraswitch.com/) |

Please see below for full lists of startup arguments you may use to configure the Gateway.

#### Required Gateway Arguments <a href="#required-gateway-arguments" id="required-gateway-arguments"></a>

{% hint style="info" %}
**Note**: The --network=host tag is a required startup parameter for the Docker command. It gives the container access to all network interfaces on the host machine. For more information, see [here](https://docs.bloxroute.com/solana/solana-gateway-setup#startup).
{% endhint %}

<table data-header-hidden><thead><tr><th width="155.966796875"></th><th width="266.54815673828125"></th><th width="137.63385009765625"></th><th></th></tr></thead><tbody><tr><td>Parameter</td><td>Description</td><td>Default</td><td>Example</td></tr><tr><td><code>auth-header</code></td><td>​<a href="https://app.gitbook.com/o/-MEhXlkTc0qsyh2r6DQY/s/-MEhQI8zckriC1VzHORZ/~/changes/1071/apis/authorization-headers/~/overview">Authorization header.</a>​</td><td>Must be provided (Authorization required)</td><td>ZDE0ZTVmZTYtNjBhOC00NTUzLTliZjQtNTU0ODE3MjNlMDRlOmRlYTJiM3F3cWJnNHJ2ZWc0MjQydmJlM2EzcnUyanQ2</td></tr><tr><td><code>tvu-port</code></td><td>Port of your Solana <code>TVU</code> port. Run <code>solana-validator contact-info</code> (or <code>agave-validator contact-info</code> depending on the client) to find it.</td><td>8001</td><td>8001</td></tr><tr><td><code>ofr-host</code></td><td>Manually specifies the closest relay of the OFR via hostname. See the list of available relays above and select the one geographically closest to your node to minimize latency.</td><td>N/A</td><td>ny.solana-v2.blxrbdn.com</td></tr><tr><td><code>network-interface</code></td><td>The outbound network interface used for communication. Run <code>ifconfig</code> (Linux/macOS) or <code>ipconfig</code> (Windows) to find the correct interface. Select the one with an <code>inet</code> value that matches your machine’s public IP.</td><td>N/A</td><td>eno1</td></tr><tr><td><code>port</code></td><td>The gateway receives shreds through OFR by communicating with bloXroute's OFR Relay, which uses <strong>UDP</strong> port <code>18888</code> by default. Please make sure the port is open <strong>Inbound</strong>.</td><td>18888</td><td>18888</td></tr></tbody></table>

#### Optional Gateway Arguments <a href="#optional-gateway-arguments" id="optional-gateway-arguments"></a>

<table data-header-hidden><thead><tr><th width="156.48828125"></th><th width="274.87762451171875"></th><th width="133.89117431640625"></th><th></th></tr></thead><tbody><tr><td>Parameter</td><td>Description</td><td>Default</td><td>Example</td></tr><tr><td><code>log-level</code></td><td>Sets the log level of the Gateway stdout.​Users should change log-file-level only if a detailed log is required. [Options: <code>TRACE</code>, <code>DEBUG</code>, <code>INFO</code>, <code>WARN</code>, <code>ERROR</code>].</td><td>INFO</td><td>DEBUG</td></tr><tr><td><code>log-file-level</code></td><td>The log level of the log file (found in the <code>logs</code> directory). Users should change log-file-level only if a detailed log is required. [Options: <code>TRACE</code>, <code>DEBUG</code>, <code>INFO</code>, <code>WARN</code>, <code>ERROR</code>].</td><td>DEBUG</td><td>DEBUG (can be set to TRACE, INFO, WARN, or ERROR depending on verbosity needs)</td></tr><tr><td><code>broadcast-addresses</code></td><td>list of <code>ip:port</code> of addresses to send shreds to</td><td>Empty (must be manually specified if needed)</td><td><p>92.168.0.254:1234,</p><p>122.168.0.254:1235</p></td></tr><tr><td><code>broadcast-from-ofr-only</code></td><td>true for sending only shreds from ofr to addresses provided in <code>broadcast-addresses</code>, false to send all shreds</td><td>false</td><td>true/false</td></tr><tr><td><code>no-validator</code></td><td>Specifies if gateway should run without node. This flag is available to users with Enterprise Elite plan or above.</td><td>false</td><td>true/false</td></tr><tr><td><code>log-max-size</code></td><td>Max log file size in MB</td><td>100</td><td>100</td></tr><tr><td><code>log-max-backups</code></td><td>Max log file backups</td><td>10</td><td>10</td></tr><tr><td><code>log-max-age</code></td><td>Max days to keep log file</td><td>10</td><td>10</td></tr><tr><td><code>dynamic-port-range</code></td><td>Range to use for dynamically assigned ports for shreds propagation over UDP, should not conflict with solana/agave dynamic port range</td><td>18889-19888</td><td>18889-19888</td></tr><tr><td><code>staked-node</code></td><td>If this flag is enabled while running a staked node, the gateway will not send shreds that have already been received from the staked node</td><td>false</td><td>true/false</td></tr></tbody></table>