Below you can see some P2P nodes I run in various networks.
All of them support IPv6, most of them support IPv4 (where possible).
| name | The hostname of the node. Also in DNS, signed using DNSSEC. They send valid TLS certs if possible, because my domain is HSTS preloaded. |
|---|---|
| version | What software version the node is using. |
| ipv6 | Whether the node supports IPv6. This will always be yes. |
| ipv4 | Whether the node supports IPv4. Additionally might contain information on the NAT. IPv4 does not grow on trees, neither does money. |
| mode | Operational mode of the node. Like whether it's a full node, a minimal node to save space, or an exit node allowing every filth out of it. Depends on the network. |
| storage | On which storage type the blockchain or similar is stored. Expect big blockchains to sit on HHDs, SSDs are only getting more expensive. |
| location | City, ISP, Hypervisor. |
| status | Operational / Maintenance / Offline |
Always address these by their hostnames. DO NOT use the IP literals, whether that's IPv6 or IPv4 unless absolutely necessary! They can and probably will change!
Also, as they send valid LetsEncrypt cerificates if possible, you WILL see a security error when connecting using IP-Addresses.
With domain names, clients can also choose whether to connect using IPv6 or to fall back to IPv4 if necessary. It's just better.
NAT64 also works better on domain names to clients that don't query ipv4only.arpa and do 464XLAT, but this isn't really needed here as all of my nodes support IPv6 anyway.P2P port is 18080. RPC port is 18089. RPC supports TLS using a LetsEncrypt certificate. They can be used from a browser, as they send a CORS header.
Tor support: P2P port is 18083, RPC port is 18089. Don't use HTTPS, you will get a certificate error and tor is already encrypted.
You may see my torrc. It's the same on all nodes.
Note: monerod has problems with IPv6. This is why you see a lot of add-priority-node in my config. I'm trying to make it work the best.
| name | version | ipv6 | ipv4 | mode | storage | location | links |
|---|---|---|---|---|---|---|---|
|
xmr1.julias.zone xmr1.julias37xypb2ccrelyofyg6wotueho7kskqe5ujj5bowfs7dosndsid.onion |
monero-x86_64-linux-gnu-v0.18.3.4 | yes | yes, but nat44 | full node | hdd | Nuremberg Vodafone dedi1.julias.zone |
monerod.conf get_info tor get_info |
|
xmr2.julias.zone xmr2.julias2xi7ieqd6w67ztx3auhcvyklcgxm3ayf6ya6duk2ulce5hupid.onion |
monero-x86_64-linux-gnu-v0.18.3.4 | yes | yes, but nat44 | pruned node | ssd | Nuremberg Hetzner dedi2.julias.zone |
monerod.conf get_info tor get_info |
| name | port | ipv6 | ipv4 | mode | location | links | notice |
|---|---|---|---|---|---|---|---|
| tor1.julias.zone | 9001 | yes | yes, but nat44 | entry/middle | Nuremberg Vodafone dedi1.julias.zone |
torrc | Major websites block not just exit nodes, but also simply relays apparently. Are they too lazy to check the exit policy??? |