forum.bitel.ru :: Просмотр темы - Помогите, после обновления accel-pppd не появляются сессии

11-25/09:59:56 WARN [rdsLstnr-p-6-t-61] DialUpNas - Not found connection for update packet:
Packet type: Accounting-Request
Identifier: 114
Authenticator: {DE CC FA D3 77 3C 2B 05 70 1C FF 7D 4D 6D 7B 7C}
Attributes:
User-Name=zzzzzzzz
NAS-Identifier=vpn1
NAS-IP-Address=10.77.3.6
NAS-Port=141
Service-Type=2
Framed-Protocol=1
Framed-IP-Address=91.232.171.92
Acct-Input-Octets=154
Acct-Output-Octets=24032
Acct-Status-Type=3
Acct-Session-Time=6784
Acct-Input-Packets=13
Acct-Session-Id=5aedc3f09bb6abfd
Acct-Authentic=1
NAS-Port-Id=ppp141
Acct-Output-Packets=309
Acct-Output-Gigawords=0
Acct-Input-Gigawords=0
NAS-Port-Type=5
Calling-Station-Id=xx.xx.xx.xx
Called-Station-Id=xx.xx.xx.xx

11-25/10:02:11 ERROR [rdsLstnr-p-5-t-32] DialUpNasConnection - Stop without start!
11-25/10:02:11 INFO [rdsLstnr-p-6-t-80] update - REQUEST:
Packet type: Accounting-Request
Identifier: 23
Authenticator: {20 95 D0 D3 6D 90 3C 9D 3C CF 6F 9D 81 FF 16 A9}

11-25/10:07:12 INFO [rdsLstnr-p-5-t-101] connections - [ 2577; xx; 22955 ] DialUpNASConnection stoppingConnection
11-25/10:07:12 INFO [rdsLstnr-p-5-t-101] connections - [ 2577; xxyy; 22955 ] DialUpNASConnection has stop Packet => false
11-25/10:07:13 INFO [rdsLstnr-p-6-t-45] connections - [ FAKE; xxzzz; 44486 ] DialUpNASConnection update connection..
11-25/10:07:14 INFO [Thread-24] connections - [ FAKE; zziuu; 44493 ] Set status SUSPENDED on UpdateSuspendedSetter, time after last update: 1270451

Клиент: вер. 6.0 сборка 1390 от 21.10.2015 16:04:34
os: Linux; java: Java HotSpot(TM) Server VM, v.1.7.0_80
ВНИМАНИЕ: Спецификация версии 1.7 не рекомендуется
Сервер: вер. 6.0 сборка 1868 от 26.10.2015 16:04:29
os: Linux; java: Java HotSpot(TM) 64-Bit Server VM, v.1.7.0_80
ВНИМАНИЕ: Спецификация версии 1.7 не рекомендуется

12-01/16:49:15 INFO [pool-3-thread-1] connections - Restore Connections NAS: M1_NAS
12-01/16:49:51 INFO [rdsLstnr-p-3-t-1] connections - [ ф-2015-12-0001; user1; 91866 ] Request for taking calculate period..
12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] connections - [ ф-2015-12-0001; user1; 91866 ] Request period to script..
12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] connections - [ ф-2015-12-0001; user1; 91866 ] Set start and end of month.
12-01/16:49:51 INFO [rdsLstnr-p-3-t-1] connections - [ ф-2015-12-0001; user1; 91866 ] calculatePeriodStart: 2015-12-01 16:49:51; calculatePeriodEnd: 2015-12-3
12-01/16:52:14 INFO [Thread-12] connections - [ ф-2015-12-0001; user1; 91866 ] Removing WAIT session, time after create: 143
12-01/16:52:14 INFO [Thread-12] connections - [ ф-2015-12-0001; user1; 91866 ] Dropping connection
12-01/16:52:14 INFO [Thread-12] connections - [ ф-2015-12-0001; user1; 91866 ] DialUpNASConnection stoppingConnection
12-01/16:52:14 INFO [Thread-12] connections - [ ф-2015-12-0001; user1; 91866 ] DialUpNASConnection has stop Packet => false

processor 12-01/16:52:14 ERROR [Thread-12] DialUpNasConnection - Stop without start!

12-01/16:49:14 INFO [main] NasList - Loading NAS list...
12-01/16:49:14 INFO [main] PodNasConnectionInspector - logCoa=false
12-01/16:49:14 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.inspectors.PodNasConnectionInspector$1 socket init ok.
12-01/16:49:14 DEBUG [main] Nas - activate services: [0]
12-01/16:49:14 INFO [main] processor - Starting zombi checker M1_NAS
12-01/16:49:14 INFO [main] processor - Starting wait remover timeout=120 M1_NAS
12-01/16:49:14 INFO [Thread-11] processor - Starting ZombiChecker for Nas id: M1_NAS; ip: 192.168.100.1
12-01/16:49:14 INFO [Thread-12] processor - Starting WaitRemover for Nas id: M1_NAS; ip: 192.168.100.1
12-01/16:49:14 INFO [main] processor - Starting connections month breaker M1_NAS
12-01/16:49:14 INFO [Thread-14] TariffOptionWatcher - Starting TariffOptionWatcher for Nas id: M1_NAS; ip: 192.168.100.1
12-01/16:49:14 INFO [main] NasList - LOADED NAS: Nas id: M1_NAS; ip: 192.168.100.1
CONFIG:
callback.support=0
card.activate.service=0
drop.sleep.timeout=3600
month.break=1
nas.inspector.class=bitel.billing.server.processor.PoDNASConnectionInspector
nas.inspector.coa.retries=10
nas.inspector.coa.threads=4
nas.inspector.coa.timeout=5
nas.inspector.kill.max_messages=5
nas.inspector.radius.attributes=User-Name;Framed-IP-Address;Acct-Session-Id;NAS-Identifier;NAS-IP-Address
nas.inspector.radius.port=3799
nas.inspector.sleep_time=60
nas.port_time.default.*=6
nas.port_traffic.default.*=4:RADIN;5:RADOUT
pppd.version=2.4.3
snmp.version=2

12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.network.radius.RadiusProcessor$1@265649cf to BG.Event.ru.bitel.bgbilling.kernel.even
12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.network.radius.RadiusProcessor$2@29e8ce6a to BG.Event.ru.bitel.bgbilling.modules.cal
12-01/16:49:14 INFO [main] DetailCompressRules - Session detail compress rules:
12-01/16:49:14 INFO [main] processor - Dynamic DNS init => false
12-01/16:49:15 INFO [main] processor - Connection count checker..
12-01/16:49:15 INFO [main] processor - UPDATE mode SLEEP setter, timeout=30
12-01/16:49:15 INFO [main] DialUpRadiusProcessor - Restored 0/0 connections (100.00%)
12-01/16:49:15 INFO [main] DialUpRadiusProcessor - Restored 0/0 connections (100.00%)
12-01/16:49:15 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.contract.status.server.StatusCache$1@4ffcd6f to BG.Event.ru.bitel.bgbilling.kernel.e
12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$1@6b8a3955 to BG.Event.bitel.billing.server.dialup.bean
12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$2@300a3b6c to BG.Event.bitel.billing.server.dialup.bean
12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$3@2bad1914 to BG.Event.bitel.billing.server.call.bean.b
12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$4@4e452646 to BG.Event.bitel.billing.server.call.bean.b
12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$5@7fa81658 to BG.Event.bitel.billing.server.dialup.bean
12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$6@7eded5df to BG.Event.ru.bitel.bgbilling.kernel.event.
12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$7@3fdbfec9 to BG.Event.ru.bitel.bgbilling.kernel.event.
12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$8@d72f8f7 to BG.Event.ru.bitel.bgbilling.kernel.tariff.
12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$9@fa08f61 to BG.Event.ru.bitel.bgbilling.kernel.tariff.
12-01/16:49:15 INFO [main] StaticAddressMonitor - Reload static addresses..
12-01/16:49:34 INFO [Thread-13] processor - Starting ConnectionBreaker for: Nas id: M1_NAS; ip: 192.168.100.1
12-01/16:52:14 ERROR [Thread-12] DialUpNasConnection - Stop without start!

