BUG? automatic mtu inside of LXC

[mvrhov]

Hey,

I've just spent 4 days figuring out why there is no transfer of data on hetzener vswitch between multiple proxmox machines...
The problem was mtu.. which has to be set on the actual interface and not the bridge. Now the problem remaining is that the Proxmox doesn't set the mtu of the LXC so the mtu inside of lxc remains 1500 which means that there is a high probability that a lot of packet leaving the proxmox server are fragmeted.

 

[Alwin]

You can set the mtu size through pct set <vmid> or directly in the config.
https://pve.proxmox.com/pve-docs/chapter-pct.html#pct_container_network

 

[mvrhov]

But this is not automatic (which should be) so you can easily forget.

 

[Alwin]

You can use hookscripts to set the MTU on startup or create the container on the CLI. There it is possible to set the MTU right on creation.
https://pve.proxmox.com/pve-docs/chapter-pct.html#_hookscripts

Also, another possible option might be to set the advmss on the route (man ip-route).

 

[Abd7]

You can use hookscripts to set the MTU on startup or create the container on the CLI. There it is possible to set the MTU right on creation.
https://pve.proxmox.com/pve-docs/chapter-pct.html#_hookscripts

Also, another possible option might be to set the advmss on the route (man ip-route).

Any hint how to set MTU on startup for LXC ?