The idea about giving specific sizes to choose from was to help prevent the admin from having to guess. We started with the two values, but were also thinking that feedback would give other optimal sizes as well.
But I do see the need to still include the ability to specify a preferred MTU value in an input field. Taking this action assumes that an "out of the ordinary" situation requires it, and that the admin knows what he is doing. I think Garrett's suggestion can be useful here. Custom tasks can be done in an "Advanced" window, so that the current MTU window is reserved for the more common "default" configurations. But optimal sizes can still be added to the two that are currently in the prototype, if there are any recommendations. Raoul Artem Kachitchkine wrote: > >> I proposed this at one point to Jenya, but evidently this would >> violate GUI convention and was forbidden. > > I'd like to hear from Jenya. I don't really care about the specifics of > implementation, but the GUI needs to be useful, and in this case we need > the ability to input a custom value in addition to selecting from preset > values. > > -Artem
