Port Forwarding & Firewall
Overview
This guide explains how to configure network settings and set up port forwarding for Autonomys Network. Correct port forwarding is essential to ensure proper communication between your node, farmer, and the Autonomys Network.
By opening specific ports on your router, you allow external traffic to reach your node, which is necessary for blockchain synchronization, data exchange, and remote procedure calls (RPC).
Additionally, you may need to adjust your system's firewall settings to allow traffic through the specified ports. Firewalls typically block unsolicited incoming connections, so it's important to ensure that the required ports are open. These adjustments will enable effective communication with the Autonomy Network.
Ports to Forward & Firewall Access
Ensure each node on the same network runs on unique ports. Adjust the ports mentioned in this guide if using multiple nodes or if default ports have been changed.
For security reasons, RPC ports 9944 and 9945 should never be exposed to the internet via port forwarding unless you're operating a public RPC server. However, if the node and farmer are on different computers on the same network, these ports should be allowed through the firewall on the node.
- Space Acres
- Advanced CLI (Farmer)
- Advanced CLI (Domain Operator)
- RPC Server (Public)
Port | Protocol | ↪️ | 🛡️ | Component | Purpose |
---|---|---|---|---|---|
30333 | TCP | ☑️ | ☑️ | Node (Consensus) | Facilitate block, transaction, and PoT gossip exchange. |
30433 | TCP | ☑️ | ☑️ | Node (DSN) | Retrieve and serve pieces of data and metadata related to archival history from the P2P network. |
Port | Protocol | ↪️ | 🛡️ | Component | Purpose |
---|---|---|---|---|---|
30333 | TCP | ☑️ | ☑️ | Node (Consensus) | Facilitate block, transaction, and PoT gossip exchange. |
30433 | TCP | ☑️ | ☑️ | Node (DSN) | Retrieve and serve pieces of data and metadata related to archival history from the P2P network. |
30533 | TCP | ☑️ | ☑️ | Фермер | Retrieve blockchain archival history. |
9944 | TCP | ❌ | ☑️ | Node (Consensus RPC) | Required for farmer operation. |
Port | Protocol | ↪️ | 🛡️ | Component | Purpose |
---|---|---|---|---|---|
30333 | TCP | ☑️ | ☑️ | Node (Consensus) | Facilitate block, transaction, and PoT gossip exchange. |
30334 | TCP | ☑️ | ☑️ | Node (Domain) | Essential for a domain node to maintain strong connectivity with the P2P network. |
30433 | TCP | ☑️ | ☑️ | Node (DSN) | Retrieve and serve pieces of data and metadata related to archival history from the P2P network. |
Port | Protocol | ↪️ | 🛡️ | Component | Purpose |
---|---|---|---|---|---|
9944 | TCP | ☑️ | ☑️ | Node (Consensus RPC) | Enables transaction submissions via HTTP and WebSocket, supports slot challenges, and provides access to real-time and historical blockchain data for querying events, transactions, block contents, and chain state. |
9945 | TCP | ☑️ | ☑️ | Node (Domain RPC) | Enables sending transactions, including deploying and calling smart contracts. |
Legend: The ↪️ column indicates whether the port should be forwarded on the router, while the 🛡️ column specifies if inbound firewall access should be allowed through the operating system.
Steps to Forward Ports
Since the port forwarding process varies by router, follow these general steps:
-
Find Your Router’s IP Address: Check your network settings to locate your router’s IP address. You will also need the internal IP address of the computer running the Autonomys components.
-
Access Router Settings: Open your router’s settings by entering the router's IP address into a web browser. You may need the default login credentials, often printed on the router or provided by your ISP.
-
Set Up Port Forwarding: In the router's configuration interface, navigate to Advanced Settings or Port Forwarding and enter the following details:
- The internal IP address of your computer
- Consult the tables above for the ports and protocols that need to be forwarded (30333, 30433, 30533, etc.).
Once entered, apply the changes and reboot your router if necessary.
Manufacturer instructions
Here are the links to port forwarding guides from five major consumer router manufacturers:
TP-Link
You can configure port forwarding through the "Forwarding" section on the router's web interface. You'll add a new rule under "Virtual Servers" and specify the device and ports you want to open. TP-Link Port Forwarding guide
Netgear
On Netgear routers, port forwarding is set up by navigating to the "Advanced Setup" section and selecting "Port Forwarding/Port Triggering." Netgear Port Forwarding guide
Linksys
Log in to your router’s web interface and configure port forwarding under the "Apps and Gaming" section of the "Security" tab. Linksys Port Forwarding Guide
ASUS
On ASUS routers, port forwarding is set up via the "WAN" tab, where you’ll find the "Virtual Server/Port Forwarding" option. ASUS Port Forwarding Guide
D-Link
For D-Link routers, port forwarding is done in the "Advanced" tab under "Port Forwarding." You’ll add a rule and enter the necessary details. D-Link Port Forwarding Guide
Firewall Configuration
🐧 Linux Advanced CLI (Farmer)
If you are using Linux with UFW (Uncomplicated Firewall) enabled, you will need to allow traffic on the necessary ports to ensure your node and farmer can communicate properly. Use the following commands to update your firewall settings:
sudo ufw allow 30333,30433 comment 'Autonomys Node'
sudo ufw allow 30533 comment 'Autonomys Farmer'
sudo ufw allow from 192.168.1.0/24 to any port 9944 proto tcp comment 'Autonomys Node RPC'
Network Configuration Scenarios
Scenario | Required Action |
---|---|
Using a Router | Ensure that the necessary ports are properly forwarded to the machine running your services. |
Firewall | Configure your firewall settings to ensure the required ports are open for incoming and outgoing traffic. |
No Firewall | No additional configuration is necessary if a firewall is not in use. |
Direct Internet Connection | If you are connected directly to the internet without a router, no port forwarding is required. |
Additional Resources and Verification
Autonomys provides these links for reference only and does not guarantee the accuracy, completeness, or reliability of the information contained within them. Users are advised to verify the details independently and use these resources at their own discretion.