that is not possible, both nodes should agree on protocol first, so if both support duplex, they might agree on enabling it.
At least this is my understanding. Additionally I have this setup in production with duplex on relay and legacy on bp and I do not produce dual blocks.
That config line is no longer necessary with version 1.35.7. I have deleted it from my configs. You just need to have this line:
“EnableP2P”: true,
And appropriate mainnet-topology.json file.
Yes, that is also what I believe.
So if you want to control when relays can pull blocks from your backup producer then you had better run them in legacy mode, or firewall both inbound and outbound TCP connection establishment (which would presumably also prevent the producer from remaining in sync).
However, what will you do if legacy mode goes the way of the Dodo with future node versions???
yes, seems you are right about it. Not sure how I can disable duplex now when p2p is enabled. "TestEnableDevelopmentNetworkProtocols": false, do not disable duplex now.
Not sure if it ever goes away, but if does, I will search for a new solution. I tend to fix problem as they arrive, not sure if it is best approach, though.
I don’t think you can. Just don’t enable P2P and then you should only get the legacy uni-directional connections which you can selectively firewall.