Jump to content
Калькуляторы

SE100 - профили непонятная штука

привет.

имею se100, lanbilling.

Необходимо создать еще один профиль со своими фильтрами.

 

Профили на se100

subscriber default

qos policy policing qos-default-in

qos policy metering qos-default-out

ppp mtu 1492

dns primary xx.xx.xx.xx

dns secondary xx.xx.xx.xx

forward policy L2-MNGT-FILTER-in in

 

subscriber profile redir-lk

qos policy policing qos-default-in

qos policy metering qos-default-out

http-redirect profile LK

ppp mtu 1492

dns primary xx.xx.xx.xx

dns secondary xx.xx.xx.xx

forward policy HTTP-REDIRECT-LK in

 

subscriber profile timer-zone <--- новый профиль

qos policy policing qos-default-in

qos policy metering qos-default-out

ppp mtu 1492

dns primary xx.xx.xx.xx

dns secondary xx.xx.xx.xx

!

 

есть уже работающая учетка redir-lk, она успешно поднимается и размещается в профиль redir-lk

redir-lk

Session state Up

Circuit 2/4 vlan-id 500 pppoe 5928

Internal Circuit 2/4:511:63:31/6/2/49752

Interface bound pppoe

Current port-limit unlimited

Session time left 80371

Protocol Stack IPV4

profile redir-lk (applied)

ip address xx.xx.xx.xx(applied)

ppp mtu 1492 (applied from sub_profile)

dns primary xx.xx.xx.xx (applied from sub_profile)

dns secondary xx.xx.xx.xx (applied from sub_profile)

timeout absolute 86400 (applied)

acct-interim-interval 600 (applied)

qos-dynamic-param (applied)

police-class-rate cls-INET rate-absolute 10240 (applied)

police-class-burst cls-INET 1310720 (applied)

police-class-excess-burst cls-INET 1966080 (applied)

meter-class-rate cls-INET rate-absolute 10240 (applied)

meter-class-burst cls-INET 1310720 (applied)

meter-class-excess-burst cls-INET 1966080 (applied)

qos-policing-policy qos-default-in (applied from sub_profile)

qos-metering-policy qos-default-out (applied from sub_profile)

http-redirect-profile LK (applied from sub_profile)

forward policy in HTTP-REDIRECT-LK (applied from sub_profile)

 

Выход радиуса при тесте

 

 

Radius authentication test response:

Server: xx.xx.xx.xx/1812

Server response: Accepted.

------------------------------

Attributes list:

Session-Timeout = 86400

Service-Type = 2

Framed-Protocol = 1

Framed-IP-Address = xx.xx.xx.xx

Framed-IP-Netmask = 255.255.255.255

Class = 00023505

Dynamic_QoS_Param = police-class-rate cls-INET rate-absolute 10240

Dynamic_QoS_Param = police-class-burst cls-INET 1310720

Dynamic_QoS_Param = police-class-excess-burst cls-INET 1966080

Dynamic_QoS_Param = meter-class-rate cls-INET rate-absolute 10240

Dynamic_QoS_Param = meter-class-burst cls-INET 1310720

Dynamic_QoS_Param = meter-class-excess-burst cls-INET 1966080

/t Vendor 1 = xxxxxx.../t Vendor 1 = xxxxxx... Sub_Profile_Name = redir-lk

------------------------------

Send count: 1

Send time: Nov 4 20:10:51 2012

Response time: Nov 4 20:10:51 2012

 

Создал еще одну учетку, для профиля timer-zone

и вот прикол, она получает настройки из дефолтного профиля(смотрите на фильтр) хотя пишет что промещена в нужный мне профиль. проверил на разных SE100 , картина одинаковая.

 

выход радиуса

Server: xx.xx.xx.xx/1812

Server response: Accepted.

------------------------------

Attributes list:

Session-Timeout = 86400

Service-Type = 2

Framed-Protocol = 1

Framed-IP-Address = xx.xx.xx.xx

Framed-IP-Netmask = 255.255.255.255

Class = 00023931

Sub_Profile_Name = timer-zone

------------------------------

Send count: 1

Send time: Nov 4 20:12:24 2012

Response time: Nov 4 20:12:24 2012

 

Что получаем при подключении

 

testaa

Session state Up

Circuit 2/4 vlan-id 500 pppoe 6948

Internal Circuit 2/4:511:63:31/6/2/60851

Interface bound pppoe

Current port-limit unlimited

Session time left 86399

Protocol Stack IPV4

profile timer-zone (applied)

ip address xx.xx.xx.xx (applied)

ppp mtu 1492 (applied from sub_profile)

dns primary xx.xx.xx.xx (applied from sub_profile)

dns secondary xx.xx.xx.xx(applied from sub_profile)

timeout absolute 86400 (applied)

acct-interim-interval 600 (applied)

qos-policing-policy qos-default-in (applied from sub_profile)

qos-metering-policy qos-default-out (applied from sub_profile)

forward policy in L2-MNGT-FILTER-in (applied from sub_default)

 

почему идет наследование настроек дефолтного профиля?

Edited by lxsv

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.