12-01/16:49:10 INFO [main] DefaultServerSetup - Binding javax.jms.ConnectionFactory[org.apache.activemq.ActiveMQConnectionFactory@69a0aec1] to java:comp/env/m
12-01/16:49:10 INFO [main] DefaultServerSetup - Init DB connection pools
12-01/16:49:10 INFO [main] DefaultServerSetup - Binding JDBC pool "master" to java:comp/env/jdbc/master
12-01/16:49:10 INFO [main] AnnotatedMBean - Register MBean ru.bitel.bgbilling.server.util:type=DatabaseConnectionPool,name=master
12-01/16:49:10 INFO [main] DefaultServerSetup - Init trash pools..
12-01/16:49:11 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.server.util.Setup$1@577a2815 to BG.Event.ru.bitel.bgbilling.kernel.event.events.system.Modu
12-01/16:49:11 INFO [main] DefaultServerSetup - Init trash pools..
12-01/16:49:14 INFO [main] Radius - Starting radius auth_port:1812 acct_port:1813 admin_port:1955
12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.script.server.ScriptEventListener$1@6cae887c to BG.Event.ru.bitel.bgbilling.kernel.s
12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.script.server.DynamicScriptEventListener$1@64868d8 to BG.Event.ru.bitel.bgbilling.ke
12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.script.server.DynamicScriptEventListener$2@1c684684 to BG.Event.ru.bitel.bgbilling.k
12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.module.server.ModuleCache$1@7918fabc to BG.Event.ru.bitel.bgbilling.kernel.module.se
12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.module.server.ModuleCache$2@3e55155c to BG.Event.ru.bitel.bgbilling.kernel.module.se
12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent.
12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent.
12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent.
12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent.
12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent.
12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent.
12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent.
12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor$1@31026921 to BG.LocalEven
12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor$1@271ec5ce to BG.LocalEven
12-01/16:49:14 INFO [main] Radius - Init processor.
<------>class: ru.bitel.bgbilling.modules.dialup.radius.DialUpRadiusProcessor
<------>mid: 1
12-01/16:49:14 INFO [main] radius - Eap not enabled (keystore file not loaded).
12-01/16:49:15 INFO [main] Radius - Starting authentication listener...
12-01/16:49:15 INFO [main] Setup - Load config for mid=1
12-01/16:49:15 INFO [main] DatagramChannelListener - Open socket [0.0.0.0/0.0.0.0:1812]
12-01/16:49:15 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.RadiusListener socket init ok.
12-01/16:49:15 INFO [main] Radius - Starting accounting listener...
12-01/16:49:15 INFO [main] DatagramChannelListener - Open socket [0.0.0.0/0.0.0.0:1813]
12-01/16:49:15 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.RadiusListener socket init ok.
12-01/16:49:15 INFO [Thread-21] AdminPortListener - Starting AdminPortListener on 1955
12-01/16:49:51 INFO [rdsLstnr-p-3-t-1] RadiusListenerWorker - REQUEST:
Packet type: Access-Request
Identifier: 1
Authenticator: {61 A2 54 97 F3 39 FB 76 5F 89 78 32 50 56 AE 3B}
Attributes:
User-Name=user1
NAS-Port-Id=
NAS-Identifier=m1_nas
CHAP-Password={01 0C E2 56 2D 59 F6 3A E5 F8 BF 33 A3 72 6F 4D 52}
NAS-IP-Address=192.168.100.1
NAS-Port=-1
Service-Type=2
Framed-Protocol=1
Calling-Station-Id=52:54:00:f5:63:ab
NAS-Port-Type=5
CHAP-Challenge=a�T��9�v_�x2PV�;
Called-Station-Id=52:54:00:2c:ee:28
Packet type: Access-Request
Identifier: 1
Authenticator: {61 A2 54 97 F3 39 FB 76 5F 89 78 32 50 56 AE 3B}
Attributes:
User-Name=user1
NAS-Port-Id=
NAS-Identifier=m1_nas
CHAP-Password={01 0C E2 56 2D 59 F6 3A E5 F8 BF 33 A3 72 6F 4D 52}
NAS-IP-Address=192.168.100.1
NAS-Port=-1
Service-Type=2
Framed-Protocol=1
Calling-Station-Id=52:54:00:f5:63:ab
NAS-Port-Type=5
CHAP-Challenge=a�T��9�v_�x2PV�;
Called-Station-Id=52:54:00:2c:ee:28

12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] RadiusProcessor - Create new radius session.
12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] AbstractRadiusProcessor - Finding login..
12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] AbstractRadiusProcessor - Login found: 1
12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] AbstractRadiusProcessor - Checking access allow...
12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] AbstractRadiusProcessor - Checking password...
12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] AbstractRadiusProcessor - Checking contract status
12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] AbstractRadiusProcessor - Checking balance...
12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] ContractTariffOptionList - Create:.
12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] DialUpRadiusProcessor - Checking tariff...
12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] DialUpRadiusProcessor - Set address time: 0
12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] ProcessorRequest - Sending to /192.168.100.1:43233
12-01/16:49:51 INFO [rdsLstnr-p-3-t-1] RadiusListenerWorker - RESPONSE:
Packet type: Access-Accept
Identifier: 1
Authenticator: {92 A7 70 0F 66 57 97 6F 3D AC 4A 00 E1 94 86 86}
Attributes:
Acct-Interim-Interval=60
Service-Type=2
Framed-Protocol=1
Framed-IP-Address=192.168.200.108

Process time auth: 186

12-01/16:49:52 INFO [rdsLstnr-p-4-t-1] RadiusListenerWorker - REQUEST:
Packet type: Accounting-Request
Identifier: 1
Authenticator: {4F 19 B7 49 BB DB 68 3A 6F 90 FF D8 73 69 27 EB}
Attributes:
User-Name=user1
NAS-Identifier=m1_nas
NAS-IP-Address=192.168.100.1
NAS-Port=0
Service-Type=2
Framed-IP-Address=192.168.200.108
Acct-Input-Octets=0
Acct-Output-Octets=0
Acct-Status-Type=1
Acct-Session-Time=0
Acct-Input-Packets=0
Acct-Session-Id=c7711dfa845cebdd
Acct-Authentic=1
NAS-Port-Id=ppp0
Acct-Output-Packets=0
Acct-Output-Gigawords=0
Acct-Input-Gigawords=0
NAS-Port-Type=5
Calling-Station-Id=52:54:00:f5:63:ab
Called-Station-Id=52:54:00:2c:ee:28

