Package: racoon
Version: 1:0.5.2-1
Severity: important
Freshly installed, racoon doesn't work if you use racoon-tool to
generate the configuration file. This is what happens:
~# /etc/init.d/racoon start
Loading IPSEC/crypto modules...
IPSEC/crypto modules loaded.
Starting IKE (ISAKMP/Oakley) server: racoon: failed to parse
configuration file.
racoon-tool: racoon did not start.
It seems that racoon-tool doesn't generate the file
/var/lib/racoon/racoon.conf, and thus racoon doesn't find any configuration
file when it starts. Reconfiguring racoon to use the "direct" method of
configuration works. But of course, then you have to generate the
configuration file by hand, and that sucks :-)
The workaround: execute "/etc/init.d/racoon reload", which makes
racoon-tool (re)generate the configuration file. What I don't understand is
that, after you've got a working configuration file, you can safely do a
restart and a new configuration is created flawlessly.
Hope this helps.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored:
LC_ALL set to [EMAIL PROTECTED])
Versions of packages racoon depends on:
ii debconf 1.4.30.13 Debian configuration management sy
ii ipsec-tools 1:0.5.2-1 IPsec tools for Linux
ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an
ii libssl0.9.7 0.9.7e-3 SSL shared libraries
ii perl 5.8.4-8 Larry Wall's Practical Extraction
-- debconf information:
* racoon/config_mode: racoon-tool
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
