Ability to specify to hub external IP and port

BYOND Forums

Announcements · BYOND Help · Bug Reports · Feature Requests · Beta Testers · Beta Bugs · Developer Help · Design Philosophy · Demos & Libraries · Tutorials & Snippets · Art & Sound · Classified Ads · Game Updates · Contests & Events · Linux Talk · On Topic · Off Topic

ID:2953443

Nov 24, 7:06 am (Edited on Nov 24, 6:01 pm)

Anticept

Applies to:

Status:

Open

Issue hasn't been assigned a status value.

We need the ability to specify what ip and port to use to the byond hub if we want to override the automatic detection.

Currently, there is an issue where if a router has an IP block assigned, and NAT is in use, many NAT services will default to the routers's IP.

This is fine if that is the intention, but if a server is meant to use another external IP in the block, an outbound NAT rule has to be used to prevent the hub from identifying the wrong external IP.

Outbound NAT can be finicky sometimes, and NATing a whole host will then constrain all services to that external IP which is also undesirable.

It would be far better to have a way to override auto detection instead.

This would also solve the issue with internal container ports being different from external, or remapped ports crossing NAT. Since the listening port is reported by dream daemon, it will report the WRONG port in those scenarios.

Nov 25, 8:49 pm
Lummox JR	Unfortunately this is not an easy change, as it would necessarily involve multiple edits to the hub.

Dec 11, 2:40 pm
Immibis	Can you configure your NAT to use that IP for requests to the BYOND hub?

Dec 11, 11:39 pm (Edited on Dec 13, 5:32 pm)
Anticept	Source NAT is not an ideal solution. It affects all services on a host. It's already being worked around, but it would be much more desirable to have the option to specify port and IP manually. EDIT: If you mean use destination nat for that particular port, yes that can be done. However, it would be preferred that we not use the router IP.