[rbak-nsp] SMS PPPoE RADIUS Config

Soe Prapti prapti.soe at gmail.com
Fri Aug 3 00:43:29 EDT 2012


Hi Chris,

I never use SMS, but in SER below is reply from radius :
AUTH PROCESS
auth attributes
- check/control attributes
        username
        - User-Name     : username at realm
        - Stripped-User-Name    : username (without @realm)
        password
        calling-station-id
- reply attributes
        framedipaddress
- group check/control attributes
        simultaneous-use -> session count
        ip-pool
- group reply attributes
        session-timeout
        acct-interim-interval
        framedipaddress
        client-dns-pri
        client-dns-sec
status
- accept
        enable
- reject
        disable
- accept with private ip address
        isolir
        pendingps
        retensi
        blocked
group
- by paket/service
- by status
- by nasipaddress
(combined group)
proxy
- local
- proxied
        speedyprepaid
support for attribute value swapping
logs
- auth success
- auth fail
        - user not found
        - wrong password
        - different cli
        - session exceeded
ippool
- static ippool
- dynamic ippool

ACCT PROCESS
stored in database, should be query-able
definition
- session       : accounting start & interim-update
- accounting    : accounting stop
local
- standard
- additional
proxied
- need ack
- no need ack
attributes
        AcctSessionId
        UserName
        Realm
        NASIPAddress
        NASPortId
        "ClientIPAddress"
        AcctStartTime
        AcctStopTime
        AcctSessionTime
        AcctAuthentic
        AcctInputOctets
        AcctOutputOctets
        CalledStationId
        "CallingStationId"
        AcctTerminateCause
        FramedIPAddress
        "ClientMACAddress"
        AcctStartDelay
        AcctStopDelay
        AcctStatusType
dump-able
- session
- accounting



On Fri, Aug 3, 2012 at 8:53 AM, Chris L <cjl at viptalk.net> wrote:

> Could someone please share the radius reply items they are returning for
> the initial on-demand ATM PVC authentication from a Redback device that
> tells it to start up a PPPoE session on the PVC?
>
> I know it's old hardware but it's for a temporary project.
>
> This is what we receive at the RADIUS server when there's activity on the
> on-demand PVC.
>
> rad_recv: Access-Request packet from host 172.99.99.12 port 1812, id=200,
> length=82
>         User-Name = "RDBACKS5P0.0.502"
>         User-Password = "Redback"
>         NAS-Identifier = "8873-Redback"
>         Service-Type = Dialout-Framed-User
>         NAS-Port = 208350
>
> From looking at the static configs in the manual, the attributes below
> look like what needs to be returned to put the circuit in PPPoE mode.
>
> I'm returning this but I'm never seeing the PPPoE authentication packet
> from the client router hit RADIUS.  In fact,   A circuit is never created
> in the SMS.  These exchanges just keep repeating.
>
> Login OK: [rdbacks5p0.0.502] (from client 1928redback port 208496)
> Sending Access-Accept of id 102 to 172.99.99.12 port 1812
>         Service-Type = Framed-User
>         PVC_Profile_Name = "1000-384"
>         Bind_Auth_Context = "pppoecontext"
>         PVC_Encapsulation_Type = AAA-ENCAPS-ATM-PPPOE
>         Bind_Type = AAA-AUTH-BIND
>
> Any help appreciated.
> _______________________________________________
> redback-nsp mailing list
> redback-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/redback-nsp
>



-- 
Regards,

Suparti
081384850602
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20120803/685ae74e/attachment.html>


More information about the redback-nsp mailing list