Thanks forthe quick reply.
>>If I'll ever get it working, I will let you know.
Haven't got any bits working?

-----Original Message-----
From: Norbert Wegener [mailto:[EMAIL PROTECTED]]
Sent: 08 January 2003 12:53
To: [EMAIL PROTECTED]
Subject: Re: l2tp/ipsec


If I'll ever get it working, I will let you know.

Norbert


Cressatti, Dominique wrote:
> Hi Norber,
> 
> Would you have rp-l2tp working with Win2000
> using chap by any chance?
> If yes, I'd be very grateful if you could tell
> me how you configured /etc/l2tp/l2tp.conf and
> the Win2000 client
> 
> Regards
> Dom
> 
> -----Original Message-----
> From: Norbert Wegener [mailto:[EMAIL PROTECTED]]
> Sent: 08 January 2003 12:31
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: l2tp/ipsec
> 
> 
> Hello David,
> I got the latest CVS snapshot for pppd. As your address in mentioned in 
> pppd-radius.8, I thought, you could tell me the system requirements to 
> compile the radius plugins. On linux 2.4.19/2.4.20 I run configure and 
> then make. Unfortunately make complains and dies with those messages:
> ....
> ....
> make -C radiusclient
> make[3]: Wechsel in das Verzeichnis 
> �/home/norbert/tmp/ppp/pppd/plugins/radius/radiusclient�
> cd . && autoheader
> WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
> WARNING: and `config.h.top', to define templates for `config.h.in'
> WARNING: is deprecated and discouraged.
> 
> WARNING: Using the third argument of `AC_DEFINE' and
> WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without
> WARNING: `acconfig.h':
> 
> WARNING:   AC_DEFINE([NEED_MAIN], 1,
> WARNING:             [Define if a function `main' is needed.])
> 
> WARNING: More sophisticated templates can also be produced, see the
> WARNING: documentation.
> aclocal.m4:49: error: m4_defn: undefined macro: _m4_divert_diversion
> ../autoconf/oldnames.m4:113: AM_PROG_INSTALL is expanded from...
> aclocal.m4:49: the top level
> autoheader: autom4te failed with exit status: 1
>   at /usr/bin/autoheader line 163
> make[3]: *** [stamp-h.in] Fehler 1
> make[3]: Verlassen des Verzeichnisses 
> �/home/norbert/tmp/ppp/pppd/plugins/radius/radiusclient�
> make[2]: *** [radiusclient/lib/.libs/libradiusclient.a] Fehler 2
> make[2]: Verlassen des Verzeichnisses 
> �/home/norbert/tmp/ppp/pppd/plugins/radius�
> make[1]: *** [all] Fehler 2
> make[1]: Verlassen des Verzeichnisses �/home/norbert/tmp/ppp/pppd/plugins�
> make: *** [all] Fehler 2
> Any ideas?
> Thanks
> Norbert
> 
> 
> David F. Skoll wrote:
> 
>>On Fri, 3 Jan 2003, norbert wegener wrote:
>>
>>
>>
>>>Maybe this question is a little bit off topic, but
>>>as far as I know there is hardly a radius, that supports ippool
>>>management.
>>
>>
>>Cistron radiusd lets you generate an IP address from a base address and
>>the "port number".  For real modem pools, the port number corresponds
>>to a physical port.  For virtual interfaces, you can use the PPP unit
>>number as the port number (ie ppp0 = port 0, ppp3 = port 3, etc.)
>>
>>Regards,
>>
>>David.
> 
> 
> 


-- 
Norbert Wegener    Phone:(49)2012661379 Fax:(49)2012661377
SBS Essen,Germany  Mail: [EMAIL PROTECTED]      Mailfax:(49)2018165521379
CA Cert: http://w4.siemens.de/de2/flash/digital_id/digital_id.html

Reply via email to