Почему /var/run/radattr.pppX могут быть пустыми?

Установка, настройка, поддержка
worky
Сообщения: 67
Зарегистрирован: Пт мар 13, 2009 6:41 pm

Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение worky » Ср дек 16, 2009 7:56 pm

абиллс 0.41, убунту 8.04. юзеры коннектятся через пптп, авторизуются. но: айпи из пула, а не из биллинга даются; скорость не режится и пр
в логах пптпд вижу:

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

Plugin /usr/lib/pptpd/pptpd-logwtmp.so loaded.
pptpd-logwtmp: $Version$
using channel 2551
Using interface ppp6
Connect: ppp6 <--> /dev/pts/6
sent [LCP ConfReq id=0x1 <mru 1462> <asyncmap 0x0> <auth chap MD5> <magic 0xd58e6cb0> <pcomp> <accomp>]
rcvd [LCP ConfReq id=0x0 <mru 1400> <magic 0x359f5938> <pcomp> <accomp> <callback CBCP>]
sent [LCP ConfRej id=0x0 <callback CBCP>]
rcvd [LCP ConfReq id=0x1 <mru 1400> <magic 0x359f5938> <pcomp> <accomp>]
sent [LCP ConfAck id=0x1 <mru 1400> <magic 0x359f5938> <pcomp> <accomp>]
sent [LCP ConfReq id=0x1 <mru 1462> <asyncmap 0x0> <auth chap MD5> <magic 0xd58e6cb0> <pcomp> <accomp>]
rcvd [LCP ConfAck id=0x1 <mru 1462> <asyncmap 0x0> <auth chap MD5> <magic 0xd58e6cb0> <pcomp> <accomp>]
sent [LCP EchoReq id=0x0 magic=0xd58e6cb0]
sent [CHAP Challenge id=0xfe <fba1fb7de48ec9e6881ed37c2641b761>, name = "server"]
rcvd [LCP Ident id=0x2 magic=0x359f5938 "MSRASV5.10"]
rcvd [LCP Ident id=0x3 magic=0x359f5938 "MSRAS-1-BOMBA"]
rcvd [LCP EchoRep id=0x0 magic=0x359f5938]
rcvd [CHAP Response id=0xfe <d2194fa92ce324e5a74ef851fd0b80a6>, name = "12"]
[b]RADATTR plugin wrote 0 line(s) to file /var/run/radattr.ppp6.[/b]
sent [CHAP Success id=0xfe ""]
sent [IPCP ConfReq id=0x1 <compress VJ 0f 01> <addr 172.16.1.1>]
rcvd [CCP ConfReq id=0x4 <mppe +H -M -S -L -D +C>]
sent [CCP ConfReq id=0x1]
sent [CCP ConfRej id=0x4 <mppe +H -M -S -L -D +C>]
rcvd [IPCP ConfReq id=0x5 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-wins 0.0.0.0> <ms-dns3 0.0.0.0> <ms-wins 0.0.0.0>]
sent [IPCP ConfRej id=0x5 <ms-wins 0.0.0.0> <ms-wins 0.0.0.0>]
rcvd [IPCP ConfRej id=0x1 <compress VJ 0f 01>]
sent [IPCP ConfReq id=0x2 <addr 172.16.1.1>]
rcvd [CCP ConfAck id=0x1]
rcvd [CCP TermReq id=0x6"5\37777777637Y8\000<\37777777715t\000\000\002\37777777734"]
sent [CCP TermAck id=0x6]
rcvd [IPCP ConfReq id=0x7 <addr 0.0.0.0> <ms-dns1 0.0.0.0> <ms-dns3 0.0.0.0>]
sent [IPCP ConfNak id=0x7 <addr 192.168.1.2> <ms-dns1 195.225.145.2> <ms-dns3 172.31.1.2>]
rcvd [IPCP ConfAck id=0x2 <addr 172.16.1.1>]
rcvd [IPCP ConfReq id=0x8 <addr 192.168.1.2> <ms-dns1 195.225.145.2> <ms-dns3 172.31.1.2>]
sent [IPCP ConfAck id=0x8 <addr 192.168.1.2> <ms-dns1 195.225.145.2> <ms-dns3 172.31.1.2>]
local  IP address 172.16.1.1
remote IP address 192.168.1.2
pptpd-logwtmp.so ip-up ppp6 12 192.168.0.156
Script /etc/ppp/ip-up started (pid 7472)
Script /etc/ppp/ip-up finished (pid 7472), status = 0x0
sent [CCP ConfReq id=0x1]
sent [CCP ConfReq id=0x1]
rcvd [CCP TermAck id=0x1]
sent [CCP TermReq id=0x2"No compression negotiated"]
rcvd [CCP TermAck id=0x1]
rcvd [CCP TermAck id=0x2"No compression negotiated"]
радиус пишет такое в логи

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

