Message too long

Need help configuring your VPN? Just post here and you'll get that help.
Forum rules
Please use the [oconf] BB tag for openvpn Configurations. See viewtopic.php?f=30&t=21589 for an example.
Post Reply
sunilmh
OpenVPN User
Posts: 31
Joined: Tue May 24, 2011 6:32 am

Message too long

Post by sunilmh » Tue Jun 07, 2011 10:56 am

Hi,

I'm getting very frequest log mentioned below on my openvpn server.

read UDPv4 [EMSGSIZE Path-MTU=1404]: Message too long (code=90)

I gone through some of details and found mssfix has to be updated in server.conf.
Can any one help me out to understand the extact problem and what will be the impact of this on vpn connectivity?


Thanks in advance,
Sunil

User avatar
janjust
Forum Team
Posts: 2703
Joined: Fri Aug 20, 2010 2:57 pm
Location: Amsterdam
Contact:

Re: Message too long

Post by janjust » Tue Jun 07, 2011 12:16 pm

this message shows up when OpenVPN detects that packets get fragment somewhere between client and server; to improve performance it is recommend to tweak some parameters, such as 'fragment' (udp mode only) and 'mssfix'; if you're running in udp mode I'd recommend to add

Code: Select all

fragment 1400
to both client and server configs - this should improve the overall performance of the VPN link.

sunilmh
OpenVPN User
Posts: 31
Joined: Tue May 24, 2011 6:32 am

Re: Message too long

Post by sunilmh » Tue Jun 07, 2011 1:03 pm

Thanks JJK,

Will try it out,

fragment 1400 &
for mssfix do i need to mention the same value as fragment ?


Thanks,
Sunil

User avatar
janjust
Forum Team
Posts: 2703
Joined: Fri Aug 20, 2010 2:57 pm
Location: Amsterdam
Contact:

Re: Message too long

Post by janjust » Tue Jun 07, 2011 3:10 pm

if you don't specify a size for 'mssfix' the same value is used as for 'fragment' . So

Code: Select all

fragment 1400
mssfix
is identical to

Code: Select all

fragment 1400
mssfix 1400

sunilmh
OpenVPN User
Posts: 31
Joined: Tue May 24, 2011 6:32 am

Re: Message too long

Post by sunilmh » Wed Jun 08, 2011 11:55 am

I understand 'fragment' & 'mssfix' should be lower than "EMSGSIZE Path-MTU messgae value".
I hope my understanding on this is right.

eg: EMSGSIZE Path-MTU=1308

Code: Select all

fragment 1300
mssfix 1300

User avatar
janjust
Forum Team
Posts: 2703
Joined: Fri Aug 20, 2010 2:57 pm
Location: Amsterdam
Contact:

Re: Message too long

Post by janjust » Wed Jun 08, 2011 12:29 pm

that sounds right, but I'm not 100% certain ; your best bet is to manually determine the MTU size first; this be done using

Code: Select all

ping -M do -s <size> server-IP
on linux and using

Code: Select all

ping -f -l <size> server-IP
on windows; start with size=1200 and work your way up until the pings stop working. That's the maximum (payload) MTU size; on a regular LAN you should find size=1472 . This translates to an MTU of 1500 ; if the maximum size found is 1300 then set 'fragment' to 1300+28. YMMV

sunilmh
OpenVPN User
Posts: 31
Joined: Tue May 24, 2011 6:32 am

Re: Message too long

Post by sunilmh » Fri Jun 10, 2011 12:07 pm

Do I need to add mssfix also to both server and client ?

User avatar
janjust
Forum Team
Posts: 2703
Joined: Fri Aug 20, 2010 2:57 pm
Location: Amsterdam
Contact:

Re: Message too long

Post by janjust » Fri Jun 10, 2011 12:11 pm

yes you would need to add it on both sides.

sunilmh
OpenVPN User
Posts: 31
Joined: Tue May 24, 2011 6:32 am

Re: Message too long

Post by sunilmh » Mon Jul 04, 2011 7:22 am

Hi,

If we get a continuous logs for message too long on server side,

1. Does it affect the tunnel connectivity ?
2. Does the established connection gets arbupt exit ?


Thanks

Post Reply