[RP-PPPoE] radattr.so cant receive values from radius

[Insane Laughing Clown]

Mike Tesliuk wrote:
> this is my script to set the bandwidth
>
>   
Ahh cool thanks for sharing.


>
> when i do a freeradius -X i get this
>
>
> rlm_sql (sql): Reserving sql socket id: 2
> rlm_sql (sql): Released sql socket id: 2
> ++[sql] returns ok
> ++[exec] returns noop
> Sending Access-Accept of id 55 to 127.0.0.1 port 44560
>         Framed-Protocol = PPP
>         Framed-Compression = Van-Jacobson-TCP-IP
>         RP-Downstream-Speed-Limit := 64
>         RP-Upstream-Speed-Limit := 64
>         Framed-IP-Address = 187.109.35.137
>         Framed-IP-Netmask = 255.255.255.0
> Finished request 13.
> Going to the next request
> Waking up in 4.9 seconds.
>
>
>
> on the tcpdump i receive this.
>
>         Access Accept (2), id: 0x4f, Authenticator:
> 5e73ab60745587970ee22eee96aeb604
>           Framed Protocol Attribute (7), length: 6, Value: PPP
>             0x0000:  0000 0001
>           Framed Compression Attribute (13), length: 6, Value: VJ TCP/IP
>             0x0000:  0000 0001
>           Vendor Specific Attribute (26), length: 12, Value: Vendor:
> Unknown (10055)
>             Vendor Attribute: 2, Length: 4, Value: ...@
>             0x0000:  0000 2747 0206 0000 0040
>           Vendor Specific Attribute (26), length: 12, Value: Vendor:
> Unknown (10055)
>             Vendor Attribute: 1, Length: 4, Value: ...@
>             0x0000:  0000 2747 0106 0000 0040
>           Framed IP Address Attribute (8), length: 6, Value: 187.109.35.137
>             0x0000:  bb6d 2389
>           Framed IP Network Attribute (9), length: 6, Value: 255.255.255.0
>             0x0000:  ffff ff00
>
>
>
>
>   
Ok, your radius is working and it is indeed returning the right 
attributes. So my question now is, do you have the roaringpenguin 
dictionary installed on your pppoe server machine?? Betcha don't.

On your server machine, pppd will use 'radiusclient', and the default 
dictionaries supplied do not include the roaring penguin attributes. 
Typically, you'll need to install the dictionary file and then connect 
it to your main dictionary usually with a simple statement such as the 
following in your main dictionary file:

INCLUDE /etc/radiusclient/dictionary.roaringpenguin


For some reason - and I do not know if this is a recent bug, a design 
decision or what - the embedded 'radiusclient' in pppd (or at least, the 
one I use) doesn't seem to understand standard dictionary files without 
a minor modification, which is to append the 'vendor name' after the 
attribute type. My version of the roaringpenguin dictionary file is 
below, YMMV. My ppp also corrupts attributes if loading dictionary files 
without this modification.... maybe I'll track that down later.

Good luck and let us know if this fixes you.

Mike-


# -*- text -*-
##############################################################################
#
#       Roaring Penguin attributes
#
#       $Id$
#
##############################################################################

VENDOR          Roaring-Penguin                 10055

BEGIN-VENDOR    Roaring-Penguin

# Upstream speed limit in kb/s
ATTRIBUTE       RP-Upstream-Speed-Limit                 1       integer 
RoaringPenguin
 # Downstream speed limit in kb/s
ATTRIBUTE       RP-Downstream-Speed-Limit               2       integer 
RoaringPenguin

# Send a HURL
ATTRIBUTE       RP-HURL                                 3       string 
RoaringPenguin

# Send a MOTM
ATTRIBUTE       RP-MOTM                                 4       string 
RoaringPenguin

# Maximum sessions per user
ATTRIBUTE       RP-Max-Sessions-Per-User                5       integer 
RoaringPenguin

END-VENDOR      Roaring-Penguin
~