1st don't put any public IP addresses
in an email. Some people could use
them to launch an attack against those
IP addresses. Replace them by W.X.Y.Z
for example.

2nd why did you specify your public IP address
as the local one?
I believe you should the use the private one,
may be that's the cause of your problem.

Apart from that sorry but I haven't got any other
clue.

Dom

-----Original Message-----
From: Thierry Coutelier [mailto:[EMAIL PROTECTED]
Sent: 25 March 2003 14:17
To: [EMAIL PROTECTED]
Subject: Re: Packets sent to wrong LAC with L2TPD



Here is my l2tpd.conf

/etc/l2tp/l2tpd.conf  

; config file for LNS server to act with Ascend
;
;
[global]                                ; Global parameters:
port = 1701                             ; * Bind to port 1701
auth file = /etc/l2tp/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.1-192.168.0.20     ; * Allocate from this IP range
lac = 194.7.201.18 - 194.7.201.24       ; * These can connect as LAC's
lac = 192.168.37.0 - 192.168.37.255
lac = 133.33.225.129
lac = 222.228.32.248
lac = 222.222.36.0 - 222.222.36.255
hidden bit = no                         ; * Use hidden AVP's?
local ip = 217.28.32.20                 ; * 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 = yes                       ; * Refuse CHAP authentication
refuse authentication = no              ; * Refuse authentication altogether
require authentication = yes            ; * Require peer to authenticate
unix authentication = no                ; * Use /etc/passwd for auth.
name = nsabvpn2                         ; * 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 = no                          ; * Challenge authenticate peer ;




Cressatti, Dominique wrote:

>Am surprised, cause am using it in
>production with 2 LAC and I haven't
>seen any issues.
>
>What does your /etc/l2tp/l2tpd.conf
>looks like?
>
>Dom
>
>-----Original Message-----
>From: Thierry Coutelier [mailto:[EMAIL PROTECTED]
>Sent: 24 March 2003 14:24
>To: [EMAIL PROTECTED]
>Subject: Packets sent to wrong LAC with L2TPD
>
>
>Hello,
>
>I'm using l2tpd 0.69 as LNS server.
>We have an ISP forwading ppp sessions to out tunnel.
>Everything works fine when there is only one LAC.
>When using more LAC's ( for ex. A and B) we get the problem that 
>sometimes packets
> from tunnel from LAC-A are answered to the tunnel on LAC-B.
>
>Here is a sample tcpdump on the LNS server (I do not have
>access to the LAC severs):
>
>
>---
>Thierry Coutelier
>http://www.linux.lu
>
>  
>



Reply via email to