Две сессии одновременно под одним логином

Технические вопросы по UTM 5.0
olegnv
Сообщения: 53
Зарегистрирован: Чт сен 08, 2011 07:48

Две сессии одновременно под одним логином

Сообщение olegnv »

Сегодня столкнулся с такой вещью:
Человек подключается по pppoe, входит в сеть, интернет работает. В другом месте включается роутер, где соединение настроено на используемый логин и подключается к интернету. Если подключен только роутер, то подключение с рабочей станции по pppoe не происходит.
Полноценной работу не назовешь, не всегда страницы сразу открываются.
С другими логинами пока не проверял, но с этим ситуация воспроизводится.

Разве такое поведение нормально для UTM5? У нас 5.2.1-008 release.
Как с этим бороться?

gtk
Сообщения: 232
Зарегистрирован: Пт янв 21, 2005 18:33

Сообщение gtk »

Вам, что нужно? чтобы работало две сессии под одним логином или наоборот? не нужно?

olegnv
Сообщения: 53
Зарегистрирован: Чт сен 08, 2011 07:48

Сообщение olegnv »

gtk писал(а):Вам, что нужно? чтобы работало две сессии под одним логином или наоборот? не нужно?
Не нужно.

gtk
Сообщения: 232
Зарегистрирован: Пт янв 21, 2005 18:33

Сообщение gtk »

конфиг радиуса можете показать?

ekex
Сообщения: 42
Зарегистрирован: Вт май 05, 2009 11:54

Сообщение ekex »

olegnv писал(а): Не нужно.
Копайте в сторону "разрешенные CID"

gtk
Сообщения: 232
Зарегистрирован: Пт янв 21, 2005 18:33

Сообщение gtk »

ekex писал(а):
olegnv писал(а): Не нужно.
Копайте в сторону "разрешенные CID"
Офигительно, а если >20k всем сиды прописывать?

ekex
Сообщения: 42
Зарегистрирован: Вт май 05, 2009 11:54

Сообщение ekex »

gtk писал(а):Офигительно, а если >20k всем сиды прописывать?
ага... штатный радиус не умеет запрещать повторную авторизацию с тем же логином

gtk
Сообщения: 232
Зарегистрирован: Пт янв 21, 2005 18:33

Сообщение gtk »

ekex писал(а):
gtk писал(а):Офигительно, а если >20k всем сиды прописывать?
ага... штатный радиус не умеет запрещать повторную авторизацию с тем же логином
вы ошибаетесь.

Топик Стартер, скорее всего менял дефолтные значения в конфиге.

ekex
Сообщения: 42
Зарегистрирован: Вт май 05, 2009 11:54

Сообщение ekex »

gtk писал(а): вы ошибаетесь.

Топик Стартер, скорее всего менял дефолтные значения в конфиге.
ок, покажите мне в конфиге(дефолтном) радиуса это волшебное значение

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

##
## /netup/utm5/radius5.cfg
## UTM5 RADIUS server configuration file
##

## =============================================================================
## MAIN RADIUS SERVER PARAMETERS
## =============================================================================

## core_host
##  Description: IP address of a host running the utm5_core
##  Possible values: an IP address
##  Required field.
core_host=127.0.0.1

## core_port
##  Description: UTM5 core listening port. Equal to stream_bind_port parameter
##   in utm5.cfg.
##  Possible values: an integer from 1 to 65534
##  Required field.
core_port=12758

## radius_login
##  Description: A system user login to access the UTM5 core.
##  Possible values&#58; <string>
##  Default value&#58; radius

## radius_password
##  Description&#58; A system user password to access the UTM5 core.
##  Possible values&#58; <string>
##  Default value&#58; radius

## radius_ssl_type
##  Description&#58; SSL connection type. If 'none' is set, the connection
##   is unencrypted.
##  Possible values&#58; tls1, ssl3, none
##  Default value&#58; none
#radius_ssl_type=none

## radius_acct_host
##  Description&#58; IP address of the host receiving Accounting-Requests.
##  Possible values&#58; interface IP address or 0.0.0.0
##  Default value&#58; 0.0.0.0

## radius_acct_port
##  Description&#58; Port of the host receiving Accounting-Requests.
##  Possible values&#58; an integer from 1 to 65534
##  Default value&#58; 1813

## radius_auth_host
##  Description&#58; IP address of the host receiving Access-Requests.
##  Possible values&#58; interface IP address or 0.0.0.0
##  Default value&#58; 0.0.0.0

## radius_auth_port
##  Description&#58; Port of the host receiving Access-Requests.
##  Possible values&#58; an integer from 1 to 65534
##  Default value&#58; 1812

## radius_auth_mppe
##  Description&#58; Enables MPPE 128 bit key generation used for authorization
##   via MS-CHAP-v2 protocol.
##  Possible values&#58; enable
##  Default value&#58; the keys are not generated
radius_auth_mppe=enable

## radius_auth_vap
##  Description&#58; If the value is set, authorization of blocked users, whose
##   logins are set in IP traffic service link, is disallowed.
##  Possible values&#58; 1
##  Default value&#58; authorization is allowed

## radius_ippool_acct_timeout
##  Description&#58; A time interval during which the IP address is labeled as
##   occupied after sending Access-Accept.
##  Possible values&#58; time in seconds 
##  Default value&#58; 30

## radius_ippool_timeout
##  Description&#58; A time interval during which the IP address is labeled as
##   occupied after receiving Accounting-Start.
##  Possible values&#58; time in seconds
##  Default value&#58; The address is labeled as occupied until coming of the
##   Stop packet

## radius_auth_null
##  Description&#58; If enabled, the RADIUS server authorizes requests without
##   User-Password&#40;2&#41; attribute, if the user's password, defined in the
##   service link, is empty.
##  Possible values&#58; yes, enable
##  Default value&#58; authorization without a password is not performed
#radius_auth_null=yes

## radius_auth_h323_remote_address
##  Description&#58; If enabled, then telephone calls authentication is performed
##   using h323-remote-address&#40;9;23&#41; attribute value, but not using
##   User-Name&#40;1&#41; attribute. The attribute value is used as a login.
##  Possible values&#58; enable, on, yes
##  Default value&#58; replacement of login with h323-remote-address is not
##   performed

## radius_nas_port_vpn
##  Description&#58; This parameter is checked against NAS-Port-Type&#40;61&#41; attribute
##   value when connecting using the login specified in the IP traffic service
##   link. Several values can be set.
##  Possible values&#58; a positive integer
##  Default value&#58; Checking against NAS-Port-Type for the IP traffic service
##   link is not performed

## radius_nas_port_dialup
##  Description&#58; This parameter is checked against NAS-Port-Type&#40;61&#41; attribute
##   value when connecting using the login specified in the Dial-up service
##   link. Several values can be set.
##  Possible values&#58; a positive integer
##  Default value&#58; checking against NAS-Port-Type for the Dial-up service link
##   is not performed

## radius_nas_port_tel
##  Description&#58; This parameter is checked against NAS-Port-Type&#40;61&#41; attribute
##   value when connecting using the login specified in the Telephony service
##   link. Several values can be set.
##  Possible values&#58; a positive integer
##  Default value&#58; checking against NAS-Port-Type for the Telephony service
##   link is not performed

## radius_card_autoadd
##  Description&#58; If 'yes' is set, the automatic registration of users is
##   enabled via the RADIUS server using prepaid cards. In this case in the
##   Login field a user enters the card number and in the Password field - the
##   PIN code. In case of the Telephony service, in the Login field it is
##   entered the PIN code or its first part and the remainder is used as a
##   password.

##  Possible values&#58; yes, on, enable
##  Default value&#58; automatic registration is not performed
radius_card_autoadd=yes

## send_xpgk_ep_number
##  Description&#58; If this option is enabled, for the Telephony service, when a
##   user is being authorized, in Access-Accept it is transmitted the
##   Cisco-AVPair&#40;9;1&#41; attribute with the value&#58;
##   xpgk-ep-number=<a semicolon separated list of telephone numbers>.
##  Possible values&#58; <any>
##  Default value&#58; telephone numbers are not transmitted in affirmative replies
##   to authorization requests

## send_h323_ivr_in
##  Description&#58; If this option is enabled, for the Telephony service, when a
##   user is being authorized, in Access-Accept it is transmitted the
##   Cisco-AVPair&#40;9;1&#41; attribute with the value&#58; h323-ivr-in=terminal-alias&#58;
##   <a semicolon separated list of telephone numbers>.
##  Possible values&#58; <any>
##  Default value&#58; telephone numbers are not transmitted in affirmative replies
##   to authorization requests

## enable_fast_telephony
##  Description&#58; This option enables the rapid mechanism for determination of
##   directions and zones when rating telephone calls. In this case templates
##   for telephone directions must contain the digits from 0 to 9 and the
##   symbols&#58; ^ $ + &#41;&#40; |.
##  Possible values&#58; enable, yes
##  Default value&#58; the default mechanism for determination of zone/direction
##   is used

## h323_origin_reject
##  Description&#58; Sets zero cost for Accounting-Requests in which the
##   h323-call-origin&#40;9;26&#41; attribute equals the value of this parameter.
##  Possible values&#58; <string>
##  Default value&#58; unset
#h323_origin_reject=originate &#123;answer|callback|etc&#125;

## interim_update_interval
##  Description&#58; Enables session control mechanism using Interim-Update
##   packets. The value is transmitted in the Acct-Interim-Interval&#40;85&#41;
##   attribute of the Access-Accept packet.
##  Possible values&#58; time in seconds, more than 61
##  Default value&#58; the default session closure control mechanism is used

## radius_default_session_timeout
##  Description&#58; A value of the Session-Timeout&#40;27&#41; attribute transmitted in
##   Access-Accept for the IP traffic service link.
##  Possible values&#58; a positive integer
##  Default value&#58; 86400

## radius_callback_avpair_enable
##  Description&#58; Enables transmission of the Cisco-AVPair&#40;9;1&#41; attribute with
##   the value lcp&#58;callback-dialstring=<callback number>, where
##   <callback number> is the part of the login from the beginning to the
##   '&#58;'-symbol.
##  Possible values&#58; <any>
##  Default value&#58; unset

## radius_acct_rewrite_login_answer
##  Description&#58; If the value of the h323-call-origin&#40;9;26&#41; attribute is
##   'originate', then setting this parameter enables replacing of the login
##   with the value of the h323-remote-address&#40;9;23&#41; attribute when processing
##   Accounting-Request packets.
##  Possible values&#58; enable, on, true
##  Default value&#58; unset

## radius_acct_rewrite_login_originate
##  Description&#58; If the value of the h323-call-origin&#40;9;26&#41; attribute is
##   'answer', then setting this parameter enables replacing of the login with
##   the value of the h323-remote-address&#40;9;23&#41; attribute when processing
##   Accounting-Request packets.
##  Possible values&#58; enable, on, true
##  Default value&#58; unset

## =============================================================================
## LOGGING &#40;valid if logfile rotation is enabled&#41;
## =============================================================================

## log_level
##  Description&#58; Logging level.
##  Possible values&#58; 0, 1, 2, 3
##  Default value&#58; 1

## log_file_main
##  Description&#58; Main logfile path.
##  Possible values&#58; <filename>
##  Default value&#58; STDERR
log_file_main=/netup/utm5/log/radius.log

## log_file_debug
##  Description&#58; Debug logfile path.
##  Possible values&#58; <filename>
##  Default value&#58; STDERR
log_file_debug=/netup/utm5/log/radius.log

## log_file_critical
##  Description&#58; Critical logfile path.
##  Possible values&#58; <filename>
##  Default value&#58; STDERR

## rotate_logs
##  Description&#58; Enables rotation of logfiles.
##  Possible values&#58; yes, on, enable
##  Default value&#58; rotation is disabled

## max_logfile_size
##  Description&#58; Maximum logfile size. When logfile size reaches this limit,
##   a rotation is performed.
##  Possible values&#58; a size in bytes
##  Default value&#58; 10485760

## max_logfile_count
##  Description&#58; Maximum number of logfiles to retain. Valid if logfile rotation
##   is on.
##  Default value&#58; not limited

## guest_pool_name
##  Description&#58; named IP pool of guest users
##  Possible values&#58; pool name
##  Default value&#58; not set

## blocked_pool_name
##  Description&#58; named IP pool of blocked users
##  Possible values&#58; pool name
##  Default value&#58; not set

## auth_unknown_users
##  Description&#58; authorize unknown users as IP pool users and assign IP address from guest_pool_name
##   if it's set
##  Possible values&#58; yes, on, enable
##  Default value&#58; disabled

Аватара пользователя
TiRider
Сообщения: 568
Зарегистрирован: Сб июн 07, 2008 12:43

Сообщение TiRider »

В услуге коммутируемый доступ. Лимит одновременных сессий = 1.
на циске:

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

bba-group pppoe <name>
 virtual-template 1
 mac-address <mac-cisco-router-subinterface>
 sessions per-mac limit 1
 sessions per-vlan limit 1500
 sessions auto cleanup