12-01/16:49:52 DEBUG [rdsLstnr-p-4-t-1] ProcessorRequest - Sending to /192.168.100.1:33046
12-01/16:49:52 INFO [rdsLstnr-p-4-t-1] RadiusListenerWorker - RESPONSE:
Packet type: Accounting-Response
Identifier: 1
Authenticator: {F8 96 B8 E3 FD 42 09 0C C4 2D EF 4A 30 F3 11 F1}
Attributes:

Process time start: 5

12-01/16:50:52 INFO [rdsLstnr-p-4-t-2] update - REQUEST:
Packet type: Accounting-Request
Identifier: 2
Authenticator: {09 88 52 2D CB 01 43 4D 66 E2 29 D7 B8 D1 5D 90}
Attributes:
User-Name=user1
NAS-Identifier=m1_nas
NAS-IP-Address=192.168.100.1
NAS-Port=0
Service-Type=2
Framed-Protocol=1
Framed-IP-Address=192.168.200.108
Acct-Input-Octets=1327
Acct-Output-Octets=96
Acct-Status-Type=3
Acct-Session-Time=60
Acct-Input-Packets=13
Acct-Session-Id=c7711dfa845cebdd
Acct-Authentic=1
NAS-Port-Id=ppp0
Acct-Output-Packets=6
Acct-Output-Gigawords=0
Acct-Input-Gigawords=0
NAS-Port-Type=5
Calling-Station-Id=52:54:00:f5:63:ab
Called-Station-Id=52:54:00:2c:ee:28
12-01/16:50:52 WARN [rdsLstnr-p-4-t-2] DialUpNas - Not found connection for update packet:.
Packet type: Accounting-Request
Identifier: 2
Authenticator: {09 88 52 2D CB 01 43 4D 66 E2 29 D7 B8 D1 5D 90}
Attributes:
User-Name=user1
NAS-Identifier=m1_nas
NAS-IP-Address=192.168.100.1
NAS-Port=0
Service-Type=2
Framed-Protocol=1
Framed-IP-Address=192.168.200.108
Acct-Input-Octets=1327
Acct-Output-Octets=96
Acct-Status-Type=3
Acct-Session-Time=60
Acct-Input-Packets=13
Acct-Session-Id=c7711dfa845cebdd
Acct-Authentic=1
NAS-Port-Id=ppp0
Acct-Output-Packets=6
Acct-Output-Gigawords=0
Acct-Input-Gigawords=0
NAS-Port-Type=5
Calling-Station-Id=52:54:00:f5:63:ab
Called-Station-Id=52:54:00:2c:ee:28

12-01/16:50:52 DEBUG [rdsLstnr-p-4-t-2] ProcessorRequest - Sending to /192.168.100.1:42792
12-01/16:50:52 INFO [rdsLstnr-p-4-t-2] update - RESPONSE:
Packet type: Accounting-Response
Identifier: 2
Authenticator: {7C 28 3E 41 19 31 93 7C 62 A6 A4 64 CD 1D BF 22}
Attributes:

Process time update: 7

12-01/16:50:59 DEBUG [setup-sched-p-1-t-1] RadiusProcessor - After clean old rad sessions: 0
12-01/16:51:52 INFO [rdsLstnr-p-4-t-3] update - REQUEST:
Packet type: Accounting-Request
Identifier: 3
Authenticator: {92 05 93 58 11 E8 2E B3 80 C2 16 30 42 ED 7D 26}
Attributes:
User-Name=user1
NAS-Identifier=m1_nas
NAS-IP-Address=192.168.100.1
NAS-Port=0
Service-Type=2
Framed-Protocol=1
Framed-IP-Address=192.168.200.108
Acct-Input-Octets=1327
Acct-Output-Octets=96
Acct-Status-Type=3
Acct-Session-Time=120
Acct-Input-Packets=13
Acct-Session-Id=c7711dfa845cebdd
Acct-Authentic=1
NAS-Port-Id=ppp0
Acct-Output-Packets=6
Acct-Output-Gigawords=0
Acct-Input-Gigawords=0
NAS-Port-Type=5
Calling-Station-Id=52:54:00:f5:63:ab
Called-Station-Id=52:54:00:2c:ee:28

12-01/16:51:52 WARN [rdsLstnr-p-4-t-3] DialUpNas - Not found connection for update packet:.
Packet type: Accounting-Request
Identifier: 3
Authenticator: {92 05 93 58 11 E8 2E B3 80 C2 16 30 42 ED 7D 26}
Attributes:
User-Name=user1
NAS-Identifier=m1_nas
NAS-IP-Address=192.168.100.1
NAS-Port=0
Service-Type=2
Framed-Protocol=1
Framed-IP-Address=192.168.200.108
Acct-Input-Octets=1327
Acct-Output-Octets=96
Acct-Status-Type=3
Acct-Session-Time=120
Acct-Input-Packets=13
Acct-Session-Id=c7711dfa845cebdd
Acct-Authentic=1
NAS-Port-Id=ppp0
Acct-Output-Packets=6
Acct-Output-Gigawords=0
Acct-Input-Gigawords=0
NAS-Port-Type=5
Calling-Station-Id=52:54:00:f5:63:ab
Called-Station-Id=52:54:00:2c:ee:28

12-01/16:51:52 DEBUG [rdsLstnr-p-4-t-3] ProcessorRequest - Sending to /192.168.100.1:58069
12-01/16:51:52 INFO [rdsLstnr-p-4-t-3] update - RESPONSE:
Packet type: Accounting-Response
Identifier: 3
Authenticator: {36 3C 90 29 26 39 79 99 37 A4 CC 45 F2 90 3D 3E}
Attributes:

Process time update: 8

12-01/16:52:29 INFO [rdsLstnr-p-4-t-4] RadiusListenerWorker - REQUEST:
Packet type: Accounting-Request
Identifier: 3
Authenticator: {13 90 6E BA 10 64 83 F1 81 C8 01 50 73 FD AC C4}
Attributes:
User-Name=user1
NAS-Identifier=m1_nas
NAS-IP-Address=192.168.100.1
NAS-Port=0
Service-Type=2
Framed-Protocol=1
Framed-IP-Address=192.168.200.108
Acct-Input-Octets=1327
Acct-Output-Octets=96
Acct-Status-Type=2
Acct-Session-Time=157
Acct-Input-Packets=13
Acct-Session-Id=c7711dfa845cebdd
Acct-Authentic=1
Acct-Terminate-Cause=1
NAS-Port-Id=ppp0
Acct-Output-Packets=6
Acct-Output-Gigawords=0
Acct-Input-Gigawords=0
NAS-Port-Type=5
Calling-Station-Id=52:54:00:f5:63:ab
Called-Station-Id=52:54:00:2c:ee:28

12-01/16:52:29 DEBUG [rdsLstnr-p-4-t-4] ProcessorRequest - Sending to /192.168.100.1:55432
12-01/16:52:29 INFO [rdsLstnr-p-4-t-4] RadiusListenerWorker - RESPONSE:
Packet type: Accounting-Response
Identifier: 3
Authenticator: {33 97 87 14 C1 84 82 03 A6 33 B8 78 1B F8 1C 71}
Attributes:

