forum.bitel.ru
http://forum.bitel.ru/

Проблемы с версией BGRadiusDialup_5.2_199.
http://forum.bitel.ru/viewtopic.php?f=5&t=6011		 Страница 1 из 1
Автор:  FessAectan [ 18 окт 2011, 10:12 ]
Заголовок сообщения:  Проблемы с версией BGRadiusDialup_5.2_199.
Всем привет, сабж.
Обновились до 5,2 словили глюк


Код:
10-17/23:07:23 ERROR [radiusListener-p-3-t-11] RadiusPacket - Error RADIUS packet: 010900EF2B2961B65C847CAC93EF3655D0E0FAD3200204060A0113A15012195DFDA96816487D58F5B1802E94ED652C0D383933363034392D4C2D310506000000013D06000000050606000000020706000000011F021E025705656D311A0B000030350C054C2D31400600000001410600000001430E3139322E3136382E31362E31420F3139322E3136382E31362E3131010D746573745F7470313032341A18000001370B12BB1E68586B89A81408C15B5CC1CBFFA21A3A000001371934010002ED9BE135753769AB7D8D0B37999B680000000000000000F661F3DE77976AD2F2ABF49070AFFFF8C9A9C95BE51B44D0
10-17/23:07:23 ERROR [radiusListener-p-3-t-11] RadiusListenerWorker - java.lang.IllegalArgumentException: NAS-Identifier header.length=0
ru.bitel.bgbilling.common.BGException: java.lang.IllegalArgumentException: NAS-Identifier header.length=0
   at ru.bitel.bgbilling.kernel.network.radius.RadiusPacket.parse(RadiusPacket.java:346)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusPacket.parse(RadiusPacket.java:313)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusListenerWorker.processPacket(RadiusListenerWorker.java:98)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusListenerWorker.runImpl(RadiusListenerWorker.java:87)
   at ru.bitel.common.worker.WorkerTask.run(WorkerTask.java:74)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)
   at ru.bitel.common.worker.WorkerThread.run(WorkerThread.java:40)
Caused by: java.lang.IllegalArgumentException: NAS-Identifier header.length=0
   at ru.bitel.bgbilling.kernel.network.radius.RadiusAttributeInfo.read(RadiusAttributeInfo.java:76)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusDictionary.parse(RadiusDictionary.java:517)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusDictionary.parseAttributes0(RadiusDictionary.java:607)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusDictionary.parseAttributes(RadiusDictionary.java:585)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusPacket.parse(RadiusPacket.java:340)
   ... 8 more
10-17/23:07:26 ERROR [radiusListener-p-3-t-12] RadiusPacket - Error RADIUS packet: 010900EF2B2961B65C847CAC93EF3655D0E0FAD3200204060A0113A15012E30DE51FC5A253DE33A7FD344E57B6272C0D383933363034392D4C2D310506000000013D06000000050606000000020706000000011F021E025705656D311A0B000030350C054C2D31400600000001410600000001430E3139322E3136382E31362E31420F3139322E3136382E31362E3131010D746573745F7470313032341A18000001370B12BB1E68586B89A81408C15B5CC1CBFFA21A3A000001371934010002ED9BE135753769AB7D8D0B37999B680000000000000000F661F3DE77976AD2F2ABF49070AFFFF8C9A9C95BE51B44D0
10-17/23:07:26 ERROR [radiusListener-p-3-t-12] RadiusListenerWorker - java.lang.IllegalArgumentException: NAS-Identifier header.length=0
ru.bitel.bgbilling.common.BGException: java.lang.IllegalArgumentException: NAS-Identifier header.length=0
   at ru.bitel.bgbilling.kernel.network.radius.RadiusPacket.parse(RadiusPacket.java:346)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusPacket.parse(RadiusPacket.java:313)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusListenerWorker.processPacket(RadiusListenerWorker.java:98)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusListenerWorker.runImpl(RadiusListenerWorker.java:87)
   at ru.bitel.common.worker.WorkerTask.run(WorkerTask.java:74)
   at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)
   at ru.bitel.common.worker.WorkerThread.run(WorkerThread.java:40)
Caused by: java.lang.IllegalArgumentException: NAS-Identifier header.length=0
   at ru.bitel.bgbilling.kernel.network.radius.RadiusAttributeInfo.read(RadiusAttributeInfo.java:76)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusDictionary.parse(RadiusDictionary.java:517)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusDictionary.parseAttributes0(RadiusDictionary.java:607)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusDictionary.parseAttributes(RadiusDictionary.java:585)
   at ru.bitel.bgbilling.kernel.network.radius.RadiusPacket.parse(RadiusPacket.java:340)
   ... 8 more