!
radius-server attribute 31 mac format ietf &#40;default&#41;
radius-server attribute 8 include-in-access-req
radius-server attribute 32 include-in-access-req
radius-server attribute 77 include-in-access-req

olegnv
Сообщения: 53
Зарегистрирован: Чт сен 08, 2011 07:48

Сообщение olegnv »

TiRider писал(а):В услуге коммутируемый доступ. Лимит одновременных сессий = 1.


Коммутируемый доступ - это же dialup. У нас pppoe.
В качестве NAS у нас mpd, работают несколько брасов. Ваше решение нам не подойдет, к сожалению.

gtk
Сообщения: 232
Зарегистрирован: Пт янв 21, 2005 18:33

Сообщение gtk »

olegnv писал(а):
TiRider писал(а):В услуге коммутируемый доступ. Лимит одновременных сессий = 1.


Коммутируемый доступ - это же dialup. У нас pppoe.
В качестве NAS у нас mpd, работают несколько брасов. Ваше решение нам не подойдет, к сожалению.
вы так и не показали свой конфиг радиуса.

uinman
Сообщения: 75
Зарегистрирован: Чт дек 02, 2010 06:39

Сообщение uinman »

Хотелось бы и в прям конфиг глянуть.
У меня пускает только одну сессию. Все сделано со штатным радиусом и тд.. c Mpd5.5

olegnv
Сообщения: 53
Зарегистрирован: Чт сен 08, 2011 07:48

Сообщение olegnv »

gtk писал(а):вы так и не показали свой конфиг радиуса.
## core_host
## Description: IP address of a host running the utm5_core
## Possible values: an IP address
## Required field.
core_host=127.0.0.1

## core_port
## Description: UTM5 core listening port. Equal to stream_bind_port parameter
## in utm5.cfg.
## Possible values: an integer from 1 to 65534
## Required field.
core_port=12698

## radius_login
## Description: A system user login to access the UTM5 core.
## Possible values: <string>
## Default value: radius
radius_login=radius_login
radius_password=radius_password

## radius_password
## Description: A system user password to access the UTM5 core.
## Possible values: <string>
## Default value: radius

## radius_ssl_type
## Description: SSL connection type. If 'none' is set, the connection
## is unencrypted.
## Possible values: tls1, ssl3, none
## Default value: none
#radius_ssl_type=none

## radius_acct_host
## Description: IP address of the host receiving Accounting-Requests.
## Possible values: interface IP address or 0.0.0.0
## Default value: 0.0.0.0

## radius_acct_port
## Description: Port of the host receiving Accounting-Requests.
## Possible values: an integer from 1 to 65534
## Default value: 1813

## radius_auth_host
## Description: IP address of the host receiving Access-Requests.
## Possible values: interface IP address or 0.0.0.0
## Default value: 0.0.0.0

## radius_auth_port
## Description: Port of the host receiving Access-Requests.
## Possible values: an integer from 1 to 65534
## Default value: 1812

## radius_auth_mppe
## Description: Enables MPPE 128 bit key generation used for authorization
## via MS-CHAP-v2 protocol.
## Possible values: enable
## Default value: the keys are not generated
radius_auth_mppe=enable

## radius_auth_vap
## Description: If the value is set, authorization of blocked users, whose
## logins are set in IP traffic service link, is disallowed.
## Possible values: 1
## Default value: authorization is allowed
radius_auth_vap=1

## radius_ippool_acct_timeout
## Description: A time interval during which the IP address is labeled as
## occupied after sending Access-Accept.
## Possible values: time in seconds
## Default value: 30

## radius_ippool_timeout
## Description: A time interval during which the IP address is labeled as
## occupied after receiving Accounting-Start.
## Possible values: time in seconds
## Default value: The address is labeled as occupied until coming of the
## Stop packet

##radius_ippool_timeout=0
##radius_ippool_acct_timeout=0

radius_ippool_timeout=60
interim_update_interval=120

## radius_ippool_timeout=0
## radius_auth_null
## Description: If enabled, the RADIUS server authorizes requests without
## User-Password(2) attribute, if the user's password, defined in the
## service link, is empty.
## Possible values: yes, enable
## Default value: authorization without a password is not performed
#radius_auth_null=yes

## radius_auth_h323_remote_address
## Description: If enabled, then telephone calls authentication is performed
## using h323-remote-address(9;23) attribute value, but not using
## User-Name(1) attribute. The attribute value is used as a login.
## Possible values: enable, on, yes
## Default value: replacement of login with h323-remote-address is not
## performed

