Thanks for your answer.

But I have a problem with my LAC. It is using a dynamic ip assigment, and I dont know 
which
one will take next time it connects.

Regards.

"Cressatti, Dominique" wrote:

> Specify another LNS
>
> Here a config file I use:
>
> ================================================================================
> [lns default]                                   ; Our fallthrough LNS definition
> exclusive = no                                  ; * Only permit one tunnel per host
> ip range = 10.32.0.140-10.32.0.159              ; * Allocate from this IP range
> ; no ip range = 192.168.0.3-192.168.0.9         ; * Except these hosts
> ; ip range = 192.168.0.5                        ; * But this one is okay
> ; ip range = lac1-lac2                          ; * And anything from lac1 to lac2's 
>IP
> lac = A.b.c.d-e.f.g.h                               ; * These can connect as LAC's
> ; no lac = untrusted.marko.net                  ; * This guy can't connect
> hidden bit = no                                 ; * Use hidden AVP's?
> local ip = 10.32.10.254                         ; * Our local IP to use
> ; length bit = yes                              ; * Use length bit in payload?
> require chap = yes                              ; * Require CHAP auth. by peer
> ; refuse pap = yes                              ; * Refuse PAP authentication
> ; refuse chap = no                              ; * 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 = myhostname                             ; * Report this as our hostname
> name = linuxfw1.lansa.co.uk
> ; ppp debug = no                                ; * Turn on PPP debugging
> ;pppoptfile = /etc/ppp/options.l2tpd.lns        ; * ppp options file
> ; call rws = 10                                 ; * RWS for call (-1 is valid)
> tunnel rws = 4                                  ; * RWS for tunnel (must be > 0)
> ; flow bit = yes                                ; * Include sequence numbers
> ; challenge = yes                               ; * Challenge authenticate peer
> ; pppoptfile = /etc/l2tp/options.l2tpd
>
> [lns lansabe1-lansauk1]
>
> exclusive = no
> name = lansabelfw0.lansa-europe.com
> lac = w.x.y.z
> ip range = 10.44.10.120
> local ip = 10.32.10.120
> require chap = yes
> require authentication = yes
> hidden bit = no
> tunnel rws = 4
> ================================================================================
> As you can see I 2 LNS.
> A default which will allow any external host with IP addresses
> between lac = A.b.c.d and e.f.g.h (lac = A.b.c.d-e.f.g.h)
> which will be assigned an internal IP address between 10.32.0.140 and 10.32.0.159
> (range = 10.32.0.140-10.32.0.159).
>
> And a specific on for a specific external IP address w.x.y.z (lac = w.x.y.z)
> which will get the internal IP address 10.44.10.120 (ip range = 10.44.10.120)
> and my counter part internal IP address is 10.32.10.120 (local ip = 10.32.10.120).
>
> Rgds
> Dom
>
> -----Original Message-----
> From: salvasa [mailto:salvasa@;tiagris.net]
> Sent: 06 November 2002 18:58
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: force LNS to give an IP address requested by LAC.
>
> HI all.
>
> How can I have LNS give an IP address requested by LAC?
>
> This is because I need to know the IP address of the LAC when It
> connects. I noticed that Each time I dial, LNS give me the next
> available IP address of the Pool. Therefore, I dont know what IP address
> is going to be using an specific LAC.  I cannot modify the LAC
> parameters, because I'm using a Vigor Router.
>
> Thanks in advance.
>
> Regards.



Reply via email to