panel
panel copied to clipboard
pterodactyl
admin(eggs): add `force_outgoing_ip` option
I feel like having your traffic use the expected ip is the only way to go here and not making it an option.
I feel like having your traffic use the expected ip is the only way to go here and not making it an option.
The problem is you lose internal container networking when this feature is enabled. The way the feature works is best described by the Wings PR; it creates a dedicated network per-server with the host_ipv4 option, which is the only way setting the correct outgoing IP seems to work (at least when using Docker). I previously explored having both a dedicated network for outgoing traffic and one for internal traffic, but it is either not currently possible or requires a very specific configuration in order to work correctly.
Okay. So it's a double edged sword. On one hand you get the outbound correct. On the other you lose internal networking.
A good callout.
The only thing about this is I wish pterodactyl had an option to allow the servers to bind on the public ip but without any sort of natting or having to use host networking( since this has security issues ) so you dont get the issue where on source engine servers it can show players ips as 172.19.0.1 for example( this occurs when people join the server right after its restarted or crashed ). Plus not having natting will result in better performance.
I could probably do this with netns-dockergen but using that breaks the network usage graphs. Since I used this to have it go over a tunnel before from the container.