Process time stop: 3

12-01/16:52:44 DEBUG [setup-sched-p-1-t-1] RadiusProcessor - After clean old rad sessions: 0
12-01/16:54:29 DEBUG [setup-sched-p-1-t-2] RadiusProcessor - After clean old rad sessions: 0
12-01/16:56:14 DEBUG [setup-sched-p-1-t-2] RadiusProcessor - After clean old rad sessions: 0

[2015-12-01 16:49:25]: msg: accel-ppp version 28777b9b70377e47b037cb28351b47cc4f82854a
[2015-12-01 16:49:51]: info: : send [RADIUS(1) Access-Request id=1 <User-Name "user1"> <NAS-Identifier "m1_nas"> <NAS-IP-Address 192.168.100.1> <NAS-Port 4294967295> <NAS-Port-Id ""> <NAS-Port-Type Virtual> <Service-Type Framed-User> <Framed-Protocol PPP> <Calling-Station-Id "52:54:00:f5:63:ab"> <Called-Station-Id "52:54:00:2c:ee:28"> <CHAP-Challenge > <CHAP-Password >]
[2015-12-01 16:49:52]: info: : recv [RADIUS(1) Access-Accept id=1 <Acct-Interim-Interval 60> <Service-Type Framed-User> <Framed-Protocol PPP> <Framed-IP-Address 192.168.200.108>]
[2015-12-01 16:49:52]: info: ppp0: connect: ppp0 <--> pppoe(52:54:00:f5:63:ab)
[2015-12-01 16:49:52]: info: ppp0: user1: authentication succeeded
[2015-12-01 16:49:52]: info: ppp0: send [RADIUS(1) Accounting-Request id=1 <User-Name "user1"> <NAS-Identifier "m1_nas"> <NAS-IP-Address 192.168.100.1> <NAS-Port 0> <NAS-Port-Id "ppp0"> <NAS-Port-Type Virtual> <Service-Type Framed-User> <Framed-Protocol PPP> <Calling-Station-Id "52:54:00:f5:63:ab"> <Called-Station-Id "52:54:00:2c:ee:28"> <Acct-Status-Type Start> <Acct-Authentic RADIUS> <Acct-Session-Id "c7711dfa845cebdd"> <Acct-Session-Time 0> <Acct-Input-Octets 0> <Acct-Output-Octets 0> <Acct-Input-Packets 0> <Acct-Output-Packets 0> <Acct-Input-Gigawords 0> <Acct-Output-Gigawords 0> <Framed-IP-Address 192.168.200.108>]
[2015-12-01 16:49:52]: info: ppp0: recv [RADIUS(1) Accounting-Response id=1]
[2015-12-01 16:52:29]: info: ppp0: send [RADIUS(1) Accounting-Request id=3 <User-Name "user1"> <NAS-Identifier "m1_nas"> <NAS-IP-Address 192.168.100.1> <NAS-Port 0> <NAS-Port-Id "ppp0"> <NAS-Port-Type Virtual> <Service-Type Framed-User> <Framed-Protocol PPP> <Calling-Station-Id "52:54:00:f5:63:ab"> <Called-Station-Id "52:54:00:2c:ee:28"> <Acct-Status-Type Stop> <Acct-Authentic RADIUS> <Acct-Session-Id "c7711dfa845cebdd"> <Acct-Session-Time 157> <Acct-Input-Octets 1327> <Acct-Output-Octets 96> <Acct-Input-Packets 13> <Acct-Output-Packets 6> <Acct-Input-Gigawords 0> <Acct-Output-Gigawords 0> <Framed-IP-Address 192.168.200.108> <Acct-Terminate-Cause User-Request>]
[2015-12-01 16:52:29]: info: ppp0: recv [RADIUS(1) Accounting-Response id=3]
[2015-12-01 16:52:29]: info: ppp0: disconnected

Автор:	madvamp [ 25 ноя 2015, 11:13 ]
Заголовок сообщения:	Помогите, после обновления accel-pppd не появляются сессии
Обновил я accel-pppd на НАСе до текущего, конфиги теже самые остались (добавилась только секция с ipoe), и потом радиус перестао подхватывать сессии с accel-ppp. Причем сессии с fake pool, обрабатываются, их видно в radius.sh ps. А других нет. Аутентификация проходит нормально, даже реальный IP-адрес радиус выдает из пула, но запись в таблице log_session_201511 не создается. В логах ошибки вида. Код: 11-25/09:59:56 WARN [rdsLstnr-p-6-t-61] DialUpNas - Not found connection for update packet: Packet type: Accounting-Request Identifier: 114 Authenticator: {DE CC FA D3 77 3C 2B 05 70 1C FF 7D 4D 6D 7B 7C} Attributes: User-Name=zzzzzzzz NAS-Identifier=vpn1 NAS-IP-Address=10.77.3.6 NAS-Port=141 Service-Type=2 Framed-Protocol=1 Framed-IP-Address=91.232.171.92 Acct-Input-Octets=154 Acct-Output-Octets=24032 Acct-Status-Type=3 Acct-Session-Time=6784 Acct-Input-Packets=13 Acct-Session-Id=5aedc3f09bb6abfd Acct-Authentic=1 NAS-Port-Id=ppp141 Acct-Output-Packets=309 Acct-Output-Gigawords=0 Acct-Input-Gigawords=0 NAS-Port-Type=5 Calling-Station-Id=xx.xx.xx.xx Called-Station-Id=xx.xx.xx.xx Код: 11-25/10:02:11 ERROR [rdsLstnr-p-5-t-32] DialUpNasConnection - Stop without start! 11-25/10:02:11 INFO [rdsLstnr-p-6-t-80] update - REQUEST: Packet type: Accounting-Request Identifier: 23 Authenticator: {20 95 D0 D3 6D 90 3C 9D 3C CF 6F 9D 81 FF 16 A9} Код: 11-25/10:07:12 INFO [rdsLstnr-p-5-t-101] connections - [ 2577; xx; 22955 ] DialUpNASConnection stoppingConnection 11-25/10:07:12 INFO [rdsLstnr-p-5-t-101] connections - [ 2577; xxyy; 22955 ] DialUpNASConnection has stop Packet => false 11-25/10:07:13 INFO [rdsLstnr-p-6-t-45] connections - [ FAKE; xxzzz; 44486 ] DialUpNASConnection update connection.. 11-25/10:07:14 INFO [Thread-24] connections - [ FAKE; zziuu; 44493 ] Set status SUSPENDED on UpdateSuspendedSetter, time after last update: 1270451

Автор:	zavndw [ 25 ноя 2015, 17:59 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
какие нить менялись параметры? что в логе accel?

Автор:	Amir [ 25 ноя 2015, 18:09 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
Старт-пакеты от него приходят?

Автор:	madvamp [ 26 ноя 2015, 10:35 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
Параметры на accel, которые для радиуса + pptp не менялись, версию акцеля обновил с 1.2 до текущей 1.9. Ну судя по логам: Есть Access-Request/Access-Accept т.е аутентификация проходит. а вот а аккаунтингом беда: Есть Accounting-Request/Accounting-Response. Но в логах постоянные DialUpNas - Not found connection for update packet. А старт пакет в radius.log, как примерно выглядит, а то я в терминологии (в особенности русской переводной) немного путаюсь ?

Автор:	zavndw [ 26 ноя 2015, 11:19 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
Возможно надо поставить дефолтный конфиг с 1.9 и перенести параметры из 1.2. т.к это серьезный переход, должно помочь

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

Помогите, после обновления accel-pppd не появляются сессии http://forum.bitel.ru/viewtopic.php?f=5&t=11120	Страница 1 из 1

Автор:	madvamp [ 26 ноя 2015, 15:39 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
Сейчас посмотрел конфиги с такойже тестовой сборки (такоеже ядро+акцель 1.9), которая работает с ipoe, конфиг радиуса различается только строчкой с acct-timeout. В той которая с биллингом не работает acct-timeout=0. А в другой ее вообще нет. Из документация акцеля не очень поняно за что она отвечает. Может кто могет объяснить "на пальцах", за что он отвечает?

Автор:	zavndw [ 26 ноя 2015, 19:17 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
рвет все существующие соединения если радиус сервер недоступен либо ответил не сразу

Автор:	Amir [ 26 ноя 2015, 19:57 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
Цитата: Есть Accounting-Request/Accounting-Response. Но в логах постоянные DialUpNas - Not found connection for update packet. Должны быть с Acct-Status-Type=1.

Автор:	madvamp [ 28 ноя 2015, 11:30 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
Посмотрел в логах, в обоих случаях. Старт пакеты аккаунтинга есть. А bg радиус создает запись в таблице по старт пакету или по auth-accept?

Автор:	maxkr [ 01 дек 2015, 19:40 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
Уважаемые, так чем все закончилось???? Решили? Борюсь с такой-же проблемой и все бестолку... Всю голову уже сломал:( Acct-Status-Type=1 - присутствует, но вот чего в логах вываливается: 12-01/16:34:06 INFO [Thread-23] connections - [ ф-2015-12-0001; user1; 77964 ] Removing WAIT session, time after create: 168 12-01/16:34:06 INFO [Thread-23] connections - [ ф-2015-12-0001; user1; 77964 ] Dropping connection 12-01/16:34:06 INFO [Thread-23] connections - [ ф-2015-12-0001; user1; 77964 ] DialUpNASConnection stoppingConnection 12-01/16:34:06 INFO [Thread-23] connections - [ ф-2015-12-0001; user1; 77964 ] DialUpNASConnection has stop Packet => false radius 12-01/16:30:50 ERROR [rdsLstnr-p-3-t-2] DialUpNasConnection - Stop without start! radius 12-01/16:31:17 ERROR [rdsLstnr-p-3-t-3] DialUpNasConnection - Stop without start! processor 12-01/16:34:06 ERROR [Thread-23] DialUpNasConnection - Stop without start!

Автор:	Amir [ 01 дек 2015, 19:48 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
Нужен полный лог, что происходит, когда приходит пакет с Acct-Status-Type=1.

Автор:	maxkr [ 01 дек 2015, 19:59 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
Код: Клиент: вер. 6.0 сборка 1390 от 21.10.2015 16:04:34 os: Linux; java: Java HotSpot(TM) Server VM, v.1.7.0_80 ВНИМАНИЕ: Спецификация версии 1.7 не рекомендуется Сервер: вер. 6.0 сборка 1868 от 26.10.2015 16:04:29 os: Linux; java: Java HotSpot(TM) 64-Bit Server VM, v.1.7.0_80 ВНИМАНИЕ: Спецификация версии 1.7 не рекомендуется connection.log Код: 12-01/16:49:15 INFO [pool-3-thread-1] connections - Restore Connections NAS: M1_NAS 12-01/16:49:51 INFO [rdsLstnr-p-3-t-1] connections - [ ф-2015-12-0001; user1; 91866 ] Request for taking calculate period.. 12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] connections - [ ф-2015-12-0001; user1; 91866 ] Request period to script.. 12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] connections - [ ф-2015-12-0001; user1; 91866 ] Set start and end of month. 12-01/16:49:51 INFO [rdsLstnr-p-3-t-1] connections - [ ф-2015-12-0001; user1; 91866 ] calculatePeriodStart: 2015-12-01 16:49:51; calculatePeriodEnd: 2015-12-3 12-01/16:52:14 INFO [Thread-12] connections - [ ф-2015-12-0001; user1; 91866 ] Removing WAIT session, time after create: 143 12-01/16:52:14 INFO [Thread-12] connections - [ ф-2015-12-0001; user1; 91866 ] Dropping connection 12-01/16:52:14 INFO [Thread-12] connections - [ ф-2015-12-0001; user1; 91866 ] DialUpNASConnection stoppingConnection 12-01/16:52:14 INFO [Thread-12] connections - [ ф-2015-12-0001; user1; 91866 ] DialUpNASConnection has stop Packet => false error.log Код: processor 12-01/16:52:14 ERROR [Thread-12] DialUpNasConnection - Stop without start! processor.log Код: 12-01/16:49:14 INFO [main] NasList - Loading NAS list... 12-01/16:49:14 INFO [main] PodNasConnectionInspector - logCoa=false 12-01/16:49:14 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.inspectors.PodNasConnectionInspector$1 socket init ok. 12-01/16:49:14 DEBUG [main] Nas - activate services: [0] 12-01/16:49:14 INFO [main] processor - Starting zombi checker M1_NAS 12-01/16:49:14 INFO [main] processor - Starting wait remover timeout=120 M1_NAS 12-01/16:49:14 INFO [Thread-11] processor - Starting ZombiChecker for Nas id: M1_NAS; ip: 192.168.100.1 12-01/16:49:14 INFO [Thread-12] processor - Starting WaitRemover for Nas id: M1_NAS; ip: 192.168.100.1 12-01/16:49:14 INFO [main] processor - Starting connections month breaker M1_NAS 12-01/16:49:14 INFO [Thread-14] TariffOptionWatcher - Starting TariffOptionWatcher for Nas id: M1_NAS; ip: 192.168.100.1 12-01/16:49:14 INFO [main] NasList - LOADED NAS: Nas id: M1_NAS; ip: 192.168.100.1 CONFIG: callback.support=0 card.activate.service=0 drop.sleep.timeout=3600 month.break=1 nas.inspector.class=bitel.billing.server.processor.PoDNASConnectionInspector nas.inspector.coa.retries=10 nas.inspector.coa.threads=4 nas.inspector.coa.timeout=5 nas.inspector.kill.max_messages=5 nas.inspector.radius.attributes=User-Name;Framed-IP-Address;Acct-Session-Id;NAS-Identifier;NAS-IP-Address nas.inspector.radius.port=3799 nas.inspector.sleep_time=60 nas.port_time.default.=6 nas.port_traffic.default.=4:RADIN;5:RADOUT pppd.version=2.4.3 snmp.version=2 12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.network.radius.RadiusProcessor$1@265649cf to BG.Event.ru.bitel.bgbilling.kernel.even 12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.network.radius.RadiusProcessor$2@29e8ce6a to BG.Event.ru.bitel.bgbilling.modules.cal 12-01/16:49:14 INFO [main] DetailCompressRules - Session detail compress rules: 12-01/16:49:14 INFO [main] processor - Dynamic DNS init => false 12-01/16:49:15 INFO [main] processor - Connection count checker.. 12-01/16:49:15 INFO [main] processor - UPDATE mode SLEEP setter, timeout=30 12-01/16:49:15 INFO [main] DialUpRadiusProcessor - Restored 0/0 connections (100.00%) 12-01/16:49:15 INFO [main] DialUpRadiusProcessor - Restored 0/0 connections (100.00%) 12-01/16:49:15 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.contract.status.server.StatusCache$1@4ffcd6f to BG.Event.ru.bitel.bgbilling.kernel.e 12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$1@6b8a3955 to BG.Event.bitel.billing.server.dialup.bean 12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$2@300a3b6c to BG.Event.bitel.billing.server.dialup.bean 12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$3@2bad1914 to BG.Event.bitel.billing.server.call.bean.b 12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$4@4e452646 to BG.Event.bitel.billing.server.call.bean.b 12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$5@7fa81658 to BG.Event.bitel.billing.server.dialup.bean 12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$6@7eded5df to BG.Event.ru.bitel.bgbilling.kernel.event. 12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$7@3fdbfec9 to BG.Event.ru.bitel.bgbilling.kernel.event. 12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$8@d72f8f7 to BG.Event.ru.bitel.bgbilling.kernel.tariff. 12-01/16:49:15 DEBUG [main] EventProcessor - Add bitel.billing.server.processor.dialup.EventBusListener$9@fa08f61 to BG.Event.ru.bitel.bgbilling.kernel.tariff. 12-01/16:49:15 INFO [main] StaticAddressMonitor - Reload static addresses.. 12-01/16:49:34 INFO [Thread-13] processor - Starting ConnectionBreaker for: Nas id: M1_NAS; ip: 192.168.100.1 12-01/16:52:14 ERROR [Thread-12] DialUpNasConnection - Stop without start! radius.log Код: 12-01/16:49:10 INFO [main] DefaultServerSetup - Binding javax.jms.ConnectionFactory[org.apache.activemq.ActiveMQConnectionFactory@69a0aec1] to java:comp/env/m 12-01/16:49:10 INFO [main] DefaultServerSetup - Init DB connection pools 12-01/16:49:10 INFO [main] DefaultServerSetup - Binding JDBC pool "master" to java:comp/env/jdbc/master 12-01/16:49:10 INFO [main] AnnotatedMBean - Register MBean ru.bitel.bgbilling.server.util:type=DatabaseConnectionPool,name=master 12-01/16:49:10 INFO [main] DefaultServerSetup - Init trash pools.. 12-01/16:49:11 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.server.util.Setup$1@577a2815 to BG.Event.ru.bitel.bgbilling.kernel.event.events.system.Modu 12-01/16:49:11 INFO [main] DefaultServerSetup - Init trash pools.. 12-01/16:49:14 INFO [main] Radius - Starting radius auth_port:1812 acct_port:1813 admin_port:1955 12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.script.server.ScriptEventListener$1@6cae887c to BG.Event.ru.bitel.bgbilling.kernel.s 12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.script.server.DynamicScriptEventListener$1@64868d8 to BG.Event.ru.bitel.bgbilling.ke 12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.script.server.DynamicScriptEventListener$2@1c684684 to BG.Event.ru.bitel.bgbilling.k 12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.module.server.ModuleCache$1@7918fabc to BG.Event.ru.bitel.bgbilling.kernel.module.se 12-01/16:49:14 DEBUG [main] EventProcessor - Add ru.bitel.bgbilling.kernel.module.server.ModuleCache$2@3e55155c to BG.Event.ru.bitel.bgbilling.kernel.module.se 12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent. 12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent. 12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent. 12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent. 12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent. 12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent. 12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor@411fd5a3 to BG.LocalEvent. 12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor$1@31026921 to BG.LocalEven 12-01/16:49:14 DEBUG [main] LocalEventProcessor - Add listener ru.bitel.bgbilling.kernel.event.processors.CommonKernelEventProcessor$1@271ec5ce to BG.LocalEven 12-01/16:49:14 INFO [main] Radius - Init processor. <------>class: ru.bitel.bgbilling.modules.dialup.radius.DialUpRadiusProcessor <------>mid: 1 12-01/16:49:14 INFO [main] radius - Eap not enabled (keystore file not loaded). 12-01/16:49:15 INFO [main] Radius - Starting authentication listener... 12-01/16:49:15 INFO [main] Setup - Load config for mid=1 12-01/16:49:15 INFO [main] DatagramChannelListener - Open socket [0.0.0.0/0.0.0.0:1812] 12-01/16:49:15 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.RadiusListener socket init ok. 12-01/16:49:15 INFO [main] Radius - Starting accounting listener... 12-01/16:49:15 INFO [main] DatagramChannelListener - Open socket [0.0.0.0/0.0.0.0:1813] 12-01/16:49:15 INFO [main] DatagramChannelListener - ru.bitel.bgbilling.kernel.network.radius.RadiusListener socket init ok. 12-01/16:49:15 INFO [Thread-21] AdminPortListener - Starting AdminPortListener on 1955 12-01/16:49:51 INFO [rdsLstnr-p-3-t-1] RadiusListenerWorker - REQUEST: Packet type: Access-Request Identifier: 1 Authenticator: {61 A2 54 97 F3 39 FB 76 5F 89 78 32 50 56 AE 3B} Attributes: User-Name=user1 NAS-Port-Id= NAS-Identifier=m1_nas CHAP-Password={01 0C E2 56 2D 59 F6 3A E5 F8 BF 33 A3 72 6F 4D 52} NAS-IP-Address=192.168.100.1 NAS-Port=-1 Service-Type=2 Framed-Protocol=1 Calling-Station-Id=52:54:00:f5:63:ab NAS-Port-Type=5 CHAP-Challenge=a�T��9�v_�x2PV�; Called-Station-Id=52:54:00:2c:ee:28 Packet type: Access-Request Identifier: 1 Authenticator: {61 A2 54 97 F3 39 FB 76 5F 89 78 32 50 56 AE 3B} Attributes: User-Name=user1 NAS-Port-Id= NAS-Identifier=m1_nas CHAP-Password={01 0C E2 56 2D 59 F6 3A E5 F8 BF 33 A3 72 6F 4D 52} NAS-IP-Address=192.168.100.1 NAS-Port=-1 Service-Type=2 Framed-Protocol=1 Calling-Station-Id=52:54:00:f5:63:ab NAS-Port-Type=5 CHAP-Challenge=a�T��9�v_�x2PV�; Called-Station-Id=52:54:00:2c:ee:28 12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] RadiusProcessor - Create new radius session. 12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] AbstractRadiusProcessor - Finding login.. 12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] AbstractRadiusProcessor - Login found: 1 12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] AbstractRadiusProcessor - Checking access allow... 12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] AbstractRadiusProcessor - Checking password... 12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] AbstractRadiusProcessor - Checking contract status 12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] AbstractRadiusProcessor - Checking balance... 12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] ContractTariffOptionList - Create:. 12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] DialUpRadiusProcessor - Checking tariff... 12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] DialUpRadiusProcessor - Set address time: 0 12-01/16:49:51 DEBUG [rdsLstnr-p-3-t-1] ProcessorRequest - Sending to /192.168.100.1:43233 12-01/16:49:51 INFO [rdsLstnr-p-3-t-1] RadiusListenerWorker - RESPONSE: Packet type: Access-Accept Identifier: 1 Authenticator: {92 A7 70 0F 66 57 97 6F 3D AC 4A 00 E1 94 86 86} Attributes: Acct-Interim-Interval=60 Service-Type=2 Framed-Protocol=1 Framed-IP-Address=192.168.200.108 Process time auth: 186 12-01/16:49:52 INFO [rdsLstnr-p-4-t-1] RadiusListenerWorker - REQUEST: Packet type: Accounting-Request Identifier: 1 Authenticator: {4F 19 B7 49 BB DB 68 3A 6F 90 FF D8 73 69 27 EB} Attributes: User-Name=user1 NAS-Identifier=m1_nas NAS-IP-Address=192.168.100.1 NAS-Port=0 Service-Type=2 Framed-IP-Address=192.168.200.108 Acct-Input-Octets=0 Acct-Output-Octets=0 Acct-Status-Type=1 Acct-Session-Time=0 Acct-Input-Packets=0 Acct-Session-Id=c7711dfa845cebdd Acct-Authentic=1 NAS-Port-Id=ppp0 Acct-Output-Packets=0 Acct-Output-Gigawords=0 Acct-Input-Gigawords=0 NAS-Port-Type=5 Calling-Station-Id=52:54:00:f5:63:ab Called-Station-Id=52:54:00:2c:ee:28 12-01/16:49:52 DEBUG [rdsLstnr-p-4-t-1] ProcessorRequest - Sending to /192.168.100.1:33046 12-01/16:49:52 INFO [rdsLstnr-p-4-t-1] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 1 Authenticator: {F8 96 B8 E3 FD 42 09 0C C4 2D EF 4A 30 F3 11 F1} Attributes: Process time start: 5 12-01/16:50:52 INFO [rdsLstnr-p-4-t-2] update - REQUEST: Packet type: Accounting-Request Identifier: 2 Authenticator: {09 88 52 2D CB 01 43 4D 66 E2 29 D7 B8 D1 5D 90} Attributes: User-Name=user1 NAS-Identifier=m1_nas NAS-IP-Address=192.168.100.1 NAS-Port=0 Service-Type=2 Framed-Protocol=1 Framed-IP-Address=192.168.200.108 Acct-Input-Octets=1327 Acct-Output-Octets=96 Acct-Status-Type=3 Acct-Session-Time=60 Acct-Input-Packets=13 Acct-Session-Id=c7711dfa845cebdd Acct-Authentic=1 NAS-Port-Id=ppp0 Acct-Output-Packets=6 Acct-Output-Gigawords=0 Acct-Input-Gigawords=0 NAS-Port-Type=5 Calling-Station-Id=52:54:00:f5:63:ab Called-Station-Id=52:54:00:2c:ee:28 12-01/16:50:52 WARN [rdsLstnr-p-4-t-2] DialUpNas - Not found connection for update packet:. Packet type: Accounting-Request Identifier: 2 Authenticator: {09 88 52 2D CB 01 43 4D 66 E2 29 D7 B8 D1 5D 90} Attributes: User-Name=user1 NAS-Identifier=m1_nas NAS-IP-Address=192.168.100.1 NAS-Port=0 Service-Type=2 Framed-Protocol=1 Framed-IP-Address=192.168.200.108 Acct-Input-Octets=1327 Acct-Output-Octets=96 Acct-Status-Type=3 Acct-Session-Time=60 Acct-Input-Packets=13 Acct-Session-Id=c7711dfa845cebdd Acct-Authentic=1 NAS-Port-Id=ppp0 Acct-Output-Packets=6 Acct-Output-Gigawords=0 Acct-Input-Gigawords=0 NAS-Port-Type=5 Calling-Station-Id=52:54:00:f5:63:ab Called-Station-Id=52:54:00:2c:ee:28 12-01/16:50:52 DEBUG [rdsLstnr-p-4-t-2] ProcessorRequest - Sending to /192.168.100.1:42792 12-01/16:50:52 INFO [rdsLstnr-p-4-t-2] update - RESPONSE: Packet type: Accounting-Response Identifier: 2 Authenticator: {7C 28 3E 41 19 31 93 7C 62 A6 A4 64 CD 1D BF 22} Attributes: Process time update: 7 12-01/16:50:59 DEBUG [setup-sched-p-1-t-1] RadiusProcessor - After clean old rad sessions: 0 12-01/16:51:52 INFO [rdsLstnr-p-4-t-3] update - REQUEST: Packet type: Accounting-Request Identifier: 3 Authenticator: {92 05 93 58 11 E8 2E B3 80 C2 16 30 42 ED 7D 26} Attributes: User-Name=user1 NAS-Identifier=m1_nas NAS-IP-Address=192.168.100.1 NAS-Port=0 Service-Type=2 Framed-Protocol=1 Framed-IP-Address=192.168.200.108 Acct-Input-Octets=1327 Acct-Output-Octets=96 Acct-Status-Type=3 Acct-Session-Time=120 Acct-Input-Packets=13 Acct-Session-Id=c7711dfa845cebdd Acct-Authentic=1 NAS-Port-Id=ppp0 Acct-Output-Packets=6 Acct-Output-Gigawords=0 Acct-Input-Gigawords=0 NAS-Port-Type=5 Calling-Station-Id=52:54:00:f5:63:ab Called-Station-Id=52:54:00:2c:ee:28 12-01/16:51:52 WARN [rdsLstnr-p-4-t-3] DialUpNas - Not found connection for update packet:. Packet type: Accounting-Request Identifier: 3 Authenticator: {92 05 93 58 11 E8 2E B3 80 C2 16 30 42 ED 7D 26} Attributes: User-Name=user1 NAS-Identifier=m1_nas NAS-IP-Address=192.168.100.1 NAS-Port=0 Service-Type=2 Framed-Protocol=1 Framed-IP-Address=192.168.200.108 Acct-Input-Octets=1327 Acct-Output-Octets=96 Acct-Status-Type=3 Acct-Session-Time=120 Acct-Input-Packets=13 Acct-Session-Id=c7711dfa845cebdd Acct-Authentic=1 NAS-Port-Id=ppp0 Acct-Output-Packets=6 Acct-Output-Gigawords=0 Acct-Input-Gigawords=0 NAS-Port-Type=5 Calling-Station-Id=52:54:00:f5:63:ab Called-Station-Id=52:54:00:2c:ee:28 12-01/16:51:52 DEBUG [rdsLstnr-p-4-t-3] ProcessorRequest - Sending to /192.168.100.1:58069 12-01/16:51:52 INFO [rdsLstnr-p-4-t-3] update - RESPONSE: Packet type: Accounting-Response Identifier: 3 Authenticator: {36 3C 90 29 26 39 79 99 37 A4 CC 45 F2 90 3D 3E} Attributes: Process time update: 8 12-01/16:52:29 INFO [rdsLstnr-p-4-t-4] RadiusListenerWorker - REQUEST: Packet type: Accounting-Request Identifier: 3 Authenticator: {13 90 6E BA 10 64 83 F1 81 C8 01 50 73 FD AC C4} Attributes: User-Name=user1 NAS-Identifier=m1_nas NAS-IP-Address=192.168.100.1 NAS-Port=0 Service-Type=2 Framed-Protocol=1 Framed-IP-Address=192.168.200.108 Acct-Input-Octets=1327 Acct-Output-Octets=96 Acct-Status-Type=2 Acct-Session-Time=157 Acct-Input-Packets=13 Acct-Session-Id=c7711dfa845cebdd Acct-Authentic=1 Acct-Terminate-Cause=1 NAS-Port-Id=ppp0 Acct-Output-Packets=6 Acct-Output-Gigawords=0 Acct-Input-Gigawords=0 NAS-Port-Type=5 Calling-Station-Id=52:54:00:f5:63:ab Called-Station-Id=52:54:00:2c:ee:28 12-01/16:52:29 DEBUG [rdsLstnr-p-4-t-4] ProcessorRequest - Sending to /192.168.100.1:55432 12-01/16:52:29 INFO [rdsLstnr-p-4-t-4] RadiusListenerWorker - RESPONSE: Packet type: Accounting-Response Identifier: 3 Authenticator: {33 97 87 14 C1 84 82 03 A6 33 B8 78 1B F8 1C 71} Attributes: Process time stop: 3 12-01/16:52:44 DEBUG [setup-sched-p-1-t-1] RadiusProcessor - After clean old rad sessions: 0 12-01/16:54:29 DEBUG [setup-sched-p-1-t-2] RadiusProcessor - After clean old rad sessions: 0 12-01/16:56:14 DEBUG [setup-sched-p-1-t-2] RadiusProcessor - After clean old rad sessions: 0

