Skip to content

server: Use addrmgr.NetAddress for ban/whitelist.#3638

Open
davecgh wants to merge 2 commits intodecred:masterfrom
davecgh:server_netaddr_for_ban_and_whitelist
Open

server: Use addrmgr.NetAddress for ban/whitelist.#3638
davecgh wants to merge 2 commits intodecred:masterfrom
davecgh:server_netaddr_for_ban_and_whitelist

Conversation

@davecgh
Copy link
Copy Markdown
Member

@davecgh davecgh commented Mar 4, 2026

This requires #3633.

Currently, the whitelist and banning detection splits the host and port multiple times since the address previously hadn't been parsed yet.

However, it is no longer necessary since the parsed address is now available as soon as the peer first connects.

This updates the detection funcs to take the parsed address directly.

@davecgh davecgh added this to the 2.2.0 milestone Mar 4, 2026
@davecgh davecgh force-pushed the server_netaddr_for_ban_and_whitelist branch from 44e1740 to e7ef66b Compare March 4, 2026 19:12
@davecgh davecgh force-pushed the server_netaddr_for_ban_and_whitelist branch from e7ef66b to 5d31339 Compare March 6, 2026 18:30
@davecgh davecgh force-pushed the server_netaddr_for_ban_and_whitelist branch from 5d31339 to 465e79e Compare March 17, 2026 06:09
davecgh added 2 commits April 6, 2026 23:14
This modifies the lifecycle of peers to use the more modern Run pattern
that based on contexts.

In particular, this replaces the Start and WaitForDisconnect methods
with a single method named Run and arranges for it to block until the
provided context is cancelled or the peer is disconnected.  This is more
flexible for the caller since it can easily turn blocking code into
async code while the reverse is not true.

The new Run method waits for all goroutines that it starts to shutdown
before returning to help ensure an orderly shutdown.

Since all exported methods that send messages to the various groroutines
via channels already select across the quit channel which is closed when
the peer disconnects, the peer is now forcibly disconnected when the
context is cancelled.

This approach allows the flexibility for callers to use any combination
of manually disconnecting peers via the Disconnect method and allowing
them to automatically be disconnected when the context is cancelled.

It also updates the server code accordingly.
Currently, the whitelist and banning detection splits the host and port
multiple times since the address previously hadn't been parsed yet.

However, it is no longer necessary since the parsed address is now
available as soon as the peer first connects.

This updates the detection funcs to take the parsed address directly.
@davecgh davecgh force-pushed the server_netaddr_for_ban_and_whitelist branch from 465e79e to cec584e Compare April 7, 2026 04:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant