help require with open vpn

[sunlight786]

hi,
i ahve install openvpn on ubuntu 9.04 and after adding all the files in openvpn folder in log file i am having this message and d,nt know what to do.
here is the message
NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.

NOTE: the current --script-security setting may allow this configuration to call user-defined scripts

i did tried to change my server ip in my configer file but nothing happend.

also i need to tell you that when i install openvpn on ubuntu 8.3 i have found no errer.
but when i install same thing on ubuntu 9.04 or 10.04 i found these erer.

any solution please?

[janjust]

with the ubuntu upgrade you probably went from openvpn 2.0 to 2.1 as well; if you are using scripts in your server config you'd need to add

Code: Select all

script-security 2

(at a mininum) to make it work again. The 2.0 behaviour can be achieved using

Code: Select all

script-security 3 system

if you do not use scripts at all then post your configs, so we can have a look.

[sunlight786]

here is my log file m8,
Wed Mar 2 20:56:09 2011 OpenVPN 2.1.0 i486-pc-linux-gnu [SSL] [LZO2] [EPOLL] [PKCS11] [MH] [PF_INET6] [eurephia] built on Jul 20 2010
Wed Mar 2 20:56:09 2011 NOTE: your local LAN uses the extremely common subnet address 192.168.0.x or 192.168.1.x. Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet.
Wed Mar 2 20:56:09 2011 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Wed Mar 2 20:56:09 2011 Diffie-Hellman initialized with 1024 bit key
Wed Mar 2 20:56:09 2011 /usr/bin/openssl-vulnkey -q -b 1024 -m <modulus omitted>
Wed Mar 2 20:56:09 2011 Control Channel Authentication: using '/etc/openvpn/ta.key' as a OpenVPN static key file
Wed Mar 2 20:56:09 2011 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Mar 2 20:56:09 2011 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication
Wed Mar 2 20:56:09 2011 TLS-Auth MTU parms [ L:1541 D:166 EF:66 EB:0 ET:0 EL:0 ]
Wed Mar 2 20:56:09 2011 ROUTE default_gateway=192.168.1.1
Wed Mar 2 20:56:09 2011 TUN/TAP device tun0 opened
Wed Mar 2 20:56:09 2011 TUN/TAP TX queue length set to 100
Wed Mar 2 20:56:09 2011 /sbin/ifconfig tun0 10.12.0.1 pointopoint 10.12.0.2 mtu 1500
Wed Mar 2 20:56:09 2011 /sbin/route add -net 10.12.0.0 netmask 255.255.255.0 gw 10.12.0.2
Wed Mar 2 20:56:09 2011 Data Channel MTU parms [ L:1541 D:1450 EF:41 EB:4 ET:0 EL:0 ]
Wed Mar 2 20:56:09 2011 Socket Buffers: R=[112640->131072] S=[112640->131072]
Wed Mar 2 20:56:09 2011 UDPv4 link local (bound): [undef]
Wed Mar 2 20:56:09 2011 UDPv4 link remote: [undef]
Wed Mar 2 20:56:09 2011 MULTI: multi_init called, r=256 v=256
Wed Mar 2 20:56:09 2011 IFCONFIG POOL: base=10.12.0.4 size=62
Wed Mar 2 20:56:09 2011 IFCONFIG POOL LIST
Wed Mar 2 20:56:09 2011 Initialization Sequence Completed



also her is my server.confg

port 19903
proto udp
dev tun
ca /etc/openvpn/ca.crt
cert /etc/openvpn/server.crt
key /etc/openvpn/server.key
dh /etc/openvpn/dh1024.pem
server 10.12.0.0 255.255.255.0
ifconfig-pool-persist /etc/openvpn/ipp.txt
push "route 192.168.1.0 255.255.255.0"
;push "route 192.168.1.1 255.255.255.0"
client-to-client
;duplicate-cn
keepalive 10 120
tls-auth /etc/openvpn/ta.key 0
persist-key
persist-tun
;user nobody
;group nobody
status /etc/openvpn/openvpn-status.log
log /etc/openvpn/openvpn.log
log-append /etc/openvpn/openvpn.log
verb 3


ihope this will help to figer out the problem

also as you said i have 2.1 instaed 2.0 then what is way to get THING BACK?

[janjust]

the 2 messages you are seeing are simply warnings - openvpn will function without them.
Your server log does not show anything abnormal; if a client cannot connect then post the client-side error, as well as the relevant part of the server log file.