Not only Mark is usable, there is also TOS, MSS and other flags that may be interesting. So having separate parameter for each makes configuration more complex.
On Wed, Aug 31, 2011 at 9:38 PM, David Sommerseth <openvpn.l...@topphemmelig.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 31/08/11 20:27, Alon Bar-Lev wrote: >> Maybe should extend the usage of parameter "socket-flags"? > > I considered that too, but that would require a bigger rewrite of the > - --socket-flags parser. Currently it only is doing "boolean flags". And as > - --mark takes an argument, it's not a traditional flag but more a socket > option. > > But changing --socket-flags and --mark to --socket-opts, making it > understand TCP_NODELAY and MARK=integer ... that would be a nice step > forward. Such a move should deprecate --socket-flags via a warning in 2.3, > though - and be removed in 2.4. > > > kind regards, > > David Sommerseth > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk5ef5UACgkQDC186MBRfrrlswCeO8AgU4L58h9sL1XE358dQ2Tb > yO8An0zfR+jb2ciW3WbCarIId0K5Vq/x > =Kt9e > -----END PGP SIGNATURE----- >
