-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Discovered new external address for our node #2997
Comments
Cc @tomaka |
I've followed your advice @tomaka and I am not sure I'm able to understand how the resulting logs are relating to those "new external address for our node" - if anything it seems to be the opposite, where I am getting details on other nodes, in particular those that have more than 30 addresses (?!):
At the end of the day, let's say I take the following line: 10.25.15.1 never has been part of this node (12D3KooWBg5KvtTYs1SvcV4SJno7aJ2UBBbmeZu5bubayNPBvLXM) I have just created and I assume has never existed before. The same can be said to all of the local IPs I have shared in my previous message, that are supposedly part of my node. Also all of those peer nodes have more than 30 addresses, really? There's something odd going on. |
2021-05-07 15:40:40 🔍 Discovered new external address for our node: /ip4/X.X.X.X/tcp/30333/p2p/[…]
I am getting a never ending flood of those messages mentionning IP addresses that are not configured in my system, is that a bug? If not, what is the meaning?
EDIT
This is how the log is looking currently, after running for a day:
2021-05-08 19:00:15 🔍 Discovered new external address for our node: /ip4/10.25.20.1/tcp/30333/p2p/XXX
2021-05-08 19:00:15 🔍 Discovered new external address for our node: /ip4/10.25.12.1/tcp/30333/p2p/XXX
2021-05-08 19:00:16 🔍 Discovered new external address for our node: /ip4/10.164.0.16/tcp/30333/p2p/XXX
2021-05-08 19:00:16 🔍 Discovered new external address for our node: /ip4/10.156.0.13/tcp/30333/p2p/XXX
2021-05-08 19:00:16 ⚙️ Syncing 0.3 bps, target=#7386793 (13 peers), best: #5422082 (0x22c2…5f39), finalized #5422080 (0x2581…3dc9), ⬇ 319.2kiB/s ⬆ 78.1kiB/s
2021-05-08 19:00:17 🔍 Discovered new external address for our node: /ip4/10.25.11.1/tcp/30333/p2p/XXX
2021-05-08 19:00:18 🔍 Discovered new external address for our node: /ip4/10.25.17.1/tcp/30333/p2p/XXX
2021-05-08 19:00:18 🔍 Discovered new external address for our node: /ip4/10.25.15.1/tcp/30333/p2p/XXX
2021-05-08 19:00:18 🔍 Discovered new external address for our node: /ip4/10.110.0.7/tcp/30333/p2p/XXX
2021-05-08 19:00:18 🔍 Discovered new external address for our node: /ip4/10.25.18.1/tcp/30333/p2p/XXX
2021-05-08 19:00:18 🔍 Discovered new external address for our node: /ip4/10.25.13.1/tcp/30333/p2p/XXX
2021-05-08 19:00:18 🔍 Discovered new external address for our node: /ip4/10.110.0.5/tcp/30333/p2p/XXX
2021-05-08 19:00:18 🔍 Discovered new external address for our node: /ip4/35.191.8.3/tcp/30333/p2p/XXX
2021-05-08 19:00:19 🔍 Discovered new external address for our node: /ip4/10.164.0.16/tcp/30333/p2p/XXX
2021-05-08 19:00:20 🔍 Discovered new external address for our node: /ip4/10.25.20.1/tcp/30333/p2p/XXX
2021-05-08 19:00:34 🔍 Discovered new external address for our node: /ip4/10.0.2.100/tcp/30333/p2p/XXX
2021-05-08 19:00:34 🔍 Discovered new external address for our node: /ip4/10.65.138.59/tcp/30333/p2p/XXX
Those are the IPs configured on my system:
$ sudo ip -4 addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
inet 51.161.XXX.XXX/24 brd 51.161.XXX.XXX scope global dynamic eno1
valid_lft 57918sec preferred_lft 57918sec
The text was updated successfully, but these errors were encountered: