Skip to content

Conversation

@buttercookie42
Copy link

The way I understand it, the ability to use a custom port is mainly relevant for listening (because you can't bind a socket to a port < 1023 without root on unixoid systems), and the documentation explicitly points out the scenario of configuring a non-privileged port and then use firewall rules to forward the network traffic to the unprivileged port.

In that case, it wouldn't make sense to use the same alternative ports as the destination port when sending out various broadcast messages, however this is exactly what currently happens.

We already hardcode e.g. the name server port when sending out a few messages (e.g. here), so I just propose completing that status and hardcode the remaining messages relevant for the name server and the host announcer, too.

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