[rbak-nsp] Configuration for Redback to act as LAC

[Lloyd Gall]

Hi,

With the below configuration for setting up a LAC.

Will the following situation work:

We currently have L2TP peers configured on Context - providor1 and conext - providor2.

These providers send sessions to us where we terminate them (using the Redback router as a LNS).

We have a situation where a customer wants us to match on their specialised domain for users that come in from the L2TP providers and send them on a L2TP tunnel to this customer.

We want to configure the customer within their own context and the L2TP tunnel terminating there for them. Preferably if we can we would like the redback to match the domains of sessions coming from the other L2TP providers and pass them over the L2TP tunnel to the customer (using the Redback as both a LNS and a LAC).

We are unsure if the Redback will match the sessions from a different context and pass them on to the customers context and onto the customer's L2TP tunnel.

Has anybody done anything similar to this? Does anybody know if this will work?

Regards

Lloyd Gall
Level 6, 140 Queen Street. Melbourne Victoria 3000
IVR: 1300 887 877 Direct: 03 8665 8327 M:0422 100 419 
E: lgall at staff.ains.net.au W: www.ains.com.au



This email and any attachments may contain privileged and confidential information and are intended for the named addressee only. If you have received this e-mail in error, please notify us immediately by telephone on 1300 887 877 and delete this e-mail immediately. Any confidentiality, privilege or copyright is not waived or lost because this e-mail has been sent to you in error. It is your responsibility to check this e-mail and any attachments for viruses.
BE GREEN! Read from the screen.


-----Original Message-----
From: redback-nsp [mailto:redback-nsp-bounces at puck.nether.net] On Behalf Of Voigt, Thomas
Sent: Tuesday, 3 September 2013 7:32 PM
To: redback-nsp at puck.nether.net
Subject: Re: [rbak-nsp] Configuration for Redback to act as LAC

Hi,
 
Curtis Raams wrote:
 
> Does anyone have configuration for an SE-400 to act as a LAC for L2TP DSL sessions for a specific realm?

Not specially for SE-400, but it should be the same as on our SE-600/1200 here:

######################

context foo
 domain <your-realm.com>
 aaa authentication subscriber none

 subscriber default
   tunnel domain

 interface <ip-interface> loopback
  description L2TP-Interface
  ip address <lac-ip>

l2tp-peer name <lns-on-the-other-side> media udp-ip remote ip <lns-ip> local <lac-ip>
  domain <your-realm.com>
  function lac-only
  propagate qos to l2tp
  propagate qos from l2tp 

######################

This should be minimal config for LAC function.

--
Regards 

Thomas
 



_______________________________________________
redback-nsp mailing list
redback-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/redback-nsp

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com ______________________________________________________________________

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________