-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: upgrade go-libp2p-kad-dht #10378
Changes from all commits
fd65820
31388b5
34fbe89
90b0f7a
324424f
bc873c4
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -117,6 +117,7 @@ config file at runtime. | |
- [`Routing`](#routing) | ||
- [`Routing.Type`](#routingtype) | ||
- [`Routing.AcceleratedDHTClient`](#routingaccelerateddhtclient) | ||
- [`Routing.LoopbackAddressesOnLanDHT`](#routingloopbackaddressesonlandht) | ||
- [`Routing.Routers`](#routingrouters) | ||
- [`Routing.Routers: Type`](#routingrouters-type) | ||
- [`Routing.Routers: Parameters`](#routingrouters-parameters) | ||
|
@@ -1612,6 +1613,18 @@ Default: `false` | |
|
||
Type: `flag` | ||
|
||
### `Routing.LoopbackAddressesOnLanDHT` | ||
|
||
**EXPERIMENTAL: `Routing.LoopbackAddressesOnLanDHT` configuration may change in future release** | ||
|
||
Whether loopback addresses (e.g. 127.0.0.1) should not be ignored on the local LAN DHT. | ||
|
||
Most users do not need this setting. It can be useful during testing, when multiple Kubo nodes run on the same machine but some of them do not have `Discovery.MDNS.Enabled`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ℹ️ I played a bit with various setups and this seems to be useful only when mDNS discovery is not available. Had two nodes with MDNS, and they discovered each other and connected over Added this note so our config docs explain why and when the option matters, so users save time and not bother with it. |
||
|
||
Default: `false` | ||
|
||
Type: `bool` (missing means `false`) | ||
|
||
### `Routing.Routers` | ||
|
||
**EXPERIMENTAL: `Routing.Routers` configuration may change in future release** | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💭
LoopbackAddressesOnLanDHT
Feels overly specific given how generic go-libp2p config option is:PrivateRoutingTableFilter
PrivateQueryFilter
LoopbackAddressesOnLanDHT
is set totrue
in KuboWe have similar setup for WAN.
I would expect this a Flag to be named close to what we do in libp2p config,
Routing.DisableNoAddressFiltersOnLanDHT
and have similar one for WAN (Routing.DisableAddressFiltersOnWanDHT
) just in case we break people running custom overlay networks that don't follow official RFCs (giving them an escape hatch to self-fix, without having to report bugs to us).I don't know how real this problem is, we would have to itnterview someone working with IPFS and overlays, so don't want to block on this.
For now, if we make
LoopbackAddressesOnLanDHT
aFlag
we can leave this as-is, and fix later, if/once someone reports we broke their setup.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed to Flag. I would keep it as-is for now and see if someone complains. Otherwise we'll have to add many options. I had already discussed yesterday with @aschmahmann and we had decided on removing the WAN option for now.