Panel: Add custom configuration for setting MTU of servers interfaces created via docker

[SAMXPS]

Is your feature request related to a problem? Please describe.
Yes, we are having problems configuring the panel because we need custom MTU settings so that our network connection works properly inside the servers.

Describe the solution you'd like
I'd like some way of configuring the MTU of interfaces created here:
https://github.com/pterodactyl/wings/blob/develop/environment/docker.go#L91

The default MTU of 1500 doesn't work for us.

Other solutions considered
We considered changing the source code by ourselves and trying to add this functionality, but we need more help to do so.

[parkervcp]

You can just change that one line and re-compile wings to have a different MTU. Go is quite easy to compile.

[SAMXPS]

Ok, I will try that.

After,
Would you like me to create a custom configuration setting and pull request as a feature?

https://prnt.sc/ve4nnt

[parkervcp]

I think it being a configurable value makes sense.

[sergiz]

You can create a new docker network and simply point wings to use it ("docker.network.name" config). Or delete "pterodactyl_nw" and recreate it manually with desired settings.

[parkervcp]

While that is possible making it a configurable value would be good for more people.

[schrej]

I think this was possible with the old daemon as well.

[sergiz]

I think this was possible with the old daemon as well.

Negative
https://github.com/pterodactyl/daemon/blob/208f85ca96e400dec43faf28bcc34e28a0bd8424/src/controllers/network.js#L85

[SAMXPS]

While that is possible making it a configurable value would be good for more people.

Yes. That would be great.

[SAMXPS]

You can create a new docker network and simply point wings to use it ("docker.network.name" config). Or delete "pterodactyl_nw" and recreate it manually with desired settings.

This worked for me! Thank you very much!

[DaneEveritt]

I think since you can just create custom networks Im going to leave it at that.

It's been five years and you're the first person to find this needed, and it was easily resolved with a custom network (which would allow allow all the customization you'd ever need, without us having to support effectively an entire docker config as well).