Есть такая схема:
Sw1(id=25,opt82)->NAS(id=24,radius+opt82)->Inet(radius).
Есть сервис в котором установлены Sw1+port.
NAS отправляет запрос "access" на радиус, к котором присутствуют данные с opt.82.
В Inet (Access+Accounting) есть дополнительный ProtocolHandler, который устанавливает agentRemoteId и interfaceId.
Авторизация проходит правильно, согласно порта и свитча.
Но в мониторе сервис привязывается к NAS, не к SW1.
Поиск сервиса установлен так: radius.servSearchMode=1,4,0.
Лог Access:
Код:
Packet type: Access-Request
Identifier: 1
Authenticator: {A6 12 AC F1 25 0C A7 01 E5 A8 94 4A EF D0 91 09}
Attributes:
User-Name=192.168.8.2:2
User-Password=192.168.8.2:2
NAS-Identifier=nas01
NAS-IP-Address=192.168.1.103
NAS-Port=0
Calling-Station-Id=00:0c:42:34:39:3d
NAS-Port-Type=15
Called-Station-Id=eth0.20
Common options: {agentRemoteId=192.168.8.2, interfaceId=2}
radius 05-16/09:50:02 DEBUG [rdsLstnr-p-8-t-3] RadiusProcessor - Create new radius session.
radius 05-16/09:50:02 DEBUG [rdsLstnr-p-8-t-3] InetNas - agentRemoteId=192.168.8.2
radius 05-16/09:50:02 INFO [rdsLstnr-p-8-t-3] InetNas - Found agentDevice:25
radius 05-16/09:50:02 DEBUG [rdsLstnr-p-8-t-3] InetNas - findServ agentDeviceRuntime=ru.bitel.bgbilling.modules.inet.runtime.device.InetDeviceRuntime@1767553
radius 05-16/09:50:02 INFO [rdsLstnr-p-8-t-3] InetNas - Search serv on deviceId=25; interfaceId=2
radius 05-16/09:50:02 DEBUG [rdsLstnr-p-8-t-3] InetRadiusProcessor - Password verification disabled.
radius 05-16/09:50:02 INFO [rdsLstnr-p-8-t-3] InetRadiusProcessor - [username=192.168.8.2:2] Authenticated as inetServId:50
radius 05-16/09:50:02 DEBUG [rdsLstnr-p-8-t-3] InetRadiusProcessor - Identifier from request: null
radius 05-16/09:50:02 DEBUG [rdsLstnr-p-8-t-3] InetRadiusProcessor - MAC-address from request:
radius 05-16/09:50:02 DEBUG [rdsLstnr-p-8-t-3] InetAccountingPeriodList - Create:
AccountingPeriod: 28: 01.05.2013 00:00:00.0 - 31.05.2013 23:59:59.999
radius 05-16/09:50:02 INFO [rdsLstnr-p-8-t-3] InetApplication - inetServ[id=50] balance ok: -505.54 [-5000.00]
radius 05-16/09:50:02 INFO [rdsLstnr-p-8-t-3] InetApplication - TariffOptionMap: {}
radius 05-16/09:50:02 INFO [rdsLstnr-p-8-t-3] InetApplication - OptionSet: [7]
radius 05-16/09:50:02 INFO [rdsLstnr-p-8-t-3] InetRadiusProcessor - Write new waiting connection to DB
radius 05-16/09:50:02 INFO [rdsLstnr-p-8-t-3] InetRadiusProcessor - New connection id=25018
radius 05-16/09:50:02 INFO [rdsLstnr-p-8-t-3] InetRadiusProcessor - Return code=0
radius 05-16/09:50:02 INFO [rdsLstnr-p-8-t-3] InetConnectionKeyMap - Put auth accept 192.168.252.81
radius 05-16/09:50:02 INFO [rdsLstnr-p-8-t-3] InetRadiusProcessor - RESPONSE_BEFORE_POSTPROCESS:
Packet type: Access-Accept
Identifier: 1
Лог Accounting:
Код:
Packet type: Accounting-Request
Identifier: 1
Authenticator: {F3 22 CC 15 0F B2 24 F5 71 86 D0 91 CB C5 C2 1B}
Attributes:
User-Name=192.168.8.2:2
NAS-Identifier=nas01
NAS-IP-Address=192.168.1.103
NAS-Port=0
Framed-IP-Address=192.168.252.81
Acct-Input-Octets=0
Acct-Output-Octets=0
Acct-Status-Type=1
Acct-Session-Time=0
Acct-Input-Packets=0
Acct-Session-Id=07101cdcd74dddad
Acct-Authentic=1
Acct-Output-Packets=0
Acct-Output-Gigawords=0
Acct-Input-Gigawords=0
NAS-Port-Type=15
Calling-Station-Id=00:0c:42:34:39:3d
Called-Station-Id=eth0.20
Common options: {agentRemoteId=192.168.8.2, interfaceId=2}
radius 05-16/09:50:02 INFO [rdsLstnr-p-7-t-1] InetNas - Found agentDevice:25
radius 05-16/09:50:02 INFO [rdsLstnr-p-7-t-1] InetNas - Search serv on deviceId=25; interfaceId=2
radius 05-16/09:50:02 INFO [rdsLstnr-p-7-t-1] InetRadiusProcessor - Creating NasConnection from radius accounting packet
radius 05-16/09:50:02 INFO [rdsLstnr-p-7-t-1] InetRadiusProcessor - Connection exist in db
radius 05-16/09:50:02 INFO [rdsLstnr-p-7-t-1] Accounting - Update connection to DB
radius 05-16/09:50:02 INFO [rdsLstnr-p-7-t-1] Accounting - Write new session to DB
radius 05-16/09:50:02 INFO [rdsLstnr-p-7-t-1] Accounting - New session's id=16864
radius 05-16/09:50:02 INFO [rdsLstnr-p-7-t-1] connection - 25018:16864 Register ip: 192.168.252.81
radius 05-16/09:50:02 INFO [rdsLstnr-p-7-t-1] InetConnectionKeyMap - Put connection add 192.168.252.81
radius 05-16/09:50:02 INFO [rdsLstnr-p-7-t-1] RadiusListenerWorker - RESPONSE:
Packet type: Accounting-Response
Identifier: 1
Authenticator: {A9 34 B7 24 E2 70 EA 8D AB A8 B9 69 92 D6 AE DC}
Attributes:
Как сделать, что бы такие сессии привязывались не к NAS, а к свитчу?