From 4baa4ce2b3ad5450b9eb3f59b61da80ffc990113 Mon Sep 17 00:00:00 2001 From: Mike Spreitzer Date: Tue, 26 Jan 2016 14:06:17 -0500 Subject: [PATCH] Document using Q_ML2_PLUGIN_PATH_MTU I tested it, and it works! Change-Id: Ic345ededc37b2e0b7b5dbeb397aa55540d5c3bd8 Related-Bug: #1527675 --- doc/source/guides/neutron.rst | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/doc/source/guides/neutron.rst b/doc/source/guides/neutron.rst index 84295a50ce..7f93bad4c5 100644 --- a/doc/source/guides/neutron.rst +++ b/doc/source/guides/neutron.rst @@ -23,7 +23,9 @@ Physical Network Setup In most cases where DevStack is being deployed with a single interface, there is a hardware router that is being used for external connectivity and DHCP. The developer machine is connected to this -network and is on a shared subnet with other machines. +network and is on a shared subnet with other machines. The +`local.conf` exhibited here assumes that 1500 is a reasonable MTU to +use on that network. .. nwdiag:: @@ -434,6 +436,16 @@ bridge, to forward traffic sent by guest VMs. Miscellaneous Tips ================== +Non-Standard MTU on the Physical Network +---------------------------------------- + +DevStack defaults to assume that the MTU on the physical network +is 1500. A different MTU can be specified by adding the following to +the `localrc` part of `local.conf` on each machine. + +:: + Q_ML2_PLUGIN_PATH_MTU=1500 + Disabling Next Generation Firewall Tools ----------------------------------------