Hello, I've got ebox running as a domU in Xen with two physical Network Cards. One for my external network (192.168.100.0/24) and one for my internal(192.168.0.1). My OpenVPN Network is a 192.168.66.0/24 network.
In the Server Configuration I had disabled NAT and EBOX2EBOX connections. I had enabled Allow-Client2Cl. connections. In the advertised networks pane I added my 192.168.0.0/24 local Lan. My ebox local Lan IP is 192.168.0.1 and my Xen Server got the 192.168.0.244
My first problem is when connecting over OpenVPN from the Internet using the Linux client configuration package the connection establishs correctly but I can only connect to my ebox(192.168.0.1) my xen server isn't available from outside.
My second problem is connecting using the complete Windows Configuration package. I always get errors like this and the connection don't establishs:
Wed Sep 10 19:54:24 2008 TCP connection established with 84.xx.110.xx:xxxx
Wed Sep 10 19:54:24 2008 TCPv4_CLIENT link local: [undef]
Wed Sep 10 19:54:24 2008 TCPv4_CLIENT link remote: 84.xx.110.xx:xxx
Wed Sep 10 19:54:24 2008 TLS: Initial packet from 84.xx.110.xx:xxx, sid=47a9b
cc7 281f4775
Wed Sep 10 19:54:24 2008 VERIFY ERROR: depth=1, error=certificate is not yet val
id: /C=ES/ST=Nation/L=Nowhere/O=qsm/CN=Certification_Authority_Certificate
Wed Sep 10 19:54:24 2008 TLS_ERROR: BIO read tls_read_plaintext error: error:140
90086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
Wed Sep 10 19:54:24 2008 TLS Error: TLS object -> incoming plaintext read error
Wed Sep 10 19:54:24 2008 TLS Error: TLS handshake failed
Wed Sep 10 19:54:24 2008 Fatal TLS error (check_tls_errors_co), restarting
Wed Sep 10 19:54:24 2008 TCP/UDP: Closing socket
Wed Sep 10 19:54:24 2008 SIGUSR1[soft,tls-error] received, process restarting
Wed Sep 10 19:54:24 2008 Restart pause, 5 second(s)
I also disbled the Windows Firewall for my openvpn network card and removed the quotes in the openvpn config file surrounding the filenames.
Nothing worked
I appreciate any help or idea