Hi,

We are wanting to use L2TPd to terminate dial-up sessions from our local 
carrier (nothing fancy there).

We have all of the physical services delivered and are having a few 
problems with L2TPD and or PPP and I hope someone out there can shed some 
light or point me in the right direction.

Our configuration is:
l2tpd-0.69-1
ppp-2.4.1-10
linux 2.4.21 (custom kernel (ppp is compiled as a module))

Our L2TP configuration is very simple because our provider only makes 
connections to us (now as i saw someone was flamed for putting real world 
information into their e-mail i have replaced it - if its required please 
let me know and i will supply it).

/etc/modules.conf
<snip>
..
alias char-major-108    ppp_generic
alias tty-ldisc-3       ppp_async
alias tty-ldisc-14      ppp_synctty
alias ppp-compress-21   bsd_comp
alias ppp-compress-24   ppp_deflate
alias ppp-compress-26   ppp_deflate
..
</snip>

/etc/l2tpd/l2tpd.conf
<snip>
[global]                                ; Global parameters:
port = 1701;                            * Bind to port 1701
auth file = /etc/l2tpd/l2tp-secrets;    * Where our challenge secrets are
access control = no;                    * Refuse connections without IP match
;
[lns default]                           ; Our fallthrough LNS definition
exclusive = no;                         * Only permit one tunnel per host
ip range = 192.168.0.10 - 192.168.0.255;* Allocate from this IP range
lac = xxx.xx.xx.x - xxx.xx.xx.xxx;      * These can connect as LAC's
hidden bit = no;                        * Use hidden AVP's?
local ip = 192.168.0.1;                 * Our local IP to use
length bit = yes;                       * Use length bit in payload?
require chap = no;                      * Require CHAP auth. by peer
refuse pap = no;                        * Refuse PAP authentication
refuse chap = no;                       * Refuse CHAP authentication
refuse authentication = no;             * Refuse authentication altogether
require authentication = yes;           * Require peer to authenticate
unix authentication = yes;              * Use /etc/passwd for auth.
name = myservername;                    * Report this as our hostname
ppp debug = yes;                        * Turn on PPP debugging
pppoptfile = /etc/ppp/options;          * PPP option file
tunnel rws = 4;                         * RWS for tunnel (must be > 0)
flow bit = yes;                         * Include sequence numbers
challenge = yes;                        * Challenge authenticate peer
</snip>

Basicly the secrets is configured to allow anyone to connect using 
mysecret (as far as I can tell).

/etc/l2tpd/l2tp-secrets
<snip>
..
*       *       mysecret
..
</snip>

/etc/ppp/options
<snip>
lock
auth
debug
logfd 2
logfile /var/log/l2tpd.log
passive
nodetach
noccp
novj
novjccomp
nopcomp
noaccomp
</snip>

The user we are using exists only in /etc/passwd and their username and 
password are correct I have manually logged into the server with them.

I'm running l2tpd in the foreground and it looks like its working 
correctly, it spawns a copy of pppd with the following parameters (so a 
ps tells me):

/usr/sbin/pppd passive -detach 192.168.0.1:192.168.0.10 auth login name 
myservername debug file /etc/ppp/options

The ppp debug file displays the following:

/var/log/l2tpd.log
<snip>
..
using channel 38
Using interface ppp0
Connect: ppp0 <--> /dev/pts/6
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <auth pap> <magic 0x12f269b4>]
..
sent [LCP ConfReq id=0x1 <asyncmap 0x0> <auth pap> <magic 0x12f269b4>]
LCP: timeout sending Config-Requests
..
</snip>

If i do a 'ifconfig -a' I notice the ppp0 adapter is configured but no IP 
address and is not up (no surprise there).

Basicly its not working, i have been looking at this most of the afternoon
and if any one can help I would be very very happy...

Cheers.

-- 
Tim Philips

-----------------------------------------------------
iSERVE - You're in Business
www.iserve.co.nz |  [EMAIL PROTECTED]  | 0800 144 737
=====================================================




Reply via email to