>>rp-l2tp must know ahead of time the IP address of the peer Can you expand? because I tried the following: ============= # Peer section section peer peer 195.157.58.113 strict-ip-check 0 port 1701 lac-handler sync-pppd lns-handler sync-pppd hide-avps no ============== So given that I have "strict-ip-check 0", I would think that if am coming from 195.157.58.114 it would still work. Or am wrong? If am right then may there is bug in code.
>>It would not be too hard to add road-warrior support I've looked at your code but my c/c++ is bit rusty. May be you could give some idea and or where you are matching the IP address. I think I may be able to extend that part with something along the line of IP address/netmask. Regards Dom -----Original Message----- From: David F. Skoll [mailto:[EMAIL PROTECTED]] Sent: 08 January 2003 19:35 To: [EMAIL PROTECTED] Subject: RE: rp-l2tp On Wed, 8 Jan 2003, Cressatti, Dominique wrote: > Same story, even I have n_hdlc loaded, > yet I get a message > "...IPAddress is not authorized to create a tunnel." rp-l2tp must know ahead of time the IP address of the peer. It does not work in a "road warrior" mode, unfortunately. If your peer is always coming from a fixed IP address, just add the appropriate "section peer" section. It would not be too hard to add road-warrior support, but unfortunately, I don't have time to do it. I'm still looking for someone to take over rp-l2tp from me... Regards, David.
