Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(ASCEND) L2TP tunnel problems?


Hello,

 Did anyone succeed on setting up of the L2TP tunnels ? 
If so, could you please share that experience ?

I tried to set up a L2TP tunnel between two MAXes, but failed.
On the LNS site I always get the message :

L2TPCM-27: Connection state changed to WAITING, routeID = 0
L2TPCM-27: virtualCallAnswerCall. RouteID 189, LinearPort 12
L2TPCM-27: virtualCallUp
L2TPCM-27: sending IncomingCallReply
L2TPCM-27: virtualCallLocallyCleared
L2TPCM-27: sending CallDisconnectedNotify
L2TPCM-27: transportRxCallback from [xxx.xxx.xxx.xxx:1701/27]
L2TPCM-27: Event = RxInCallCon
L2TPCM-27: received InCallCon but can't find callID 189
                              ^^^^^^^^^^^^^^^^^^^^^^^^^
and on the LAC site

L2TPCM-31: Event = RxCallDiscNotify
L2TPCM: Clear call, route = 143
L2TPCM: _callStateChanged: Route = 143, Connected = 0, Carrier = 0
L2TPCM: Call not found for route 143
  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

 I tried both setups, per-line and per-users basis, mentioned in
separate Ascend's document "What is L2TP and how to set it up" as 
well as in Max's docs, however both of them don't work for me.

In Max's configuration I have :

Ethernet->Mod Conf -> L2 Tunneling options...
PPTP Enabled=No
L2TP=LAC (and LNS on the other site or Both)
Line 1 tunnel=L2TP (or None for per-users basis setup)
Route line=xxx.xxx.xxx.xxx (or empty for per-users basis).

Radius entry looks like:

l2tp    Password = "xxxx"
        User-Service = Framed-User,
        Framed-Protocol = PPP,
        Ascend-Link-Compression = Link-Comp-None,
        Ascend-Callback = Callback-No,
        Ascend-Route-IPX = Route-IPX-No,
        Ascend-Route-IP  = Route-IP-Yes,
        Tunnel-Type = L2TP,
        Tunnel-Medium-Type = IP,
        Tunnel-Server-Endpoint = xxx.xxx.xxx.xx, (IP addr of second MAX)
        Framed-Netmask = 255.255.255.255,
        Ascend-Metric = 2,
        Framed-Routing = None,
        Ascend-Idle-Limit = 300

In case of per-user tunnel, a call from Win95 client  should be
authenticated twice and as Ascend's doc says it's necessary to
apply pathes for Win95 but it doesn't say which ones. I tried Dun1.3,
seems the latest update from Microsoft. On the the hand, I have the same
problem in case of per-line  L2TP tunnel also, when a remote client is
authenticated only once and any PPP call to LAC is delivered to LNS
transparently through the tunnel and should looks like normal dial-in call
to LNS.

My  environment is :

 TAOS - 6.0.10(on one box) and 6.0.4 (on another).
 Win95 DUN 1.3


	 Thanks in advance,
		Andrey Bobyshev.





++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>
Follow-Ups: