Bitcoin Forum
September 01, 2026, 05:47:18 PM *
News: Latest Bitcoin Core release: 31.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Is this a valid approach for testing P2P behind CGNAT?  (Read 35 times)
slw2qdc6xqca (OP)
Newbie
*
Offline

Activity: 18
Merit: 0


View Profile WWW
Today at 12:36:35 PM
 #1

I'm testing a P2P node running on Android/Termux behind CGNAT.
For testing, I used a temporary Pinggy tunnel to expose one node.
The remote node discovered the peer and successfully synced the chain. The "/chain" response from the public endpoint matched both local nodes (3 blocks).

POST /add_peer → 200
GET /peers → 200
GET /chain → 200

Public endpoint → 3 blocks
127.0.0.1:5000 → 3 blocks
127.0.0.1:8080 → 3 blocks

Is this a reasonable approach for testing P2P connectivity behind CGNAT, or is there a better approach?
DireWolfM14
Copper Member
Legendary
*
Online Online

Activity: 2968
Merit: 5833



View Profile WWW
Today at 03:02:35 PM
 #2

I've never used Termux.  Can it run a Tor node?

One of my properties doesn't have great internet options, so while living there I opted for Starlink which uses CGNAT unless you want to pay like $300 a month for static direct IP.  I found the simplest way to run P2P was to use Tor and set up hidden services for all the services I wanted access to outside the local network.  It was very reliable and relatively simple to set up.

Another option is to host a small remote server running a wireguard server and nginx reverse proxy, and connect the local node devices to that.  That's a bit more complex, but you'll have a clearnet address to connect to rather than just onion addresses.

slw2qdc6xqca (OP)
Newbie
*
Offline

Activity: 18
Merit: 0


View Profile WWW
Today at 04:09:22 PM
 #3

I've never used Termux.  Can it run a Tor node?

One of my properties doesn't have great internet options, so while living there I opted for Starlink which uses CGNAT unless you want to pay like $300 a month for static direct IP.  I found the simplest way to run P2P was to use Tor and set up hidden services for all the services I wanted access to outside the local network.  It was very reliable and relatively simple to set up.

Another option is to host a small remote server running a wireguard server and nginx reverse proxy, and connect the local node devices to that.  That's a bit more complex, but you'll have a clearnet address to connect to rather than just onion addresses.

Thanks for the suggestions. I’m currently testing P2P networking on Android/Termux behind CGNAT, so I’m using a temporary tunnel to provide an externally reachable endpoint. The goal is only to test peer discovery and blockchain synchronization, not production deployment. The test successfully discovered the peer and synchronized the chain
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!