chtito2 писал(а):А чем с практической точки зрения для Абиллса отличается многопотоковый Perl от многопотокового FreeRADIUS?
А в многопотоковом perl в ABillS возникает race condition при доступе к базе . Причем возникает он почему-то только в radauth.pl и только если дергать его через rlm_perl.
Комментарии: viewtopic.php?t=3964 и viewtopic.php?t=3778 .
та поддержка многопотокового перла добавлена уже давно
ченжлог писал(а):2.11.2008
*
Улучшена поддержка rlm_perl:
1.
Доработана работа с потоковым Perl (threaded).
и с радиусом например 1.1.7 прекрасно работает... тут дело видимо в самом радиусе...
Любой тупик - это тщательно замаскированный выход.
prov:/etc#
Ready to process requests.
rad_recv: Access-Request packet from host 127.0.0.1 port 40442, id=47, length=137
Service-Type = Framed-User
Framed-Protocol = PPP
User-Name = "204"
MS-CHAP-Challenge = 0xb8c2ebc41dc1b846d26b7a2fa9761238
MS-CHAP2-Response = 0x780056cb768629ef6c221d7be07f556c1cf30000000000000000a91b7d51ff4b6f71372fbf434917020c25637e271a970100
Calling-Station-Id = ".291"
NAS-IP-Address = 127.0.0.1
NAS-Port = 0
auth: No authenticate method (Auth-Type) configuration found for the request: Rejecting the user
auth: Failed to validate the user.
Login incorrect: [204/<no User-Password attribute>] (from client shortname port 0 cli .291)
Delaying reject of request 1 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
Sending delayed reject for request 1
Sending Access-Reject of id 47 to 127.0.0.1 port 40442
Waking up in 4.9 seconds.
Cleaning up request 1 ID 47 with timestamp +35
Ready to process requests.
Отключил... только все одно... такое ощущение что какой то атрибут не передается....
}
Listening on authentication address * port 1812
Listening on accounting address * port 1813
Listening on proxy address * port 1814
Ready to process requests.
rad_recv: Access-Request packet from host 127.0.0.1 port 39314, id=51, length=146
Service-Type = Framed-User
Framed-Protocol = PPP
User-Name = "204"
MS-CHAP-Challenge = 0x57fb055c2644d577d0c78869894521c0
MS-CHAP2-Response = 0xc500c271f175c579201ff2a6d614f7239443000000000000000097207b92cacfb5cf4964ac183bddee70cff3c1a85ee6452b
Calling-Station-Id = "192.168.2.120"
NAS-IP-Address = 127.0.0.1
NAS-Port = 0 auth: No authenticate method (Auth-Type) configuration found for the request: Rejecting the user
auth: Failed to validate the user.
Login incorrect: [204/<no User-Password attribute>] (from client shortname port 0 cli 192.168.2.120)
Delaying reject of request 0 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
Sending delayed reject for request 0
Sending Access-Reject of id 51 to 127.0.0.1 port 39314
Waking up in 4.9 seconds.
Cleaning up request 0 ID 51 with timestamp +7
Ready to process requests.
May 20 12:22:58 localhost pptpd[4178]: CTRL: local address = 192.168.2.4
May 20 12:22:58 localhost pptpd[4178]: CTRL: remote address = 192.168.1.1
May 20 12:22:58 localhost pptpd[4178]: CTRL: pppd options file = /etc/ppp/pptpd-options
May 20 12:22:58 localhost pptpd[4178]: CTRL: Client 192.168.2.120 control connection started
May 20 12:22:58 localhost pptpd[4178]: CTRL: Received PPTP Control Message (type: 1)
May 20 12:22:58 localhost pptpd[4178]: CTRL: Made a START CTRL CONN RPLY packet
May 20 12:22:58 localhost pptpd[4178]: CTRL: I wrote 156 bytes to the client.
May 20 12:22:58 localhost pptpd[4178]: CTRL: Sent packet to client
May 20 12:22:58 localhost pptpd[4178]: CTRL: Received PPTP Control Message (type: 7)
May 20 12:22:58 localhost pptpd[4178]: CTRL: Set parameters to 100000000 maxbps, 64 window size
May 20 12:22:58 localhost pptpd[4178]: CTRL: Made a OUT CALL RPLY packet
May 20 12:22:58 localhost pptpd[4178]: CTRL: Starting call (launching pppd, opening GRE)
May 20 12:22:58 localhost pptpd[4178]: CTRL: pty_fd = 6
May 20 12:22:58 localhost pptpd[4178]: CTRL: tty_fd = 8
May 20 12:22:58 localhost pptpd[4179]: CTRL (PPPD Launcher): program binary = /usr/sbin/pppd
May 20 12:22:58 localhost pptpd[4179]: CTRL (PPPD Launcher): local address = 192.168.2.4
May 20 12:22:58 localhost pptpd[4179]: CTRL (PPPD Launcher): remote address = 192.168.1.1
May 20 12:22:58 localhost pptpd[4178]: CTRL: I wrote 32 bytes to the client.
May 20 12:22:58 localhost pptpd[4178]: CTRL: Sent packet to client
May 20 12:22:58 localhost pppd[4179]: Plugin radius.so loaded.
May 20 12:22:58 localhost pppd[4179]: RADIUS plugin initialized.
May 20 12:22:58 localhost pppd[4179]: Plugin radattr.so loaded.
May 20 12:22:58 localhost pppd[4179]: RADATTR plugin initialized.
May 20 12:22:58 localhost pppd[4179]: pppd 2.4.4 started by root, uid 0
May 20 12:22:58 localhost pppd[4179]: Using interface ppp0
May 20 12:22:58 localhost pppd[4179]: Connect: ppp0 <--> /dev/pts/4
May 20 12:22:58 localhost pptpd[4178]: GRE: Bad checksum from pppd.
May 20 12:22:58 localhost pptpd[4178]: CTRL: Received PPTP Control Message (type: 15)
May 20 12:22:58 localhost pptpd[4178]: CTRL: Got a SET LINK INFO packet with standard ACCMs
May 20 12:22:58 localhost pptpd[4178]: GRE: accepting packet #0
May 20 12:22:58 localhost pptpd[4178]: GRE: accepting packet #1
May 20 12:23:01 localhost pptpd[4178]: GRE: accepting packet #2
May 20 12:23:01 localhost pptpd[4178]: CTRL: Received PPTP Control Message (type: 15)
May 20 12:23:01 localhost pptpd[4178]: CTRL: Ignored a SET LINK INFO packet with real ACCMs!
May 20 12:23:01 localhost pptpd[4178]: GRE: accepting packet #3
May 20 12:23:01 localhost pptpd[4178]: GRE: accepting packet #4
May 20 12:23:01 localhost pptpd[4178]: GRE: accepting packet #5
May 20 12:23:01 localhost pptpd[4178]: GRE: accepting packet #6
May 20 12:23:02 localhost pppd[4179]: Peer 204 failed CHAP authentication
May 20 12:23:02 localhost pptpd[4178]: CTRL: Received PPTP Control Message (type: 15)
May 20 12:23:02 localhost pptpd[4178]: CTRL: Got a SET LINK INFO packet with standard ACCMs
May 20 12:23:02 localhost pptpd[4178]: GRE: accepting packet #7
May 20 12:23:02 localhost pppd[4179]: Connection terminated.
May 20 12:23:02 localhost pppd[4179]: Exit.
May 20 12:23:02 localhost pptpd[4178]: GRE: read(fd=6,buffer=8058640,len=8196) from PTY failed: status = -1
error = Input/output error, usually caused by unexpected termination of pppd, check option syntax and pppd l
Слишком гадкий чтобы жить, слишком редкий чтобы сдохнуть...
Спасибо за совет! Но я не буду использовать pptpd как рабочий вариант, на нем просто тестю, а так рабочим будет PPPoE сервер. Просто в сети есть уже один PPPoE сервер и тесты приходится проводить на vpn... Я с этими граблями на рррое сервере наступал, там вобще 64 соединения по умолчанию, спасибо ran за оперативную помощь в аське.
Кстати все заработало, Alive пакеты бегают, в мониторринге пользователеи отображаются, и что самое для меня главное - заработали суточные лимиты
Спасибо всем кто ответил!
Слишком гадкий чтобы жить, слишком редкий чтобы сдохнуть...