Thanks for the input! I didn't see that mentioned anywhere before.
After having created the directory and ran depmod -a the directory now
received some content.
root@vps1703 [/]# ll /lib/modules/2.6.32-042stab090.3/
total 48
drwxr-xr-x 2 root root 4096 Jun 27 16:02 ./
drwxr-xr-x 3 root root 4096
Please disregard the small version difference (stab090.3 vs stab090.4)
- I am testing on two different servers with minor differences in the
Kernel installed. The one throwing the 090.3 error actually runs the
090.3 kernel. Sorry for the inconsistancy.
On Fri, Jun 27, 2014 at 3:27 PM, Ian wrote:
On 26/06/2014 18:52, Rene C. wrote:
> Going through the whole thing again I fell over this fatal error
> during the ipsec restart:
>
> ipsec_setup: FATAL: Could not load
> /lib/modules/2.6.32-042stab090.3/modules.dep: No such file or
> directory
>
> I installed both openswan xl2tpd though yum (ep
Could you do strace for this command: ipsec verify ?
strace -o /root/trace -s 1024 -f ipsec verify
And send trace to paste.org.
On Thu, Jun 26, 2014 at 10:23 PM, Rene C. wrote:
> Ok ... it doesn't need anything to be in modules.dep?
>
> /lib/modules/2.6.32-042stab090.3 didn't exist, I had to c
Ok ... it doesn't need anything to be in modules.dep?
/lib/modules/2.6.32-042stab090.3 didn't exist, I had to create it. So
what will happen after next kernel update? This doesn't seem right.
Both the hwnode and the vps server runs 64 bit version of Linux, so
there's also a /lib64 - but no /lib6
Hello!
You can try to do something like this:
touch /lib/modules/2.6.32-042stab090.3/modules.dep
It can suppress ipsec_setup warnings.
On Thu, Jun 26, 2014 at 9:52 PM, Rene C. wrote:
> Going through the whole thing again I fell over this fatal error
> during the ipsec restart:
>
> ipsec_setup:
Going through the whole thing again I fell over this fatal error
during the ipsec restart:
ipsec_setup: FATAL: Could not load
/lib/modules/2.6.32-042stab090.3/modules.dep: No such file or
directory
I installed both openswan xl2tpd though yum (epel repo) but neither
seem to add anything to /lib/mo
I already upgraded the kernel to the latest before the last test:
[root@server14 ~]# uname -a
Linux server14.-sanitized- 2.6.32-042stab090.4 #1 SMP Mon Jun 16
Sorry if I didn't make that very clear
On Thu, Jun 26, 2014 at 1:38 PM, Pavel Odintsov
wrote:
> Hello!
>
> I'm not sure about your probl
Hello!
I'm not sure about your problems but we have few production
installation with this configuration. But we use only up to date
kernels like 90.x series. What kernel you used for tests?
On Thu, Jun 26, 2014 at 5:28 AM, spameden wrote:
>
>
>
> 2014-06-25 22:19 GMT+04:00 Rene C. :
>
>> No, I w
2014-06-25 22:19 GMT+04:00 Rene C. :
> No, I went in the direction of l2tp as recommended. It both seems more
> secure and more compatible with both windows and android clients than
> openvpn.
>
'more secure' ?
did you audit OpenVPN/OpenSSL code? How can you say so.
There are clients for both
No, I went in the direction of l2tp as recommended. It both seems more
secure and more compatible with both windows and android clients than
openvpn.
I still get the "Checking for IPsec support in kernel
[FAILED]" error from the check, although the latest openvz
kernel is now installed.
Wh
2014-06-23 11:31 GMT+04:00 Rene C. :
> Sorry, still stuck:
>
Did you try OpenVPN configuration that I've suggested?
About IPSEC: not sure, check your syslog logs might give you some tips.
>
> [root@server14 ~]# uname -a
> Linux server14.-sanitized- 2.6.32-042stab090.4 #1 SMP Mon Jun 16
> 15:13:
Sorry, still stuck:
[root@server14 ~]# uname -a
Linux server14.-sanitized- 2.6.32-042stab090.4 #1 SMP Mon Jun 16
15:13:38 MSK 2014 x86_64 x86_64 x86_64 GNU/Linux
[root@server14 ~]# for x in tun ppp_async pppol2tp
xfrm4_mode_transport xfrm4_mode_tunnel xfrm_ipcomp esp4; do lsmod |
grep $x; done
xfr
2014-06-21 10:47 GMT+04:00 Rene C. :
> I got the openvpn part itself down, no problem, but getting it to work
> in a container is a lot of hassle. Many pages, but most are outdated
> and things keeps changing. Anyone know how to get it to work TODAY?
>
> The server is an otherwise normal server wi
Yep, rebooted the container.
Here's the modules present:
[root@server18 ~]# lsmod
Module Size Used by
esp45406 0
xfrm_ipcomp 4626 0
xfrm4_mode_tunnel 2019 0
pppol2tp 22749 0
pppox 2712 1 pppol2tp
ppp_asyn
Hello!
IPsec should work from 84.8 kernel according to
https://openvz.org/IPsec but I found explicit reference about IPsec
only in 84.10: http://openvz.org/Download/kernel/rhel6-testing/042stab084.10
Did you restart CT after loading kernel modules for l2tp?
On Sun, Jun 22, 2014 at 7:05 PM, Rene
Ok I gave your suggestion a shot, using your link through Google
translate and http://www.maxwhale.com/how-to-install-l2tp-vpn-on-centos/
for comparison.
Everything seems to go well until the 'ipsec verify' part when it says:
[root@vps1418 /]# ipsec verify
Checking your system to see if IPsec got
Hello!
In modern version of OpenVZ you can use l2tp with ipsec support
instead OpenVPN: http://habrahabr.ru/company/FastVPS/blog/205162/
(sorry this manual in russian language but it's very simple). It's
very useable because you do not need any special clients on Windows
hosts. Maybe you can try t
On Sat, Jun 21, 2014 at 8:47 AM, Rene C. wrote:
> I got the openvpn part itself down, no problem, but getting it to work
> in a container is a lot of hassle. Many pages, but most are outdated
> and things keeps changing. Anyone know how to get it to work TODAY?
>
> The server is an otherwise norma
Hi, thanks for your quick reply.
I did actually, but when I just did it again in order to be able to
copy/paste the error here it actually didn't throw any now.
Now, when I'm connected to the server, I can access websites on the
server itself, although very slow, but nothing outside, so I think I
did you try using source NAT as in
iptables -t nat -A POSTROUTING -s /24 -j SNAT --to-source
Admin
RoseHosting.com
On 6/21/2014 1:47 AM, Rene C. wrote:
I got the openvpn part itself down, no problem, but getting it to work
in a container is a lot of hassle. Many pages, but most are outdated
21 matches
Mail list logo