# Reserved node doesn't work

**URL:** <https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720>\
**Category:** Incentivized Testnet\
**Tags:** nodes, cli\
**Created:** [September 7, 2023, 9:43am UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720 "2023-09-07T09:43:43Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![pascal](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/pascal/32/1150_2.png) [@pascal](https://forum.autonomys.xyz/u/pascal)\
**Post date:** [September 7, 2023, 9:43am UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720/1 "2023-09-07T09:43:43Z")

</div>

Try connect to another node with `--reserved-nodes`, but the connection never established

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [September 7, 2023, 1:58pm UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720/2 "2023-09-07T13:58:22Z")

</div>

Should work, we use it actively. I think it shouldn’t, but it may refuse to connect to nodes from private IP range (like LAN) unless you allow private IPs explicitly.

---

<div class="post-metadata">

**Author:** ![pascal](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/pascal/32/1150_2.png) [@pascal](https://forum.autonomys.xyz/u/pascal)\
**Post date:** [September 7, 2023, 2:26pm UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720/3 "2023-09-07T14:26:01Z")

</div>

I have 2 nodes, one (A) is running with default config, another (B) tries to connect to A via local ip like 172.1.13.14.

---

<div class="post-metadata">

**Author:** ![pascal](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/pascal/32/1150_2.png) [@pascal](https://forum.autonomys.xyz/u/pascal)\
**Post date:** [September 7, 2023, 2:26pm UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720/4 "2023-09-07T14:26:35Z")

</div>

Btw, how to enable private IPS

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [September 7, 2023, 2:44pm UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720/5 "2023-09-07T14:44:37Z")

</div>

There is both Subspace networking and Substrate networking stacks in the node and there is just Subspace networking stack in farmer, you can find all CLI options by running an app with `--help`.

Also note that both nodes should add each other to reserved for feature to work properly.

---

<div class="post-metadata">

**Author:** ![pascal](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/pascal/32/1150_2.png) [@pascal](https://forum.autonomys.xyz/u/pascal)\
**Post date:** [September 10, 2023, 2:14am UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720/6 "2023-09-10T02:14:27Z")

</div>

doesn’t work for me even though I enabled the `--dsn-enable-private-ips --allow-private-ip`.

---

<div class="post-metadata">

**Author:** ![pascal](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/pascal/32/1150_2.png) [@pascal](https://forum.autonomys.xyz/u/pascal)\
**Post date:** [September 10, 2023, 2:19am UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720/7 "2023-09-10T02:19:34Z")

</div>

Another question, my full synced node can not catch up the chain header easily every time I restart it, what’s the reason?

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [September 10, 2023, 2:25am UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720/8 "2023-09-10T02:25:52Z")

</div>

> [@pascal](#):
>
> doesn’t work for me even though I enabled the `--dsn-enable-private-ips --allow-private-ip`.

You’d need to provide commands from all nodes you’re running, I can’t guess what is happening there.

> [@pascal](#):
>
> Another question, my full synced node can not catch up the chain header easily every time I restart it, what’s the reason?

Can you be more specific? Vague descriptions of a problem are not possible to diagnose in most cases.

---

<div class="post-metadata">

**Author:** ![pascal](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/pascal/32/1150_2.png) [@pascal](https://forum.autonomys.xyz/u/pascal)\
**Post date:** [September 10, 2023, 2:28am UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720/9 "2023-09-10T02:28:19Z")

</div>

For 1st node, `./subspace-node --rpc-cors all --out-peers 100 --in-peers 100 --rpc-methods unsafe --rpc-external --chain gemini-3f --execution wasm --blocks-pruning archive --reserved-nodes /ip4/172.18.23.13/tcp/60004/p2p/12D3KooWAuA1y6V8ANzRwQB6G2TH4Xhtffis5dWpxaoNxHae7Whs --rpc-port 11011 --dsn-enable-private-ips --allow-private-ip --state-pruning archive --validator --base-path $DATA`.  
For 2nd node, `./subspace-node --rpc-cors all --out-peers 100 --in-peers 100 --rpc-methods unsafe --rpc-external --chain gemini-3f --execution wasm --blocks-pruning archive --reserved-only --reserved-nodes /ip4/172.18.23.82/tcp/30433/p2p/12D3KooWSdovffL4tsmQ5qxkFPQ3FhxeZawMJzSwH9NW993wLGYf --dsn-enable-private-ips --allow-private-ip --state-pruning archive --validator --base-path $DATA --dsn-listen-on /ip4/0.0.0.0/tcp/60004`.

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [September 10, 2023, 2:31am UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720/10 "2023-09-10T02:31:39Z")

</div>

> [@pascal](#):
>
> `--dsn-listen-on /ip4/0.0.0.0/tcp/60004`

This is DSN IP/port, it is not the same port as Substrate uses, this is your problem. For Substrate networking you should use `--listen-addr` instead. Yes, there are two networking stacks in the node.

---

<div class="post-metadata">

**Author:** ![pascal](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/pascal/32/1150_2.png) [@pascal](https://forum.autonomys.xyz/u/pascal)\
**Post date:** [September 10, 2023, 2:40am UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720/11 "2023-09-10T02:40:17Z")

</div>

Reserved-node works only if both they add each other as reserved-node? I remember it works in another way in last testnet.

---

<div class="post-metadata">

**Author:** ![nazar-pc](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/nazar-pc/32/6_2.png) [@nazar-pc](https://forum.autonomys.xyz/u/nazar-pc)\
**Post date:** [September 10, 2023, 2:41am UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720/12 "2023-09-10T02:41:51Z")

</div>

It always worked that way. I’m not sure what you’re trying to achieve here though, it’ll likely be useless, meaning it will only slightly decrease the network communication and increase the network latency for the second node. Not entirely sure why are you even bothering with it.

---

<div class="post-metadata">

**Author:** ![pascal](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.autonomys.xyz/pascal/32/1150_2.png) [@pascal](https://forum.autonomys.xyz/u/pascal)\
**Post date:** [September 10, 2023, 2:48am UTC](https://forum.autonomys.xyz/t/reserved-node-doesnt-work/1720/13 "2023-09-10T02:48:44Z")

</div>

I’m sure this is a different way, I’m top5 miner for both last 2 testnets. Anyway, doesn’t matter.
