Using Noble-IP tunnel to manage p2p traffic

How To
,
1

Hello Community,

I try to run an Ocean Node instance. This is using libp2p and using tcp on port 9000 and web sockets on 9001. For that , I have setup a NobleIP static IP inbound proxy and outbound proxy. But if I want the p2p traffic to go both ways, NobleIP folks tell me I should setup a Tunnel. It means running noble-tunnel in the setup script of my instance (a docker instance).

Would anyone provide me with some guidance on how to do this so I have get out of the try and fail loop ?

Thanks!

PS: and yes I have setup my DNS CNAME :slight_smile:

2

Hey @jeanbapt :wave:

Do you have an easy way for us to reproduce?

3

Yes Yann, ideally :

Take the docker image on

docker pull oceanprotocol/ocean-node

Take this DEV account for eth/sepolia/optimism (never use this for real stuff , for dev only, put the PRIVATE_KEY as a secret env variable).

Address: 0xaA4eB80FBa155A31d4fc8aB02278631615Af1fAc // This is used also as the ALLOWED_ADMINS env variable below
PRIVATE_KEY =7b53962ecdf9e67080ed184962d2b11f43a077d1c7d822a76500552e0833421a

Put your Static IP (you get it from Noble-IP inbound proxy dashboard). I can set one up for you if needed. Import this edited bulk into your Koyeb settings. That should work.

ALLOWED_ADMINS=[“0xaA4eB80FBa155A31d4fc8aB02278631615Af1fAc”,]
DB_URL=“” // it should start a SQLite by default
INDEXER_NETWORKS=“[“11155111”, “23295”,“11155420”]”
P2P_ANNOUNCE_ADDRESSES=[“/ip4/–yr static Ip here –/tcp/9000”,“/ip4/–yr static IP here –/ws/tcp/9001”,“/dns4/–yr external dns pointing at noble-IP outbound proxy–/tcp/9000”,“/dns4/–yr external dns pointing at noble-IP outbound proxy–/ws/tcp/9001”]
PRIVATE_KEY=@PRIVATE_KEY //Use the private Key above with a SECRET
RPCS={ “11155111”: { “rpc”: “https://rpc.sepolia.org”, “fallbackRPCs”: [“https://rpc.sepolia.org”, “https://rpc.sepolia.org”], “chainId”: 11155111, “network”: “ethereum-sepolia”, “chunkSize”: 1000 }, “23295”: { “rpc”: “https://oasis-sapphire-testnet.core.chainstack.com/99883b327c7af824c6809434db8ab83a”, “fallbackRPCs”: [“https://testnet.sapphire.oasis.dev”], “chainId”: 23295, “network”: “oasis-sapphire-testnet”, “chunkSize”: 100 }, “11155420”: { “rpc”: “https://sepolia.optimism.io”, “fallbackRPCs”: [“https://public.stackup.sh/api/v1/node/optimism-sepolia”], “chainId”: 11155420, “network”: “optimism-sepolia”, “chunkSize”: 1000 } }

You should be able to spin a node, go to --internal Koyeb addess / dashboard to check it .
example (mine) : JB’s node dashboard

Copy your NodeId.

Once this runs, check by doing :

https://node1.oceanprotocol.com:8000/getP2PPeer?peerId=16Uiu2HAmF8YLLnx4eS5bkkWgyZNUHGbkY55j8aiK4zQDL3k4512B

(replace my peerId by yours (you got it from the dashboard). You should see your node being recognised by this external node from ocean-protocol.

At this point you should have reproduced the config. The folks at Ocean protocol tell me that I should be able to telnet the node from my local machine and I can’t and therefore external p2p nodes can’t connect to my node.

You can check all the live nodes on the global nodes and select mine or yours by using the filters there either on the Node Id or the external (Noble-IP) static ip.

If it is properly configured, you should see the Reward eligibility flag at OK. Note that this is refreshed every 40mn.

Thank you for your help,

JB

PS:
Mark, who is trying to help from Noble-IP, tells me I should probably setup a reverse proxy at Koyeb or setup a specific outbound proxy for port 9001.