RE: (PM) Radius

MED, Wipro Systems, Inc ("Nair,)
Wed, 14 Apr 1999 19:26:12 -0500

Hi
---------
From: Thomas C Kinnen[SMTP:tkinnen@livingston.com]
Reply To: Thomas C Kinnen
Sent: Tuesday, March 23, 1999 5:48 PM
To: Portmaster Users
Subject: Re: (PM) Radius

"Nair, Shibu (MED, Wipro Systems, Inc)" wrote:

> When i have configured RADIUS for PM3, it is taking the ports
and
> showing
> on "sh global" command...
> It is taking port "1645" for radius server and "1646" for
accounting
> server ...
>
> Is that ok or do i have to modify the same...?

That's the default ports for RADIUS on the PM3. You may want to
change them
to 1812 and 1813 which are the RFC ports unless you have other
boxes that
can not talk on those ports.

I have tried with these ports too (1812 - Radius and 1813 as Accounting
servers)...
Now also Radius users are not getting connected successfully (able to
establish connectivity with local users created on PM3) ...

My settings are given below,

sh global :

Default Host: 0.0.0.0
Alternate Hosts:
IP Gateway: 3.87.88.254
Gateway Metric: 1
Default Routing: Quiet (Off)
OSPF Priority: 1
OSPF Router ID: 3.87.88.225
Name Service: NIS
Name Server: iscmed
Domain: ISC
Telnet Access Port: 23
Loghost: iscmed
Maximum PMconsole: 10
Assigned Address: 0.0.0.0
RADIUS Server: olcapp-p3 1812
Alternate Server: 0.0.0.0
Accounting Server: olcapp-p3 1813
Alt. Acct. Server: 0.0.0.0
ChoiceNet Server: 0.0.0.0
Alt. ChNet Server: 0.0.0.0
PPP Authentication: PAP: off CHAP: on
ISDN Switch Type: att-5ess
End Point Disc: None
Disabled Modules: IPX BGP

"Pls note that Radius is working perfectly with PM2e portmasters..."

Also my debug status during the connection,

set debu 0x51
set cons

Sending LCP_CONFIGURE_REQUEST to port S0 of 25 bytes containing:
01 01 00 19 02 06 00 00 00 00 03 05 c2 23 05 05
06 99 89 62 aa 07 02 08 02
Received LCP_CONFIGURE_ACK on port S0 of 21 bytes containing:
02 01 00 19 02 06 00 00 00 00 03 05 c2 23 05 05
06 99 89 62 aa 07 02 08 02
Received LCP_CONFIGURE_REQUEST on port S0 of 19 bytes containing:
01 02 00 17 02 06 00 0a 00 00 05 06 00 af 4f 65
07 02 08 02 0d 03 06
Sending LCP_CONFIGURE_REJECT to port S0 of 7 bytes containing:
04 02 00 07 0d 03 06
Sending LCP_CONFIGURE_REQUEST to port S0 of 25 bytes containing:
01 02 00 19 02 06 00 00 00 00 03 05 c2 23 05 05
06 99 89 62 aa 07 02 08 02
Received LCP_CONFIGURE_ACK on port S0 of 21 bytes containing:
02 02 00 19 02 06 00 00 00 00 03 05 c2 23 05 05
06 99 89 62 aa 07 02 08 02
Received LCP_CONFIGURE_REQUEST on port S0 of 19 bytes containing:
01 03 00 17 02 06 00 0a 00 00 05 06 00 af 4f 65
07 02 08 02 0d 03 06
Sending LCP_CONFIGURE_REJECT to port S0 of 7 bytes containing:
04 03 00 07 0d 03 06
Sending LCP_CONFIGURE_REQUEST to port S0 of 25 bytes containing:
01 03 00 19 02 06 00 00 00 00 03 05 c2 23 05 05
06 99 89 62 aa 07 02 08 02
Received LCP_CONFIGURE_ACK on port S0 of 21 bytes containing:
02 03 00 19 02 06 00 00 00 00 03 05 c2 23 05 05
06 99 89 62 aa 07 02 08 02
Received LCP_CONFIGURE_REQUEST on port S0 of 19 bytes containing:
01 04 00 17 02 06 00 0a 00 00 05 06 00 af 4f 65
07 02 08 02 0d 03 06
Sending LCP_CONFIGURE_REJECT to port S0 of 7 bytes containing:
04 04 00 07 0d 03 06
Sending LCP_CONFIGURE_REQUEST to port S0 of 25 bytes containing:
01 04 00 19 02 06 00 00 00 00 03 05 c2 23 05 05
06 99 89 62 aa 07 02 08 02
Received LCP_CONFIGURE_ACK on port S0 of 21 bytes containing:
02 04 00 19 02 06 00 00 00 00 03 05 c2 23 05 05
06 99 89 62 aa 07 02 08 02
Received LCP_CONFIGURE_REQUEST on port S0 of 16 bytes containing:
01 05 00 14 02 06 00 0a 00 00 05 06 00 af 4f 65
07 02 08 02
Sending LCP_CONFIGURE_ACK to port S0 of 20 bytes containing:
02 05 00 14 02 06 00 0a 00 00 05 06 00 af 4f 65
07 02 08 02
S0: LCP Open
Sending CHAP_CONF_CHALLENGE to port S0 of 28 bytes containing:
01 01 00 1c 10 3e e0 3d cc 3e 86 6d dd 90 b9 1b
b4 12 83 96 6d 6f 6c 63 2d 70 6d 35
Sending CHAP_CONF_CHALLENGE to port S0 of 28 bytes containing:
01 02 00 1c 10 35 6a 8d 57 b1 0d 4d 15 47 b3 54
c1 3b 57 40 dc 6f 6c 63 2d 70 6d 35
Received CHAP_CONF_RESPONSE on port S0 of 28 bytes containing:
02 02 00 1c 10 5f 8e f2 60 d4 19 84 d3 74 d4 c4
32 6d 84 e5 3d 6d 73 61 33 35 31 35
Received CHAP_CONF_RESPONSE on port S0 of 28 bytes containing:
02 02 00 1c 10 5f 8e f2 60 d4 19 84 d3 74 d4 c4
32 6d 84 e5 3d 6d 73 61 33 35 31 35
Received CHAP_CONF_RESPONSE on port S0 of 28 bytes containing:
02 02 00 1c 10 5f 8e f2 60 d4 19 84 d3 74 d4 c4
32 6d 84 e5 3d 6d 73 61 33 35 31 35
Received CHAP_CONF_RESPONSE on port S0 of 28 bytes containing:
02 02 00 1c 10 5f 8e f2 60 d4 19 84 d3 74 d4 c4
32 6d 84 e5 3d 6d 73 61 33 35 31 35
Received CHAP_CONF_RESPONSE on port S0 of 28 bytes containing:
02 02 00 1c 10 5f 8e f2 60 d4 19 84 d3 74 d4 c4
32 6d 84 e5 3d 6d 73 61 33 35 31 35
Received CHAP_CONF_RESPONSE on port S0 of 28 bytes containing:
02 02 00 1c 10 5f 8e f2 60 d4 19 84 d3 74 d4 c4
32 6d 84 e5 3d 6d 73 61 33 35 31 35
Received CHAP_CONF_RESPONSE on port S0 of 28 bytes containing:
02 02 00 1c 10 5f 8e f2 60 d4 19 84 d3 74 d4 c4
32 6d 84 e5 3d 6d 73 61 33 35 31 35
Sending CHAP_CONF_FAILURE to port S0 of 17 bytes containing:
04 02 00 11 49 6e 76 61 6c 69 64 20 4c 6f 67 69
6e
Sending LCP_TERMINATE_ACK to port S0 of 4 bytes containing:
06 05 00 04
S0: Connection Failed

Pls help me on this...

--
Thomas C Kinnen - <tkinnen@ra.lucent.com> <tkinnen@sobhrach.com>
[RADIUS Test Engineer] - LUCENT Technologies RABU
"All of the opinions stated above are my own and not my
employer's,
unless they were given to me by my employer"
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive:
<URL:http://www.livingston.com/Tech/archive/>

-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>