EasyVpn

Status
Not open for further replies.
When I push the connect button on my desktop client. During the creation of the connection I select the ca, certificate and key that were generated by the servers GUI (through elastix gui).
 
Following my last message, I have finally managed to connect to openvpn. But I cannot communicate with my LAN (even with the private IP of the server). More specific, my LAN in which openvpn/elastix belongs is 192.168.100.0/24. Elastix is 192.168.100.20 and openvpn "hears" at 192.168.100.1. After successfully connected from a windows client, I got the IP 192.168.100.6/30 with a pushed default route to 192.168.100.5. Unfortunately, I cannot communicate with none of my servers in the LAN not even with elastix. Do you have any idea why this is happening? The server config is:

Code:
port 2294
proto tcp
dev tun
ca ca.crt
cert server.crt
key server.key
dh dh1024.pem
server 192.168.100.0 255.255.255.0
ifconfig-pool-persist ipp.txt
keepalive 10 120
comp-lzo
user asterisk
group asterisk
persist-key
persist-tun
status openvpn-status.log
verb 3
client-to-client
#111crl-verify /etc/openvpn/crl.pem


Another issue is that although I have configured ipp.txt to give specific IP (and not 192.168.100.6), it seems that this config is ignored. This issue is not important, I just mention it. Finally, can I use Elastix IP for terminating the vpn connection or I can only use the IP of the VPN?
 
You can't use the same network segment in your Virtual Private Network and in your real network. Clean-all and regenerate the configuration.

In the server settings use a different network(do not use 192.168.100.0) use something like 10.200.200.0 and try again.
 
Hello,

I have tried whet you suggested but still I cannot reach the LAN. I also added the push "route 192.168.100.0 255.255.255.0" command in server config but nothing changed. The client has been assigned the IP 172.16.255.6. Even if I try to ping this IP from inside the Elastix server the result is the same. The routing table inside the Elastix server is:

Code:
[root@elastix ~]# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
172.16.255.2    *               255.255.255.255 UH    0      0        0 tun0
192.168.100.0   *               255.255.255.0   U     0      0        0 eth0
172.16.255.0    172.16.255.2    255.255.255.0   UG    0      0        0 tun0
169.254.0.0     *               255.255.0.0     U     0      0        0 eth0
default         192.168.100.254 0.0.0.0         UG    0      0        0 eth0

It is possible to have no access to other servers because they do not know how to return traffic to the vpn subnet but I cannot find why I cannot access the elastix/openVPN server. Please if anyone can help, he is welcomed :)
 
After hours of searching I noticed in var/log/messages the following message:

Code:
Bad LZO decompression header byte: 42


So I figured out that the problem had to do with the compression. I changed some settings on my client and viola! ping is now working!

You have done great work with the addon. Thank you.
 
Hey team,

Been a few weeks since I responded to this so I thought I would report back and advise I have it working and so far working great.

Thanks team for all the help.

amphibian
 
Status
Not open for further replies.

Forum statistics

Threads
111,858
Messages
589,427
Members
164,698
Latest member
RRusev