As part of the recent refactoring of qp2p, the default local address was changed to `127.0.0.1`, on the basis that it is more secure to require users to opt-in to public reachability. Sadly, this change was quite disruptive
Is this perhaps why when attempting to run-baby-fleming with latest releases it complains about port forwarding?
I did. I just got distracted with RealLife™ and was forced to send my acceptance using the telepathy protocol whilst dealing with some twat from the DWP who thinks I owe them £56 from 2009.
Make with the MAID or there will be consequences !!!
Death to civil servants, especially ALL DWP employees!!!
5304782refactor!: Simplify node address config and improve validation
Node address configuration has been simplified to just two CLI options:
--local-addr to set the local address that will be bound. This still
defaults to 0.0.0.0:0 (any IP, random port).
--public-addr to set the public address that will be written in
connection info files/logs. If unspecified, this will be resolved by
qp2p by querying from a contact, if any, or falling back to the
resolved local address once bound.
In particular, --first is now a flag, and no longer takes an address
value.
Validation of address parameters has also changed:
Public addresses must be concrete (e.g. not 0.0.0.0 or port 0 ) and
non-loopback (e.g. not 127.0.0.1 ).
If the local address uses a loopback IP (e.g. 127.0.0.1 ), a public
address cannot be specified (since the node will not be public).
If --first is set, then either a public address, or a local address
with a concrete IP, must be specified.
Ultimately this should make the address configuration easier to
understand, and make it harder to start an unreachable node.
Considering my experience in trying to set up a test net on ARM Oracle Cloud, I wonder about the impact of this. I had problems with nodes not advertising their public address before; will this solve the problem or make it impossible to spin nodes on these cloud instances? Time (test nets) will tell, I suppose…
Ouch, yes we do.
Have almost as painfully as you typing the genesis key been trying to start one up for a few days and then last night while driving home I had the duh “I have been an idiot light bulb moment”.
Sep 14 04:38:15.439 INFO safe_network::routing::core: Section updated: prefix: (), key: PublicKey(18bf…b7ef), elders: 9f9b23… at 207.154.197.50:42218, a8f2e2… at 140.238.207.60:36295, a9803c… at 164.90.176.31:42217, da0802… at 139.59.134.149:42219
Taking them offline for now, will wait for an official test before running a community network.