Regarding vpn error

hi friends,

i have installed openvpn in centos server.i got all the details from the client including client.key .when i tried to communicate the client it shows the following error

Fri Jan 4 15:42:22 2013: IMPORTANT: OpenVPN's default port number is now 1194, based on an official port number assignment by IANA. OpenVPN 2.0-beta16 and earlier used 5000 as the default port.
Fri Jan 4 15:42:22 2013: WARNING: Make sure you understand the semantics of --tls-remote before using it (see the man page).
Fri Jan 4 15:42:22 2013: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Fri Jan 4 15:42:22 2013: WARNING: file 'gatekeeper-udp-1194.p12' is group or others accessible
Fri Jan 4 15:42:22 2013: WARNING: file 'gatekeeper-udp-1194-tls.key' is group or others accessible
Fri Jan 4 15:42:22 2013: Control Channel Authentication: using 'gatekeeper-udp-1194-tls.key' as a OpenVPN static key file
Fri Jan 4 15:42:22 2013: LZO compression initialized
Fri Jan 4 15:42:22 2013: UDPv4 link local (bound): [undef]:1194
Fri Jan 4 15:42:22 2013: UDPv4 link remote: 108.217.253.176:1194
Fri Jan 4 15:42:23 2013: WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Fri Jan 4 15:42:35 2013: [GTEMMQ-SERVER] Peer Connection Initiated with 108.217.253.176:1194
Fri Jan 4 15:42:43 2013: TUN/TAP device tun0 opened
Fri Jan 4 15:42:43 2013: /sbin/ip link set dev tun0 up mtu 1500
Fri Jan 4 15:42:43 2013: /sbin/ip addr add dev tun0 local 192.168.200.14 peer 192.168.200.13
Fri Jan 4 15:42:43 2013: ERROR: Linux route add command failed: external program exited with error status: 2
Fri Jan 4 15:42:43 2013: Initialization Sequence Completed

give your suggestion

Comments

Post a Comment

Popular posts from this blog

yum failed 6 times. Cannot continue!

Error while cPanel installation: (ERROR): - ssystem [EXIT_CODE] '/usr/bin/yum' exited with 1 (ignored) (DEBUG): - ssystem [END] (FATAL): yum failed 6 times. Cannot continue! fix: It looks like you have some name resolution issues on the server. Just run the following commands on your server and it will resolve the name resolution issues. #echo "nameserver 8.8.8.8" >> /etc/resolv.conf #echo "nameserver 8.8.4.4" >> /etc/resolv.conf if it is not working properly still facing same error, then here we go, # rpm -e --nodeps bind-chroot # rpm -e --nodeps bind # yum install bind
Read more

Resolved: DOCKER: Error response from daemon: Could not attach to network / rpc error: code = 7 desc = network not manually attachable.

Image
I got this error: 'docker: Error response from daemon: Could not attach to network <nw-name>: rpc error: code = 7 desc = network <nw-name> not manually attachable.' when i try to create the container on the overlay network on swarm mode enabled, In docker 1.12 with swarm mode enabled, "Swarm" scoped networks (see the "SCOPE" column) cannot be used for docker run, only for services and now it has been rectified. I'm using updated version of docker, but still why i'm experiencing the error ? because the network just created but not manually attachable. To fix the issue we gonna use --attachable flag while creating network. [ --attachable             Enable manual container attachment ] (Need to create service on the overlay network, so that the overlay network will available / list on the worker node) docker inspect attnw (attnw is our test network)should show your own c
Read more

unexpectedly shrunk window (repaired) in dmesg log - TCP Peer

Don't Panic, This normally occurs when a client decides to reduce its TCP window size, without the server expecting it. This can be the case when fragmentation is an issue, or when the client is using an embedded device with very little NIC buffer memory. This is a completely normal behaviour, and you’re likely to see quite a few such packets in your log. The messages are informational only, and are used to debug networking issues. I’d be worried if you saw hundreds of thousands of these packets, since there are attacks that involve packet fragmentation and small window sizes, but otherwise it’s just the normal sort of noise you should expect to see on any internet-facing network. In fact, the “repaired” part of your message is showing that your network driver fixed the issue, which is usually done by concatenating the payloads of two fragmented packets together. Shouldn’t be an issue at all. … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … … 
Read more