forum.bitel.ru http://forum.bitel.ru/ |
|
GPON.IPoE.DHCP.Авторизация по SN ONT. http://forum.bitel.ru/viewtopic.php?f=44&t=13309 |
Страница 1 из 1 |
Автор: | DVShatskikh [ 18 апр 2019, 20:42 ] |
Заголовок сообщения: | GPON.IPoE.DHCP.Авторизация по SN ONT. |
Добрый день! Схема следующая: Абоненты сидят по GPON на Huawei MA5683T. В качестве BRAS используется Redback SE-100. Заведены два устройства, SE100 (id:4) и дочерним к нему Huawei (id:8). Huawei вставляет в option82: серийный номер ONT и свой hostname. SE100 выполняет функцию dhcp proxy. Хотелось бы реализовать авторизацию чисто по серийнику ONT. C RADIUS проблем, в принципе, нет. Серийник подставляется в User-name и проходит авторизация по login. А вот с DHCP что делать??? |
Автор: | Amir [ 19 апр 2019, 04:24 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Если в Calling-Station-Id приходит MAC-адрес, то можно указать: dhcp.key.pattern=$deviceId:$mac Если MAC-адрес приходит в другом атрибуте, то есть параметры: radius.callingStationId.vendor= radius.callingStationId.type= radius.callingStationId.prefix= |
Автор: | Amir [ 19 апр 2019, 04:30 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
В случае, когда DHCP не проходит через SmartEdge (т.е. когда BRAS стартует сессию по IP-пакету, а не по DHCP DISCOVER) и биллинг выдает адрес не основываясь на информации о RADIUS-сессии сейчас также можно использовать логин/серийный номер: https://docs.bitel.ru/pages/viewpage.ac ... d=43385877 Цитата: dhcp.option82.login.code=2
dhcp.option82.login.hex=.* |
Автор: | DVShatskikh [ 19 апр 2019, 13:25 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] RadiusListenerWorker - REQUEST: Packet type: Access-Request Identifier: 10 Authenticator: {0A 1A 76 EE AA 44 D2 E2 A6 86 48 43 26 00 6B EA} Attributes: NAS-Identifier=BLG-CORE-SE100-1 User-Name=00:15:60:ca:28:90 User-Password=Redback NAS-IP-Address=172.31.255.11 NAS-Port=553648528 Service-Type=5 NAS-Port-Id=2/1 vlan-id 400 clips 131083 NAS-Port-Type=5 OS-Version=12.1.1.12p1 Agent-Remote-Id={42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} Mac-Addr=00-15-60-ca-28-90 Agent-Circuit-Id={34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} Platform-Type=4 Medium-Type=11 UNKNOWN[2352-202]={3D 3D 07 01 00 15 60 CA 28 90} UNKNOWN[2352-202]={0C 0C 0A 57 6F 72 6B 43 6F 6D 70 30 37} UNKNOWN[2352-125]={4D 53 46 54 20 35 2E 30} NAS-Real-Port=553648528 UNKNOWN[3561--1]={02 13 42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} UNKNOWN[3561--1]={01 12 34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS: Packet type: Access-Request Identifier: 10 Authenticator: {0A 1A 76 EE AA 44 D2 E2 A6 86 48 43 26 00 6B EA} Attributes: NAS-Identifier=BLG-CORE-SE100-1 User-Name=4857544357545F55 User-Password=Redback NAS-IP-Address=172.31.255.11 NAS-Port=553648528 Service-Type=5 NAS-Port-Id=2/1 vlan-id 400 clips 131083 NAS-Port-Type=5 Calling-Station-Id=001560ca2890 OS-Version=12.1.1.12p1 Agent-Remote-Id={42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} Mac-Addr=00-15-60-ca-28-90 Agent-Circuit-Id={34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} Platform-Type=4 Medium-Type=11 UNKNOWN[2352-202]={3D 3D 07 01 00 15 60 CA 28 90} UNKNOWN[2352-202]={0C 0C 0A 57 6F 72 6B 43 6F 6D 70 30 37} UNKNOWN[2352-125]={4D 53 46 54 20 35 2E 30} NAS-Real-Port=553648528 UNKNOWN[3561--1]={02 13 42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} UNKNOWN[3561--1]={01 12 34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} Common options: {macAddress=00-15-60-ca-28-90, interfaceId=4857544357545F55, agentRemoteId=BLG-STR-MA5683T-1, agentCircuitId=4857544357545F55} radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetNas - Search by username=4857544357545F55 radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetRadiusProcessor - [username=4857544357545F55] Authenticated as inetServId:1691 radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetNas - Found agentDevice by identifier: 8 radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetApplication - contract tariffOptions: {} radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetApplication - inetServ[id=1691] balance ok: -918.14 [-1000.00] radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetApplication - OptionSet: [8] radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetRadiusIpAddressUtils - Not found free static IP in serv radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetRadiusIpAddressUtils - Set ip from pool radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetRadiusProcessor - Write new waiting connection to DB radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetRadiusProcessor - New connection id=453397 radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetRadiusProcessor - Return code=0 radius 04-19/10:22:11 ERROR [rdsLstnr-p-9-t-10] InetDhcpHelperProcessor - Incorrect userName: 4857544357545F55 radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetRadiusProcessor - RESPONSE_BEFORE_POSTPROCESS: Packet type: Access-Accept Identifier: 10 Authenticator: {} Attributes: Acct-Interim-Interval=600 Framed-IP-Address=10.0.13.95 Service-Parameter:1=Burst=102400 Rate=102400 ExBurst=102400 Service-Name:1=SERVICE_INET Service-Options:1=0 Process time auth: 3 radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] InetRadiusListenerWorker - RESPONSE (3ms): Packet type: Access-Accept Identifier: 10 Authenticator: {25 37 77 09 3D 0A 80 25 9C 2A 33 81 58 29 09 B4} Attributes: Acct-Interim-Interval=600 Service-Parameter:1=Burst=102400 Rate=102400 ExBurst=102400 Service-Name:1=SERVICE_INET Service-Options:1=0 Process time auth: 3 radius 04-19/10:22:11 INFO [rdsLstnr-p-9-t-10] HourlyDataLogEntry - Create dataLog file: /opt/BGInetAccess/data/radius/source_4/2019/2019-04/2019-04-19/log_2019-04-19-10.001.bgdl mq 04-19/10:22:11 INFO [event-proc-p-2-t-1] InetConnectionManager - Add connection: InetConnection [id=453398-0, iface=4:553648528, sessId=0100FFFF7800000B-5CB9772B, start=19.04.2019 10:22:11, uname=424c472d5354522d4d4135363833542d31:343835373534343335373 53435463535, addr=[IpAddress:null]] mq 04-19/10:22:11 INFO [event-proc-p-2-t-1] InetDhcpHelperProcessor - IP is null 4:001560CA2890 dhcp 04-19/10:22:11 INFO [dhcpLstnr-p-11-t-9] InetAbstractDhcpProcessor - REQUEST: Message type: BOOT_REQUEST Dhcp message type: DHCP Discover{1} htype: 1, hlen: 6, hops: 1 xid: 1430607186, secs: 0, flags: 11111111111111111000000000000000 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} {116}={01} Client-ident.{61}={01001560CA2890} Requested IP{50}=169.254.73.157 Host name{12}={WorkComp07} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC00} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} dhcp 04-19/10:22:11 INFO [dhcpLstnr-p-11-t-9] InetAbstractDhcpProcessor - REQUEST_AFTER_PREPROCESS: Message type: BOOT_REQUEST Dhcp message type: DHCP Discover{1} htype: 1, hlen: 6, hops: 1 xid: 1430607186, secs: 0, flags: 11111111111111111000000000000000 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} {116}={01} Client-ident.{61}={01001560CA2890} Requested IP{50}=169.254.73.157 Host name{12}={WorkComp07} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC00} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} Common options: {interfaceId=4857544357545F55, agentRemoteId=BLG-STR-MA5683T-1, agentCircuitId=4857544357545F55} dhcp 04-19/10:22:11 ERROR [dhcpLstnr-p-11-t-9] InetDhcpHelperProcessor - Not found params for request: 8:001560CA2890 (pattern: $deviceId:$mac, servSearchMode: 0, deviceId: 8, agentDeviceId: 8, mac: 001560CA2890) dhcp 04-19/10:22:11 INFO [dhcpLstnr-p-11-t-9] InetAbstractDhcpProcessor - RESPONSE: Message type: BOOT_RESPONSE Dhcp message type: DHCP NAK{6} htype: 1, hlen: 6, hops: 1 xid: 1430607186, secs: 0, flags: 11111111111111111000000000000000 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} connection 04-19/10:22:11 INFO [sa-p-14-t-95] ServiceActivatorSet - Connecting to device connection 04-19/10:22:11 INFO [sa-p-14-t-95] ServiceActivatorDeviceWorker - Do task deviceId: 4; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountingEvent] moduleId: 1; pluginId: no; cid: 7; scid: -1; userId: 0; type: 1; deviceId: 4; co nnectionId: 453398; timestamp: 1555658531801 connection 04-19/10:22:11 INFO [sa-p-14-t-95] InetApplication - OptionSet: [] connection 04-19/10:22:11 INFO [sa-p-14-t-95] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=4; inetServId: 79; call: true; oldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 04-19/10:22:11 INFO [sa-p-14-t-95] ServiceActivatorDeviceWorker - Processing deviceId:4; command ServiceActivatorEvent type=4; inetServId: 79; call: true; oldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 04-19/10:22:11 INFO [sa-p-14-t-95] ServiceActivatorSet - Invoking onAccountingStart connection 04-19/10:22:11 INFO [sa-p-14-t-95] ServiceActivatorDeviceWorker - Process event type[4] result=true connection 04-19/10:22:16 INFO [sa-p-14-t-95] ServiceActivatorDeviceWorker - Do task deviceId: 4; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountingEvent] moduleId: 1; pluginId: no; cid: 7; scid: -1; userId: 0; type: 2; deviceId: 4; co nnectionId: 453398; timestamp: 1555658536082 connection 04-19/10:22:16 INFO [sa-p-14-t-95] InetApplication - OptionSet: [] connection 04-19/10:22:16 INFO [sa-p-14-t-95] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=5; inetServId: 79; call: true; oldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 04-19/10:22:16 INFO [sa-p-14-t-95] ServiceActivatorDeviceWorker - Processing deviceId:4; command ServiceActivatorEvent type=5; inetServId: 79; call: true; oldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 04-19/10:22:16 INFO [sa-p-14-t-95] ServiceActivatorSet - Invoking onAccountingStop connection 04-19/10:22:16 INFO [sa-p-14-t-95] ServiceActivatorDeviceWorker - Process event type[5] result=true mq 04-19/10:22:16 INFO [event-proc-p-2-t-1] InetConnectionManager - Remove connection: InetConnection [id=453398-0, iface=4:553648528, sessId=0100FFFF7800000B-5CB9772B, start=19.04.2019 10:22:11, uname=424c472d5354522d4d4135363833542d31:343835373534343335 37353435463535, addr=[IpAddress:null]] mq 04-19/10:22:16 INFO [event-proc-p-2-t-1] InetDhcpHelperProcessor - Remove connection remove 4:001560CA2890 [IpAddress:null]: false connection 04-19/10:22:18 INFO [sa-p-14-t-95] ServiceActivatorSet - Disconnecting from device |
Автор: | Amir [ 19 апр 2019, 18:10 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
dhcp.key.deviceTypeIds указан в конфиге? Попробуйте в inet-access.xml поменять InetDhcpHelperProcessor на InetDhcpProcessor, если версия >=7.1 или на InetDhcpProcessor2 если версия <7.1 |
Автор: | DVShatskikh [ 19 апр 2019, 19:09 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Попробовал. Ситуация принципиально не изменилась. |
Автор: | Amir [ 19 апр 2019, 19:27 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Должен был как минимум перестать писать "Incorrect userName ...". Как максимум - перед выдачей Access-Accept должен писать "Put auth accept ...". |
Автор: | DVShatskikh [ 19 апр 2019, 19:55 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Так и есть. Но общий результат не изменился radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] RadiusListenerWorker - REQUEST: Packet type: Access-Request Identifier: 0 Authenticator: {BA 54 A9 88 6D A3 EB D5 6C 7B 34 0C DE 52 6C B9} Attributes: NAS-Identifier=BLG-CORE-SE100-1 User-Name=00:15:60:ca:28:90 User-Password=Redback NAS-IP-Address=172.31.255.11 NAS-Port=553648528 Service-Type=5 NAS-Port-Id=2/1 vlan-id 400 clips 131073 NAS-Port-Type=5 OS-Version=12.1.1.12p1 Agent-Remote-Id={42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} Mac-Addr=00-15-60-ca-28-90 Agent-Circuit-Id={34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} Platform-Type=4 Medium-Type=11 UNKNOWN[2352-202]={3D 3D 07 01 00 15 60 CA 28 90} UNKNOWN[2352-202]={0C 0C 0A 57 6F 72 6B 43 6F 6D 70 30 37} UNKNOWN[2352-125]={4D 53 46 54 20 35 2E 30} NAS-Real-Port=553648528 UNKNOWN[3561--1]={02 13 42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} UNKNOWN[3561--1]={01 12 34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS: Packet type: Access-Request Identifier: 0 Authenticator: {BA 54 A9 88 6D A3 EB D5 6C 7B 34 0C DE 52 6C B9} Attributes: NAS-Identifier=BLG-CORE-SE100-1 User-Name=4857544357545F55 User-Password=Redback NAS-IP-Address=172.31.255.11 NAS-Port=553648528 Service-Type=5 NAS-Port-Id=2/1 vlan-id 400 clips 131073 NAS-Port-Type=5 Calling-Station-Id=001560ca2890 OS-Version=12.1.1.12p1 Agent-Remote-Id={42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} Mac-Addr=00-15-60-ca-28-90 Agent-Circuit-Id={34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} Platform-Type=4 Medium-Type=11 UNKNOWN[2352-202]={3D 3D 07 01 00 15 60 CA 28 90} UNKNOWN[2352-202]={0C 0C 0A 57 6F 72 6B 43 6F 6D 70 30 37} UNKNOWN[2352-125]={4D 53 46 54 20 35 2E 30} NAS-Real-Port=553648528 UNKNOWN[3561--1]={02 13 42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} UNKNOWN[3561--1]={01 12 34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} Common options: {macAddress=00-15-60-ca-28-90, interfaceId=4857544357545F55, agentRemoteId=BLG-STR-MA5683T-1, agentCircuitId=4857544357545F55} radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetNas - Search by username=4857544357545F55 radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetRadiusProcessor - [username=4857544357545F55] Authenticated as inetServId:1700 radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetNas - Found agentDevice by identifier: 8 radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetApplication - contract tariffOptions: {} radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetApplication - inetServ[id=1700] balance ok: -918.14 [-1000.00] radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetApplication - OptionSet: [8] radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetRadiusIpAddressUtils - Not found free static IP in serv radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetRadiusIpAddressUtils - Set ip from pool radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetRadiusProcessor - Write new waiting connection to DB radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetRadiusProcessor - New connection id=453494 radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetRadiusProcessor - Return code=0 radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetConnectionMap - Put auth accept deviceId:4;mac:001560CA2890 radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetRadiusProcessor - RESPONSE_BEFORE_POSTPROCESS: Packet type: Access-Accept Identifier: 0 Authenticator: {} Attributes: Acct-Interim-Interval=600 Framed-IP-Address=10.0.0.5 Service-Parameter:1=Burst=102400 Rate=102400 ExBurst=102400 Service-Name:1=SERVICE_INET Service-Options:1=0 Process time auth: 44 radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] InetRadiusListenerWorker - RESPONSE (53ms): Packet type: Access-Accept Identifier: 0 Authenticator: {C9 DA A1 F9 EA A1 57 C9 36 8F 5F 23 59 61 F2 0E} Attributes: Acct-Interim-Interval=600 Service-Parameter:1=Burst=102400 Rate=102400 ExBurst=102400 Service-Name:1=SERVICE_INET Service-Options:1=0 Process time auth: 47 radius 04-19/16:52:20 INFO [rdsLstnr-p-9-t-1] HourlyDataLogEntry - Create dataLog file: /opt/BGInetAccess/data/radius/source_4/2019/2019-04/2019-04-19/log_2019-04-19-16.003.bgdl connection 04-19/16:52:21 INFO [sa-p-15-t-49] ServiceActivatorSet - Connecting to device connection 04-19/16:52:21 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Do task deviceId: 4; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountingEvent] moduleId: 1; pluginId: no; cid: 7; scid: -1; userId: 0; type: 1; deviceId: 4; connectionId: 453495; timestamp: 1555681941198 mq 04-19/16:52:21 INFO [event-proc-p-2-t-1] InetConnectionManager - Add connection: InetConnection [id=453495-0, iface=4:553648528, sessId=0100FFFF78000001-5CB9D29D, start=19.04.2019 16:52:21, uname=424c472d5354522d4d4135363833542d31:34383537353434333537353435463535, addr=[IpAddress:null]] mq 04-19/16:52:21 INFO [event-proc-p-2-t-1] InetConnectionMap - Ip is null deviceId:4;mac:001560CA2890 connection 04-19/16:52:21 INFO [sa-p-15-t-49] InetApplication - OptionSet: [] connection 04-19/16:52:21 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=4; inetServId: 79; call: true; oldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 04-19/16:52:21 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Processing deviceId:4; command ServiceActivatorEvent type=4; inetServId: 79; call: true; oldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 04-19/16:52:21 INFO [sa-p-15-t-49] ServiceActivatorSet - Invoking onAccountingStart connection 04-19/16:52:21 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Process event type[4] result=true dhcp 04-19/16:52:21 INFO [dhcpLstnr-p-12-t-1] AbstractInetDhcpProcessor2 - REQUEST: Message type: BOOT_REQUEST Dhcp message type: DHCP Discover{1} htype: 1, hlen: 6, hops: 1 xid: 1430607191, secs: 0, flags: 11111111111111111000000000000000 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} {116}={01} Client-ident.{61}={01001560CA2890} Requested IP{50}=169.254.73.157 Host name{12}={WorkComp07} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC00} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} dhcp 04-19/16:52:21 INFO [dhcpLstnr-p-12-t-1] AbstractInetDhcpProcessor2 - REQUEST_AFTER_PREPROCESS: Message type: BOOT_REQUEST Dhcp message type: DHCP Discover{1} htype: 1, hlen: 6, hops: 1 xid: 1430607191, secs: 0, flags: 11111111111111111000000000000000 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} {116}={01} Client-ident.{61}={01001560CA2890} Requested IP{50}=169.254.73.157 Host name{12}={WorkComp07} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC00} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} Common options: {interfaceId=4857544357545F55, agentRemoteId=BLG-STR-MA5683T-1, agentCircuitId=4857544357545F55} dhcp 04-19/16:52:21 ERROR [dhcpLstnr-p-12-t-1] InetDhcpProcessor2 - Not found params for request: (pattern: $deviceId:$mac, servSearchMode: 0, deviceId: 4, agentDeviceId: dhcp 04-19/16:52:21 INFO [dhcpLstnr-p-12-t-1] AbstractInetDhcpProcessor2 - RESPONSE: Message type: BOOT_RESPONSE Dhcp message type: DHCP NAK{6} htype: 1, hlen: 6, hops: 1 xid: 1430607191, secs: 0, flags: 11111111111111111000000000000000 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} connection 04-19/16:52:24 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Do task deviceId: 4; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaStateModifyEvent] moduleId: 1; pluginId: no; cid: 7; scid: -1; userId: 0; deviceId: 4; inetServId: 79; connectionId: 453495; state: 0; accessCode: 20; timestamp: 1555681944199 connection 04-19/16:52:24 INFO [sa-p-15-t-49] InetApplication - OptionSet: [] connection 04-19/16:52:24 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=2; inetServId: 79; call: true; oldState: 1; newState: 0; oldOptionSet: ; newOptionSet: connection 04-19/16:52:24 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Processing deviceId:4; command ServiceActivatorEvent type=2; inetServId: 79; call: true; oldState: 1; newState: 0; oldOptionSet: ; newOptionSet: connection 04-19/16:52:24 INFO [sa-p-15-t-49] ServiceActivatorSet - Invoking connectionModify connection 04-19/16:52:24 INFO [sa-p-15-t-49] SmartEdgeServiceActivator - Connection modify: oldState: 1; newState: 0; oldOptionSet: []; newOptionSet: [] connection 04-19/16:52:24 INFO [sa-p-15-t-49] SmartEdgeServiceActivator - Connection disable connection 04-19/16:52:24 INFO [sa-p-15-t-49] SmartEdgeServiceActivator - sendCommands connection 04-19/16:52:24 INFO [sa-p-15-t-49] SmartEdgeServiceActivator - Send enable services CoA: Packet type: CoA-Request Identifier: 2 Authenticator: {A2 DC 3E 92 DA 39 49 B7 C0 11 AE F4 31 9C 82 94} Attributes: Acct-Session-Id=0100FFFF78000001-5CB9D29D Service-Name:2=SERVICE_BLOCKED Service-Options:2=1 connection 04-19/16:52:24 INFO [sa-p-15-t-49] RadiusClient - Sending to /172.31.255.11:3799 Packet type: CoA-Request Identifier: 2 Authenticator: {A2 DC 3E 92 DA 39 49 B7 C0 11 AE F4 31 9C 82 94} Attributes: Acct-Session-Id=0100FFFF78000001-5CB9D29D Service-Name:2=SERVICE_BLOCKED Service-Options:2=1 connection 04-19/16:52:24 INFO [sa-p-15-t-49] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.RadiusClient$RadiusDatagramChannelListener socket init ok. connection 04-19/16:52:24 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Process event type[2] result=true connection 04-19/16:52:24 INFO [rds-clnt-/172.31.255.11-3799] RadiusClient - Recieved from /172.31.255.11:3799 Packet type: CoA-NAK Identifier: 2 Authenticator: {34 3B 1F 57 31 88 94 AC C5 F0 59 65 8F 24 DA 1C} Attributes: Error-Cause=0 Event-Timestamp=1555681952 connection 04-19/16:52:25 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Do task deviceId: 4; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountingEvent] moduleId: 1; pluginId: no; cid: 7; scid: -1; userId: 0; type: 2; deviceId: 4; connectionId: 453495; timestamp: 1555681945720 connection 04-19/16:52:25 INFO [sa-p-15-t-49] InetApplication - OptionSet: [] connection 04-19/16:52:25 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=5; inetServId: 79; call: true; oldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 04-19/16:52:25 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Processing deviceId:4; command ServiceActivatorEvent type=5; inetServId: 79; call: true; oldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 04-19/16:52:25 INFO [sa-p-15-t-49] ServiceActivatorSet - Invoking onAccountingStop connection 04-19/16:52:25 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Process event type[5] result=true connection 04-19/16:52:25 INFO [sa-p-15-t-49] EventWorker - Future is done connection 04-19/16:52:25 WARN [sa-p-15-t-49] ServiceActivatorDeviceWorker - Task return false mq 04-19/16:52:25 INFO [event-proc-p-2-t-1] InetConnectionManager - Remove connection: InetConnection [id=453495-0, iface=4:553648528, sessId=0100FFFF78000001-5CB9D29D, start=19.04.2019 16:52:21, uname=424c472d5354522d4d4135363833542d31:34383537353434333537353435463535, addr=[IpAddress:null]] mq 04-19/16:52:25 INFO [event-proc-p-2-t-1] InetConnectionMap - Remove connection remove deviceId:4;mac:001560CA2890 connection 04-19/16:52:28 INFO [sa-p-15-t-49] ServiceActivatorSet - Disconnecting from device radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] RadiusListenerWorker - REQUEST: Packet type: Access-Request Identifier: 1 Authenticator: {AC 40 D8 45 52 8A 44 34 47 1C A4 74 E7 8C 13 3D} Attributes: NAS-Identifier=BLG-CORE-SE100-1 User-Name=00:15:60:ca:28:90 User-Password=Redback NAS-IP-Address=172.31.255.11 NAS-Port=553648528 Service-Type=5 NAS-Port-Id=2/1 vlan-id 400 clips 131074 NAS-Port-Type=5 OS-Version=12.1.1.12p1 Agent-Remote-Id={42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} Mac-Addr=00-15-60-ca-28-90 Agent-Circuit-Id={34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} Platform-Type=4 Medium-Type=11 UNKNOWN[2352-202]={3D 3D 07 01 00 15 60 CA 28 90} UNKNOWN[2352-202]={0C 0C 0A 57 6F 72 6B 43 6F 6D 70 30 37} UNKNOWN[2352-125]={4D 53 46 54 20 35 2E 30} NAS-Real-Port=553648528 UNKNOWN[3561--1]={02 13 42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} UNKNOWN[3561--1]={01 12 34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS: Packet type: Access-Request Identifier: 1 Authenticator: {AC 40 D8 45 52 8A 44 34 47 1C A4 74 E7 8C 13 3D} Attributes: NAS-Identifier=BLG-CORE-SE100-1 User-Name=4857544357545F55 User-Password=Redback NAS-IP-Address=172.31.255.11 NAS-Port=553648528 Service-Type=5 NAS-Port-Id=2/1 vlan-id 400 clips 131074 NAS-Port-Type=5 Calling-Station-Id=001560ca2890 OS-Version=12.1.1.12p1 Agent-Remote-Id={42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} Mac-Addr=00-15-60-ca-28-90 Agent-Circuit-Id={34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} Platform-Type=4 Medium-Type=11 UNKNOWN[2352-202]={3D 3D 07 01 00 15 60 CA 28 90} UNKNOWN[2352-202]={0C 0C 0A 57 6F 72 6B 43 6F 6D 70 30 37} UNKNOWN[2352-125]={4D 53 46 54 20 35 2E 30} NAS-Real-Port=553648528 UNKNOWN[3561--1]={02 13 42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} UNKNOWN[3561--1]={01 12 34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} Common options: {macAddress=00-15-60-ca-28-90, interfaceId=4857544357545F55, agentRemoteId=BLG-STR-MA5683T-1, agentCircuitId=4857544357545F55} radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetNas - Search by username=4857544357545F55 radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetRadiusProcessor - [username=4857544357545F55] Authenticated as inetServId:1700 radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetNas - Found agentDevice by identifier: 8 radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetApplication - contract tariffOptions: {} radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetApplication - inetServ[id=1700] balance ok: -918.14 [-1000.00] radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetApplication - OptionSet: [8] radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetRadiusIpAddressUtils - Not found free static IP in serv radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetRadiusIpAddressUtils - Set ip from pool radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetRadiusProcessor - Write new waiting connection to DB radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetRadiusProcessor - New connection id=453496 radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetRadiusProcessor - Return code=0 radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetConnectionMap - Put auth accept deviceId:4;mac:001560CA2890 radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetRadiusProcessor - RESPONSE_BEFORE_POSTPROCESS: Packet type: Access-Accept Identifier: 1 Authenticator: {} Attributes: Acct-Interim-Interval=600 Framed-IP-Address=10.0.0.6 Service-Parameter:1=Burst=102400 Rate=102400 ExBurst=102400 Service-Name:1=SERVICE_INET Service-Options:1=0 Process time auth: 11 radius 04-19/16:52:31 INFO [rdsLstnr-p-9-t-2] InetRadiusListenerWorker - RESPONSE (14ms): Packet type: Access-Accept Identifier: 1 Authenticator: {02 14 F4 44 DB A4 79 80 3A C5 31 8B 8C A5 1C A5} Attributes: Acct-Interim-Interval=600 Service-Parameter:1=Burst=102400 Rate=102400 ExBurst=102400 Service-Name:1=SERVICE_INET Service-Options:1=0 Process time auth: 12 connection 04-19/16:52:31 INFO [sa-p-15-t-49] ServiceActivatorSet - Connecting to device connection 04-19/16:52:31 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Do task deviceId: 4; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountingEvent] moduleId: 1; pluginId: no; cid: 7; scid: -1; userId: 0; type: 1; deviceId: 4; connectionId: 453497; timestamp: 1555681951681 connection 04-19/16:52:31 INFO [sa-p-15-t-49] InetApplication - OptionSet: [] connection 04-19/16:52:31 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=4; inetServId: 79; call: true; oldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 04-19/16:52:31 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Processing deviceId:4; command ServiceActivatorEvent type=4; inetServId: 79; call: true; oldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 04-19/16:52:31 INFO [sa-p-15-t-49] ServiceActivatorSet - Invoking onAccountingStart connection 04-19/16:52:31 INFO [sa-p-15-t-49] ServiceActivatorDeviceWorker - Process event type[4] result=true mq 04-19/16:52:31 INFO [event-proc-p-2-t-1] InetConnectionManager - Add connection: InetConnection [id=453497-0, iface=4:553648528, sessId=0100FFFF78000002-5CB9D2A7, start=19.04.2019 16:52:31, uname=424c472d5354522d4d4135363833542d31:34383537353434333537353435463535, addr=[IpAddress:null]] mq 04-19/16:52:31 INFO [event-proc-p-2-t-1] InetConnectionMap - Ip is null deviceId:4;mac:001560CA2890 dhcp 04-19/16:52:31 INFO [dhcpLstnr-p-12-t-2] AbstractInetDhcpProcessor2 - REQUEST: Message type: BOOT_REQUEST Dhcp message type: DHCP Discover{1} htype: 1, hlen: 6, hops: 1 xid: 1430607191, secs: 2816, flags: 11111111111111111000000000000000 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} {116}={01} Client-ident.{61}={01001560CA2890} Requested IP{50}=169.254.73.157 Host name{12}={WorkComp07} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC00} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} dhcp 04-19/16:52:31 INFO [dhcpLstnr-p-12-t-2] AbstractInetDhcpProcessor2 - REQUEST_AFTER_PREPROCESS: Message type: BOOT_REQUEST Dhcp message type: DHCP Discover{1} htype: 1, hlen: 6, hops: 1 xid: 1430607191, secs: 2816, flags: 11111111111111111000000000000000 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} {116}={01} Client-ident.{61}={01001560CA2890} Requested IP{50}=169.254.73.157 Host name{12}={WorkComp07} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC00} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} Common options: {interfaceId=4857544357545F55, agentRemoteId=BLG-STR-MA5683T-1, agentCircuitId=4857544357545F55} dhcp 04-19/16:52:31 ERROR [dhcpLstnr-p-12-t-2] InetDhcpProcessor2 - Not found params for request: (pattern: $deviceId:$mac, servSearchMode: 0, deviceId: 4, agentDeviceId: dhcp 04-19/16:52:31 INFO [dhcpLstnr-p-12-t-2] AbstractInetDhcpProcessor2 - RESPONSE: Message type: BOOT_RESPONSE Dhcp message type: DHCP NAK{6} htype: 1, hlen: 6, hops: 1 xid: 1430607191, secs: 0, flags: 11111111111111111000000000000000 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} connection 04-19/16:52:36 INFO [sa-p-15-t-49] ServiceActivatorSet - Disconnecting from device |
Автор: | Amir [ 21 апр 2019, 22:56 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Выложили обновление модуля, была проблема с DHCP при поиске по логину в связке с RADIUS |
Автор: | DVShatskikh [ 23 апр 2019, 14:16 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Обновился. Not fount params for request пропала, но сервис DHCP все-равно не находит. radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] RadiusListenerWorker - REQUEST: Packet type: Access-Request Identifier: 14 Authenticator: {FE 41 B2 E4 2E F3 38 46 8A 67 89 75 D3 59 A9 F2} Attributes: NAS-Identifier=BLG-CORE-SE100-1 User-Name=00:15:60:ca:28:90 User-Password=Redback NAS-IP-Address=172.31.255.11 NAS-Port=553648528 Service-Type=5 NAS-Port-Id=2/1 vlan-id 400 clips 131083 NAS-Port-Type=5 OS-Version=12.1.1.12p1 Agent-Remote-Id={42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} Mac-Addr=00-15-60-ca-28-90 Agent-Circuit-Id={34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} Platform-Type=4 Medium-Type=11 UNKNOWN[2352-202]={3D 3D 07 01 00 15 60 CA 28 90} UNKNOWN[2352-202]={0C 0C 0A 57 6F 72 6B 43 6F 6D 70 30 37} UNKNOWN[2352-125]={4D 53 46 54 20 35 2E 30} NAS-Real-Port=553648528 UNKNOWN[3561--1]={02 13 42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} UNKNOWN[3561--1]={01 12 34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetRadiusProcessor - REQUEST_AFTER_PREPROCESS: Packet type: Access-Request Identifier: 14 Authenticator: {FE 41 B2 E4 2E F3 38 46 8A 67 89 75 D3 59 A9 F2} Attributes: NAS-Identifier=BLG-CORE-SE100-1 User-Name=4857544357545F55 User-Password=Redback NAS-IP-Address=172.31.255.11 NAS-Port=553648528 Service-Type=5 NAS-Port-Id=2/1 vlan-id 400 clips 131083 NAS-Port-Type=5 Calling-Station-Id=001560ca2890 OS-Version=12.1.1.12p1 Agent-Remote-Id={42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} Mac-Addr=00-15-60-ca-28-90 Agent-Circuit-Id={34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} Platform-Type=4 Medium-Type=11 UNKNOWN[2352-202]={3D 3D 07 01 00 15 60 CA 28 90} UNKNOWN[2352-202]={0C 0C 0A 57 6F 72 6B 43 6F 6D 70 30 37} UNKNOWN[2352-125]={4D 53 46 54 20 35 2E 30} NAS-Real-Port=553648528 UNKNOWN[3561--1]={02 13 42 4C 47 2D 53 54 52 2D 4D 41 35 36 38 33 54 2D 31} UNKNOWN[3561--1]={01 12 34 38 35 37 35 34 34 33 35 37 35 34 35 46 35 35} Common options: {macAddress=00-15-60-ca-28-90, interfaceId=4857544357545F55, agentRemoteId=BLG-STR-MA5683T-1, agentCircuitId=4857544357545F55} radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetNas - Search by username=4857544357545F55 radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetRadiusProcessor - [username=4857544357545F55] Authenticated as inetServId:1700 radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetNas - Found agentDevice by identifier: 8 radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetApplication - contract tariffOptions: {} radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetApplication - inetServ[id=1700] balance ok: -918.14 [-1000.00] radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetApplication - OptionSet: [8] radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetRadiusIpAddressUtils - Not found free static IP in serv radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetRadiusIpAddressUtils - Set ip from pool radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetRadiusProcessor - Write new waiting connection to DB radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetRadiusProcessor - New connection id=453513 radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetRadiusProcessor - Return code=0 radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetConnectionMap - Put auth accept deviceId:4;mac:001560CA2890 radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetRadiusProcessor - RESPONSE_BEFORE_POSTPROCESS: Packet type: Access-Accept Identifier: 14 Authenticator: {} Attributes: Acct-Interim-Interval=600 Framed-IP-Address=10.0.0.78 Service-Parameter:1=Burst=102400 Rate=102400 ExBurst=102400 Service-Name:1=SERVICE_INET Service-Options:1=0 Process time auth: 5 radius 04-23/11:13:27 INFO [rdsLstnr-p-9-t-7] InetRadiusListenerWorker - RESPONSE (6ms): Packet type: Access-Accept Identifier: 14 Authenticator: {DB 0A 60 93 F5 B4 B7 8D 46 67 3B E6 8D 61 66 19} Attributes: Acct-Interim-Interval=600 Service-Parameter:1=Burst=102400 Rate=102400 ExBurst=102400 Service-Name:1=SERVICE_INET Service-Options:1=0 Process time auth: 5 connection 04-23/11:13:27 INFO [sa-p-15-t-12] ServiceActivatorSet - Connecting to device connection 04-23/11:13:27 INFO [sa-p-15-t-12] ServiceActivatorDeviceWorker - Do task deviceId: 4; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountingEvent] moduleId: 1; pluginId: no; cid: 7; scid: -1; userId: 0; type: 1; deviceId: 4; connectionId: 453514; timestamp: 1556007207035 connection 04-23/11:13:27 INFO [sa-p-15-t-12] InetApplication - OptionSet: [] connection 04-23/11:13:27 INFO [sa-p-15-t-12] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=4; inetServId: 79; call: true; oldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 04-23/11:13:27 INFO [sa-p-15-t-12] ServiceActivatorDeviceWorker - Processing deviceId:4; command ServiceActivatorEvent type=4; inetServId: 79; call: true; oldState: 1; newState: 1; oldOptionSet: ; newOptionSet: connection 04-23/11:13:27 INFO [sa-p-15-t-12] ServiceActivatorSet - Invoking onAccountingStart connection 04-23/11:13:27 INFO [sa-p-15-t-12] ServiceActivatorDeviceWorker - Process event type[4] result=true mq 04-23/11:13:27 INFO [event-proc-p-2-t-1] InetConnectionManager - Add connection: InetConnection [id=453514-0, iface=4:553648528, sessId=0100FFFF7800000B-5CBEC935, start=23.04.2019 11:13:27, uname=424c472d5354522d4d4135363833542d31:34383537353434333537353435463535, addr=[IpAddress:null]] mq 04-23/11:13:27 INFO [event-proc-p-2-t-1] InetConnectionMap - Ip is null deviceId:4;mac:001560CA2890 dhcp 04-23/11:13:27 INFO [dhcpLstnr-p-12-t-1] AbstractInetDhcpProcessor2 - REQUEST: Message type: BOOT_REQUEST Dhcp message type: DHCP Discover{1} htype: 1, hlen: 6, hops: 1 xid: 1430607196, secs: 0, flags: 0 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} {116}={01} Client-ident.{61}={01001560CA2890} Requested IP{50}=10.0.0.77 Host name{12}={WorkComp07} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC00} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} dhcp 04-23/11:13:27 INFO [dhcpLstnr-p-12-t-1] AbstractInetDhcpProcessor2 - REQUEST_AFTER_PREPROCESS: Message type: BOOT_REQUEST Dhcp message type: DHCP Discover{1} htype: 1, hlen: 6, hops: 1 xid: 1430607196, secs: 0, flags: 0 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} {116}={01} Client-ident.{61}={01001560CA2890} Requested IP{50}=10.0.0.77 Host name{12}={WorkComp07} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC00} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} Common options: {interfaceId=4857544357545F55, agentRemoteId=BLG-STR-MA5683T-1, agentCircuitId=4857544357545F55} dhcp 04-23/11:13:27 INFO [dhcpLstnr-p-12-t-1] AbstractInetDhcpProcessor2 - RESPONSE: Message type: BOOT_RESPONSE Dhcp message type: DHCP Offer{2} htype: 1, hlen: 6, hops: 1 xid: 1430607196, secs: 0, flags: 0 Client IP: 0.0.0.0 Your IP: 10.0.0.78 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} IP Address Lease Time{51}=300 Server Identifier{54}={00000000} Router{3}=10.0.0.1 Subnet mask{1}=255.255.0.0 DNS{6}={B9FDB505B9FDB605} dhcp 04-23/11:13:30 INFO [dhcpLstnr-p-12-t-2] AbstractInetDhcpProcessor2 - REQUEST: Message type: BOOT_REQUEST Dhcp message type: DHCP Discover{1} htype: 1, hlen: 6, hops: 1 xid: 1430607196, secs: 1024, flags: 0 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} {116}={01} Client-ident.{61}={01001560CA2890} Requested IP{50}=10.0.0.77 Host name{12}={WorkComp07} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC00} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} dhcp 04-23/11:13:30 INFO [dhcpLstnr-p-12-t-2] AbstractInetDhcpProcessor2 - REQUEST_AFTER_PREPROCESS: Message type: BOOT_REQUEST Dhcp message type: DHCP Discover{1} htype: 1, hlen: 6, hops: 1 xid: 1430607196, secs: 1024, flags: 0 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} {116}={01} Client-ident.{61}={01001560CA2890} Requested IP{50}=10.0.0.77 Host name{12}={WorkComp07} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC00} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} Common options: {interfaceId=4857544357545F55, agentRemoteId=BLG-STR-MA5683T-1, agentCircuitId=4857544357545F55} dhcp 04-23/11:13:30 INFO [dhcpLstnr-p-12-t-2] AbstractInetDhcpProcessor2 - RESPONSE: Message type: BOOT_RESPONSE Dhcp message type: DHCP Offer{2} htype: 1, hlen: 6, hops: 1 xid: 1430607196, secs: 0, flags: 0 Client IP: 0.0.0.0 Your IP: 10.0.0.78 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} IP Address Lease Time{51}=300 Server Identifier{54}={00000000} Router{3}=10.0.0.1 Subnet mask{1}=255.255.0.0 DNS{6}={B9FDB505B9FDB605} connection 04-23/11:13:31 INFO [sa-p-15-t-12] ServiceActivatorDeviceWorker - Do task deviceId: 4; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaStateModifyEvent] moduleId: 1; pluginId: no; cid: 7; scid: -1; userId: 0; deviceId: 4; inetServId: 79; connectionId: 453514; state: 0; accessCode: 20; timestamp: 1556007211706 connection 04-23/11:13:31 INFO [sa-p-15-t-12] InetApplication - OptionSet: [] connection 04-23/11:13:31 INFO [sa-p-15-t-12] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=2; inetServId: 79; call: true; oldState: 1; newState: 0; oldOptionSet: ; newOptionSet: connection 04-23/11:13:31 INFO [sa-p-15-t-12] ServiceActivatorDeviceWorker - Processing deviceId:4; command ServiceActivatorEvent type=2; inetServId: 79; call: true; oldState: 1; newState: 0; oldOptionSet: ; newOptionSet: connection 04-23/11:13:31 INFO [sa-p-15-t-12] ServiceActivatorSet - Invoking connectionModify connection 04-23/11:13:31 INFO [sa-p-15-t-12] SmartEdgeServiceActivator - Connection modify: oldState: 1; newState: 0; oldOptionSet: []; newOptionSet: [] connection 04-23/11:13:31 INFO [sa-p-15-t-12] SmartEdgeServiceActivator - Connection disable connection 04-23/11:13:31 INFO [sa-p-15-t-12] SmartEdgeServiceActivator - sendCommands connection 04-23/11:13:31 INFO [sa-p-15-t-12] SmartEdgeServiceActivator - Send enable services CoA: Packet type: CoA-Request Identifier: 4 Authenticator: {3C 9C 39 2A BD 2A E0 E1 CE 8E B4 13 47 E6 53 10} Attributes: Acct-Session-Id=0100FFFF7800000B-5CBEC935 Service-Name:2=SERVICE_BLOCKED Service-Options:2=1 connection 04-23/11:13:31 INFO [sa-p-15-t-12] RadiusClient - Sending to /172.31.255.11:3799 Packet type: CoA-Request Identifier: 4 Authenticator: {3C 9C 39 2A BD 2A E0 E1 CE 8E B4 13 47 E6 53 10} Attributes: Acct-Session-Id=0100FFFF7800000B-5CBEC935 Service-Name:2=SERVICE_BLOCKED Service-Options:2=1 connection 04-23/11:13:31 INFO [sa-p-15-t-12] ServiceActivatorDeviceWorker - Process event type[2] result=true connection 04-23/11:13:31 INFO [rds-clnt-/172.31.255.11-3799] RadiusClient - Recieved from /172.31.255.11:3799 Packet type: CoA-NAK Identifier: 4 Authenticator: {58 26 D7 AD C9 48 4A E6 96 44 72 BF 0C 79 9F C5} Attributes: Error-Cause=550 Event-Timestamp=1556007226 UNKNOWN[2352-193]={01 00 02 26} Service-Name:1=SERVICE_BLOCKED connection 04-23/11:13:34 INFO [sa-p-15-t-12] EventWorker - Future is done connection 04-23/11:13:34 WARN [sa-p-15-t-12] ServiceActivatorDeviceWorker - Task return false connection 04-23/11:13:34 INFO [sa-p-15-t-12] ServiceActivatorSet - Disconnecting from device dhcp 04-23/11:13:38 INFO [dhcpLstnr-p-12-t-3] AbstractInetDhcpProcessor2 - REQUEST: Message type: BOOT_REQUEST Dhcp message type: DHCP Discover{1} htype: 1, hlen: 6, hops: 1 xid: 1430607196, secs: 3072, flags: 0 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} {116}={01} Client-ident.{61}={01001560CA2890} Requested IP{50}=10.0.0.77 Host name{12}={WorkComp07} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC00} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} dhcp 04-23/11:13:38 INFO [dhcpLstnr-p-12-t-3] AbstractInetDhcpProcessor2 - REQUEST_AFTER_PREPROCESS: Message type: BOOT_REQUEST Dhcp message type: DHCP Discover{1} htype: 1, hlen: 6, hops: 1 xid: 1430607196, secs: 3072, flags: 0 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} {116}={01} Client-ident.{61}={01001560CA2890} Requested IP{50}=10.0.0.77 Host name{12}={WorkComp07} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC00} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} Common options: {interfaceId=4857544357545F55, agentRemoteId=BLG-STR-MA5683T-1, agentCircuitId=4857544357545F55} dhcp 04-23/11:13:38 INFO [dhcpLstnr-p-12-t-3] AbstractInetDhcpProcessor2 - RESPONSE: Message type: BOOT_RESPONSE Dhcp message type: DHCP Offer{2} htype: 1, hlen: 6, hops: 1 xid: 1430607196, secs: 0, flags: 0 Client IP: 0.0.0.0 Your IP: 10.0.0.78 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} IP Address Lease Time{51}=300 Server Identifier{54}={00000000} Router{3}=10.0.0.1 Subnet mask{1}=255.255.0.0 DNS{6}={B9FDB505B9FDB605} dhcp 04-23/11:13:38 INFO [dhcpLstnr-p-12-t-4] AbstractInetDhcpProcessor2 - REQUEST: Message type: BOOT_REQUEST Dhcp message type: DHCP Request{3} htype: 1, hlen: 6, hops: 1 xid: 1430607196, secs: 3072, flags: 0 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} Client-ident.{61}={01001560CA2890} Requested IP{50}=10.0.0.78 Server Identifier{54}={C0A86396} Host name{12}={WorkComp07} Client FQDN{81}={000000576F726B436F6D7030372E} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC0100} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} dhcp 04-23/11:13:38 INFO [dhcpLstnr-p-12-t-4] AbstractInetDhcpProcessor2 - REQUEST_AFTER_PREPROCESS: Message type: BOOT_REQUEST Dhcp message type: DHCP Request{3} htype: 1, hlen: 6, hops: 1 xid: 1430607196, secs: 3072, flags: 0 Client IP: 0.0.0.0 Your IP: 0.0.0.0 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} Client-ident.{61}={01001560CA2890} Requested IP{50}=10.0.0.78 Server Identifier{54}={C0A86396} Host name{12}={WorkComp07} Client FQDN{81}={000000576F726B436F6D7030372E} Vendor class ident.{60}={4D53465420352E30} Param request list{55}={1, 15, 3, 6, 44, 46, 47, 31, 33, -7, 43} {43}={DC0100} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} Common options: {interfaceId=4857544357545F55, agentRemoteId=BLG-STR-MA5683T-1, agentCircuitId=4857544357545F55} dhcp 04-23/11:13:38 INFO [dhcpLstnr-p-12-t-4] AbstractInetDhcpProcessor2 - RESPONSE: Message type: BOOT_RESPONSE Dhcp message type: DHCP ACK{5} htype: 1, hlen: 6, hops: 1 xid: 1430607196, secs: 0, flags: 0 Client IP: 0.0.0.0 Your IP: 10.0.0.78 Server IP: 0.0.0.0 Relay IP: 172.31.255.11 Client MAC: {001560CA2890} Agent information{82}= sub{1}={34383537353434333537353435463535} sub{2}={424C472D5354522D4D4135363833542D31} IP Address Lease Time{51}=300 Server Identifier{54}={00000000} Router{3}=10.0.0.1 Subnet mask{1}=255.255.0.0 DNS{6}={B9FDB505B9FDB605} |
Автор: | Amir [ 23 апр 2019, 15:52 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
А что не так? Выдает же DHCP OFFER/ACK |
Автор: | DVShatskikh [ 26 апр 2019, 18:09 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Так он вяжется к гостевому сервису, а не к конкретному абоненту. InetRadiusProcessor - [username=4857544357545F55] Authenticated as inetServId:1700 connection 04-23/11:13:31 INFO [sa-p-15-t-12] ServiceActivatorDeviceWorker - Processing deviceId:4; command ServiceActivatorEvent type=2; inetServId: 79; call: true; oldState: 1; newState: 0; oldOptionSet: ; newOptionSet: |
Автор: | Amir [ 29 апр 2019, 17:41 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Это уже с DHCP не связано - т.к. происходит еще при Access-Request. Может быть что-то меняли еще? Сейчас точно есть сервис с логином 4857544357545F55 и он привязан к одному из устройств дерева Access+Accounting (например, самому Access+Accounting)? |
Автор: | DVShatskikh [ 09 май 2019, 03:31 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Конечно есть. Он же при авторизации по радиусу находится, а DHCP ищет по совокупности, как я понимаю, deviceid:mac. В логе это видно как uname=424c472d5354522d4d4135363833542d31:34383537353434333537353435463535 Если поставить это как Username, то получается обратная ситуация - RADIUS не находит, а DHCP находит. |
Автор: | DVShatskikh [ 15 май 2019, 16:14 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
up! |
Автор: | Amir [ 15 май 2019, 16:20 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Цитата: InetRadiusProcessor - [username=4857544357545F55] Authenticated as inetServId:1700 Это и есть авторизация по RADIUS, а раз 1700 - это гостевой сервис, то значит логин 4857544357545F55 не находится
|
Автор: | DVShatskikh [ 15 май 2019, 16:33 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
1700-нормальный сервис. Радиус его находит. Гостевой-79. За него цепляется DHCP, потому что не находит сервис по своему варианту uname |
Автор: | Amir [ 20 май 2019, 16:21 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Нужен доступ, посмотреть |
Автор: | DVShatskikh [ 21 май 2019, 15:43 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Доступ сделал. Параметры в личке |
Автор: | Amir [ 23 май 2019, 22:08 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Проблема была в том, что у вас в предобработке Access-Request подменялся User-Name, а в предобработке Accounting - нет. Т.е. DHCP был не при чем. При получении Accounting-пакета биллинг первым делом пытается найти абонента, а потом уже идет работа с сессией. У вас же поиск стоит по User-Name - получалось что для биллинга Access-Request от одного абонента, а Accounting-Request - от другого |
Автор: | Amir [ 23 май 2019, 22:10 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
P.S. Изначально в модуле Inet для IPoE делали поиск по User-Name, но потом добавили другие виды поиска, по VLAN/порту, которые извлекаются из какого-либо значения. В каких-то случаях удобнее использовать такой вид поиска, вместо того, чтобы в предобработке сохранения сервиса генерировать User-Name. Но в случае PON может быть наоборот - проще прописать в User-Name идентификатор ONU, чем завязываться на порты OLT. Также можно делать привязку через доп. действие ЛК (или на событие логина в ЛК или в какой-нибудь странице авторизации), вытаскивая VLAN или порт или ONU ID из сессии и сохраняя значения в сервис - тогда меньше работы оператору при смене оборудования |
Автор: | DVShatskikh [ 28 май 2019, 02:57 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
Амир, большое спасибо! P.S. У нас так и сделана привязка, через событие логина в старый ЛК. Жаль только с новым ЛК этот фокус не работает. |
Автор: | snark [ 14 июн 2019, 14:41 ] |
Заголовок сообщения: | Re: GPON.IPoE.DHCP.Авторизация по SN ONT. |
DVShatskikh писал(а): Схема следующая: Абоненты сидят по GPON на Huawei MA5683T. В качестве BRAS используется Redback SE-100. Заведены два устройства, SE100 (id:4) и дочерним к нему Huawei (id:8). Huawei вставляет в option82: серийный номер ONT и свой hostname. SE100 выполняет функцию dhcp proxy. Хотелось бы реализовать авторизацию чисто по серийнику ONT. Пардон, но нахуа?
|
Страница 1 из 1 | Часовой пояс: UTC + 5 часов [ Летнее время ] |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |