Hotspot (mikrotik) не считает время

Технические вопросы по UTM 5.0
Ответить
MadMike
Сообщения: 230
Зарегистрирован: Чт май 05, 2005 07:02

Hotspot (mikrotik) не считает время

Сообщение MadMike »

Version:5.2.1-005-rhel5
Mikrotik 3.2

Поставил по статье http://www.netup.ru/UTM5/articles.php?n=4

Вариант с веб-интерфейсом UTM работает.
Вариант с микротик - микротик с радиусом завязался, карточки сгенерированные ест, но почему то не учитывает время? по interim передает сколько байт пришло/ушло к клиенту, а на время забивает, хотя в услуге цена за час указана.

вот лог радиуса при вводе карточки в веб-интерфейсе микротика. По нему видно что радиус микротику не передает никакого Calculated maximum session time не передает.
Может какую опцию нужно указать в конфигах или микротике?

Код: Выделить всё

?Debug &#58; Mar 07 18&#58;42&#58;25 RADIUS DBA&#58; NAS found. Data size <0>                        
?Debug &#58; Mar 07 18&#58;42&#58;25 AcctServer&#58; Acct packet with session ID&#58; 8020001b           
?Debug &#58; Mar 07 18&#58;42&#58;25 RADIUS DBA&#58; NAS found. Data size <0>                        
?Debug &#58; Mar 07 18&#58;42&#58;25 AcctServer&#58; Acct-Start packet                               
?Debug &#58; Mar 07 18&#58;42&#58;25 AcctServer&#58; Acct-Start&#58; User <329>                          
?Debug &#58; Mar 07 18&#58;42&#58;25 AcctServer&#58; Acct-Session-Time &#40;46&#41; not present in accounting packet. 
?Debug &#58; Mar 07 18&#58;42&#58;25 AcctServer&#58; No h323-setup-time &#40;9, 25&#41; attribute in accountig start packet. Setting to NOW <1267965745>!                                                                                                                           
 ERROR &#58; Mar 07 18&#58;42&#58;25 RADIUS DBA&#58; Can't find login <329>                                                                   
?Debug &#58; Mar 07 18&#58;42&#58;25 RADIUS DBA&#58; Searching card login <000000329>                                                         
?Debug &#58; Mar 07 18&#58;42&#58;25 RADIUS DBA&#58; Info for login <329> found. type <5>                                                     
?Debug &#58; Mar 07 18&#58;42&#58;25 RADIUS DBA&#58; login_store iter->second.hotspot.session_count&#58;0                                         
?Debug &#58; Mar 07 18&#58;42&#58;25 RADIUS DBA&#58; info for user found. type <5> info addr <152619432>                                      
?Debug &#58; Mar 07 18&#58;42&#58;25 RADIUS DBA&#58; search_user_info return info <152619432>                                                 
?Debug &#58; Mar 07 18&#58;42&#58;25 RADIUS DBA&#58; search_user_info return valid info                                                       
?Debug &#58; Mar 07 18&#58;42&#58;25 RADIUS DBA&#58; Setting interim interval <61> for session id <8020001b>                                  
?Debug &#58; Mar 07 18&#58;42&#58;25 RADIUS DBA&#58; Calling send_session_log_init_sync ...                                                   
?Debug &#58; Mar 07 18&#58;42&#58;25 RADIUS Stream&#91;plugin&#93;&#58; send_session_log_init_sync                                                    
?Debug &#58; Mar 07 18&#58;42&#58;25 RADIUS Stream&#91;plugin&#93;&#58; init log id <10>                                                              
?Debug &#58; Mar 07 18&#58;42&#58;25 AcctServer&#58; Reply packet dump&#58; RPacket&#58;                                                              
Code&#58; 5; ID&#58; 89                                                                                                               

?Debug &#58; Mar 07 18&#58;42&#58;25 RadiusSocket&#58; Moving RADIUS packet into send queue
?Debug &#58; Mar 07 18&#58;42&#58;25 AcctServer&#58; Next...                               
?Debug &#58; Mar 07 18&#58;42&#58;25 RadiusSocket&#58; Waiting for RADIUS raw data         
?Debug &#58; Mar 07 18&#58;42&#58;25 RadiusSocket&#58; RADIUS raw data sent                
?Debug &#58; Mar 07 18&#58;42&#58;25 RADIUS Stream&#91;plugin&#93;&#58; Ping reply received        
?Debug &#58; Mar 07 18&#58;42&#58;30 RADIUS Stream&#91;plugin&#93;&#58; Ping reply received        
?Debug &#58; Mar 07 18&#58;42&#58;35 RADIUS Stream&#91;plugin&#93;&#58; Ping reply received 
и настройки Mikrotik

