forum.bitel.ru
http://forum.bitel.ru/

Не работает гостевая сессия+radius.disable.servId [РЕШЕНО]
http://forum.bitel.ru/viewtopic.php?f=44&t=8867		 Страница 1 из 1
Автор:  Магнитка.RU [ 21 янв 2014, 17:40 ]
Заголовок сообщения:  Не работает гостевая сессия+radius.disable.servId [РЕШЕНО]
bgbilling 6.0 (1277 от 06.01.2014) схема IPOE+RedBack(SE100)+InetDhcpHelperProcessor.

Здравствуйте, хочу сделать гостевой доступ, создал фиктивный договор и сервис в состоянии "закрыт", прописал radius.disable.servId, при подключении клиента с непрописанного коммутатора
радиус определяет ево как гостевого и запоминает как 3:0:1 но DhcpListnerWorker определяет ево как 3:3:24 и не находит сопоставления для сессии. Подскажите есть ли решения в данной ситуации ?

Конфиг биллинга
Код:
radius.servSearchMode=1
radius.key.pattern=$deviceId:$remoteId:$circuitId
dhcp.deviceSearchMode=0
dhcp.servSearchMode=1
dhcp.key.pattern=$deviceId:$remoteId:$circuitId


Лог ошибки
Код:
radius 01-21/17:16:40 DEBUG [rdsLstnr-p-8-t-2] RadiusProcessor - Create new radius session.
radius 01-21/17:16:40 DEBUG [rdsLstnr-p-8-t-2] InetNas - agentRemoteId=java.nio.DirectByteBufferR[pos=0 lim=6 cap=6]
radius 01-21/17:16:40  INFO [rdsLstnr-p-8-t-2] InetNas - AgentDevice not found.
radius 01-21/17:16:40 DEBUG [rdsLstnr-p-8-t-2] InetNas - findServ agentDeviceRuntime=null
radius 01-21/17:16:40  INFO [rdsLstnr-p-8-t-2] InetNas - Search serv on deviceId=3; interfaceId=24
radius 01-21/17:16:40  INFO [rdsLstnr-p-8-t-2] InetRadiusProcessor - [username=d4:ca:6d:53:35:d0] InetServ not found.
radius 01-21/17:16:40 DEBUG [rdsLstnr-p-8-t-2] InetRadiusProcessor - Use disable.inetServ.
radius 01-21/17:16:40  INFO [rdsLstnr-p-8-t-2] InetRadiusProcessor - [username=d4:ca:6d:53:35:d0] Authenticated as inetServId:12
radius 01-21/17:16:40 DEBUG [rdsLstnr-p-8-t-2] InetNas - agentRemoteId=java.nio.DirectByteBufferR[pos=0 lim=6 cap=6]
radius 01-21/17:16:40  INFO [rdsLstnr-p-8-t-2] InetNas - AgentDevice not found.
radius 01-21/17:16:40 DEBUG [rdsLstnr-p-8-t-2] InetRadiusProcessor - AccessCode is 1. Set to disable realm (rejectToAccept)
radius 01-21/17:16:40  INFO [rdsLstnr-p-8-t-2] InetRadiusProcessor - Write new waiting connection to DB
radius 01-21/17:16:40  INFO [rdsLstnr-p-8-t-2] InetRadiusProcessor - New connection id=49674
radius 01-21/17:16:40  INFO [rdsLstnr-p-8-t-2] InetRadiusProcessor - Return code=0
radius 01-21/17:16:40  INFO [rdsLstnr-p-8-t-2] InetDhcpHelperProcessor - Put auth accept 3:0:1
radius 01-21/17:16:40  INFO [rdsLstnr-p-8-t-2] InetRadiusProcessor - RESPONSE_BEFORE_POSTPROCESS:
Packet type: Access-Accept
Identifier: 32
Authenticator: {}
Attributes:
  Reply-Message=1
  Framed-IP-Address=172.28.0.74
  DHCP-Max-Leases=1
  IP-Interface-Name=REJECT

Process time auth: 7

radius 01-21/17:16:40 DEBUG [rdsLstnr-p-8-t-2] ProcessorRequest - Sending to /10.0.0.11:1812
radius 01-21/17:16:40  INFO [rdsLstnr-p-8-t-2] InetRadiusListenerWorker - RESPONSE:
Packet type: Access-Accept
Identifier: 32
Authenticator: {83 98 5E 15 12 BC 8B 65 1D 72 19 F1 5C 1F CF 32}
Attributes:
  Reply-Message=1
  DHCP-Max-Leases=1
  IP-Interface-Name=REJECT

Process time auth: 12

connection 01-21/17:16:40 DEBUG [sa-p-13-t-7] AcknowledgeConsumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountin
gEvent] moduleId: 1; pluginId: no; cid: 4; scid: -1; userId: 0; type: 1; deviceId: 3; connectionId: 49674; timestamp: 1390303000463
connection 01-21/17:16:40  INFO [sa-p-13-t-7] ServiceActivatorDeviceWorker - Do task deviceId: 3; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAcc
ountingEvent] moduleId: 1; pluginId: no; cid: 4; scid: -1; userId: 0; type: 1; deviceId: 3; connectionId: 49674; timestamp: 1390303000463
connection 01-21/17:16:40  INFO [sa-p-13-t-7] InetApplication - OptionSet: []
connection 01-21/17:16:40  INFO [sa-p-13-t-7] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=4; inetServId: 12; call: true; oldS
tate: -1; newState: -1; oldOptionSet: ; newOptionSet:
connection 01-21/17:16:40  INFO [sa-p-13-t-7] ServiceActivatorDeviceWorker - Processing deviceId:3; command ServiceActivatorEvent type=4; inetServId: 12; call: t
rue; oldState: -1; newState: -1; oldOptionSet: ; newOptionSet:
connection 01-21/17:16:40  INFO [sa-p-13-t-7] ServiceActivatorSet - Invoking onAccountingStart
connection 01-21/17:16:40  INFO [sa-p-13-t-7] ServiceActivatorDeviceWorker - Process event type[4] result=true
dhcp 01-21/17:16:40  INFO [dhcpLstnr-p-10-t-10] InetAbstractDhcpProcessor - REQUEST:
Message type: BOOT_REQUEST
Dhcp message type: DHCP Discover{1}
htype: 1, hlen: 6, hops: 1
xid: 1562973304, secs: 8, flags: -32768
Client IP: 0.0.0.0
Your IP: 0.0.0.0
Server IP: 0.0.0.0
Relay IP: 172.28.0.1
Client MAC: {D4CA6D5335D0}
  Parameter request list{55}={1, 121, 3, 33, 6, 42}
  Host name{12}={office-wifi}
  {61}={01D4CA6D5335D0}
  Agent information{82}=
    sub{1}={0004000B0018}
    sub{2}={0006001FCE106AF6}

dhcp 01-21/17:16:40 DEBUG [dhcpLstnr-p-10-t-10] InetAbstractDhcpProcessor - OP_BOOT_REQUEST
dhcp 01-21/17:16:40 DEBUG [dhcpLstnr-p-10-t-10] InetAbstractDhcpProcessor - Found device by giaddr id=3
dhcp 01-21/17:16:40  INFO [dhcpLstnr-p-10-t-10] InetAbstractDhcpProcessor - REQUEST_AFTER_PREPROCESS:
Message type: BOOT_REQUEST
Dhcp message type: DHCP Discover{1}
htype: 1, hlen: 6, hops: 1
xid: 1562973304, secs: 8, flags: -32768
Client IP: 0.0.0.0
Your IP: 0.0.0.0
Server IP: 0.0.0.0
Relay IP: 172.28.0.1
Client MAC: {D4CA6D5335D0}
  Parameter request list{55}={1, 121, 3, 33, 6, 42}
  Host name{12}={office-wifi}
  {61}={01D4CA6D5335D0}
  Agent information{82}=
    sub{1}={0004000B0018}
    sub{2}={0006001FCE106AF6}

