[rbak-nsp] Problem with Pppoe over link-grouo

Заикин Станислав zaikin_s at ufanet.ru
Sun Mar 3 05:40:42 EST 2019


02.03.2019 13:07, Bartek Mickiewicz пишет:
>
> Hi,
> I'm running Smartedge router for PPPOE clients connections, after I 
> added interfaces witch are used for incoming connections I ran into a 
> problem. Clients can't authorize their sessions.
> Here is my link-group configuration:
> link-group Erry access
>  encapsulation dot1q
>  maximum-links 2
>  lacp active
>  dot1q pvc 394 encapsulation multi
>   circuit protocol pppoe
>    bind authentication chap context pp01 maximum 2000
> And here is fragment of subscribers log
> 9301 IN Fri Mar 1 20:43:18.844557
>
>         IPC_ENDPOINT = PPPd, MSG_TYPE = SESSION_DOWN, term_ec = 26
>         terminate cause = Subscriber provisioning failed
>         Username = testtest812,
>         CCT_HANDLE = Unknown circuit
>         Internal Circuit = 255/22:13:59/6/2/292112
>         aaa_idx = 11abe66b, extern_handle = fd, pvd_idx = 40080004,
>         Event code = 0
>
> And in database I see
> Subscriber provisioning failed
>
>
>
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp

Hello,

Subscriber provisioning failed could mean two things:

1) You don't send some necessary attributes.

2) You send multiple attributes, which incompatible with each other.

You can try to run "debug aaa exception" and you will see what is wrong.

Can you show your RADIUS access-request and access-accept for this session?

-- 
Stanislav Zaikin
Network Engineer
JSC Ufanet

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20190303/ebc9de06/attachment.html>


More information about the redback-nsp mailing list