Hi, Yury. I affraid that our configuration doesn't help because we have quite complicated configuration with many NAS servers etc. And anyway, configuration depends on NAS software.
You must explain clearly your problem.
Check that you do not forward AUTH packets to kannel. Only accounting packets must be sent to kannel from NAS.
Yury Mikhienko wrote:
Hi, Vjacheslav.
Can you send me your worked NAS (may be RAS in additional) configuration (approximate of course)?
Hi, Yury.
There are two differnet things: accounting and authorization. There are even differnet default ports (1813 and 1812). So accounting packets has been not used for authorization. You must be able to configure AUTH packets at NAS to go directly to RAS.
Yury Mikhienko wrote:
No, not "radius-acct" section. with RADIUS config I'm mean the radius server config. My problem detail: 1. Kannel get account request from NAS properlly. 2. Kannel succesfully forward that request to radius server 3. Kannel got responce from radius server. but radius server do not autorize accounting request. May be I need configure radius server for forwarding autorization responce to NAS directly? (but how?)
Hi, Yury. I didn't undestand your problem. And what you mean "RADIUS config"? Is it kannel "radius-acct" section? Yury Mikhienko wrote:
Hi Vjacheslav ! Can you send me your RADIUS config, for example?
I as yet not configure the NAS-KANNEL-RADIUS scheme for this time :(( RADIUS did not autorize request from NAS (forwarding from kannel) my logs: ... 2003-09-30 16:44:23 [1] INFO: RADIUS PDU type: Accounting_Request 2003-09-30 16:44:23 [1] INFO: RADIUS: Mapping `172.16.188.2 <-> 7xxxxxxxxxx' for session id <0033FDED> added. /************ FORWARD DATA to RADIUS *****************************/ 2003-09-30 16:44:23 [1] INFO: RADIUS: Got data from remote RADIUS <1.1.1.3:1813> 2003-09-30 16:44:23 [1] DEBUG: Octet string at 131d58: 2003-09-30 16:44:23 [1] DEBUG: len: 20 2003-09-30 16:44:23 [1] DEBUG: size: 21 2003-09-30 16:44:23 [1] DEBUG: immutable: 0 2003-09-30 16:44:23 [1] DEBUG: data: 05 d9 00 14 a1 2b 54 d0 0e f8 a1 68 95 d9 55 09 .....+T....h..U. 2003-09-30 16:44:23 [1] DEBUG: data: c9 28 a5 f6 .(.. 2003-09-30 16:44:23 [1] DEBUG: Octet string dump ends. 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Mapping table contains 1 elements 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Session table contains 1 elements 2003-09-30 16:44:23 [1] DEBUG: RADIUS: Client table contains 1 elements ...
-- Vjacheslav Chekushin mailto:[EMAIL PROTECTED] Latvian Mobile Phone Company http://www.lmt.lv