Код: Выделить всё

&#91;admin@MikroTik&#93; > ip hotspot profile print
Flags&#58; * - default
 0 * name="default" hotspot-address=0.0.0.0 dns-name="" html-directory=hotspot rate-limit="" http-proxy=0.0.0.0&#58;0
     smtp-server=0.0.0.0 login-by=cookie,http-chap http-cookie-lifetime=3d split-user-domain=no use-radius=no

 1   name="hsprof1" hotspot-address=10.0.0.1 dns-name="10.0.0.1" html-directory=hotspot rate-limit="" http-proxy=0.0.0.0&#58;0
     smtp-server=0.0.0.0 login-by=cookie,http-chap http-cookie-lifetime=3d split-user-domain=no use-radius=yes
     radius-accounting=yes radius-interim-update=1m nas-port-type=wireless-802.11 radius-default-domain=""
     radius-location-id="" radius-location-name="" radius-mac-format=XX&#58;XX&#58;XX&#58;XX&#58;XX&#58;XX
&#91;admin@MikroTik&#93; > ip hotspot print
Flags&#58; X - disabled, I - invalid, S - HTTPS
 #   NAME                   INTERFACE                   ADDRESS-POOL                   PROFILE                   IDLE-TIMEOUT
 0   hotspot1               ether2                      dhcp-pool-1                    hsprof1                   5m
&#91;admin@MikroTik&#93; >
Может у кого есть предположения какие?

MadMike
Сообщения: 230
Зарегистрирован: Чт май 05, 2005 07:02

Сообщение MadMike »

поставил UTM5.2.1-006 Centos - тоже самое.

Попробовал в качестве НАСа использовать AP Planet WSG-402

радиус вроде разрешает

Код: Выделить всё

 ERROR &#58; Mar 09 16&#58;36&#58;08 RADIUS DBA&#58; Can't find login <4>
?Debug &#58; Mar 09 16&#58;36&#58;08 RADIUS DBA&#58; Searching card login <000000004>
?Debug &#58; Mar 09 16&#58;36&#58;08 RADIUS DBA&#58; Info for login <4> found. type <5>
?Debug &#58; Mar 09 16&#58;36&#58;08 RADIUS DBA&#58; login_store iter->second.hotspot.session_count&#58;0
 Info  &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; User <4> added.
?Debug &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; Auth scheme&#58; PAP
?Debug &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; PAP&#58; <42697647> vs <42697647>
?Debug &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; PAP&#58; Authorized user <4>
?Debug &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; User from 2.0.168.192
?Debug &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; Checking c0a80002&#58; c0a80000/ffffff00
?Debug &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; Hotspot session limit&#58;0 session count&#58;0 for user&#58;4
?Debug &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; Calculated maximum recv limit&#58; -1
?Debug &#58; Mar 09 16&#58;36&#58;08 RADIUS DBA&#58; hotspot_link_update called for slink&#58;4
?Debug &#58; Mar 09 16&#58;36&#58;08 RADIUS DBA&#58; soft hotspot_link_update for slink&#58;4 session_count&#58;1
?Debug &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; Calling fill radius attributes for service. Attr storage size <0>
?Debug &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; Calling fill radius attributes for slink. Attr storage size <0>
?Debug &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; Calling fill radius attributes for NAS. Attr storage size <0>
 Notice&#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; Login OK <4> from NAS <192.168.5.43> CLID <00-30-4F-41-03-B2> Calling-station <00-06-5B-D5-2E-93>
?Debug &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; Setting interim update interval from config
?Debug &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; Auth reply&#58; RPacket&#58;
Code&#58; 2; ID&#58; 2

?Debug &#58; Mar 09 16&#58;36&#58;08 RADIUS Packet&#58; raw data constructed! size <20>
?Debug &#58; Mar 09 16&#58;36&#58;08 RadiusSocket&#58; Moving RADIUS packet into send queue
?Debug &#58; Mar 09 16&#58;36&#58;08 RadiusSocket&#58; RADIUS raw data sent
?Debug &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; Next...
?Trace &#58; Mar 09 16&#58;36&#58;08 AuthServer&#58; Process loop step
?Debug &#58; Mar 09 16&#58;36&#58;08 RadiusSocket&#58; Waiting for RADIUS raw data
Но Ап выдает в веб-интерфейс "No session timeout reply" - видать ругается нне получая разрешенного времени работы клиента от радиус.

Подозреваю таки UMT в этих приколах...

Ответить