1 |
On Sunday 24 January 2010 21:38:23 Konstantinos Agouros wrote: |
2 |
> Hi, |
3 |
> |
4 |
> since I am a while out of the game of doing ipsec with Linux: |
5 |
> What's the way to go? Strongswan/Openswan or ipsec-tools for kame/racoon. |
6 |
|
7 |
Openswan is simpler to configure, although I have not tried it yet. I have |
8 |
however tried to establish a racoon based VPN connection to a router and after |
9 |
I wasted an awful lot of time I gave up. :-( |
10 |
|
11 |
I think my problem was that I hadn't set up sysctl (amidst other things) to |
12 |
forward connections correctly. Either way I found the whole IPSec/Racoon |
13 |
experience ridiculously complicated compared to say, ssh. |
14 |
|
15 |
> Emerge -p gave me some ~ for ipsec-tools while openswan goes without. |
16 |
|
17 |
IPSec-tools will fail to compile lately. To overcome this you need to emerge |
18 |
~ARCH linux-headers and then emerge ipsec-tools (there's a bug about it). You |
19 |
can downgrade linux-headers after you emerge ipsec-tools. |
20 |
|
21 |
> Any input welcome. I need this for a road warrior setup. |
22 |
|
23 |
Well, if you need VPN, you need VPN. Personally, I would try to setup a ssh |
24 |
tunnel (using the -D flag) or another SOCKS5 proxy of some sort at home for |
25 |
this purpose and play with mtu sizes to get it to work without fragmentation. |
26 |
If you use ssh I would recommend using public keys and remove passwd |
27 |
authentication. |
28 |
|
29 |
However, if you succeed in setting up a VPN connection for road warrior usage |
30 |
please write a HOWTO! I will happily try it to see if it will work with my |
31 |
router. ;-) |
32 |
-- |
33 |
Regards, |
34 |
Mick |