## radius_nas_port_vpn
## Description: This parameter is checked against NAS-Port-Type(61) attribute
## value when connecting using the login specified in the IP traffic service
## link. Several values can be set.
## Possible values: a positive integer
## Default value: Checking against NAS-Port-Type for the IP traffic service
## link is not performed

## radius_nas_port_dialup
## Description: This parameter is checked against NAS-Port-Type(61) attribute
## value when connecting using the login specified in the Dial-up service
## link. Several values can be set.
## Possible values: a positive integer
## Default value: checking against NAS-Port-Type for the Dial-up service link
## is not performed

## radius_nas_port_tel
## Description: This parameter is checked against NAS-Port-Type(61) attribute
## value when connecting using the login specified in the Telephony service
## link. Several values can be set.
## Possible values: a positive integer
## Default value: checking against NAS-Port-Type for the Telephony service
## link is not performed

## radius_card_autoadd
## Description: If 'yes' is set, the automatic registration of users is
## enabled via the RADIUS server using prepaid cards. In this case in the
## Login field a user enters the card number and in the Password field - the
## PIN code. In case of the Telephony service, in the Login field it is
## entered the PIN code or its first part and the remainder is used as a
## password.

## Possible values: yes, on, enable
## Default value: automatic registration is not performed
radius_card_autoadd=no

## send_xpgk_ep_number
## Description: If this option is enabled, for the Telephony service, when a
## user is being authorized, in Access-Accept it is transmitted the
## Cisco-AVPair(9;1) attribute with the value:
## xpgk-ep-number=<a semicolon separated list of telephone numbers>.
## Possible values: <any>
## Default value: telephone numbers are not transmitted in affirmative replies
## to authorization requests

## send_h323_ivr_in
## Description: If this option is enabled, for the Telephony service, when a
## user is being authorized, in Access-Accept it is transmitted the
## Cisco-AVPair(9;1) attribute with the value: h323-ivr-in=terminal-alias:
## <a semicolon separated list of telephone numbers>.
## Possible values: <any>
## Default value: telephone numbers are not transmitted in affirmative replies
## to authorization requests

## enable_fast_telephony
## Description: This option enables the rapid mechanism for determination of
## directions and zones when rating telephone calls. In this case templates
## for telephone directions must contain the digits from 0 to 9 and the
## symbols: ^ $ + )( |.
## Possible values: enable, yes
## Default value: the default mechanism for determination of zone/direction
## is used

## h323_origin_reject
## Description: Sets zero cost for Accounting-Requests in which the
## h323-call-origin(9;26) attribute equals the value of this parameter.
## Possible values: <string>
## Default value: unset
#h323_origin_reject=originate {answer|callback|etc}

## interim_update_interval
## Description: Enables session control mechanism using Interim-Update
## packets. The value is transmitted in the Acct-Interim-Interval(85)
## attribute of the Access-Accept packet.
## Possible values: time in seconds, more than 61
## Default value: the default session closure control mechanism is used
interim_update_interval=120

## radius_default_session_timeout
## Description: A value of the Session-Timeout(27) attribute transmitted in
## Access-Accept for the IP traffic service link.
## Possible values: a positive integer
## Default value: 86400

## radius_callback_avpair_enable
## Description: Enables transmission of the Cisco-AVPair(9;1) attribute with
## the value lcp:callback-dialstring=<callback number>, where
## <callback number> is the part of the login from the beginning to the
## ':'-symbol.
## Possible values: <any>
## Default value: unset

## radius_acct_rewrite_login_answer
## Description: If the value of the h323-call-origin(9;26) attribute is
## 'originate', then setting this parameter enables replacing of the login
## with the value of the h323-remote-address(9;23) attribute when processing
## Accounting-Request packets.
## Possible values: enable, on, true
## Default value: unset

## radius_acct_rewrite_login_originate
## Description: If the value of the h323-call-origin(9;26) attribute is
## 'answer', then setting this parameter enables replacing of the login with
## the value of the h323-remote-address(9;23) attribute when processing
## Accounting-Request packets.
## Possible values: enable, on, true
## Default value: unset

gtk
Сообщения: 232
Зарегистрирован: Пт янв 21, 2005 18:33

Сообщение gtk »

radius_ippool_timeout=60 - закоментируйте эту строчку

Ответить