That's not how MTU works.
Your host should fragment as needed when routing, in fact it does that
perfectly well for me.
The only case where you need to lower your bridge MTU is if you were to
bridge your host's eth0 or tun0 into lxdbr0, but based on the above,
that's not what you're doing at all.
It is perfectly normal for there to be varying MTU on the internet, in
fact when accessing a lot of websites, the target server is using a
lower MTU than your machine's, yet everything still works fine and you
don't have to lower your eth0 MTU to whatever MTU the website you're
trying to reach is using.
root@snappy:~# tracepath vorash.stgraber.org
1?: [LOCALHOST] pmtu 1500
1: 10.178.150.1 0.075ms
1: 10.178.150.1 0.056ms
2: sateda.lan.mtl.stgraber.net 0.313ms
3: sateda.lan.mtl.stgraber.net 0.392ms pmtu 1486
3: 206.248.154.104 15.269ms asymm 4
4: ae2-2150-bdr01-tor2.teksavvy.com 14.568ms
5: ae1-2170-bdr01-tor.teksavvy.com 14.771ms asymm 4
6: no reply
7: be10-1215.bhs-g2-a9.qc.ca 30.082ms
8: vl20.bhs-g2-a75.qc.ca 22.711ms
9: be50-7.bhs-3a-a9.qc.ca 23.463ms
10: vorash.stgraber.org 22.773ms reached
Resume: pmtu 1486 hops 10 back 10
As you can see, lxdbr0 is 1500, an intermediary router sets it to 1486
and everything works.
** Changed in: lxd (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572026
Title:
be more clever about MTU of lxdbr0
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1572026/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
