netdumpd receives HERALD requests on 20023 by default, and returns a random port to accept the response from the remote client. To help working in cloud & bigcorp environments, it would be useful to allow a one-off invocation of netdumpd on a fixed response port, or restrict the port range that netdumpd will support accepting responses on.
The way it works now is, - client sends a message to netdumpd on port 20023 - server replies using an ephemeral port, sends messages to the client on port 20024 I think what you want is a one-shot mode for netdumpd, where it only uses ports r20023/20024? One limitation is that one wouldn't be able to use this on a system that's running a persistent instance of netdumpd. Maybe that's acceptable though. Even nicer would be if the server could initiate a netdump...