Hi,
plugins {
eap-radius {
secret =
server = xxx.xxx.xxx.xxx
}
}
This configuration sub-section must occur within the charon section, the
following definition works for me:
charon {
# ...
eap-radius {
secret = test
On Fri, 2010-04-09 at 07:58 +0200, François Pérou wrote:
http://www.mail-archive.com/users@lists.strongswan.org/msg01798.html
Dear Dimitrios,
I modified to have pluto running in debug mode on Carol:
http://www.gooze.eu/howto/using-strongswan-with-smart-cards/configuring-road-warrior-carol
I've tried it, the logs say the same as with the plugin block:
eap-radius {
strongSwan version? If you use pre 4.3.5, try eap_radius instead:
strongswan-4.3.5
- Plugin names have been streamlined: EAP plugins now have a dash after eap
(e.g. eap-sim), as it is used
Hi Daniel,
the problem is the following:
Apr 9 09:13:58 id-soft pluto[29125]:
DUS #2: protocol/port in Phase 1 ID Payload must be 0/0 or 17/500
but are 17/0
Section 4.6.2 Identification Payload Content of RFC 2407 states the
following requirement:
During Phase I negotiations, the ID
François Pérou wrote:
On Fri, 2010-04-09 at 07:58 +0200, François Pérou wrote:
Dear Dimitrios,
I modified to have pluto running in debug mode on Carol:
http://www.gooze.eu/howto/using-strongswan-with-smart-cards/configuring-road-warrior-carol
This seems to work fine on Carol side with
Hi,
The strongswan conf parser though thinks that this a syntactical }.
Yes, the strongswan.conf parser has some shortcomings, and this is
definitely one that needs a fix.
I think this is something that should be fixed in upcoming releases ?
Probably a lex/yacc based parser would make sense.
Hi Everyone,
I am a developer at Vyatta [ http://www.vyatta.org/ ] and I would like to start
by thanking and congratulating the Strongswan developers and community for
building this robust and stable software. With release Vyatta Core 6.0 which
happened last week, we've integrated Strongswan