Автор:	Amir [ 01 дек 2015, 20:10 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
Модуль Dialup довольно старый и идентифицирует сессии по атрибуту Nas-Port. В данном случае от accel-pppd похоже приходят не корректные значения Nas-Port - во первых, разные в Access-Request и Accounting-Request, во вторых, возможно одинаково для всех сессий - 0. Смотреть настройки accel-pppd или вернуться на предыдущую версию accel-pppd, в которой Nas-Port передавался корректно. В модуле Inet сессии идентифицируются по атрибуту Acct-Session-Id.

Автор:	nik247 [ 01 дек 2015, 20:20 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
Попробуте поискать ответ здесь: http://accel-ppp.org/forum/viewtopic.php?f=11&t=462

Страница 1 из 1	Часовой пояс: UTC + 5 часов [ Летнее время ]
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/

Автор:	maxkr [ 01 дек 2015, 20:26 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
Попробую поставить аксель постарее:) Проверял на нескольких одновременных сессиях с разных виндовых клиентов - номера портов выдает разные но последовательно (0,1 и т.д.) А вот кусок из акселя: Код: [2015-12-01 16:49:25]: msg: accel-ppp version 28777b9b70377e47b037cb28351b47cc4f82854a [2015-12-01 16:49:51]: info: : send [RADIUS(1) Access-Request id=1 <User-Name "user1"> <NAS-Identifier "m1_nas"> <NAS-IP-Address 192.168.100.1> <NAS-Port 4294967295> <NAS-Port-Id ""> <NAS-Port-Type Virtual> <Service-Type Framed-User> <Framed-Protocol PPP> <Calling-Station-Id "52:54:00:f5:63:ab"> <Called-Station-Id "52:54:00:2c:ee:28"> <CHAP-Challenge > <CHAP-Password >] [2015-12-01 16:49:52]: info: : recv [RADIUS(1) Access-Accept id=1 <Acct-Interim-Interval 60> <Service-Type Framed-User> <Framed-Protocol PPP> <Framed-IP-Address 192.168.200.108>] [2015-12-01 16:49:52]: info: ppp0: connect: ppp0 <--> pppoe(52:54:00:f5:63:ab) [2015-12-01 16:49:52]: info: ppp0: user1: authentication succeeded [2015-12-01 16:49:52]: info: ppp0: send [RADIUS(1) Accounting-Request id=1 <User-Name "user1"> <NAS-Identifier "m1_nas"> <NAS-IP-Address 192.168.100.1> <NAS-Port 0> <NAS-Port-Id "ppp0"> <NAS-Port-Type Virtual> <Service-Type Framed-User> <Framed-Protocol PPP> <Calling-Station-Id "52:54:00:f5:63:ab"> <Called-Station-Id "52:54:00:2c:ee:28"> <Acct-Status-Type Start> <Acct-Authentic RADIUS> <Acct-Session-Id "c7711dfa845cebdd"> <Acct-Session-Time 0> <Acct-Input-Octets 0> <Acct-Output-Octets 0> <Acct-Input-Packets 0> <Acct-Output-Packets 0> <Acct-Input-Gigawords 0> <Acct-Output-Gigawords 0> <Framed-IP-Address 192.168.200.108>] [2015-12-01 16:49:52]: info: ppp0: recv [RADIUS(1) Accounting-Response id=1] [2015-12-01 16:52:29]: info: ppp0: send [RADIUS(1) Accounting-Request id=3 <User-Name "user1"> <NAS-Identifier "m1_nas"> <NAS-IP-Address 192.168.100.1> <NAS-Port 0> <NAS-Port-Id "ppp0"> <NAS-Port-Type Virtual> <Service-Type Framed-User> <Framed-Protocol PPP> <Calling-Station-Id "52:54:00:f5:63:ab"> <Called-Station-Id "52:54:00:2c:ee:28"> <Acct-Status-Type Stop> <Acct-Authentic RADIUS> <Acct-Session-Id "c7711dfa845cebdd"> <Acct-Session-Time 157> <Acct-Input-Octets 1327> <Acct-Output-Octets 96> <Acct-Input-Packets 13> <Acct-Output-Packets 6> <Acct-Input-Gigawords 0> <Acct-Output-Gigawords 0> <Framed-IP-Address 192.168.200.108> <Acct-Terminate-Cause User-Request>] [2015-12-01 16:52:29]: info: ppp0: recv [RADIUS(1) Accounting-Response id=3] [2015-12-01 16:52:29]: info: ppp0: disconnected NAS-Port 4294967295 в access-request'е, а в логах радиуса NAS-Port=-1.... А уже в Accounting-Request 0...

Автор:	maxkr [ 01 дек 2015, 20:31 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
nik247 писал(а): Попробуте поискать ответ здесь: http://accel-ppp.org/forum/viewtopic.php?f=11&t=462 Ну, собственно, что и требовалось... Спасибо

Автор:	nik247 [ 01 дек 2015, 20:33 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
maxkr писал(а): nik247 писал(а): Попробуте поискать ответ здесь: http://accel-ppp.org/forum/viewtopic.php?f=11&t=462 Ну, собственно, что и требовалось... Спасибо Я там свое решение описал для 6.0 Inet.

Автор:	Amir [ 01 дек 2015, 21:11 ]
Заголовок сообщения:	Re: Помогите, после обновления accel-pppd не появляются сесс
Inet 6.0 Nas-Port ждет в RADIUS-Accounting, но насколько помню, если его не будет в Access-Request - то не проблема. C Inet 6.1 Nas-Port не обязателен и в RADIUS-Accounting.