dhcp 01-21/17:16:40  INFO [dhcpLstnr-p-10-t-10] InetAbstractDhcpProcessor - Agent device not found by agentRemoteId=001fce106af6
dhcp 01-21/17:16:40 DEBUG [dhcpLstnr-p-10-t-10] InetDhcpHelperProcessor - request.giaddr = 172.28.0.1
dhcp 01-21/17:16:40 ERROR [dhcpLstnr-p-10-t-10] InetDhcpHelperProcessor - Not found params for request: 3:3:24 (pattern: $deviceId:$remoteId:$circuitId, servSear
chMode: 1, deviceId: 3, agentDeviceId: 3, mac: D4CA6D5335D0)
dhcp 01-21/17:16:40  INFO [dhcpLstnr-p-10-t-10] InetAbstractDhcpProcessor - RESPONSE_BEFORE_POSTPROCESS:
Message type: BOOT_RESPONSE
Dhcp message type: DHCP NAK{6}
htype: 1, hlen: 6, hops: 1
xid: 1562973304, secs: 0, flags: -32768
Client IP: 0.0.0.0
Your IP: 0.0.0.0
Server IP: 0.0.0.0
Relay IP: 172.28.0.1
Client MAC: {D4CA6D5335D0}
  Agent information{82}=
    sub{1}={0004000B0018}
    sub{2}={0006001FCE106AF6}
dhcp 01-21/17:16:40  INFO [dhcpLstnr-p-10-t-10] InetAbstractDhcpProcessor - RESPONSE:
Message type: BOOT_RESPONSE
Dhcp message type: DHCP NAK{6}
htype: 1, hlen: 6, hops: 1
xid: 1562973304, secs: 0, flags: -32768
Client IP: 0.0.0.0
Your IP: 0.0.0.0
Server IP: 0.0.0.0
Relay IP: 172.28.0.1
Client MAC: {D4CA6D5335D0}
  Agent information{82}=
    sub{1}={0004000B0018}
    sub{2}={0006001FCE106AF6}

