OpenVPN Support Forum

Hi, guys.
I'm a fresh man to OpenVPN, so I'm trying the MOST Simple configuration called "static key sample", by steping the HowTo in here : https://openvpn.net/index.php/open-sour ... howto.html.

But I am always receiving a error message : ".....write to TUN/TAP : Invalid argument (code=22)
".
The version of OpenVPN on client side is 2.3.6 for OpenWRT;
and the version on server side is 2.3.2 x86_64.
I tried both of TCP and UDP, but the issue always exist.
I tried with "comp-lzo yes" or "comp-lzo no", but the issue always exist.
I have used the configuration in the mini HowTo doc in both side, so I guess that it is not because of my fault ?

This is the configuration of my server.
"
dev tun
local {}
port 7715
proto tcp-server
ifconfig 10.8.0.1 10.8.0.2
secret california.key
comp-lzo no
push "comp-lzo no"
"

and this is of my client:
"
dev tun
nobind
port 7715
proto tcp-client
remote {ip of my server}
ifconfig 10.8.0.2 10.8.0.1
secret california.key
comp-lzo no
"

Sorry about my incondite English, I'm a Chinese.
Thanks!

evilroach wrote:version on server side is 2.3.2 x86_64

Worth updating ..

evilroach wrote:version of OpenVPN on client side is 2.3.6 for OpenWRT

Note for xWRT: Option --comp-lzo is called comp_lzo ..

Please see this report:
https://community.openvpn.net/openvpn/t ... comment:15

Traffic wrote:

evilroach wrote:version on server side is 2.3.2 x86_64

Worth updating ..

evilroach wrote:version of OpenVPN on client side is 2.3.6 for OpenWRT

Note for xWRT: Option --comp-lzo is called comp_lzo ..

Please see this report:
https://community.openvpn.net/openvpn/t ... comment:15

Thank you very much.
I tried with "comp_lzo" directive in the conf of client, but I had been rejected, and received a prompt looked like "can not recognise comp_lzo directive....."

Maybe I should update my server's openvpn.

thanks again!

Traffic wrote:Worth updating ...

I have upgraded to 2.3.8_x64 on the server side, but I'm still receiving such warning.

Traffic wrote:Note for xWRT: Option --comp-lzo is called comp_lzo ...

I saw the topic you mentioned before, so I tried both of two directives, not only "comp-lzo", but also "comp_lzo".
But the problem is always occuring !

Moderation problems ..