Wed Dec 16 21:51:35 2009
        Acct-Session-Id = "4B293A471E3000"
        User-Name = "12"
        Acct-Status-Type = Start
        Service-Type = Framed-User
        Framed-Protocol = PPP
        Calling-Station-Id = "192.168.0.156"
        Acct-Authentic = RADIUS
        NAS-Port-Type = Async
        Framed-IP-Address = 192.168.1.2
        NAS-IP-Address = 192.168.0.2
        NAS-Port = 6
        Acct-Delay-Time = 0
        Client-IP-Address = 127.0.0.1
        Acct-Unique-Session-Id = "95b990f8bff50d99"
        Timestamp = 1260993095

ran
Сообщения: 2298
Зарегистрирован: Вс окт 21, 2007 2:29 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение ran » Чт дек 17, 2009 7:08 am

айпи из пула, а не из биллинга даются
по каким-то причинам не передаются от радиуссервера радиусклиенту необходимые атрибуты... эхх... сколько ж раз я уже в этом форуме произносил эту фразу
radiusd -X
Любой тупик - это тщательно замаскированный выход.

worky
Сообщения: 67
Зарегистрирован: Пт мар 13, 2009 6:41 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение worky » Чт дек 17, 2009 8:16 am

дада, забыл
rad_recv: Accounting-Request packet from host 127.0.0.1:32883, id=34, length=111
Acct-Session-Id = "4B29E8823DB300"
User-Name = "olya"
Acct-Status-Type = Start
Service-Type = Framed-User
Framed-Protocol = PPP
Calling-Station-Id = "192.168.0.220"
Acct-Authentic = RADIUS
NAS-Port-Type = Async
Framed-IP-Address = 192.168.1.1
NAS-IP-Address = 192.168.0.2
NAS-Port = 5
Acct-Delay-Time = 0
Processing the preacct section of radiusd.conf
modcall: entering group preacct for request 2
modcall[preacct]: module "preprocess" returns noop for request 2
rlm_acct_unique: Hashing 'NAS-Port = 5,Client-IP-Address = 127.0.0.1,NAS-IP-Address = 192.168.0.2,Acct-Session-Id = "4B29E8823DB300",User-Name = "olya"'
rlm_acct_unique: Acct-Unique-Session-ID = "9c46d85dc642b5e1".
modcall[preacct]: module "acct_unique" returns ok for request 2
acct_users: Matched entry DEFAULT at line 1
modcall[preacct]: module "files" returns ok for request 2
modcall: leaving group preacct (returns ok) for request 2
Processing the accounting section of radiusd.conf
modcall: entering group accounting for request 2
radius_xlat: '/var/log/freeradius/radacct/127.0.0.1/detail-20091217'
rlm_detail: /var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /var/log/freeradius/radacct/127.0.0.1/detail-20091217
modcall[accounting]: module "detail" returns ok for request 2
modcall: leaving group accounting (returns ok) for request 2
Sending Accounting-Response of id 34 to 127.0.0.1 port 32883
Finished request 2
Going to the next request
/usr/abills/libexec/ext_acct//README: 1: External: not found
/usr/abills/libexec/ext_acct//README: 3: exacct_program: not found
/usr/abills/libexec/ext_acct//README: 5: MUST: not found
/usr/abills/libexec/ext_acct//README: 6: example:: not found
Waking up in 6 seconds...
--- Walking the entire request list ---
Cleaning up request 1 ID 33 with timestamp 4b29e882
Cleaning up request 2 ID 34 with timestamp 4b29e882
Nothing to do. Sleeping until we see a request.

worky
Сообщения: 67
Зарегистрирован: Пт мар 13, 2009 6:41 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение worky » Чт дек 17, 2009 8:26 am

при запуске через -Х вначале пишет

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

