Routing

Expand all | Collapse all

LNS MX480 Subscriber Managmnet with Freeradius (( Accounting Problem )

Jump to Best Answer
  • 1.  LNS MX480 Subscriber Managmnet with Freeradius (( Accounting Problem )

    Posted 01-31-2018 00:15

    Dear Sir

     

    I deployment MX480 as LNS to provide ADSL/VDSL service . the authentication is done successfuly with Freeradius3 but the accounting not send to Freeradius . I use mysql module in Freeradius . the Radius server listen on port 1812 for auth and 1813 for accounting . but there is not received any account-request to Freeradius .( i run freeradius on debug mode ) .

     

    ################# Authentication ################

    the log of authenticaion . I notice that some attribute not support but i don't understand what the problem in Attr-type=13

    BTW , in freeradius the RADIUS Attribute 13 is Framed-Compression  and the junos default send it with  Framed-Compression = Van-Jacobson-TCP-IP but i add it to radius as none but the msg still told me that unsupport . 

    Spoiler
    an 31 09:40:24.247967 radius-access-request: User-Name added: 22982868@bnett
    Jan 31 09:40:24.247973 radius-access-request: User-Password added: ""
    Jan 31 09:40:24.247988 radius-access-request: Service-Type added: 2
    Jan 31 09:40:24.247998 radius-access-request: Framed-Protocol added: 1
    Jan 31 09:40:24.248008 radius-access-request: Chargeable-User-Identity added:
    Jan 31 09:40:24.248016 radius-access-request: Acct-Session-Id added: 51
    Jan 31 09:40:24.248028 radius-access-request: DHCP-MAC-Address (Juniper-ERX-VSA) added: 0000.0000.0000
    Jan 31 09:40:24.248037 radius-access-request: NAS-Identifier added: 93.184.1.20
    Jan 31 09:40:24.248046 radius-access-request: NAS-Port added: 00 00 00 00
    Jan 31 09:40:24.248054 radius-access-request: NAS-Port-Type added: 5
    Jan 31 09:40:24.248063 radius-access-request: L2tp-Tx-connect-speed (Juniper-ERX-VSA) added: 14945108
    Jan 31 09:40:24.248091 radius-access-request: L2tp-Rx-connect-speed (Juniper-ERX-VSA) added: 14945108
    Jan 31 09:40:24.248105 radius-access-request: PPPoE-Description (Juniper-ERX-VSA) added: pppoe 00:00:00:00:00:00
    Jan 31 09:40:24.248122 authd_create_application_specific_radius_server: Evaluating RADIUS server 93.184.1.170 to add to the server list
    Jan 31 09:40:24.248129 Evaluating RADIUS server 93.184.1.170 to add to the server list
    Jan 31 09:40:24.248140 Verify source address 5db80114 in routing instance index=0
    Jan 31 09:40:24.248176 authd_radius_server_add: server 93.184.1.170 retry 3, timeout 3
    Jan 31 09:40:24.248226 Request queued successfully
    Jan 31 09:40:24.248238 REQUEST: AUTHEN - module_index 0 module(radius) return: ASYNC
    Jan 31 09:40:24.248248 UserAccess:22982868@bnett session-id:51 state:start
    Jan 31 09:40:24.248256 Auth-FSM: GRES-Mirror for session-id:51 state:AuthStart(1)
    Jan 31 09:40:24.248262 doPersistedDataUpdates
    Jan 31 09:40:24.248267 doPersistedDataUpdates
    Jan 31 09:40:24.259913 authd_radius_get_config:Using radius option config from access profile stanza
    Jan 31 09:40:24.259938 RADIUS server 93.184.1.170:1812 was used for last request
    Jan 31 09:40:24.259954 loadDefaultService:: default service for the subscriber is empty
    Jan 31 09:40:24.259961 Radius result is CLIENT_REQ_STATUS_SUCCESS
    Jan 31 09:40:24.259972 Parsing RADIUS message for session-id:51
    Jan 31 09:40:24.259986 radius-access-accept: Framed-Protocol received: 1
    Jan 31 09:40:24.259992 RADIUS Attribute: Parse Error: "Unsupported attribute type" Radius Standard Attr-Type: 13
    Jan 31 09:40:24.260006 radius-access-accept: Egress-Policy-Name (Juniper-ERX-VSA) received: Speed16M
    Jan 31 09:40:24.260016 Framework - module(radius) return: SUCCESS

     

    ####################### Accounting

    on the below logs , the accounting request msg is done and the Accounting  immediate update  done .

    But the problem is Accounting use port 1812 as mention on Accounting RESPONSE Received .

     

     

    Spoiler
    Jan 31 09:42:32.849843  ======= Subscriber accounting START triggered ==============
    Jan 31 09:42:32.849852 Finding a client snapshot session-id:52
    Jan 31 09:42:32.849883 AccFsm::current state=Acc-Init(0) event=1 session-id:52
    Jan 31 09:42:32.849891 ACC-FSM:sendAccStart_a1 for session-id:52
    Jan 31 09:42:32.849898 sendAuthModuleAcctReports
    Jan 31 09:42:32.849903 Authd module Accounting
    Jan 31 09:42:32.849921 Authd acctg module start
    Jan 31 09:42:32.849927 authd_radius_send_acctg_msg: Starting RADIUS accounting session-id:52
    Jan 31 09:42:32.849933 authd_radius_send_acctg_msg: session-id:52 profile=ADSL-radius-profile username=22476012@bnett acctg_id=(52), ls=default, lr=default
    Jan 31 09:42:32.849948 radius-acct-start: User-Name added: 22476012@bnett
    Jan 31 09:42:32.849968 Accounting START event time not set, setting to subscriber start time
    Jan 31 09:42:32.849975 radius-acct-start: Acct-Status-Type added: 1
    Jan 31 09:42:32.849983 radius-acct-start: Acct-Session-Id added: 52
    Jan 31 09:42:32.849996 radius-acct-start: Event-Timestamp added: 2018-01-31 09:42:33
    Jan 31 09:42:32.850008 radius-acct-start: Acct-Delay-Time added: 0
    Jan 31 09:42:32.850018 radius-acct-start: Service-Type added: 2
    Jan 31 09:42:32.850027 radius-acct-start: Framed-Protocol added: 1
    Jan 31 09:42:32.850044 radius-acct-start: Filter-Id added: IPV4-egress:Speed16M-si-0/0/0.3221225523-out
    Jan 31 09:42:32.850055 radius-acct-start: Cos-Shaping-Rate (Juniper-ERX-VSA) added: Port speed: 32000000k
    Jan 31 09:42:32.850066 radius-acct-start: Tunnel-Type added: Tag () 3
    Jan 31 09:42:32.850075 radius-acct-start: Tunnel-Medium-Type added: Tag () 1
    Jan 31 09:42:32.850083 radius-acct-start: Tunnel-Client-Endpoint added: 10.74.32.235
    Jan 31 09:42:32.850091 radius-acct-start: Tunnel-Server-Endpoint added: 93.184.1.20
    Jan 31 09:42:32.850099 radius-acct-start: Tunnel-Assignment-ID added: 41346
    Jan 31 09:42:32.850107 radius-acct-start: Tunnel-Client-Auth-ID added: PALTEL
    Jan 31 09:42:32.850115 radius-acct-start: Tunnel-Server-Auth-ID added: BNET
    Jan 31 09:42:32.850124 radius-acct-start: Acct-Tunnel-Connection added: 3753343194
    Jan 31 09:42:32.850135 radius-acct-start: Acct-Authentic added: 1
    Jan 31 09:42:32.850147 radius-acct-start: DHCP-MAC-Address (Juniper-ERX-VSA) added: 0000.0000.0000
    Jan 31 09:42:32.850154 radius-acct-start: Egress-Policy-Name (Juniper-ERX-VSA) added: Speed16M
    Jan 31 09:42:32.850164 radius-acct-start: Framed-IP-Address added: 46.18.16.40
    Jan 31 09:42:32.850173 radius-acct-start: Framed-IP-Netmask added: 255.255.255.255
    Jan 31 09:42:32.850181 radius-acct-start: NAS-Identifier added: 93.184.1.20
    Jan 31 09:42:32.850190 radius-acct-start: NAS-Port added: 00 00 00 00
    Jan 31 09:42:32.850198 radius-acct-start: NAS-Port-Type added: 5
    Jan 31 09:42:32.850207 radius-acct-start: L2tp-Tx-connect-speed (Juniper-ERX-VSA) added: 14945108
    Jan 31 09:42:32.850216 radius-acct-start: L2tp-Rx-connect-speed (Juniper-ERX-VSA) added: 14945108
    Jan 31 09:42:32.850225 radius-acct-start: Virtual-Router (Juniper-ERX-VSA) added: default:default
    Jan 31 09:42:32.850235 radius-acct-start: PPPoE-Description (Juniper-ERX-VSA) added: pppoe 00:00:00:00:00:00
    Jan 31 09:42:32.850254 authd_create_application_specific_radius_server: Evaluating RADIUS server 93.184.1.170 to add to the server list
    Jan 31 09:42:32.850261 Evaluating RADIUS server 93.184.1.170 to add to the server list
    Jan 31 09:42:32.850269 Verify source address 5db80114 in routing instance index=0
    Jan 31 09:42:32.850308 authd_radius_server_add: server 93.184.1.170 retry 5, timeout 10
    Jan 31 09:42:32.850361 Request queued successfully
    Jan 31 09:42:32.850376 accFsmExecute::new state=Acc-Start-Sent(1)
    Jan 31 09:42:32.850383 doPersistedDataUpdates
    Jan 31 09:42:32.850389 persistOnlyPrivateData m_inFlight
    Jan 31 09:42:32.850402  ======= Accounting IMMEDIATE Update triggered ==============
    Jan 31 09:42:32.850411 Subscriber accounting: subscriber-session-id:52 reqType: pfed: immediate interval: 0 threshold-type: 0
    Jan 31 09:42:32.850418 phyIfdName = si-0/0/0
    Jan 31 09:42:32.850461 Subscriber accounting: subscriber-session-id:52 reqType: pfed: initial interval: 600 threshold-type: 0
    Jan 31 09:42:32.850489 phyIfdName = si-0/0/0
    Jan 31 09:42:32.850502 ###################################################################
    Jan 31 09:42:32.850508 ################### CLIENT (RE)ACTIVATE ACK SENT ####################
    Jan 31 09:42:32.850513 ###################################################################
    Jan 31 09:42:32.850523 SEQ SendClientMsg:jpppd-client session-id:52 reply-code=1 (OK), result-subopcode=5 (SESSION_IPV4_ACTIVATE), cookie=167, rply_len=28, num_tlv_blocks=0
    Jan 31 09:42:32.850531 authd_auth_aaa_msg_destroy
    Jan 31 09:42:32.850540 authd_auth_aaa_msg_destructauth_aaa_msg: 0x9570b88
    Jan 31 09:42:32.850551 UserAccess:22476012@bnett session-id:52 state:access-granted
    Jan 31 09:42:32.850560 Auth-FSM: GRES-Mirror for session-id:52 state:AuthStateActive(9)
    Jan 31 09:42:32.850566 doPersistedDataUpdates
    Jan 31 09:42:32.850571 persistOnlyPrivateData m_inFlight
    Jan 31 09:42:32.850581 doPersistedDataUpdates
    Jan 31 09:42:33.046249 Subscriber stats callback session-id:52
    Jan 31 09:42:33.046275  ======= Accounting Volume IMMEDIATE triggered ==============
    Jan 31 09:42:33.046291 Have session start time for session-id:52
    Jan 31 09:42:33.046303 AccFsm::current state=Acc-Start-Sent(1) event=4 session-id:52
    Jan 31 09:42:33.046310 ACC-FSM:sendAccInterim_a4 for session-id:52
    Jan 31 09:42:33.046316 sendAuthModuleAcctReports
    Jan 31 09:42:33.046322 Authd module Accounting
    Jan 31 09:42:33.046331 Authd acctg module start
    Jan 31 09:42:33.046337 authd_radius_send_acctg_msg: Starting RADIUS accounting session-id:52
    Jan 31 09:42:33.046343 authd_radius_send_acctg_msg: session-id:52 profile=ADSL-radius-profile username=22476012@bnett acctg_id=(52), ls=default, lr=default
    Jan 31 09:42:33.046354 radius-acct-interim: User-Name added: 22476012@bnett
    Jan 31 09:42:33.046361 radius-acct-interim: Acct-Status-Type added: 3
    Jan 31 09:42:33.046369 radius-acct-interim: Acct-Session-Id added: 52
    Jan 31 09:42:33.046380 radius-acct-interim: Event-Timestamp added: 2018-01-31 09:42:33
    Jan 31 09:42:33.046388 radius-acct-interim: Acct-Input-Octets added: 0
    Jan 31 09:42:33.046394 radius-acct-interim: Acct-Output-Octets added: 0
    Jan 31 09:42:33.046401 radius-acct-interim: Acct-Session-Time added: 0
    Jan 31 09:42:33.046407 radius-acct-interim: Acct-Input-Packets added: 0
    Jan 31 09:42:33.046413 radius-acct-interim: Acct-Output-Packets added: 0
    Jan 31 09:42:33.046423 radius-acct-interim: Acct-Delay-Time added: 0
    Jan 31 09:42:33.046432 radius-acct-interim: Service-Type added: 2
    Jan 31 09:42:33.046441 radius-acct-interim: Framed-Protocol added: 1
    Jan 31 09:42:33.046457 radius-acct-interim: Filter-Id added: IPV4-egress:Speed16M-si-0/0/0.3221225523-out
    Jan 31 09:42:33.046468 radius-acct-interim: Cos-Shaping-Rate (Juniper-ERX-VSA) added: Port speed: 32000000k
    Jan 31 09:42:33.046477 radius-acct-interim: Tunnel-Type added: Tag () 3
    Jan 31 09:42:33.046504 radius-acct-interim: Tunnel-Medium-Type added: Tag () 1
    Jan 31 09:42:33.046513 radius-acct-interim: Tunnel-Client-Endpoint added: 10.74.32.235
    Jan 31 09:42:33.046534 radius-acct-interim: Tunnel-Server-Endpoint added: 93.184.1.20
    Jan 31 09:42:33.046542 radius-acct-interim: Tunnel-Assignment-ID added: 41346
    Jan 31 09:42:33.046550 radius-acct-interim: Tunnel-Client-Auth-ID added: PALTEL
    Jan 31 09:42:33.046558 radius-acct-interim: Tunnel-Server-Auth-ID added: BNET
    Jan 31 09:42:33.046568 radius-acct-interim: Acct-Tunnel-Connection added: 3753343194
    Jan 31 09:42:33.046578 radius-acct-interim: Acct-Authentic added: 1
    Jan 31 09:42:33.046590 radius-acct-interim: DHCP-MAC-Address (Juniper-ERX-VSA) added: 0000.0000.0000
    Jan 31 09:42:33.046598 radius-acct-interim: Egress-Policy-Name (Juniper-ERX-VSA) added: Speed16M
    Jan 31 09:42:33.046608 radius-acct-interim: Framed-IP-Address added: 46.18.16.40
    Jan 31 09:42:33.046617 radius-acct-interim: Framed-IP-Netmask added: 255.255.255.255
    Jan 31 09:42:33.046625 radius-acct-interim: Input-Gigapackets (Juniper-ERX-VSA) added: 0
    Jan 31 09:42:33.046632 radius-acct-interim: Acct-Input-Gigawords added: 0
    Jan 31 09:42:33.046645 radius-acct-interim: NAS-Identifier added: 93.184.1.20
    Jan 31 09:42:33.046654 radius-acct-interim: NAS-Port added: 00 00 00 00
    Jan 31 09:42:33.046662 radius-acct-interim: NAS-Port-Type added: 5
    Jan 31 09:42:33.046669 radius-acct-interim: Output-Gigapackets (Juniper-ERX-VSA) added: 0
    Jan 31 09:42:33.046677 radius-acct-interim: Acct-Output-Gigawords added: 0
    Jan 31 09:42:33.046684 radius-acct-interim: IPv6-Acct-Input-Octets (Juniper-ERX-VSA) added: 0
    Jan 31 09:42:33.046691 radius-acct-interim: IPv6-Acct-Output-Octets (Juniper-ERX-VSA) added: 0
    Jan 31 09:42:33.046698 radius-acct-interim: IPv6-Acct-Input-Packets (Juniper-ERX-VSA) added: 0
    Jan 31 09:42:33.046705 radius-acct-interim: IPv6-Acct-Output-Packets (Juniper-ERX-VSA) added: 0
    Jan 31 09:42:33.046712 radius-acct-interim: IPv6-Acct-Input-Gigawords (Juniper-ERX-VSA) added: 0
    Jan 31 09:42:33.046719 radius-acct-interim: IPv6-Acct-Output-Gigawords (Juniper-ERX-VSA) added: 0
    Jan 31 09:42:33.046727 radius-acct-interim: L2tp-Tx-connect-speed (Juniper-ERX-VSA) added: 14945108
    Jan 31 09:42:33.046736 radius-acct-interim: L2tp-Rx-connect-speed (Juniper-ERX-VSA) added: 14945108
    Jan 31 09:42:33.046745 radius-acct-interim: Virtual-Router (Juniper-ERX-VSA) added: default:default
    Jan 31 09:42:33.046755 radius-acct-interim: PPPoE-Description (Juniper-ERX-VSA) added: pppoe 00:00:00:00:00:00
    Jan 31 09:42:33.046772 authd_create_application_specific_radius_server: Evaluating RADIUS server 93.184.1.170 to add to the server list
    Jan 31 09:42:33.046780 Evaluating RADIUS server 93.184.1.170 to add to the server list
    Jan 31 09:42:33.046786 Verify source address 5db80114 in routing instance index=0
    Jan 31 09:42:33.046816 authd_radius_server_add: server 93.184.1.170 retry 5, timeout 10
    Jan 31 09:42:33.046860 Request queued successfully
    Jan 31 09:42:33.046875 accFsmExecute::new state=Acc-Interim-Sent(2)
    Jan 31 09:42:33.046881 doPersistedDataUpdates
    Jan 31 09:42:33.046888 clearAddrChangeImmediateUpdatePending: 0 -> 0
    Jan 31 09:42:33.046895 persistOnlyPrivateData m_inFlight
    Jan 31 09:43:32.853792 authd_radius_get_config:Using radius option config from access profile stanza
    Jan 31 09:43:32.853829 RADIUS server 93.184.1.170:1812 was used for last request
    Jan 31 09:43:32.853837 authd_radius_mark_servers_dead RADIUS server 93.184.1.170 time out (g:10, r:0)
    Jan 31 09:43:32.853853 Radius result is CLIENT_REQ_TIMEOUT
    Jan 31 09:43:32.853861 authd_radius_acctg_callback Result is :(CLIENT_REQ_TIMEOUT) reply_code:((null)) 0 session-id:52
    Jan 31 09:43:32.853877  ======= Accounting RESPONSE Received ==============
    Jan 31 09:43:32.853892 AccFsm::current state=Acc-Interim-Sent(2) event=2 session-id:52
    Jan 31 09:43:32.853901 ACC-FSM:processAccStartRsp_a2 for session-id:52
    Jan 31 09:43:32.853912 persistOnlyPrivateData
    Jan 31 09:43:32.853941 accFsmExecute::new state=Acc-Interim-Sent(2)
    Jan 31 09:43:32.853948 doPersistedDataUpdates
    Jan 31 09:43:32.853954 persistOnlyPrivateDatam_privateDataPersisted
    Jan 31 09:43:33.049212 authd_radius_get_config:Using radius option config from access profile stanza
    Jan 31 09:43:33.049257 RADIUS server 93.184.1.170:1812 was used for last request
    Jan 31 09:43:33.049265 authd_radius_mark_servers_dead RADIUS server 93.184.1.170 time out (g:10, r:0)
    Jan 31 09:43:33.049279 Radius result is CLIENT_REQ_TIMEOUT
    Jan 31 09:43:33.049286 authd_radius_acctg_callback Result is :(CLIENT_REQ_TIMEOUT) reply_code:((null)) 0 session-id:52

     

    the configuration of radius on Junos is

    Spoiler

    radius-server {
        93.184.1.170 {
            port 1812;
            accounting-port 1813;
            secret "$9$r7ZKv84oGkqfZUDH.mTQIEhSKMdbs"; ## SECRET-DATA
            accounting-timeout 10;
            accounting-retry 5;
            source-address 93.184.1.20;
        }
    profile ADSL-radius-profile {
        accounting-order radius;
        authentication-order radius;
        radius {
            authentication-server 93.184.1.170;
            accounting-server 93.184.1.170;
            options {
                interface-description-format {
                    exclude-sub-interface;
                }
                nas-identifier 93.184.1.20;
                revert-interval 0;
                client-accounting-algorithm direct;
            }
        }
        accounting {
            order radius;
            immediate-update;
            update-interval 10;
            statistics volume-time;
        }}

     

     



  • 2.  RE: LNS MX480 Subscriber Managmnet with Freeradius (( Accounting Problem )

     
    Posted 01-31-2018 00:36
    Hi,

    As per the problem description,
    Accounting is working on port 1812 but not working on port 1813.

    Did you tried monitor traffic on uplink interface?

    I am not seeing configuration issue.

    Regards,
    Rahul


  • 3.  RE: LNS MX480 Subscriber Managmnet with Freeradius (( Accounting Problem )

     
    Posted 01-31-2018 00:40
    Unsupported logs has nothing do with accounting in Junos.


  • 4.  RE: LNS MX480 Subscriber Managmnet with Freeradius (( Accounting Problem )

     
    Posted 01-31-2018 00:46
    Logs clearly stating accounting packet are getting timeout. Means Junos is sending the packet but getting timeout.

    Regards,
    Rahul


  • 5.  RE: LNS MX480 Subscriber Managmnet with Freeradius (( Accounting Problem )

     
    Posted 01-31-2018 01:11

    Hi,

     

    authd logs showing the wrong port for the accounting server is cosmetic. Can you capture the packet using below command?

     

    monitor traffic interface xxx no-resolve siz 1500 <<< Accounting message will be seen as this is RE generated packet.

     

    Please verify the port.

     

    Regards,

    Rahul



  • 6.  RE: LNS MX480 Subscriber Managmnet with Freeradius (( Accounting Problem )

    Posted 01-31-2018 01:47

    its be that not problem on Junos configuration ... the accounting-request send using 1813 .

    thanks Rahul .. its the problem may be on freeradius ...

     

     

    Spoiler
    11:31:41.645843 Out IP 93.184.1.20.52359 > 93.184.1.170.1812: RADIUS, Access Request (1), id: 0x75 length: 245 11:31:41.657416 In IP 93.184.1.170.1812 > 93.184.1.20.52359: RADIUS, Access Accept (2), id: 0x75 length: 48 11:31:41.948349 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x76 length: 446 11:31:42.220599 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x77 length: 584 11:31:48.616023 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x78 length: 589 11:31:48.616105 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x79 length: 590 11:31:51.948819 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x7a length: 446 11:31:52.220868 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x7b length: 584 11:31:58.616986 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x7c length: 589 11:31:58.617084 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x7d length: 590 11:32:01.949092 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x7f length: 446 11:32:02.221206 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x7e length: 584 11:32:08.617241 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x80 length: 589 11:32:08.617296 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x81 length: 590 11:32:11.949615 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x82 length: 446 11:32:12.221459 Out IP 93.184.1.20.52359 > 93.184.1.170.1813: RADIUS, Accounting Request (4), id: 0x83 length: 584 11:32:18.248236 Out IP 93.184.1.20.52359 > 93.184.1.170.1812: RADIUS, Access Request (1), id: 0x84 length: 245 11:32:18.257568 In IP 93.184.1.170.1812 > 93.184.1.20.52359: RADIUS, Access Accept (2), id: 0x84 length: 48

     



  • 7.  RE: LNS MX480 Subscriber Managmnet with Freeradius (( Accounting Problem )

     
    Posted 01-31-2018 00:40

    What's the JUNOS version?

     



  • 8.  RE: LNS MX480 Subscriber Managmnet with Freeradius (( Accounting Problem )

    Posted 01-31-2018 01:50

    Model: mx480
    Junos: 15.1F7.3
    JUNOS OS Kernel 64-bit 

     

     

    but it seems that Freeradius not response to traffic



  • 9.  RE: LNS MX480 Subscriber Managmnet with Freeradius (( Accounting Problem )

    Posted 01-31-2018 03:07

    The problem is that an SRX between MX and Freeradius . I acctivate just junos-radius .. I shoud add junos-radacct also in application...

     

    also we should change type of nasportid from varchar(15) to text . becouse nasportid is too long like

    nas-identifier # interface-description # interface-text-description # agent-circuit-id # agent-remote-id # postpend-vlan-tags

     NAS-Port-Id = "Ip:93.184.1.20:10.74.32.235:23497:45561:33260:4800:3753386120"

     

    ############## Another problem

    I can't commit any change on configuration  .. for example add system user or change timezone or add static route


    error: ffp_intf_ifd_hier_tagging_config_verify: Modified IFD "si-0/0/0" flags 0x20 is in use by BBE subscriber, commit denied - hierarchical-scheduler config changed
    error: foreign file propagation (ffp) failed

     

    Any Soultion



  • 10.  RE: LNS MX480 Subscriber Managmnet with Freeradius (( Accounting Problem )
    Best Answer

     
    Posted 01-31-2018 03:55