bug-gnu-radius
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-gnu-radius] cisco router GSR12016 can not work with gnuradius


From: 郑柳清
Subject: [Bug-gnu-radius] cisco router GSR12016 can not work with gnuradius
Date: Thu, 04 Sep 2003 10:32:16 +0800

hi

   I have a gnuraius server 1.1 on solairs8.
   I can use it to auth and acct user login (telnet) on all cisco router  but 
gsr12016.
 -----------------------------------------------------------
   gsr12016 configure:

   aaa authentication login default radius local
   aaa accounting exec default start-stop radius
   aaa accounting connection default start-stop radius
   radius-server host 10.0.0.1 auth-port 1812 acct-port 1813
   radius-server key cisco
------------------------------------------------------------
   gnuradius user file:

   DEFAULT Auth-Type = System,
                Simultaneous-Use = 5
           Service-Type = Login-User,
                Login-Service = Telnet
------------------------------------------------------------
   I use this configure to auth and acct user login on cisco 
2621,3640,7513,5500 , is ok.
   But when i use it to auth and acct user login on cisco gsr12016, it failed. 
GSR12016 can not auth the user and send the acct info three times.
   it seems the share key no match,but the key is all "cisco".  

   Can you help me to resolv this problem? Is this a gnuradius bug ? a cisco 
gsr router bug ? my configure is incorrect ?

   Thanks!
-----------------------------------------------------------------
   The radius log file say:
   Sep 03 23:37:40 Auth.notice: (AUTHREQ sn12016 43 zheng): Login incorrect 
