[c-nsp] 7206 Config Help - DSL Aggregration

[Paul Stewart]

Thanks.. I've come up with another solution but it's kind of "ugly"...
The l2tp provider can send me different l2tp tunnels to various loopback
connections on my side.  So, in this setup they will send each domain to
a different loopback address on our side (same PVC etc.)  I end up with
three loopback addresses per l2tp tunnel this way though...

They won't provide separate PVC's for each domain (the provider) which
was our first choice... That's what complicated this.

I agree proxy radius would be a good way to do it, but I'm trying to
avoid that for now... Long story..;) 

Thanks again everyone... It seems the obvious answer is to either
overcome the proxy radius issue or go with the loopback options....

:)

Paul



-----Original Message-----
From: Robert Blayzor [mailto:rblayzor at inoc.net] 
Sent: Thursday, August 17, 2006 5:45 PM
To: Paul Stewart
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] 7206 Config Help - DSL Aggregration

Paul Stewart wrote:
> Thanks.. Do you mean they choose based on user at domain and domain is 
> the deciding factor?  If so, that's great - please send link...;)


No.  Depending on the PPPoE client, they either pre-configure a
"service" or "service provider" at setup time.  Some clients will prompt
you the first time the PPPoE discovery happens and a list of services
(or service providers) is echoed back from the PPPoE server.  It's not a
simple "login" thing.  I believe some PPPoE servers (like Redback) can
base the context off of the username entered, but I'm not sure the Cisco
can.  At least it didn't use to that I  know of.

The way I see it, you really have two options:
1)  Proxy RADIUS
2)  Get another PVC and place customers for the other server there.

--
Robert Blayzor, BOFH
INOC, LLC
rblayzor\@(inoc.net|gmail.com)
PGP: 0x66F90BFC @ http://pgp.mit.edu
Key fingerprint = 6296 F715 038B 44C1 2720  292A 8580 500E 66F9 0BFC

Mac OS X. Because making Unix user-friendly is easier than debugging
Windows.