root@server:~# freeradius -X
Starting - reading configuration files ...
reread_config:  reading radiusd.conf
Config:   including file: /etc/freeradius/clients.conf
 main: prefix = "/usr"
 main: localstatedir = "/var"
 main: logdir = "/var/log/freeradius"
 main: libdir = "/usr/lib"
 main: radacctdir = "/var/log/freeradius/radacct"
 main: hostname_lookups = no
 main: snmp = no
 main: max_request_time = 30
 main: cleanup_delay = 5
 main: max_requests = 8096
 main: delete_blocked_requests = 0
 main: port = 0
 main: allow_core_dumps = no
 main: log_stripped_names = no
 main: log_file = "/var/log/freeradius/radius.log"
 main: log_auth = no
 main: log_auth_badpass = no
 main: log_auth_goodpass = no
 main: pidfile = "/var/run/freeradius/freeradius.pid"
 main: user = "freerad"
 main: group = "freerad"
 main: usercollide = no
 main: lower_user = "no"
 main: lower_pass = "no"
 main: nospace_user = "no"
 main: nospace_pass = "no"
 main: checkrad = "/usr/sbin/checkrad"
 main: proxy_requests = no
 security: max_attributes = 200
 security: reject_delay = 1
 security: status_server = no
 main: debug_level = 0
read_config_files:  reading dictionary
read_config_files:  reading naslist
read_config_files:  reading clients
read_config_files:  reading realms
radiusd:  entering modules setup
Module: Library search path is /usr/lib
Module: Loaded exec
 exec: wait = yes
 exec: program = "(null)"
 exec: input_pairs = "request"
 exec: output_pairs = "(null)"
 exec: packet_type = "(null)"
rlm_exec: Wait=yes but no output defined. Did you mean output=none?
Module: Instantiated exec (exec)
Module: Loaded expr
Module: Instantiated expr (expr)
Module: Loaded PAP
 pap: encryption_scheme = "crypt"
 pap: auto_header = yes
Module: Instantiated pap (pap)
Module: Loaded CHAP
Module: Instantiated chap (chap)
Module: Loaded MS-CHAP
 mschap: use_mppe = yes
 mschap: require_encryption = no
 mschap: require_strong = no
 mschap: with_ntdomain_hack = no
 mschap: passwd = "(null)"
 mschap: ntlm_auth = "(null)"
Module: Instantiated mschap (mschap)
Module: Loaded preprocess
 preprocess: huntgroups = "/etc/freeradius/huntgroups"
 preprocess: hints = "/etc/freeradius/hints"
 preprocess: with_ascend_hack = no
 preprocess: ascend_channels_per_line = 23
 preprocess: with_ntdomain_hack = no
 preprocess: with_specialix_jetstream_hack = no
 preprocess: with_cisco_vsa_hack = no
 preprocess: with_alvarion_vsa_hack = no
Module: Instantiated preprocess (preprocess)
 exec: wait = yes
 exec: program = "/usr/abills/libexec/rauth.pl pre_auth"
 exec: input_pairs = "request"
 exec: output_pairs = "config"
 exec: packet_type = "(null)"
Module: Instantiated exec (pre_auth)
Module: Loaded Acct-Unique-Session-Id
 acct_unique: key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port"
Module: Instantiated acct_unique (acct_unique)
Module: Loaded files
 files: usersfile = "/etc/freeradius/users"
 files: acctusersfile = "/etc/freeradius/acct_users"
 files: preproxy_usersfile = "/etc/freeradius/preproxy_users"
 files: compat = "no"
Module: Instantiated files (files)
Module: Loaded detail
 detail: detailfile = "/var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d"
 detail: detailperm = 384
 detail: dirperm = 493
 detail: locking = no
Module: Instantiated detail (detail)
Listening on authentication *:1812
Listening on accounting *:1813
Ready to process requests.

NiTr0
Сообщения: 767
Зарегистрирован: Пт фев 08, 2008 4:46 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение NiTr0 » Чт дек 17, 2009 9:13 am

конфиг радиуса внимательно изучайте. что-то напутали.

worky
Сообщения: 67
Зарегистрирован: Пт мар 13, 2009 6:41 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение worky » Чт дек 17, 2009 9:52 am

NiTr0 писал(а):конфиг радиуса внимательно изучайте. что-то напутали.
взял уже из ебиллса

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

authorize {
#Use if 'files' mode and mschap auth
        preprocess
        pre_auth
        #chap
        #mschap
        #eap
# don't use simultaneously 'perl' and files
#       perl
#       files
}


authenticate {
        Auth-Type PAP {
                pap
        }
        Auth-Type CHAP {
                chap
        }
        Auth-Type MS-CHAP {
                mschap
        }
# don't use simultaneously 'perl' and files
#       perl
        #eap
}