[zheng/w┍=�p;$瞍/�'�], CLID 10.0.0.23
   Sep 03 23:38:38 Auth.notice: (AUTHREQ sn12016 46 zheng): Login incorrect 
[zheng/��[�vNY���?���], CLID 10.0.0.23
   Sep 03 23:43:07 Acct.debug: acct.c:327:rad_acct_system: start: User zheng at 
NAS sn12016 port 3 session 00000008
   Sep 03 23:43:12 Acct.debug: acct.c:327:rad_acct_system: start: User zheng at 
NAS sn12016 port 3 session 00000008
   Sep 03 23:43:17 Acct.debug: acct.c:327:rad_acct_system: start: User zheng at 
NAS sn12016 port 3 session 00000008
   Sep 03 23:43:22 Acct.debug: acct.c:327:rad_acct_system: start: User zheng at 
NAS sn12016 port 3 session 00000008
   Sep 04 00:21:50 Auth.notice: (AUTHREQ sn12016 71 zheng): Login incorrect 
[zheng/]��<鼓愫
   Sep 04 00:22:15 Auth.notice: (AUTHREQ sn12016 72 zheng): Login incorrect 
[zheng/tFX)���gU����], CLID 10.0.0.23

------------------------------------------------------------------
   router debug raidius :

*Sep  4 09:41:47: RADIUS: ustruct sharecount=2
*Sep  4 09:41:47: RADIUS: Initial Transmit tty3 id 161 10.0.0.1:1813, Accou
nting-Request, len 95
*Sep  4 09:41:47:         Attribute 4 6 DA4DB101
*Sep  4 09:41:47:         Attribute 5 6 00000003
*Sep  4 09:41:47:         Attribute 61 6 00000005
*Sep  4 09:41:47:         Attribute 1 7 7A68656E
*Sep  4 09:41:47:         Attribute 31 16 3230322E
*Sep  4 09:41:47:         Attribute 40 6 00000001
*Sep  4 09:41:47:         Attribute 45 6 00000002
*Sep  4 09:41:47:         Attribute 6 6 00000007
*Sep  4 09:41:47:         Attribute 44 10 30303030
*Sep  4 09:41:47:         Attribute 41 6 00000000
*Sep  4 09:41:47: RADIUS: Received from id 161 10.0.0.1:1813, Accounting-re
sponse, len 20
*Sep  4 09:41:47: RADIUS: Response (161) failed decrypt
*Sep  4 09:41:50: RADIUS: ustruct sharecount=2
*Sep  4 09:41:50: RADIUS: Initial Transmit tty3 id 162 10.0.0.1:1813, Accou
nting-Request, len 107
*Sep  4 09:41:50:         Attribute 4 6 DA4DB101
*Sep  4 09:41:50:         Attribute 5 6 00000003
*Sep  4 09:41:50:         Attribute 61 6 00000005
*Sep  4 09:41:50:         Attribute 1 7 7A68656E
*Sep  4 09:41:50:         Attribute 31 16 3230322E
*Sep  4 09:41:50:         Attribute 40 6 00000002
*Sep  4 09:41:50:         Attribute 45 6 00000002
*Sep  4 09:41:50:         Attribute 6 6 00000007
*Sep  4 09:41:50:         Attribute 44 10 30303030
*Sep  4 09:41:50:         Attribute 49 6 00000001
*Sep  4 09:41:50:         Attribute 46 6 00000003
*Sep  4 09:41:50:         Attribute 41 6 00000000
*Sep  4 09:41:50: RADIUS: Received from id 162 10.0.0.1:1813, Accounting-re
sponse, len 20
*Sep  4 09:41:50: RADIUS: Response (162) failed decrypt
*Sep  4 09:41:52: RADIUS: Retransmit id 161
*Sep  4 09:41:52: RADIUS: acct-delay-time for 53D36AC8 (at 53D36B21) now 5
*Sep  4 09:41:52: RADIUS: Received from id 163 10.0.0.1:1813, Accounting-re
sponse, len 20
*Sep  4 09:41:52: RADIUS: Response (163) failed decrypt
*Sep  4 09:41:55: RADIUS: Retransmit id 162
*Sep  4 09:41:55: RADIUS: acct-delay-time for 53D21E30 (at 53D21E95) now 5
*Sep  4 09:41:55: RADIUS: Received from id 164 10.0.0.1:1813, Accounting-re
sponse, len 20
*Sep  4 09:41:55: RADIUS: Response (164) failed decrypt
*Sep  4 09:41:57: RADIUS: Retransmit id 163
*Sep  4 09:41:57: RADIUS: acct-delay-time for 53D36AC8 (at 53D36B21) now 10
*Sep  4 09:41:57: RADIUS: Received from id 165 10.0.0.1:1813, Accounting-re
sponse, len 20
*Sep  4 09:41:57: RADIUS: Response (165) failed decrypt
*Sep  4 09:42:00: RADIUS: Retransmit id 164
*Sep  4 09:42:00: RADIUS: acct-delay-time for 53D21E30 (at 53D21E95) now 10
*Sep  4 09:42:00: RADIUS: Received from id 166 10.0.0.1:1813, Accounting-re
sponse, len 20
*Sep  4 09:42:00: RADIUS: Response (166) failed decrypt
*Sep  4 09:42:02: RADIUS: Retransmit id 165
*Sep  4 09:42:02: RADIUS: acct-delay-time for 53D36AC8 (at 53D36B21) now 15
*Sep  4 09:42:02: RADIUS: Received from id 167 10.0.0.1:1813, Accounting-re
sponse, len 20
*Sep  4 09:42:02: RADIUS: Response (167) failed decrypt
*Sep  4 09:42:05: RADIUS: Retransmit id 166
*Sep  4 09:42:05: RADIUS: acct-delay-time for 53D21E30 (at 53D21E95) now 15
*Sep  4 09:42:05: RADIUS: Received from id 168 10.0.0.1:1813, Accounting-re
sponse, len 20
*Sep  4 09:42:05: RADIUS: Response (168) failed decrypt
*Sep  4 09:42:07: RADIUS: No response for id 167
*Sep  4 09:42:10: RADIUS: No response for id 168


  


――――――――――――――――――――――――――――――――――――――――――――――――――――――――
                                                 liuqing.zheng     
address@hidden
                                                                                
     2003-09-04
――――――――――――――――――――――――――――――――――――――――――――――――――――――――






reply via email to

[Prev in Thread] Current Thread [Next in Thread]