dhcp 01-21/17:16:40 DEBUG [dhcpLstnr-p-10-t-10] ProcessorRequest - Sending to /10.0.0.11:67
mq 01-21/17:16:40 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.oss.systems.inventory.resource.common.event.IpResourceSubscribedEv
ent] moduleId: 1; pluginId: no; cid: 4; scid: -1; userId: -1; timestamp: 1390303000462
mq 01-21/17:16:40 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] modul
eId: 1; pluginId: no; cid: 4; scid: -1; userId: 0; type: 1; deviceId: 3; connectionId: 49674; timestamp: 1390303000463
mq 01-21/17:16:40  INFO [event-proc-p-2-t-1] InetConnectionManager - Add connection: InetConnection [id=49674-0, iface=3:578617355, sessId=0101FFFF78006320-52DE5
718, start=21.01.2014 17:16:40, uname=d4:ca:6d:53:35:d0, addr=172.28.0.74]
mq 01-21/17:16:40  INFO [event-proc-p-2-t-1] InetDhcpHelperProcessor - Put connection add 3:0:1
connection 01-21/17:16:43 DEBUG [sa-p-13-t-7] AcknowledgeConsumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaStateModi
fyEvent] moduleId: 1; pluginId: no; cid: 0; scid: -1; userId: 0; deviceId: 3; inetServId: 12; connectionId: 49673; state: 0; accessCode: 62; timestamp: 139030300
3247
connection 01-21/17:16:43  INFO [sa-p-13-t-7] ServiceActivatorDeviceWorker - Do task deviceId: 3; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaSta
teModifyEvent] moduleId: 1; pluginId: no; cid: 0; scid: -1; userId: 0; deviceId: 3; inetServId: 12; connectionId: 49673; state: 0; accessCode: 62; timestamp: 139
0303003247
connection 01-21/17:16:43 ERROR [sa-p-13-t-7] InetSaStateModifyEvent - Connection not found with id=49673
connection 01-21/17:16:43 DEBUG [sa-p-13-t-7] ServiceActivatorDeviceWorker - Skip event
connection 01-21/17:16:43 DEBUG [sa-p-13-t-7] AcknowledgeConsumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaStateModi
fyEvent] moduleId: 1; pluginId: no; cid: 0; scid: -1; userId: 0; deviceId: 3; inetServId: 12; connectionId: 49672; state: 0; accessCode: 62; timestamp: 139030300
3268
connection 01-21/17:16:43  INFO [sa-p-13-t-7] ServiceActivatorDeviceWorker - Do task deviceId: 3; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaSta
teModifyEvent] moduleId: 1; pluginId: no; cid: 0; scid: -1; userId: 0; deviceId: 3; inetServId: 12; connectionId: 49672; state: 0; accessCode: 62; timestamp: 139
0303003268
connection 01-21/17:16:43 ERROR [sa-p-13-t-7] InetSaStateModifyEvent - Connection not found with id=49672
connection 01-21/17:16:43 DEBUG [sa-p-13-t-7] ServiceActivatorDeviceWorker - Skip event
connection 01-21/17:16:43 DEBUG [sa-p-13-t-7] AcknowledgeConsumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAccountin
gEvent] moduleId: 1; pluginId: no; cid: 4; scid: -1; userId: 0; type: 2; deviceId: 3; connectionId: 49674; timestamp: 1390303003711
connection 01-21/17:16:43  INFO [sa-p-13-t-7] ServiceActivatorDeviceWorker - Do task deviceId: 3; Event[ru.bitel.bgbilling.modules.inet.access.sa.event.InetSaAcc
ountingEvent] moduleId: 1; pluginId: no; cid: 4; scid: -1; userId: 0; type: 2; deviceId: 3; connectionId: 49674; timestamp: 1390303003711
connection 01-21/17:16:43  INFO [sa-p-13-t-7] InetApplication - OptionSet: []
connection 01-21/17:16:43  INFO [sa-p-13-t-7] ServiceActivatorDeviceWorker - Command result event: ServiceActivatorEvent type=5; inetServId: 12; call: true; oldS
tate: -1; newState: -1; oldOptionSet: ; newOptionSet:
connection 01-21/17:16:43  INFO [sa-p-13-t-7] ServiceActivatorDeviceWorker - Processing deviceId:3; command ServiceActivatorEvent type=5; inetServId: 12; call: t
rue; oldState: -1; newState: -1; oldOptionSet: ; newOptionSet:
connection 01-21/17:16:43  INFO [sa-p-13-t-7] ServiceActivatorSet - Invoking onAccountingStop
connection 01-21/17:16:43  INFO [sa-p-13-t-7] ServiceActivatorDeviceWorker - Process event type[5] result=true
mq 01-21/17:16:43 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.bgbilling.modules.inet.accounting.event.InetAccountingEvent] modul
eId: 1; pluginId: no; cid: 4; scid: -1; userId: 0; type: 2; deviceId: 3; connectionId: 49674; timestamp: 1390303003711
mq 01-21/17:16:43  INFO [event-proc-p-2-t-1] InetConnectionManager - Remove connection: InetConnection [id=49674-0, iface=3:578617355, sessId=0101FFFF78006320-52
DE5718, start=21.01.2014 17:16:40, uname=d4:ca:6d:53:35:d0, addr=172.28.0.74]
mq 01-21/17:16:43  INFO [event-proc-p-2-t-1] InetDhcpHelperProcessor - Remove connection remove 3:0:1
access 01-21/17:16:44 DEBUG [access-p-6-t-1] SessionCountManager - Run SessionCountManager...
mq 01-21/17:16:44 DEBUG [event-proc-p-2-t-1] Consumer - Caught BGInetAccounting:Event[ru.bitel.oss.systems.inventory.resource.common.event.IpResourceUnsubscribed
Event] moduleId: 1; pluginId: no; cid: 4; scid: -1; userId: -1; timestamp: 1390303003737
connection 01-21/17:16:48  INFO [sa-p-13-t-7] ServiceActivatorSet - Disconnecting from device
Автор:  Магнитка.RU [ 23 янв 2014, 16:39 ]
Заголовок сообщения:  Re: Не работает InetDhcpHelperProcessor+radius.disable.servI
Решил проблему исправлением значения паттерна на $deviceId:$mac , и добавлением радиус кодов вендора redback для аттрибута macAddress. Сначало падало в InetDhcpHelperProcessor на
"Put auth accept", но после рекомпилинга динамических классов магическим образом перестало.
Сессия, для dhcp пакета находиться по $deviceId и $mac что стало правильно так нету привязки к
коммутатор+порт которые могут не существовать в случае старого паттерна $deviceId:$remoteId:$circuitId.

Код:
radius.macAddress.vendor=2352
radius.macAddress.type=145

radius.key.pattern=$deviceId:$mac
dhcp.deviceSearchMode=0
dhcp.servSearchMode=1
dhcp.key.pattern=$deviceId:$mac
Страница 1 из 1 Часовой пояс: UTC + 5 часов [ Летнее время ]
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/