|
|
Hi James, As per your recommendations I have upgraded today the Server and all the Clients in order to reflect the same installed software to avoid any 'compatibility' issues even if there might not be any. For the Server, everything went fine and I have tuned back the Server_Config.ovpn file to reflect the previous configuration with the 'proto udp' and 'tun-mtu', 'fragment' and 'mssfix' features. I have also removed the 'mute' statement and put back 'verb 9'. I have also changed all the clients in this order. Everything seems to be fine for the moment. I did not see anything about the previous 'bug'. I will send you the complete server trace tomorrow. By the way, do you have a FTP site where I can put this trace as maybe the file will be too big for your email... Thanx Laurent. -----Message d'origine----- De : James Yonan [mailto:jim@xxxxxxxxx] Envoyé : mardi 14 juin 2005 21:53 À : Laurent Männlein Objet : RE: [Openvpn-users] OpenVPN service running but shows exiting in trace Laurent, Thanks for the info. It would be easiest for me to track down the assertion in fragment.c bug if you would use the latest RC version: http://openvpn.net/beta/openvpn-2.0.1_rc3-install.exe I don't think you'll have any issues with stability of the RC -- it should be a drop-in replacement for 2.0. In fact, it may be more stable for you than 2.0 because I've changed the assertion failure to a warning. Use the same server-side config that you used before when the assertion failure occurred, i.e. where you are using fragment and mssfix. If you could add "verb 9" and remove "mute" that would be even better. If you can compress the log to a zip file, that would be perfect. More comments below.... James |