How to let geth always connect with another peer?

[wcw84]

Geth version: 1.8.1-stable-1e67410e

My geth is always out of date,
WARN [05-14|10:24:55] Synchronisation failed, dropping peer peer=86d38ff0ff7c68b9 err="no peers available or all tried for download" [...] WARN [05-14|10:31:31] Synchronisation failed, dropping peer peer=47bfe5e2ca07d84f err=timeout

and i also have a parity running in the same LAN with my geth node, which is always up to date.
So I tried to let my geth sync with my parity by "admin.addPeer(MY PARITY)" in the geth console, and it works(I could see "Imported new chain segment" in the geth logs immediately).
And the problem is that my parity peer will be removed from the peers list of my geth node(I don't know why?), which would be out of date again until I do "admin.addPeer".
So is there anyway to let my geth ALWAYS connect with my pairty?

Any help will be appreciated.

[ryanschneider]

This requires #16333, or for you to add the peer to the trusted peer list via .toml config at launch.

[wcw84]

Hi @ryanschneider ,
I can't find the admin_addTrustedPeer in my geth node:

$ curl -X POST --data '{"jsonrpc":"2.0","method":"admin_addTrustedPeer","params":[],"id":67}' -H 'Content-Type: application/json' localhost:8545
{"jsonrpc":"2.0","id":67,"error":{"code":-32601,"message":"The method admin_addTrustedPeer does not exist/is not available"}}

I have started my geth node with admin in rpcapi option.

And I don't understand what is ".toml" config?
Thanks.

[ryanschneider]

Sorry I should have been more clear: the PR I referenced hasn’t been merged yet. You can either compile from the PR branch or wait until it’s mergd and the next release is tagged.

The .toml config file is pretty under documented, but there’s a (possibly at this point out of date) example config here:

https://github.com/zhiyuan2007/sample-ethereum.toml

Unless you are pretty comfortable with Geth internals I think your best bet is to wait until a release with the above PR merged, as using the trusted peers option via the toml config is not documented anywhere I could except in the code.

[paulvi]

@wcw84 Add static-nodes.json with listed enode URL you want your geth node always try to connect to

http://ethdocs.org/en/latest/network/connecting-to-the-network.html#static-nodes-trusted-nodes-and-boot-nodes

Documentation about trusted-nodes.json is missing though.

[wcw84]

I have tried "admin.addPeer()" and the "static-nodes.json", they both work