# Configuration
### Opening the configuration window
The configuration window may be opened by right clicking on the Off System logo in your computer's tray and selecting `configuration` from the menu.
## Bootstrap
Peers are predominantly discovered arbitrarily as a result of searches for content. The bootstrap section of the configuration window determines the peers hat your node will attempt to make connections with upon start up and during maintenance. **Having no bootstrap peers will inhibit a node from making connections when searching for content**.
#### Adding a Bootstrap Peer
1. Obtain the `locator` of the Peer you wish to bootstrap
2. Paste the `locator` text into the text field labeled `Locator`
3. Click the `add` button
#### Removing a Bootstrap Peer
1. Find the row with the `Node ID` of the desired peer in the table
2. Click the `x` icon on the furthest right portion of the row
#### Boostrapping to Last Known Connections
This feature will upon restart attempt a best effort restoration of your node's most recent connections before it went offline.
1. Check the checkbox labeled `Bootstrap to last known connections`
## Network
The network section of the configuration defines how your node will make connections to other peers as well as http clients. Your may need to configure your router or firewall to allow port forwarding for the ports listed in this configuration. By default peer connections are received on port `8200` and http clients are received on `23402`.
| Configuration Option | Description |
| ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Start Port | Defines the TCP port peer connections will be received on |
| Port Retries | Defines how many time a node will attempt to reserve a port before failure |
| HTTP Port | Defines the port that the http server will accept connections on |
| Socket Timeout | Defines how long a connection can sit idle before failure occurs |
| Use Internal IP for Connections | Defines whether to use internal network ip's only to define the node's peer location. This option may prevent connections to nodes outside your internal network |
## Storage
The storage section of the configuration defines the size and location parameters of each of the node's block caches. There are three type of blocks in the system block, mini, and nano. Files that are over 128kb stored in the block cache. Files between 128kb and 1000b are store in the mini cache. Files less than 1000b are stored in the nano cache. You may want to size the storage of each cache based upon your usage of the node. **Block Cache's are not free space and the network will try to fill or empty themselves based upon network usage and the size limitations created by their node's installers**.
| Configuration Option | Description |
| ---------------------------------------- | ----------------------------------------------------- |
| Cache Location | The location of your cache on your local file system |
| Block Cache Storage Size
| The size of your cache in mb for storing 128kb blocks |
| Mini Block Cache Storage Size | The of your cache in mb for storing 1kb blocks |
| Nano Block Cache Storage Size
| The size of you cache for storing 136b blocks |
###
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://www.off.systems/configuration.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.