CipherLabs
/
besu
mirror of https://github.com/hyperledger/besu
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
An enterprise-grade Java-based, Apache 2.0 licensed Ethereum client https://wiki.hyperledger.org/display/besu
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1443 Commits
44 Branches
214 Tags
200 MiB
 
 
Tag: Branch: Tree: 1d59f90486
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '1d59f90486'
${ noResults }
besu/docs/Configuring-Pantheon/Networking/Using-UPnP.md

1.3 KiB
Raw Blame History

description: Configuring UPnP with Pantheon

UPnP

Enable UPnP to quickly allow inbound peer connections without manual router configuration. Use UPnP in home or small office environments where a wireless router or modem provides NAT isolation.

UPnP automatically detects that a node is running in a UPnP environment and provides port forwarding.

!!! tip UPnP support is often disabled by default in networking firmware. If disabled by default, explicitly enable UPnP support.

Enabling UPnP

Use the --nat-method command line option to enable UPnP.

!!! note Enabling UPnP may slow down node startup, especially on networks without a UPnP gateway device.

When UPnP is enabled:

  • Enode advertised to other nodes during discovery is the external IP address and port.
  • External address and port are returned by the admin_NodeInfo JSON-RPC API method for the enode and listenAddr properties.

While Pantheon is running, UPnP does not support:

  • IP address changes
  • Disabling UPnP. To disable UPnP, restart the node without the --nat-method option or set to NONE.