Hi Chris,<br><br>I never use SMS, but in SER below is reply from radius :<br>AUTH PROCESS<br>
auth attributes<br>
- check/control attributes<br>
username<br>
- User-Name : username@realm<br>
- Stripped-User-Name : username (without @realm)<br>
password<br>
calling-station-id<br>
- reply attributes<br>
framedipaddress<br>
- group check/control attributes<br>
simultaneous-use -> session count<br>
ip-pool<br>
- group reply attributes<br>
session-timeout<br>
acct-interim-interval<br>
framedipaddress<br>
client-dns-pri<br>
client-dns-sec<br>
status<br>
- accept<br>
enable<br>
- reject<br>
disable<br>
- accept with private ip address<br>
isolir<br>
pendingps<br>
retensi<br>
blocked<br>
group<br>
- by paket/service<br>
- by status<br>
- by nasipaddress<br>
(combined group)<br>
proxy<br>
- local<br>
- proxied<br>
speedyprepaid<br>
support for attribute value swapping<br>
logs<br>
- auth success<br>
- auth fail<br>
- user not found<br>
- wrong password<br>
- different cli<br>
- session exceeded<br>
ippool<br>
- static ippool<br>
- dynamic ippool<br>
<br>
ACCT PROCESS<br>
stored in database, should be query-able<br>
definition<br>
- session : accounting start & interim-update<br>
- accounting : accounting stop<br>
local<br>
- standard<br>
- additional<br>
proxied<br>
- need ack<br>
- no need ack<br>
attributes<br>
AcctSessionId<br>
UserName<br>
Realm<br>
NASIPAddress<br>
NASPortId<br>
"ClientIPAddress"<br>
AcctStartTime<br>
AcctStopTime<br>
AcctSessionTime<br>
AcctAuthentic<br>
AcctInputOctets<br>
AcctOutputOctets<br>
CalledStationId<br>
"CallingStationId"<br>
AcctTerminateCause<br>
FramedIPAddress<br>
"ClientMACAddress"<br>
AcctStartDelay<br>
AcctStopDelay<br>
AcctStatusType<br>
dump-able<br>
- session<br>
- accounting<br><br><br><br><div class="gmail_quote">On Fri, Aug 3, 2012 at 8:53 AM, Chris L <span dir="ltr"><<a href="mailto:cjl@viptalk.net" target="_blank">cjl@viptalk.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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?<br>
<br>
I know it's old hardware but it's for a temporary project.<br>
<br>
This is what we receive at the RADIUS server when there's activity on the on-demand PVC.<br>
<br>
rad_recv: Access-Request packet from host 172.99.99.12 port 1812, id=200, length=82<br>
User-Name = "RDBACKS5P0.0.502"<br>
User-Password = "Redback"<br>
NAS-Identifier = "8873-Redback"<br>
Service-Type = Dialout-Framed-User<br>
NAS-Port = 208350<br>
<br>
>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.<br>
<br>
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.<br>
<br>
Login OK: [rdbacks5p0.0.502] (from client 1928redback port 208496)<br>
Sending Access-Accept of id 102 to 172.99.99.12 port 1812<br>
Service-Type = Framed-User<br>
PVC_Profile_Name = "1000-384"<br>
Bind_Auth_Context = "pppoecontext"<br>
PVC_Encapsulation_Type = AAA-ENCAPS-ATM-PPPOE<br>
Bind_Type = AAA-AUTH-BIND<br>
<br>
Any help appreciated.<br>
_______________________________________________<br>
redback-nsp mailing list<br>
<a href="mailto:redback-nsp@puck.nether.net">redback-nsp@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/redback-nsp" target="_blank">https://puck.nether.net/mailman/listinfo/redback-nsp</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Regards,<br><br>Suparti<br>081384850602<br>