[Openswan dev] [Announce] Openswan 2.4.10 Released
D. Hugh Redelmeier
hugh at mimosa.com
Wed Nov 7 02:56:33 EST 2007
| From: Paul Wouters <paul at xelerance.com>
| Xelerance releases Openswan-2.4.10
| Since this release also fixes several openwrt issues, we
| also released a binary package for openwrt, tested on a Linksys WRTG54gs
| with kamikaze 7.07, which successfully send this message through its tunnel
|
| ftp://ftp.openswan.org/openswan/binaries/openwrt/openswan_2.4.10-1_mipsel.ipk
| ftp://ftp.openswan.org/openswan/binaries/openwrt/kmod-openswan_2.4.34+2.4.10-brcm-1_mipsel.ipk
I just started trying the binary on an OpenWRT 7.09 system (x-wrt
actually).
This router is a Motorola WR850Gv2. The resources are a lot like the
Linksys WRT54gl: 4MB of flash, 16MB of RAM. This is half what the
Asus WL-500g Premium router has.
Before loading openswan, I installed tcpdump and matrix ssl. After
installing kmod_openswan, df showed:
Filesystem 1k-blocks Used Available Use% Mounted on
none 7152 744 6408 10% /tmp
/dev/mtdblock/4 1920 884 1036 46% /jffs
mini_fo:/jffs 1344 1344 0 100% /
After installing openswan proper, df showed:
Filesystem 1k-blocks Used Available Use% Mounted on
none 7152 744 6408 10% /tmp
/dev/mtdblock/4 1920 1796 124 94% /jffs
mini_fo:/jffs 1344 1344 0 100% /
So memory is getting tighter. I may have to throw something
overboard.
When did the "ipsec setup" command go away? I miss it. (It was just a
link the /etc/init.d/ipsec .)
Here's an unfortunate error. openswan (/etc/init.d/ipsec?) uses a
flag to ps(1) that busybox's ps does not implement. I have not looked
to see if the missing flag can be avoided.
root at OpenWrt:~# /etc/init.d/ipsec status
ps: illegal option -- C
BusyBox v1.4.2 (2007-11-05 13:32:21 EST) multi-call binary
Usage: ps
Report process status
Options:
w Wide output
IPsec stopped
root at OpenWrt:~#
More information about the Dev
mailing list