 El Quintron... a faint odor of kerosenePremium
join:2008-04-28
Etobicoke, ON
kudos:2 | reply to Ontarionet
Re: New CRTC filing fresh off the press! :) Tinfoil hat much? |
|
1 edit | reply to R0CKY
SUPER ...TIN...FOIL...MAN
with shiny pointed hat and a mop as his weapon, to clean up the mess.
and ya where is the link or info aobut bell saying "wholesalers should not get wholesale rates"
UM go to school university and college and see whom gets whole sale rates...um people like rocky that buy wholesale...
think cosco
"um why do we have ot sell to them in bulk at wholesale rates"
answer cause if you don't no one uses you bell, and i mean you will die very quick internet death you bleeding and now ye shall bleed more with throttling and UUB?
haha good one. |
|
|
|
| reply to Guspaz
said by Guspaz:As far as we know, Juniper's ERX hardware doesn't support MPPE to begin with. The ERXs were not involved in the connections anywhere. We had a dedicated Cisco 7200 to terminate the PPPoE sessions, and had our own RADIUS server. Also Cisco supports mppe + pppoe (typical old-school wireless setup).
said by Guspaz:So it's not really a surprised that your auth requests were rejected. Your whole post comes off arrogant + condescending. Butt out if you have nothing of value to add. |
|
 GuspazGuspazPremium,MVM
join:2001-11-05
Montreal, QC
kudos:16
1 edit | said by derekm:said by Guspaz:As far as we know, Juniper's ERX hardware doesn't support MPPE to begin with. The ERXs were not involved in the connections anywhere. We had a dedicated Cisco 7200 to terminate the PPPoE sessions, and had our own RADIUS server. Also Cisco supports mppe + pppoe (typical old-school wireless setup). In which case, yeah, you should be able to get it working. It's possible that there's something on Bell's end that is preventing it from working, although I'm not as firm on the authentication process as DSL_Ricer is. I do know that the current technique used for Bell's PPPoE solution is to double-authenticate, since Bell needs to know where to forward your request (so you auth with Bell, and then with the wholesaler's endpoint).
AFAIK Bell normally just accepts anything and passes it off to the realm endpoint to reject/accept, although my memory is really fuzzy here. If they're simply denying the auth request outright instead of passing it on, that might explain the behaviour you're seeing, and would also seem to violate the GAS tariff (although Bell could probably find an excuse as to why it wouldn't).
said by derekm:said by Guspaz:So it's not really a surprised that your auth requests were rejected. Your whole post comes off arrogant + condescending. Butt out if you have nothing of value to add. It was very obviously neither arrogant nor condescending (nor was it intended to be), so I'll just pretend that you weren't incredibly rude in response. The street goes both ways. |
|
jfmezeiPremium
join:2007-01-03
Pointe-Claire, QC
kudos:22 Reviews:
 ·ELECTRONICBOX
| >I do know that the current technique used for Bell's PPPoE solution is to
>double-authenticate, since Bell needs to know where to forward your
>request (so you auth with Bell, and then with the wholesaler's endpoint).
Mr Guspaz,
first, congratulations on graduating and getting a job. (did I get this right?)
You only send one authentication request. Bell takes a peek at it and then forwards it to the proper ISP.
It is not clear to me if Bell send the PAP to the ISP whose router then sends a radius authentication, or whether the BAS sends a radius authentication request to the ISP and the BAS responds to the end user whether authentication worked or not.
However, the following dialogue for the PPP/LCP/IPCP is obviously between the end user and the ISP.
But there is only one cycle of authentication. |
|
 TSI MarcPremium,VIP
join:2006-06-23
Chatham, ON
kudos:3 | I think Guspaz is referring to the MLPPP setup on ERX01 with the "list" where there is a double auth request but it's only because it's doing RADIUS tunnel forwarding. i.e. if the realm is hard mapped, which is what I'll be setting up for the dedicated equipment, it's also what's needed to get windows mlppp working again, if it's hard mapped then the router does not need anything else to know what to do.. so it does not need to re-authenticate; all it needs it the realm name and it has that in the username forwarded from one router to another.
--
TSI Marc - TekSavvy Solutions Inc. |
|