вот такая ересь в логах и соответственно авторизация не работает
Автор:  FessAectan [ 18 окт 2011, 10:19 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
Если же оставить версию 5.0 то авторизация работает, но на 200-300 абонентов, дальше начинает утекать память и перестает авторизировать.
Автор:  Amir [ 19 окт 2011, 00:42 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
Цитата:
ru.bitel.bgbilling.common.BGException: java.lang.IllegalArgumentException: NAS-Identifier header.length=0

Исправлено
Автор:  FessAectan [ 19 окт 2011, 09:16 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
Amir писал(а):
Цитата:
ru.bitel.bgbilling.common.BGException: java.lang.IllegalArgumentException: NAS-Identifier header.length=0

Исправлено

Это исправлено, но воз и ныне там, теперь в логах следующее

Код:
10-19/09:50:05  INFO [radiusListener-p-3-t-8] RadiusListenerWorker - REQUEST:
Packet type: Access-Request
Identifier: 147
Authenticator: {D6 46 07 A5 F4 5D 76 1B 72 2A F8 67 E7 1B C6 B6}
Attributes:
  User-Name=test_tp1024
  NAS-Identifier=
  NAS-IP-Address=10.1.19.161
  Tunnel-Type={00 00 00 01}
  NAS-Port=1
  Tunnel-Medium-Type={00 00 00 01}
  Tunnel-Client-Endpoint={31 39 32 2E 31 36 38 2E 31 36 2E 31 31}
  Service-Type=2
  Tunnel-Server-Endpoint={31 39 32 2E 31 36 38 2E 31 36 2E 31}
  Framed-Protocol=1
  Acct-Session-Id=9017645-L-1
  NAS-Port-Id=em1
  Message-Authenticator=�d6�Z�<�?��.�U��
  NAS-Port-Type=5
  Calling-Station-Id=
  Called-Station-Id=
  mpd-link=L-1
  MS-CHAP2-Response=�y{�
�(H���?�G               ����
         �����g��:�S�Y
  MS-CHAP-Challenge=�h�|��f�<���G

10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream - java.lang.ClassCastException: [B cannot be cast to java.lang.Integer
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.info.IntegerInfo.wrapValue(IntegerInfo.java:1)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.tlv.Tlv.<init>(Tlv.java:36)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.RadiusAttribute.<init>(RadiusAttribute.java:39)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.RadiusAttribute.<init>(RadiusAttribute.java:51)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.MSUtils.addMppeKeys(MSUtils.java:268)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.MSUtils.checkMSChapV2Password(MSUtils.java:502)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.MSUtils.checkMSChapV2Password(MSUtils.java:432)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.RadiusUtils.checkPassword(RadiusUtils.java:545)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.RadiusSession.checkPassword(RadiusSession.java:119)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.AbstractRadiusProcessor.authenticationImpl(AbstractRadiusProcessor.java:380)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.modules.dialup.radius.DialUpRadiusProcessor.authenticationImpl(DialUpRadiusProcessor.java:589)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.modules.dialup.radius.DialUpRadiusProcessor.authenticationImpl(DialUpRadiusProcessor.java:1)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.AbstractRadiusProcessor.authentication(AbstractRadiusProcessor.java:198)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.RadiusSession.authentication(RadiusSession.java:114)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.RadiusSession.accessRequest(RadiusSession.java:92)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.RadiusProcessor.accessRequestImpl(RadiusProcessor.java:360)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.AbstractRadiusProcessor.accessRequestImpl(AbstractRadiusProcessor.java:182)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.RadiusProcessor.accessRequest(RadiusProcessor.java:347)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.RadiusListenerWorker.accessRequest(RadiusListenerWorker.java:289)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.RadiusListenerWorker.processPacket(RadiusListenerWorker.java:163)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.bgbilling.kernel.network.radius.RadiusListenerWorker.runImpl(RadiusListenerWorker.java:87)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.common.worker.WorkerTask.run(WorkerTask.java:74)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at java.lang.Thread.run(Thread.java:662)
10-19/09:50:05 ERROR [radiusListener-p-3-t-8] LoggingPrintStream -    at ru.bitel.common.worker.WorkerThread.run(WorkerThread.java:40)
10-19/09:50:05  INFO [radiusListener-p-3-t-8] RadiusListenerWorker - RESPONSE:
Packet type: Access-Reject
Identifier: 147
Authenticator: {2B 41 45 FE 67 F0 62 9F 54 62 1F 5C 46 4B 11 B2}
Attributes:
  Reply-Message=2
  Message-Authenticator=
  MS-MPPE-Recv-Key=��3�L�
�+Ӕ˴v?��Ԭ=�              �Ih=1,�
  MS-MPPE-Send-Key=��WV�3�vR�z�Y&08pCJ��
                                        7�
                                          Ё
  MS-MPPE-Encryption-Types=4
  MS-CHAP2-Success=?S=0B450BA23A0A26BD42A02FA8FCCE825AED837BF1

Process time auth: 75


У клиента так же 691, в логах NAS'а так же статус busy.
Автор:  Amir [ 19 окт 2011, 12:59 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
У вас dictionary.xml из 5.2 или свой?
Похоже что у вас в dictionary MS-MPPE-Encryption-Policy integer, а в том, что с 5.2 идет - octets, и при добавлении использовались octets.
Выложили обновление, чтобы MS-MPPE-Encryption-Policy добавлялся в зависимости от того, что в dictionary.
Автор:  FessAectan [ 19 окт 2011, 14:59 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
словарь из архива, не свой.
Истина уже где-то близко, теперь лог выглядит так



Код:
10-19/15:58:48  INFO [radiusListener-p-3-t-8] RadiusListenerWorker - REQUEST:
Packet type: Access-Request
Identifier: 133
Authenticator: {F6 56 BA 65 A1 C6 57 D6 13 CB 4F 40 1A D0 E6 A1}
Attributes:
  User-Name=test_tp1024
  NAS-Identifier=
  NAS-IP-Address=10.1.19.161
  Tunnel-Type={00 00 00 01}
  NAS-Port=1
  Tunnel-Medium-Type={00 00 00 01}
  Tunnel-Client-Endpoint={31 39 32 2E 31 36 38 2E 31 36 2E 31 30}
  Service-Type=2
  Tunnel-Server-Endpoint={31 39 32 2E 31 36 38 2E 31 36 2E 31}
  Framed-Protocol=1
  Acct-Session-Id=9039763-L-1
  NAS-Port-Id=re1
  Message-Authenticator=Wi�����iOE�
  NAS-Port-Type=5
  Calling-Station-Id=
  Tunnel-Client-Auth-ID={6C 6F 63 61 6C}
  Called-Station-Id=
  mpd-link=L-1
  MS-CHAP2-Response=��X�aW7rS���3J-��H���Q�ހM*ݖ�h�l?���
  MS-CHAP-Challenge=�hl   .�;��y   U_

10-19/15:58:48 ERROR [radiusListener-p-3-t-8] DialUpNasConnection - Stop without start!
10-19/15:58:48  INFO [radiusListener-p-3-t-8] RadiusListenerWorker - RESPONSE:
Packet type: Access-Accept
Identifier: 133
Authenticator: {0C 67 5F 6F 9C 4E C5 85 2F 70 9A 21 01 C7 74 37}
Attributes:
  Acct-Interim-Interval=10
  Message-Authenticator=
  Service-Type=2
  Framed-Protocol=1
  Framed-IP-Address=1.1.1.1
  mpd-filter=1#1=match dst net 2.2.2.2/21 or dst net 10.8.25.0/24
  mpd-filter=2#1=match src net 2.2.2.2/21 or src net 10.8.25.0/24
  mpd-limit=in#1=flt1 pass
  mpd-limit=in#2=all rate-limit 20480000 3840000 7680000 pass
  mpd-limit=out#1=flt2 pass
  mpd-limit=out#2=all rate-limit 20480000 3840000 7680000 pass
  MS-MPPE-Recv-Key=�P{>1/rMd�
                             �t���c�i��`��5x_��{-�
  MS-MPPE-Send-Key=�I��������G��������e`v=fdR
  MS-MPPE-Encryption-Policy=1
  MS-MPPE-Encryption-Types=4
  MS-CHAP2-Success=?S=03FA2395B3379D2E628AF139C9129FFDD4E07A43

Process time auth: 25

10-19/15:58:48  INFO [radiusListener-p-3-t-9] RadiusListenerWorker - REQUEST:
Packet type: Access-Request
Identifier: 133
Authenticator: {F6 56 BA 65 A1 C6 57 D6 13 CB 4F 40 1A D0 E6 A1}
Attributes:
  User-Name=test_tp1024
  NAS-Identifier=
  NAS-IP-Address=10.1.19.161
  Tunnel-Type={00 00 00 01}
  NAS-Port=1
  Tunnel-Medium-Type={00 00 00 01}
  Tunnel-Client-Endpoint={31 39 32 2E 31 36 38 2E 31 36 2E 31 30}
  Service-Type=2
  Tunnel-Server-Endpoint={31 39 32 2E 31 36 38 2E 31 36 2E 31}
  Framed-Protocol=1
  Acct-Session-Id=9039763-L-1
  NAS-Port-Id=re1
  Message-Authenticator=����=!   �E�e�P�
  NAS-Port-Type=5
  Calling-Station-Id=
  Tunnel-Client-Auth-ID={6C 6F 63 61 6C}
  Called-Station-Id=
  mpd-link=L-1
  MS-CHAP2-Response=��X�aW7rS���3J-��H���Q�ހM*ݖ�h�l?���
  MS-CHAP-Challenge=�hl   .�;��y   U_

^[[?1;2c10-19/15:58:48 ERROR [radiusListener-p-3-t-9] DialUpNasConnection - Stop without start!
10-19/15:58:48  INFO [radiusListener-p-3-t-9] RadiusListenerWorker - RESPONSE:
Packet type: Access-Accept
Identifier: 133
Authenticator: {5D 87 09 E2 9B 75 F1 63 FE BA AE 05 32 1E 71 DA}
Attributes:
  Acct-Interim-Interval=10
  Message-Authenticator=
  Service-Type=2
  Framed-Protocol=1
  Framed-IP-Address=1.1.1.1
  mpd-filter=1#1=match dst net 2.2.2.2/21 or dst net 10.8.25.0/24
  mpd-filter=2#1=match src net 2.2.2.2/21 or src net 10.8.25.0/24
  mpd-limit=in#1=flt1 pass
  mpd-limit=in#2=all rate-limit 20480000 3840000 7680000 pass
  mpd-limit=out#1=flt2 pass
  mpd-limit=out#2=all rate-limit 20480000 3840000 7680000 pass
  MS-MPPE-Recv-Key=����V"[�!P�HL�S)뤕*tA���
  MS-MPPE-Send-Key=ЁuI���J�
                           ̒�ܱD���C�o����
  MS-MPPE-Encryption-Policy=1
  MS-MPPE-Encryption-Types=4
  MS-CHAP2-Success=?S=03FA2395B3379D2E628AF139C9129FFDD4E07A43

Process time auth: 56
Автор:  Amir [ 19 окт 2011, 15:16 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
У клиента ошибка или он подключается при этом?
Автор:  FessAectan [ 19 окт 2011, 15:23 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
Так же 691... =(
Автор:  Amir [ 19 окт 2011, 16:01 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
FessAectan писал(а):
MS-MPPE-Recv-Key=����V"[�!P�HL�S)뤕*tA���
У вас точно радиус 5.2 без старых библиотек? Сейчас бинарные атрибуты в лог распечатываются как {01 02 03 04 ...}

А если не MSCHAPv2, а CHAP или PAP?
Автор:  FessAectan [ 19 окт 2011, 16:15 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
Заново скачал с ftp, обновил, лог выглядит вот так
Авторизация не проходит, с pap/chap/ms-chap сейчас поиграюсь

Поигрался, авторизация никак не проходит
Код:
Process time auth: 52

10-19/17:16:59  INFO [radiusListener-p-3-t-5] RadiusListenerWorker - REQUEST:
Packet type: Access-Request
Identifier: 70
Authenticator: {58 59 19 3C 50 66 2F B6 16 7E EF EA E3 31 DE C4}
Attributes:
  User-Name=test_tp1024
  NAS-Identifier=
  NAS-IP-Address=10.1.19.161
  Tunnel-Type:0=1
  NAS-Port=1
  Tunnel-Medium-Type:0=1
  Tunnel-Client-Endpoint=192.168.16.11
  Service-Type=2
  Tunnel-Server-Endpoint=192.168.16.1
  Framed-Protocol=1
  Acct-Session-Id=9044454-L-1
  NAS-Port-Id=re1
  Message-Authenticator={0D 65 DF 69 E2 A8 67 EF 4C F2 28 08 88 DF CF 7D}
  NAS-Port-Type=5
  Calling-Station-Id=
  Called-Station-Id=
  mpd-link=L-1
  MS-CHAP2-Response={01 00 35 31 6C DF 13 CA 71 C8 ED 20 4D CC 2B B4 9D FF 00 00 00 00 00 00 00 00 08 E7 48 92 1F E5 D3 B3 3C 96 FF 9D DD 1C CF 91 30 8A 41 5D 8A C1 E8 B5}
  MS-CHAP-Challenge={BB 1E 68 73 8F 0A BE 1F 63 94 FA 54 98 D3 C3 F2}

10-19/17:16:59 ERROR [radiusListener-p-3-t-5] DialUpNasConnection - Stop without start!
10-19/17:16:59  INFO [radiusListener-p-3-t-5] RadiusListenerWorker - RESPONSE:
Packet type: Access-Accept
Identifier: 70
Authenticator: {64 AF 37 39 E4 B9 78 C4 AE 4E A1 5F 9E 0F B7 0A}
Attributes:
  Acct-Interim-Interval=10
  Message-Authenticator={00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
  Service-Type=2
  Framed-Protocol=1
  Framed-IP-Address=1.1.1.1
  mpd-filter=1#1=match dst net 1.1.1.1/21 or dst net 10.8.25.0/24
  mpd-filter=2#1=match src net 1.1.1.1/21 or src net 10.8.25.0/24
  mpd-limit=in#1=flt1 pass
  mpd-limit=in#2=all rate-limit 20480000 3840000 7680000 pass
  mpd-limit=out#1=flt2 pass
  mpd-limit=out#2=all rate-limit 20480000 3840000 7680000 pass
  MS-MPPE-Recv-Key={A3 38 87 C0 CE 24 99 A2 7D D0 B4 5C B4 31 D1 0A FA AC B1 FC ED 7D D8 1D F6 AF 60 66 3E 16 49 91 53 22}
  MS-MPPE-Send-Key={D7 62 96 3B BF 82 FD B3 BC 92 55 98 92 AB 6F 8C 7E 7C 32 47 A3 11 D8 DF 38 BE 8E 8C F2 78 7A 69 26 E4}
  MS-MPPE-Encryption-Policy={00 00 00 01}
  MS-MPPE-Encryption-Types={00 00 00 04}
  MS-CHAP2-Success={3F 53 3D 37 46 37 33 39 39 32 31 43 42 31 30 35 32 37 35 33 45 36 43 38 42 41 32 35 46 39 43 43 33 45 42 38 42 33 43 45 46 37 31}

Process time auth: 25

10-19/17:16:59  INFO [radiusListener-p-3-t-6] RadiusListenerWorker - REQUEST:
Packet type: Access-Request
Identifier: 70
Authenticator: {58 59 19 3C 50 66 2F B6 16 7E EF EA E3 31 DE C4}
Attributes:
  User-Name=test_tp1024
  NAS-Identifier=
  NAS-IP-Address=10.1.19.161
  Tunnel-Type:0=1
  NAS-Port=1
  Tunnel-Medium-Type:0=1
  Tunnel-Client-Endpoint=192.168.16.11
  Service-Type=2
  Tunnel-Server-Endpoint=192.168.16.1
  Framed-Protocol=1
  Acct-Session-Id=9044454-L-1
  NAS-Port-Id=re1
  Message-Authenticator={D8 D8 A5 ED 7A F2 6D 1B C4 A1 BB 2F CD 93 4F B4}
  NAS-Port-Type=5
  Calling-Station-Id=
  Called-Station-Id=
  mpd-link=L-1
  MS-CHAP2-Response={01 00 35 31 6C DF 13 CA 71 C8 ED 20 4D CC 2B B4 9D FF 00 00 00 00 00 00 00 00 08 E7 48 92 1F E5 D3 B3 3C 96 FF 9D DD 1C CF 91 30 8A 41 5D 8A C1 E8 B5}
  MS-CHAP-Challenge={BB 1E 68 73 8F 0A BE 1F 63 94 FA 54 98 D3 C3 F2}

10-19/17:16:59 ERROR [radiusListener-p-3-t-6] DialUpNasConnection - Stop without start!
10-19/17:16:59  INFO [radiusListener-p-3-t-6] RadiusListenerWorker - RESPONSE:
Packet type: Access-Accept
Identifier: 70
Authenticator: {0C AA 22 C9 52 42 D8 FF 40 BE E8 80 30 F6 C5 8F}
Attributes:
  Acct-Interim-Interval=10
  Message-Authenticator={00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
  Service-Type=2
  Framed-Protocol=1
  Framed-IP-Address=1.1.1.1
  mpd-filter=1#1=match dst net 1.1.1.1 or dst net 10.8.25.0/24
  mpd-filter=2#1=match src net 1.1.1.1 or src net 10.8.25.0/24
  mpd-limit=in#1=flt1 pass
  mpd-limit=in#2=all rate-limit 20480000 3840000 7680000 pass
  mpd-limit=out#1=flt2 pass
  mpd-limit=out#2=all rate-limit 20480000 3840000 7680000 pass
  MS-MPPE-Recv-Key={BE EB D9 DE B0 84 2F AB 95 2B 3C 56 14 98 FF 80 DD 7F 00 FF A0 6A 1C 00 F5 10 EF AA 53 19 D5 22 88 50}
  MS-MPPE-Send-Key={AC FE 5F FF F4 5C 1E 56 0A D3 90 67 8B E4 90 89 0D 4F C8 4E 39 A9 D6 77 90 17 75 3E 8D 8B BC FB 3D AD}
  MS-MPPE-Encryption-Policy={00 00 00 01}
  MS-MPPE-Encryption-Types={00 00 00 04}
  MS-CHAP2-Success={3F 53 3D 37 46 37 33 39 39 32 31 43 42 31 30 35 32 37 35 33 45 36 43 38 42 41 32 35 46 39 43 43 33 45 42 38 42 33 43 45 46 37 31}

Process time auth: 70
Автор:  Amir [ 19 окт 2011, 16:30 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
А в логах mpd можете посмотреть, почему ему Accept не нравится?
Код MSCHAPv2 от 5.1 еще немного отличается, а CHAP и PAP - нет, и, насколько знаю, у нескольких клиентов dialup радиус 5.2 нормально работает сейчас.
Автор:  FessAectan [ 19 окт 2011, 16:34 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
Лог с mpd5, это без дебага, сейчас включу дебаг выложу.
Код:
 Oct 19 17:33:13  mpd: [L-1] Accepting PPTP connection
Oct 19 17:33:13  mpd: [L-1] Link: OPEN event
Oct 19 17:33:13  mpd: [L-1] LCP: Open event
Oct 19 17:33:13  mpd: [L-1] LCP: state change Initial --> Starting
Oct 19 17:33:13  mpd: [L-1] LCP: LayerStart
Oct 19 17:33:13  mpd: [L-1] PPTP: attaching to peer's outgoing call
Oct 19 17:33:13  mpd: [L-1] Link: UP event
Oct 19 17:33:13  mpd: [L-1] LCP: Up event
Oct 19 17:33:13  mpd: [L-1] LCP: state change Starting --> Req-Sent
Oct 19 17:33:13  mpd: [L-1] LCP: SendConfigReq #1
Oct 19 17:33:13  mpd: [L-1]   ACFCOMP
Oct 19 17:33:13  mpd: [L-1]   PROTOCOMP
Oct 19 17:33:13  mpd: [L-1]   MRU 1500
Oct 19 17:33:13  mpd: [L-1]   MAGICNUM a4a3a462
Oct 19 17:33:13  mpd: [L-1]   AUTHPROTO CHAP MSOFTv2
Oct 19 17:33:13  mpd: [L-1]   MP MRRU 2048
Oct 19 17:33:13  mpd: [L-1]   MP SHORTSEQ
Oct 19 17:33:13  mpd: [L-1]   ENDPOINTDISC [802.1] 00 16 3e 00 0e b1
Oct 19 17:33:13  mpd: [L-1] LCP: rec'd Configure Request #0 (Req-Sent)
Oct 19 17:33:13  mpd: [L-1]   MRU 1400
Oct 19 17:33:13  mpd: [L-1]   MAGICNUM 78256378
Oct 19 17:33:13  mpd: [L-1]   PROTOCOMP
Oct 19 17:33:13  mpd: [L-1]   ACFCOMP
Oct 19 17:33:13  mpd: [L-1]   CALLBACK 6
Oct 19 17:33:13  mpd: [L-1] LCP: SendConfigRej #0
Oct 19 17:33:13  mpd: [L-1]   CALLBACK 6
Oct 19 17:33:13  mpd: [L-1] LCP: rec'd Configure Request #1 (Req-Sent)
Oct 19 17:33:13  mpd: [L-1]   MRU 1400
Oct 19 17:33:13  mpd: [L-1]   MAGICNUM 78256378
Oct 19 17:33:13  mpd: [L-1]   PROTOCOMP
Oct 19 17:33:13  mpd: [L-1]   ACFCOMP
Oct 19 17:33:13  mpd: [L-1] LCP: SendConfigAck #1
Oct 19 17:33:13  mpd: [L-1]   MRU 1400
Oct 19 17:33:13  mpd: [L-1]   MAGICNUM 78256378
Oct 19 17:33:13  mpd: [L-1]   PROTOCOMP
Oct 19 17:33:13  mpd: [L-1]   ACFCOMP
Oct 19 17:33:13  mpd: [L-1] LCP: state change Req-Sent --> Ack-Sent
Oct 19 17:33:15  mpd: [L-1] LCP: SendConfigReq #2
Oct 19 17:33:15  mpd: [L-1]   ACFCOMP
Oct 19 17:33:15  mpd: [L-1]   PROTOCOMP
Oct 19 17:33:15  mpd: [L-1]   MRU 1500
Oct 19 17:33:15  mpd: [L-1]   MAGICNUM a4a3a462
Oct 19 17:33:15  mpd: [L-1]   AUTHPROTO CHAP MSOFTv2
Oct 19 17:33:15  mpd: [L-1]   MP MRRU 2048
Oct 19 17:33:15  mpd: [L-1]   MP SHORTSEQ
Oct 19 17:33:15  mpd: [L-1]   ENDPOINTDISC [802.1] 00 16 3e 00 0e b1
Oct 19 17:33:15  mpd: [L-1] LCP: rec'd Configure Reject #2 (Ack-Sent)
Oct 19 17:33:15  mpd: [L-1]   MP MRRU 2048
Oct 19 17:33:15  mpd: [L-1]   MP SHORTSEQ
Oct 19 17:33:15  mpd: [L-1]   ENDPOINTDISC [802.1] 00 16 3e 00 0e b1
Oct 19 17:33:15  mpd: [L-1] LCP: SendConfigReq #3
Oct 19 17:33:15  mpd: [L-1]   ACFCOMP
Oct 19 17:33:15  mpd: [L-1]   PROTOCOMP
Oct 19 17:33:15  mpd: [L-1]   MRU 1500
Oct 19 17:33:15  mpd: [L-1]   MAGICNUM a4a3a462
Oct 19 17:33:15  mpd: [L-1]   AUTHPROTO CHAP MSOFTv2
Oct 19 17:33:15  mpd: [L-1] LCP: rec'd Configure Ack #3 (Ack-Sent)
Oct 19 17:33:15  mpd: [L-1]   ACFCOMP
Oct 19 17:33:15  mpd: [L-1]   PROTOCOMP
Oct 19 17:33:15  mpd: [L-1]   MRU 1500
Oct 19 17:33:15  mpd: [L-1]   MAGICNUM a4a3a462
Oct 19 17:33:15  mpd: [L-1]   AUTHPROTO CHAP MSOFTv2
Oct 19 17:33:15  mpd: [L-1] LCP: state change Ack-Sent --> Opened
Oct 19 17:33:15  mpd: [L-1] LCP: auth: peer wants nothing, I want CHAP
Oct 19 17:33:15  mpd: [L-1] CHAP: sending CHALLENGE #1 len: 21
Oct 19 17:33:15  mpd: [L-1] LCP: LayerUp
Oct 19 17:33:15  mpd: [L-1] LCP: rec'd Ident #2 (Opened)
Oct 19 17:33:15  mpd: [L-1]   MESG: MSRASV5.10
Oct 19 17:33:15  mpd: [L-1] LCP: rec'd Ident #3 (Opened)
Oct 19 17:33:15  mpd: [L-1]   MESG: MSRAS-0-PHILKA
Oct 19 17:33:15  mpd: [L-1] CHAP: rec'd RESPONSE #1 len: 65
Oct 19 17:33:15  mpd: [L-1]   Name: "test_tp1024"
Oct 19 17:33:15  mpd: [L-1] AUTH: Trying RADIUS
Oct 19 17:33:15  mpd: [L-1] RADIUS: Authenticating user 'test_tp1024'
Oct 19 17:33:15  mpd: [L-1] RADIUS: rad_send_request for user 'test_tp1024' failed: No valid RADIUS responses received
Oct 19 17:33:15  mpd: [L-1] AUTH: RADIUS returned error
Oct 19 17:33:15  mpd: [L-1] AUTH: Trying INTERNAL
Oct 19 17:33:15  mpd: OpenConfFile: Can't open file '/usr/local/etc/mpd5/mpd.secret': No such file or directory
Oct 19 17:33:15  mpd: [L-1] AUTH: User "test_tp1024" not found in secret file
Oct 19 17:33:15  mpd: [L-1] AUTH: INTERNAL returned: failed
Oct 19 17:33:15  mpd: [L-1] AUTH: ran out of backends
Oct 19 17:33:15  mpd: [L-1] CHAP: Auth return status: failed
Oct 19 17:33:15  mpd: [L-1] CHAP: Reply message: E=691 R=0 M=Login incorrect
Oct 19 17:33:15  mpd: [L-1] CHAP: sending FAILURE #1 len: 31
Oct 19 17:33:15  mpd: [L-1] LCP: authorization failed
Oct 19 17:33:15  mpd: [L-1] LCP: parameter negotiation failed
Oct 19 17:33:15  mpd: [L-1] LCP: state change Opened --> Stopping
Oct 19 17:33:15  mpd: [L-1] LCP: SendTerminateReq #4
Oct 19 17:33:15  mpd: [L-1] LCP: LayerDown
Oct 19 17:33:16  mpd: [L-1] LCP: rec'd Terminate Ack #4 (Stopping)
Oct 19 17:33:16  mpd: [L-1] LCP: state change Stopping --> Stopped
Oct 19 17:33:16  mpd: [L-1] LCP: LayerFinish
Oct 19 17:33:16  mpd: [L-1] PPTP call terminated
Oct 19 17:33:16  mpd: [L-1] Link: DOWN event
Oct 19 17:33:16  mpd: [L-1] LCP: Close event
Oct 19 17:33:16  mpd: [L-1] LCP: state change Stopped --> Closed
Oct 19 17:33:16  mpd: [L-1] LCP: Down event
Oct 19 17:33:16  mpd: [L-1] LCP: state change Closed --> Initial
Oct 19 17:33:16  mpd: [L-1] Link: SHUTDOWN event
Oct 19 17:33:16  mpd: [L-1] Link: Shutdown
Автор:  FessAectan [ 19 окт 2011, 16:43 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
Хотя... врядли с дебагом больше ясности стало

Код:
# cat /var/log/mpd.log
Oct 19 17:41:03  mpd: CONSOLE: Connect
Oct 19 17:41:03  mpd: CONSOLE: Allocated new console session 0x2866a008 from 192.168.16.1
Oct 19 17:41:16  mpd: [] CONSOLE: admin: set debug 5
Oct 19 17:41:17  mpd: [] CONSOLE: admin: exit
Oct 19 17:41:21  mpd: [L-1] Accepting PPTP connection
Oct 19 17:41:21  mpd: [L-1] Link: OPEN event
Oct 19 17:41:21  mpd: [L-1] LCP: Open event
Oct 19 17:41:21  mpd: [L-1] LCP: state change Initial --> Starting
Oct 19 17:41:21  mpd: [L-1] LCP: LayerStart
Oct 19 17:41:21  mpd: netgraph: SENDING MESSAGE:
Oct 19 17:41:21  mpd: netgraph: SOCKADDR: { fam=32 len=5 addr=".:" }
Oct 19 17:41:21  mpd: netgraph: NG_MESG :
Oct 19 17:41:21  mpd: netgraph:   vers   8
Oct 19 17:41:21  mpd: netgraph:   arglen 96
Oct 19 17:41:21  mpd: netgraph:   flags  0
Oct 19 17:41:21  mpd: netgraph:   token  64
Oct 19 17:41:21  mpd: netgraph:   cookie GENERIC (1137070366)
Oct 19 17:41:21  mpd: netgraph:   cmd    mkpeer (2)
Oct 19 17:41:21  mpd: netgraph:   args   { type="tee" ourhook="l1" peerhook="left2right" }
Oct 19 17:41:21  mpd: netgraph: SENDING MESSAGE:
Oct 19 17:41:21  mpd: netgraph: SOCKADDR: { fam=32 len=5 addr="l1" }
Oct 19 17:41:21  mpd: netgraph: NG_MESG :
Oct 19 17:41:21  mpd: netgraph:   vers   8
Oct 19 17:41:21  mpd: netgraph:   arglen 32
Oct 19 17:41:21  mpd: netgraph:   flags  0
Oct 19 17:41:21  mpd: netgraph:   token  66
Oct 19 17:41:21  mpd: netgraph:   cookie GENERIC (1137070366)
Oct 19 17:41:21  mpd: netgraph:   cmd    4
Oct 19 17:41:21  mpd: netgraph:   args (32 bytes)
Oct 19 17:41:21  mpd: netgraph: 0000:  6d 70 64 31 35 31 34 2d 4c 2d 31 2d 6c 74 00 08   mpd1514-L-1-lt..
Oct 19 17:41:21  mpd: netgraph: 0010:  be 00 00 00 55 cc ba 62 84 25 6d 28 00 00 00 00   ....U..b.%m(....
Oct 19 17:41:21  mpd: netgraph: SENDING MESSAGE:
Oct 19 17:41:21  mpd: netgraph: SOCKADDR: { fam=32 len=5 addr="l1" }
Oct 19 17:41:21  mpd: netgraph: NG_MESG :
Oct 19 17:41:21  mpd: netgraph:   vers   8
Oct 19 17:41:21  mpd: netgraph:   arglen 0
Oct 19 17:41:21  mpd: netgraph:   flags  0
Oct 19 17:41:21  mpd: netgraph:   token  67
Oct 19 17:41:21  mpd: netgraph:   cookie GENERIC (1137070366)
Oct 19 17:41:21  mpd: netgraph:   cmd    805306374
Oct 19 17:41:21  mpd: netgraph:   args (0 bytes)
Oct 19 17:41:21  mpd: netgraph: RECEIVED RESPONSE:
Oct 19 17:41:21  mpd: netgraph: SOCKADDR: { fam=32 len=16 addr="[df]:" }
Oct 19 17:41:21  mpd: netgraph: NG_MESG :
Oct 19 17:41:21  mpd: netgraph:   vers   8
Oct 19 17:41:21  mpd: netgraph:   arglen 72
Oct 19 17:41:21  mpd: netgraph:   flags  1
Oct 19 17:41:21  mpd: netgraph:   token  67
Oct 19 17:41:21  mpd: netgraph:   cookie GENERIC (1137070366)
Oct 19 17:41:21  mpd: netgraph:   cmd    nodeinfo (805306374)
Oct 19 17:41:21  mpd: netgraph:   args   { name="mpd1514-L-1-lt" type="tee" id=0xdf hooks=1 }
Oct 19 17:41:21  mpd: [L-1] PPTP: attaching to peer's outgoing call
Oct 19 17:41:21  mpd: netgraph: SENDING MESSAGE:
Oct 19 17:41:21  mpd: netgraph: SOCKADDR: { fam=32 len=8 addr="[df]:" }
Oct 19 17:41:21  mpd: netgraph: NG_MESG :
Oct 19 17:41:21  mpd: netgraph:   vers   8
Oct 19 17:41:21  mpd: netgraph:   arglen 96
Oct 19 17:41:21  mpd: netgraph:   flags  0
Oct 19 17:41:21  mpd: netgraph:   token  69
Oct 19 17:41:21  mpd: netgraph:   cookie GENERIC (1137070366)
Oct 19 17:41:21  mpd: netgraph:   cmd    mkpeer (2)
Oct 19 17:41:21  mpd: netgraph:   args   { type="pptpgre" ourhook="left" peerhook="session_b4ef" }
Oct 19 17:41:21  mpd: netgraph: SENDING MESSAGE:
Oct 19 17:41:21  mpd: netgraph: SOCKADDR: { fam=32 len=13 addr="[df]:.left" }
Oct 19 17:41:21  mpd: netgraph: NG_MESG :
Oct 19 17:41:21  mpd: netgraph:   vers   8
Oct 19 17:41:21  mpd: netgraph:   arglen 0
Oct 19 17:41:21  mpd: netgraph:   flags  0
Oct 19 17:41:21  mpd: netgraph:   token  71
Oct 19 17:41:21  mpd: netgraph:   cookie GENERIC (1137070366)
Oct 19 17:41:21  mpd: netgraph:   cmd    nodeinfo (805306374)
Oct 19 17:41:21  mpd: netgraph:   args   
Oct 19 17:41:21  mpd: netgraph: RECEIVED RESPONSE:
Oct 19 17:41:21  mpd: netgraph: SOCKADDR: { fam=32 len=16 addr="[e3]:" }
Oct 19 17:41:21  mpd: netgraph: NG_MESG :
Oct 19 17:41:21  mpd: netgraph:   vers   8
Oct 19 17:41:21  mpd: netgraph:   arglen 72
Oct 19 17:41:21  mpd: netgraph:   flags  1
Oct 19 17:41:21  mpd: netgraph:   token  71
Oct 19 17:41:21  mpd: netgraph:   cookie GENERIC (1137070366)
Oct 19 17:41:21  mpd: netgraph:   cmd    nodeinfo (805306374)
Oct 19 17:41:21  mpd: netgraph:   args   { type="pptpgre" id=0xe3 hooks=1 }
Oct 19 17:41:21  mpd: netgraph: SENDING MESSAGE:
Oct 19 17:41:21  mpd: netgraph: SOCKADDR: { fam=32 len=13 addr="[df]:.left" }
Oct 19 17:41:21  mpd: netgraph: NG_MESG :
Oct 19 17:41:21  mpd: netgraph:   vers   8
Oct 19 17:41:21  mpd: netgraph:   arglen 96
Oct 19 17:41:21  mpd: netgraph:   flags  0
Oct 19 17:41:21  mpd: netgraph:   token  74
Oct 19 17:41:21  mpd: netgraph:   cookie GENERIC (1137070366)
Oct 19 17:41:21  mpd: netgraph:   cmd    mkpeer (2)
Oct 19 17:41:21  mpd: netgraph:   args   { type="ksocket" ourhook="lower" peerhook="inet/raw/gre" }
Oct 19 17:41:21  mpd: netgraph: SENDING MESSAGE:
Oct 19 17:41:21  mpd: netgraph: SOCKADDR: { fam=32 len=19 addr="[df]:.left.lower" }
Oct 19 17:41:21  mpd: netgraph: NG_MESG :
Oct 19 17:41:21  mpd: netgraph:   vers   8
Oct 19 17:41:21  mpd: netgraph:   arglen 12
Oct 19 17:41:21  mpd: netgraph:   flags  0
Oct 19 17:41:21  mpd: netgraph:   token  76
Oct 19 17:41:21  mpd: netgraph:   cookie KSOCKET (942710669)
Oct 19 17:41:21  mpd: netgraph:   cmd    setopt (7)
Oct 19 17:41:21  mpd: netgraph:   args   { level=65535 name=4098 value=[ 1=0xc0 ] }
Oct 19 17:41:21  mpd: netgraph: SENDING MESSAGE:
Oct 19 17:41:21  mpd: netgraph: SOCKADDR: { fam=32 len=19 addr="[df]:.left.lower" }
Oct 19 17:41:21  mpd: netgraph: NG_MESG :
Oct 19 17:41:21  mpd: netgraph:   vers   8
Oct 19 17:41:21  mpd: netgraph:   arglen 16
Oct 19 17:41:21  mpd: netgraph:   flags  0
Oct 19 17:41:21  mpd: netgraph:   token  78
Oct 19 17:41:21  mpd: netgraph:   cookie KSOCKET (942710669)
Oct 19 17:41:21  mpd: netgraph:   cmd    bind (1)
Oct 19 17:41:21  mpd: netgraph:   args   inet/192.168.16.1
Oct 19 17:41:21  mpd: netgraph: SENDING MESSAGE:
Oct 19 17:41:21  mpd: netgraph: SOCKADDR: { fam=32 len=19 addr="[df]:.left.lower" }
Oct 19 17:41:21  mpd: netgraph: NG_MESG :
Oct 19 17:41:21  mpd: netgraph:   vers   8
Oct 19 17:41:21  mpd: netgraph:   arglen 16
Oct 19 17:41:21  mpd: netgraph:   flags  0
Oct 19 17:41:21  mpd: netgraph:   token  80
Oct 19 17:41:21  mpd: netgraph:   cookie KSOCKET (942710669)
Oct 19 17:41:21  mpd: netgraph:   cmd    connect (4)
Oct 19 17:41:21  mpd: netgraph:   args   inet/192.168.16.11
Oct 19 17:41:21  mpd: netgraph: SENDING MESSAGE:
Oct 19 17:41:21  mpd: netgraph: SOCKADDR: { fam=32 len=13 addr="[df]:.left" }
Oct 19 17:41:21  mpd: netgraph: NG_MESG :
Oct 19 17:41:21  mpd: netgraph:   vers   8
Oct 19 17:41:21  mpd: netgraph:   arglen 12
Oct 19 17:41:21  mpd: netgraph:   flags  0
Oct 19 17:41:21  mpd: netgraph:   token  82
Oct 19 17:41:21  mpd: netgraph:   cookie PPTPGRE (1082548365)
Oct 19 17:41:21  mpd: netgraph:   cmd    setconfig (1)
Oct 19 17:41:21  mpd: netgraph:   args   { enabled=1 enableDelayedAck=1 cid=0xb4ef peerCid=0x8000 recvWin=64 }
Oct 19 17:41:21  mpd: [L-1] Link: UP event
Oct 19 17:41:21  mpd: [L-1] LCP: Up event
Oct 19 17:41:21  mpd: [L-1] LCP: state change Starting --> Req-Sent
Oct 19 17:41:21  mpd: [L-1] LCP: SendConfigReq #1
Oct 19 17:41:21  mpd: [L-1]   ACFCOMP
Oct 19 17:41:21  mpd: [L-1]   PROTOCOMP
Oct 19 17:41:21  mpd: [L-1]   MRU 1500
Oct 19 17:41:21  mpd: [L-1]   MAGICNUM e717ed94
Oct 19 17:41:21  mpd: [L-1]   AUTHPROTO CHAP MSOFTv2
Oct 19 17:41:21  mpd: [L-1]   MP MRRU 2048
Oct 19 17:41:21  mpd: [L-1]   MP SHORTSEQ
Oct 19 17:41:21  mpd: [L-1]   ENDPOINTDISC [802.1] 00 16 3e 00 0e b1
Oct 19 17:41:21  mpd: [L-1] LCP: rec'd Configure Request #0 (Req-Sent)
Oct 19 17:41:21  mpd: [L-1]   MRU 1400
Oct 19 17:41:21  mpd: [L-1]   MAGICNUM 40305503
Oct 19 17:41:21  mpd: [L-1]   PROTOCOMP
Oct 19 17:41:21  mpd: [L-1]   ACFCOMP
Oct 19 17:41:21  mpd: [L-1]   CALLBACK 6
Oct 19 17:41:21  mpd: [L-1] LCP: SendConfigRej #0
Oct 19 17:41:21  mpd: [L-1]   CALLBACK 6
Oct 19 17:41:21  mpd: [L-1] LCP: rec'd Configure Request #1 (Req-Sent)
Oct 19 17:41:21  mpd: [L-1]   MRU 1400
Oct 19 17:41:21  mpd: [L-1]   MAGICNUM 40305503
Oct 19 17:41:21  mpd: [L-1]   PROTOCOMP
Oct 19 17:41:21  mpd: [L-1]   ACFCOMP
Oct 19 17:41:21  mpd: [L-1] LCP: SendConfigAck #1
Oct 19 17:41:21  mpd: [L-1]   MRU 1400
Oct 19 17:41:21  mpd: [L-1]   MAGICNUM 40305503
Oct 19 17:41:21  mpd: [L-1]   PROTOCOMP
Oct 19 17:41:21  mpd: [L-1]   ACFCOMP
Oct 19 17:41:21  mpd: [L-1] LCP: state change Req-Sent --> Ack-Sent
Oct 19 17:41:23  mpd: [L-1] LCP: SendConfigReq #2
Oct 19 17:41:23  mpd: [L-1]   ACFCOMP
Oct 19 17:41:23  mpd: [L-1]   PROTOCOMP
Oct 19 17:41:23  mpd: [L-1]   MRU 1500
Oct 19 17:41:23  mpd: [L-1]   MAGICNUM e717ed94
Oct 19 17:41:23  mpd: [L-1]   AUTHPROTO CHAP MSOFTv2
Oct 19 17:41:23  mpd: [L-1]   MP MRRU 2048
Oct 19 17:41:23  mpd: [L-1]   MP SHORTSEQ
Oct 19 17:41:23  mpd: [L-1]   ENDPOINTDISC [802.1] 00 16 3e 00 0e b1
Oct 19 17:41:23  mpd: [L-1] LCP: rec'd Configure Reject #2 (Ack-Sent)
Oct 19 17:41:23  mpd: [L-1]   MP MRRU 2048
Oct 19 17:41:23  mpd: [L-1]   MP SHORTSEQ
Oct 19 17:41:23  mpd: [L-1]   ENDPOINTDISC [802.1] 00 16 3e 00 0e b1
Oct 19 17:41:23  mpd: [L-1] LCP: SendConfigReq #3
Oct 19 17:41:23  mpd: [L-1]   ACFCOMP
Oct 19 17:41:23  mpd: [L-1]   PROTOCOMP
Oct 19 17:41:23  mpd: [L-1]   MRU 1500
Oct 19 17:41:23  mpd: [L-1]   MAGICNUM e717ed94
Oct 19 17:41:23  mpd: [L-1]   AUTHPROTO CHAP MSOFTv2
Oct 19 17:41:23  mpd: [L-1] LCP: rec'd Configure Ack #3 (Ack-Sent)
Oct 19 17:41:23  mpd: [L-1]   ACFCOMP
Oct 19 17:41:23  mpd: [L-1]   PROTOCOMP
Oct 19 17:41:23  mpd: [L-1]   MRU 1500
Oct 19 17:41:23  mpd: [L-1]   MAGICNUM e717ed94
Oct 19 17:41:23  mpd: [L-1]   AUTHPROTO CHAP MSOFTv2
Oct 19 17:41:23  mpd: [L-1] LCP: state change Ack-Sent --> Opened
Oct 19 17:41:23  mpd: [L-1] LCP: auth: peer wants nothing, I want CHAP
Oct 19 17:41:23  mpd: [L-1] CHAP: sending CHALLENGE #1 len: 21
Oct 19 17:41:23  mpd: [L-1] LCP: LayerUp
Oct 19 17:41:23  mpd: [L-1] LCP: rec'd Ident #2 (Opened)
Oct 19 17:41:23  mpd: [L-1]   MESG: MSRASV5.10
Oct 19 17:41:23  mpd: [L-1] LCP: rec'd Ident #3 (Opened)
Oct 19 17:41:23  mpd: [L-1]   MESG: MSRAS-0-PHILKA
Oct 19 17:41:23  mpd: [L-1] CHAP: rec'd RESPONSE #1 len: 65
Oct 19 17:41:23  mpd: [L-1]   Name: "test_tp1024"
Oct 19 17:41:23  mpd: [L-1] AUTH: Trying RADIUS
Oct 19 17:41:23  mpd: [L-1] RADIUS: Authenticating user 'test_tp1024'
Oct 19 17:41:23  mpd: [L-1] RADIUS: rad_send_request for user 'test_tp1024' failed: No valid RADIUS responses received
Oct 19 17:41:23  mpd: [L-1] AUTH: RADIUS returned error
Oct 19 17:41:23  mpd: [L-1] AUTH: Trying INTERNAL
Oct 19 17:41:23  mpd: OpenConfFile: Can't open file '/usr/local/etc/mpd5/mpd.secret': No such file or directory
Oct 19 17:41:23  mpd: [L-1] AUTH: User "test_tp1024" not found in secret file
Oct 19 17:41:23  mpd: [L-1] AUTH: INTERNAL returned: failed
Oct 19 17:41:23  mpd: [L-1] AUTH: ran out of backends
Oct 19 17:41:23  mpd: [L-1] CHAP: Auth return status: failed
Oct 19 17:41:23  mpd: [L-1] CHAP: Reply message: E=691 R=0 M=Login incorrect
Oct 19 17:41:23  mpd: [L-1] CHAP: sending FAILURE #1 len: 31
Oct 19 17:41:23  mpd: [L-1] LCP: authorization failed
Oct 19 17:41:23  mpd: [L-1] LCP: parameter negotiation failed
Oct 19 17:41:23  mpd: [L-1] LCP: state change Opened --> Stopping
Oct 19 17:41:23  mpd: [L-1] LCP: SendTerminateReq #4
Oct 19 17:41:23  mpd: [L-1] LCP: LayerDown
Oct 19 17:41:23  mpd: [L-1] LCP: rec'd Terminate Ack #4 (Stopping)
Oct 19 17:41:23  mpd: [L-1] LCP: state change Stopping --> Stopped
Oct 19 17:41:23  mpd: [L-1] LCP: LayerFinish
Oct 19 17:41:23  mpd: netgraph: SENDING MESSAGE:
Oct 19 17:41:23  mpd: netgraph: SOCKADDR: { fam=32 len=5 addr="l1" }
Oct 19 17:41:23  mpd: netgraph: NG_MESG :
Oct 19 17:41:23  mpd: netgraph:   vers   8
Oct 19 17:41:23  mpd: netgraph:   arglen 0
Oct 19 17:41:23  mpd: netgraph:   flags  0
Oct 19 17:41:23  mpd: netgraph:   token  84
Oct 19 17:41:23  mpd: netgraph:   cookie GENERIC (1137070366)
Oct 19 17:41:23  mpd: netgraph:   cmd    1
Oct 19 17:41:23  mpd: netgraph:   args (0 bytes)
Oct 19 17:41:23  mpd: [L-1] PPTP call terminated
Oct 19 17:41:23  mpd: netgraph: SENDING MESSAGE:
Oct 19 17:41:23  mpd: netgraph: SOCKADDR: { fam=32 len=8 addr="[e3]:" }
Oct 19 17:41:23  mpd: netgraph: NG_MESG :
Oct 19 17:41:23  mpd: netgraph:   vers   8
Oct 19 17:41:23  mpd: netgraph:   arglen 0
Oct 19 17:41:23  mpd: netgraph:   flags  0
Oct 19 17:41:23  mpd: netgraph:   token  85
Oct 19 17:41:23  mpd: netgraph:   cookie GENERIC (1137070366)
Oct 19 17:41:23  mpd: netgraph:   cmd    shutdown (1)
Oct 19 17:41:23  mpd: netgraph:   args   
Oct 19 17:41:23  mpd: [L-1] Link: DOWN event
Oct 19 17:41:23  mpd: [L-1] LCP: Close event
Oct 19 17:41:23  mpd: [L-1] LCP: state change Stopped --> Closed
Oct 19 17:41:23  mpd: [L-1] LCP: Down event
Oct 19 17:41:23  mpd: [L-1] LCP: state change Closed --> Initial
Oct 19 17:41:23  mpd: [L-1] Link: SHUTDOWN event
Oct 19 17:41:23  mpd: [L-1] Link: Shutdown
Автор:  Amir [ 19 окт 2011, 16:56 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
А радиус предыдущей версии какой Accept выдает?
Автор:  FessAectan [ 19 окт 2011, 17:07 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
Интересен так же лог tcpdump'а
А именно этот момент

Код:
 10.1.20.202.radius > 10.1.19.161.18294: [bad udp cksum 4a37!] RADIUS, length: 511


Завтра выложу логи со старым сервером.

Вложения:
tcp.txt [18.9 КБ]
Скачиваний: 490
Автор:  Amir [ 19 окт 2011, 17:24 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
У вас freebsd? Возможно проблема в java, которая у вас стоит.
На тестовых машинах такой ошибки не возникает, у других клиентов работает.
Еще есть вариант, что MessageAuthenticator не правильный, но его совсем недавно на eap-ttls проверяли.
Автор:  FessAectan [ 19 окт 2011, 19:49 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
Отпишу о версиях и используемой ОС
Код:
root@bgbilling:/# /opt/java/bin/java -version
java version "1.6.0_29"
Java(TM) SE Runtime Environment (build 1.6.0_29-b11)
Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02, mixed mode)
root@bgbilling:/# uname -srm
Linux 2.6.32-5-amd64 x86_64
Автор:  FessAectan [ 20 окт 2011, 11:08 ]
Заголовок сообщения:  Re: Проблемы с версией BGRadiusDialup_5.2_199.
Все ОК, авторизация на 5.2 проходит.
Сделал обновление радиуса и сервера, после того как разработчики обновили/исправили версии, авторизацию на живых насах уже не проверял, на стенде не работала. Вернулся на стенде на 5.0 - тоже не работает, полез проверять - опечатался в секрете для наса тестового, исправил - радиус 5.2 заработал.
Страница 1 из 1 Часовой пояс: UTC + 5 часов [ Летнее время ]
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/