Opened 12 years ago
Closed 11 years ago
#267 closed Bug / Defect (notabug)
Configuration: fragementation statements after connection profiles honored by mistake
Reported by: | cn | Owned by: | |
---|---|---|---|
Priority: | trivial | Milestone: | |
Component: | Configuration | Version: | OpenVPN 2.2.2 (Community Ed) |
Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | |
Cc: |
Description
OpenVPN 2.2.2 honors 'fragment' statements in config files written after <connection>-profiles, whereas OpenVPN 2.3.0 only honors them when they are before the <connection>-profile.
According to the manpage 2.3 behaves as expected, whereas 2.2.2 honors this by mistake.
This are minimal sample configs working for 2.2.2, but causing fragmentation error messages on the server when using 2.3.0 on the client:
nobind
<connection>
remote a.b.c.d 1101
</connection>
dev tun
secret k.key
ifconfig 10.8.0.2 10.8.0.1
fragment 1400
mssfix
port 1101
dev tun
secret k.key
ifconfig 10.8.0.1 10.8.0.2
fragment 1400
mssfix
This entry is a hint for all people stumbling over this while upgrading from 2.2 -> 2.3 ;)
Closing this ticket. Google will still find this, so any people migrating from 2.2 to 2.3 will be able to find this information.