Skip to contentSkip to conversation

Clarify mssfix documentation

PATCH In review ValdikSS 3 participants 5 messages Jan 9, 2016 – Jan 15, 2016

lore
Share & tools
lore

ValdikSS

author
#0 lore raw

PATCH 1/1 Clarify mssfix documentation

---
 doc/openvpn.8 | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)
doc/openvpn.8 +5 -1
index 9760e8b..ef77b29 100644
@@ -1381,7 +1381,11 @@ parameter is interpreted in the same way as the
 .B \-\-link\-mtu
 parameter, i.e. the UDP packet size after encapsulation
 overhead has been added in, but not including
-the UDP header itself.
+the UDP header itself. Resulting packet would be at most 28
+bytes larger for IPv4 and 48 bytes for IPv6 (20/40 bytes for IP
+header and 8 bytes for UDP header). Default value of 1450 allows
+IPv4 packets to be transmitted over a link with MTU 1473 or higher
+without IP level fragmentation.
 
 The
 .B \-\-mssfix
Signature · 1 line
2.7.0
#1 lore raw

Hi,

Quoted 11 lines · ValdikSS
---
  doc/openvpn.8 | 6 +++++-
  1 file changed, 5 insertions(+), 1 deletion(-)
doc/openvpn.8 +0 -0
index 9760e8b..ef77b29 100644
@@ -1381,7 +1381,11 @@ parameter is interpreted in the same way as the
  .B \-\-link\-mtu
  parameter, i.e. the UDP packet size after encapsulation

doc/openvpn.8 parameter is interpreted in the same way as the · line 1391

Quoted 10 lines
doc/openvpn.8 +5 -1
  overhead has been added in, but not including
-the UDP header itself.
+the UDP header itself. Resulting packet would be at most 28
+bytes larger for IPv4 and 48 bytes for IPv6 (20/40 bytes for IP
+header and 8 bytes for UDP header). Default value of 1450 allows
+IPv4 packets to be transmitted over a link with MTU 1473 or higher
+without IP level fragmentation.
 
  The
  .B \-\-mssfix

this is a clarification for the --fragment option, right? and is the 28/48 bytes also applicable in TAP mode?

JJK

author
#2 lore raw

This is applicable to both --mssfix and --fragment options I believe. Yes, it affects both tun and tap modes.

Quoted 8 lines · Jan Just Keijser

Hi,

On 09/01/16 16:53, ValdikSS wrote:

this is a clarification for the --fragment option, right? and is the 28/48 bytes also applicable in TAP mode?

JJK

#3 lore raw
Quoted 2 lines · ValdikSS

This is applicable to both --mssfix and --fragment options I believe. Yes, it affects both tun and tap modes.

ah, I thought the additional text would show up under --fragment, but I did not check the 2.4 manual page yet. Other than that, ACK from me.

JJK

Quoted 10 lines · Jan Just Keijser
Quoted 8 lines

Hi,

On 09/01/16 16:53, ValdikSS wrote:

this is a clarification for the --fragment option, right? and is the 28/48 bytes also applicable in TAP mode?

JJK

#4 lore raw
In reply to ValdikSS

Thanks.

Your patch has been applied to the master and release/2.3 branch.

commit 651591525ee933c69f442d51d2b6064f2893181d (master) commit e1dc8d22185b0ddb603af459eb0fc89462cc0541 (release/2.3)

Author: ValdikSS
Date:   Sat Jan 9 18:53:45 2016 +0300
     Clarify mssfix documentation

     Acked-by: Jan Just Keijser <[email protected]...>
     Message-Id: <[email protected]...>
     URL: http://article.gmane.org/gmane.network.openvpn.devel/10969
     Signed-off-by: Gert Doering <[email protected]...>

--
kind regards,

Gert Doering