preacct {
        preprocess
        acct_unique
        files
}
accounting {
# don't use simultaneously 'perl' and files
#       perl
        detail
}

session {
#       radutmp
#       sql
}


post-auth {
#       Post-Auth-Type REJECT {
# don't use simultaneously 'perl' and files
#               perl
#               post_auth
#       }


ran
Сообщения: 2298
Зарегистрирован: Вс окт 21, 2007 2:29 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение ran » Чт дек 17, 2009 10:21 am

rad_recv: Accounting-Request packet from host 127.0.0.1:32883, id=34, length=111
это уже аккаунтинг а нада смотреть Access-Request и ответ на него
Любой тупик - это тщательно замаскированный выход.

worky
Сообщения: 67
Зарегистрирован: Пт мар 13, 2009 6:41 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение worky » Чт дек 17, 2009 10:43 am

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

Module: Loaded exec
 exec: wait = yes
 exec: program = "(null)"
 exec: input_pairs = "request"
 exec: output_pairs = "(null)"
 exec: packet_type = "(null)"
rlm_exec: Wait=yes but no output defined. Did you mean output=none?
Module: Instantiated exec (exec)
а что вот это означает? типа не загружает пре_аутз?

worky
Сообщения: 67
Зарегистрирован: Пт мар 13, 2009 6:41 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение worky » Чт дек 17, 2009 12:21 pm

взял назад конфиги с дистра, подправил. теперь при запске пишет:

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

root@server:~# freeradius -X
Starting - reading configuration files ...
reread_config:  reading radiusd.conf
Config:   including file: /etc/freeradius/proxy.conf
Config:   including file: /etc/freeradius/clients.conf
Config:   including file: /etc/freeradius/snmp.conf
 main: prefix = "/usr"
 main: localstatedir = "/var"
 main: logdir = "/var/log/freeradius"
 main: libdir = "/usr/lib/freeradius"
 main: radacctdir = "/var/log/freeradius/radacct"
 main: hostname_lookups = no
 main: snmp = no
 main: max_request_time = 30
 main: cleanup_delay = 5
 main: max_requests = 1024
 main: delete_blocked_requests = 0
 main: port = 0
 main: allow_core_dumps = no
 main: log_stripped_names = no
 main: log_file = "/var/log/freeradius/radius.log"
 main: log_auth = no
 main: log_auth_badpass = no
 main: log_auth_goodpass = no
 main: pidfile = "/var/run/freeradius/freeradius.pid"
 main: user = "freerad"
 main: group = "freerad"
 main: usercollide = no
 main: lower_user = "no"
 main: lower_pass = "no"
 main: nospace_user = "no"
 main: nospace_pass = "no"
 main: checkrad = "/usr/sbin/checkrad"
 main: proxy_requests = no
 proxy: retry_delay = 5
 proxy: retry_count = 3
 proxy: synchronous = no
 proxy: default_fallback = yes
 proxy: dead_time = 120
 proxy: post_proxy_authorize = no
 proxy: wake_all_if_all_dead = no
 security: max_attributes = 200
 security: reject_delay = 1
 security: status_server = no
 main: debug_level = 0
read_config_files:  reading dictionary
read_config_files:  reading naslist
Using deprecated naslist file.  Support for this will go away soon.
read_config_files:  reading clients
read_config_files:  reading realms
radiusd:  entering modules setup
Module: Library search path is /usr/lib/freeradius
Module: Loaded exec
 exec: wait = yes
 exec: program = "(null)"
 exec: input_pairs = "request"
 exec: output_pairs = "(null)"
 exec: packet_type = "(null)"
rlm_exec: Wait=yes but no output defined. Did you mean output=none?
Module: Instantiated exec (exec)
Module: Loaded expr
Module: Instantiated expr (expr)
Module: Loaded PAP
 pap: encryption_scheme = "crypt"
 pap: auto_header = yes
Module: Instantiated pap (pap)
Module: Loaded CHAP
Module: Instantiated chap (chap)
Module: Loaded preprocess
 preprocess: huntgroups = "/etc/freeradius/huntgroups"
 preprocess: hints = "/etc/freeradius/hints"
 preprocess: with_ascend_hack = no
 preprocess: ascend_channels_per_line = 23
 preprocess: with_ntdomain_hack = no
 preprocess: with_specialix_jetstream_hack = no
 preprocess: with_cisco_vsa_hack = no
 preprocess: with_alvarion_vsa_hack = no
Module: Instantiated preprocess (preprocess)
 exec: wait = yes
 exec: program = "/usr/abills/libexec/rauth.pl pre_auth"
 exec: input_pairs = "request"
 exec: output_pairs = "config"
 exec: packet_type = "(null)"
Module: Instantiated exec (pre_auth)
Module: Loaded Acct-Unique-Session-Id
 acct_unique: key = "User-Name, Acct-Session-Id, NAS-IP-Address, Client-IP-Address, NAS-Port"
Module: Instantiated acct_unique (acct_unique)
Module: Loaded detail
 detail: detailfile = "/var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d"
 detail: detailperm = 384
 detail: dirperm = 493
 detail: locking = no
Module: Instantiated detail (detail)
 exec: wait = yes
 exec: program = "/usr/abills/libexec/rauth.pl post_auth"
 exec: input_pairs = "request"
 exec: output_pairs = "config"
 exec: packet_type = "(null)"
Module: Instantiated exec (post_auth)
Listening on authentication *:1812
Listening on accounting *:1813
Ready to process requests.
но толку мало - файлы radattr.pppX пустые...

worky
Сообщения: 67
Зарегистрирован: Пт мар 13, 2009 6:41 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение worky » Чт дек 17, 2009 12:29 pm

при коннекте юзера

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

rad_recv: Accounting-Request packet from host 127.0.0.1:52220, id=103, length=111
        Acct-Session-Id = "4B2A229B520B00"
        User-Name = "olya"
        Acct-Status-Type = Start
        Service-Type = Framed-User
        Framed-Protocol = PPP
        Calling-Station-Id = "192.168.0.220"
        Acct-Authentic = RADIUS
        NAS-Port-Type = Async
        Framed-IP-Address = 192.168.1.2
        NAS-IP-Address = 192.168.0.2
        NAS-Port = 5
        Acct-Delay-Time = 0
  Processing the preacct section of radiusd.conf
modcall: entering group preacct for request 5
  modcall[preacct]: module "preprocess" returns noop for request 5
rlm_acct_unique: Hashing 'NAS-Port = 5,Client-IP-Address = 127.0.0.1,NAS-IP-Address = 192.168.0.2,Acct-Session-Id = "4B2A229B520B00",User-Name = "olya"'
rlm_acct_unique: Acct-Unique-Session-ID = "561c47bdd47dc69a".
  modcall[preacct]: module "acct_unique" returns ok for request 5
modcall: leaving group preacct (returns ok) for request 5
  Processing the accounting section of radiusd.conf
modcall: entering group accounting for request 5
radius_xlat:  '/var/log/freeradius/radacct/127.0.0.1/detail-20091217'
rlm_detail: /var/log/freeradius/radacct/%{Client-IP-Address}/detail-%Y%m%d expands to /var/log/freeradius/radacct/127.0.0.1/detail-20091217
  modcall[accounting]: module "detail" returns ok for request 5
modcall: leaving group accounting (returns ok) for request 5
Sending Accounting-Response of id 103 to 127.0.0.1 port 52220
Finished request 5
Going to the next request
Waking up in 6 seconds...
--- Walking the entire request list ---
Cleaning up request 4 ID 102 with timestamp 4b2a229b
Cleaning up request 5 ID 103 with timestamp 4b2a229b
Nothing to do.  Sleeping until we see a request.

NiTr0
Сообщения: 767
Зарегистрирован: Пт фев 08, 2008 4:46 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение NiTr0 » Чт дек 17, 2009 12:30 pm

Юзер что, не шлет Auth-Request?

worky
Сообщения: 67
Зарегистрирован: Пт мар 13, 2009 6:41 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение worky » Чт дек 17, 2009 12:48 pm

NiTr0 писал(а):Юзер что, не шлет Auth-Request?
где это глянуть? как задебагить?

юзеры заходят под любыми логинами и паролями. аутентификация с биллингом не проходит.
куда рыть? что делать? в логах ничего подозрительного

ran
Сообщения: 2298
Зарегистрирован: Вс окт 21, 2007 2:29 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение ran » Пн дек 21, 2009 9:13 am

сначала от радиусклиента на радиуссеревер должен прийти где-то такой запрос
Packet-Type = Access-Request
Mon Dec 21 07:57:48 2009
Service-Type = Framed-User
Framed-Protocol = PPP
User-Name = "lptkl"
MS-CHAP-Challenge = 0x95e675f44b0571d7c6b9cb4a5d3910c2
MS-CHAP2-Response = 0xfc006ca1d04be1274d0b205f90dd28cc1f88000000000000000008ee470433b87bbb2ef21f2719c6
6c622da687cd1d1ea0dd
Calling-Station-Id = "00:A1:B0:11:31:13"
NAS-IP-Address = 192.168.1.1
NAS-Port = 14
Client-IP-Address = 127.0.0.1
на который сервер должен ответить где-то так
Packet-Type = Access-Accept
Mon Dec 21 07:57:48 2009
Session-Timeout = 0
Session-Octets-Limit = 0
PPPD-Downstream-Speed-Limit = 512
Acct-Interim-Interval = 120
PPPD-Upstream-Speed-Limit = 512
Octets-Direction = Route-IP-No
Framed-IP-Address = 10.27.0.239
Framed-IP-Netmask = 255.255.255.255
PPPD-Unit = 1008
MS-CHAP2-Success = 0xfc533d424532383130334344373845344442413336454544453644423143434545343931433034464
23533
MS-MPPE-Recv-Key = 0x77c4ef430b9047a440fc7d8d515dbcfd
MS-MPPE-Send-Key = 0xb21f3590258493c9f8e12bcd37e51959
MS-MPPE-Encryption-Policy = 0x00000001
MS-MPPE-Encryption-Types = 0x00000006
а уж потом всякие там старты и прочий аккаунтинг
Любой тупик - это тщательно замаскированный выход.

worky
Сообщения: 67
Зарегистрирован: Пт мар 13, 2009 6:41 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение worky » Вт дек 22, 2009 5:46 pm

Чем мои отличаются? При том, что я юзаю ПАП и ЧАП, и все на одном серваке настроено.
Можете дать скрин минимальной настройки наса в абиллсе для пптпд? может тут где ошибка...

Поставил с нуля сервак на убунте 8.04, сделал все по инструкции: то же - файлы пустые. какой то затык с этим радиусом.

worky
Сообщения: 67
Зарегистрирован: Пт мар 13, 2009 6:41 pm

Re: Почему /var/run/radattr.pppX могут быть пустыми?

Сообщение worky » Ср дек 23, 2009 10:14 am

вот что показывает фрирадиус -Х на новом серваке под виртуалкой
rad_recv: Access-Request packet from host 127.0.0.1:39808, id=172, length=89
Service-Type = Framed-User
Framed-Protocol = PPP
User-Name = "test"
CHAP-Challenge = 0xbc092968172f3a0e0bf8135f7e36545b1987
CHAP-Password = 0x4649b850d3115fd808e2bbf99291777001
NAS-IP-Address = 127.0.0.1
NAS-Port = 0
Processing the authorize section of radiusd.conf
modcall: entering group authorize for request 0
Exec-Program output: Auth-Type := Accept
Exec-Program-Wait: value-pairs: Auth-Type := Accept
Exec-Program: returned: 0
modcall[authorize]: module "pre_auth" returns ok for request 0
modcall[authorize]: module "preprocess" returns ok for request 0
modcall: leaving group authorize (returns ok) for request 0
rad_check_password: Found Auth-Type Accept
rad_check_password: Auth-Type = Accept, accepting the user
Login OK: [test] (from client localhost port 0)
Sending Access-Accept of id 172 to 127.0.0.1 port 39808
Finished request 0
Going to the next request
--- Walking the entire request list ---
Waking up in 6 seconds...
rad_recv: Accounting-Request packet from host 127.0.0.1:48470, id=173, length=96
Acct-Session-Id = "4B31ED3711B300"
User-Name = "test"
Acct-Status-Type = Start
Service-Type = Framed-User
Framed-Protocol = PPP
Acct-Authentic = RADIUS
NAS-Port-Type = Async
Framed-IP-Address = 192.168.1.1
NAS-IP-Address = 127.0.0.1
NAS-Port = 0
Acct-Delay-Time = 0
Finished request 1
Going to the next request
--- Walking the entire request list ---
Waking up in 5 seconds...
--- Walking the entire request list ---
Cleaning up request 0 ID 172 with timestamp 4b31ed36
Waking up in 1 seconds...
--- Walking the entire request list ---
Cleaning up request 1 ID 173 with timestamp 4b31ed37
Nothing to do. Sleeping until we see a request.

Ответить