Hi Stipe, List,
As you all know I had problem with MSISDN <-> Framed-IP-Address mapping
with cisco NAS.
Finally I found problem resolution.
Those two command are necessary for cisco NAS to transmit
Framed-IP-Adress after IP address is assingned to client:
radius-server attribute 8 include-in-ac
Hi David,
David Chkhartishvili schrieb:
>
> wapbox.log:
>
> 2003-06-20 18:11:51 [1] DEBUG: Octet string at 0x81616c8:
> 2003-06-20 18:11:51 [1] DEBUG: len: 98
> 2003-06-20 18:11:51 [1] DEBUG: size: 99
> 2003-06-20 18:11:51 [1] DEBUG: immutable: 0
> 2003-06-20 18:11:51 [1] DEBUG: data: 0
I forgot to mention that I'm using Cistron Radius ;-) , please let me
know if it might be issue.
Paul Keogh wrote:
hmmm, ok, that would be an issue.
But in the log David provided there was no client IP, even not under
different attribute name.
Then you must ask the NAS administrator to t
wapbox.log:
2003-06-20 18:11:51 [1] DEBUG: Octet string at 0x81616c8:
2003-06-20 18:11:51 [1] DEBUG: len: 98
2003-06-20 18:11:51 [1] DEBUG: size: 99
2003-06-20 18:11:51 [1] DEBUG: immutable: 0
2003-06-20 18:11:51 [1] DEBUG: data: 04 9c 00 62 52 15 df 60 ...bR..`
2003-06-20 18:11:51 [1]
Paul Keogh wrote:
>
> Another piece of hard earned experience - the client IP address that the NAS
> sees is
> not necessarily the one ultimately presented to the WAP gateway. There are
> all
> sorts of funny NAT style tricks that can happen between the NAS server and
> the
> WAP gateway, especial
>
> hmmm, ok, that would be an issue.
>
> But in the log David provided there was no client IP, even not under
> different attribute name.
>
Then you must ask the NAS administrator to turn it on. You won't necessarily
get it by default, and without it the WAP box cannot do anything as its the
only
Paul Keogh wrote:
>
> >
> > the problem is that your NAS does not deliver an 'Framed-IP-Address'
> > attribute within the acct packet, hence the folllowing inside
> > radius/radius_acct.c:update_tables():
> >
>
> My experience is that the RADIUS attribute that contains the information
> that the
>
> the problem is that your NAS does not deliver an 'Framed-IP-Address'
> attribute within the acct packet, hence the folllowing inside
> radius/radius_acct.c:update_tables():
>
My experience is that the RADIUS attribute that contains the information
that the WAP gateway needs (ie. MSISDN) varies
David Chkhartishvili schrieb:
>
> Stipe,
>
> Here is debug log from cisco:
>
> 16w0d: Attribute 4 6 D53D3A8C
> 16w0d: Attribute 5 6 0017
> 16w0d: Attribute 61 6 0004
> 16w0d: Attribute 1 5 7761701E
> 16w0d: Attribute 30 5 3532311F
> 16w0d:
Stipe,
Here is debug log from cisco:
16w0d: Attribute 4 6 D53D3A8C
16w0d: Attribute 5 6 0017
16w0d: Attribute 61 6 0004
16w0d: Attribute 1 5 7761701E
16w0d: Attribute 30 5 3532311F
16w0d: Attribute 31 10 39393138
16w0d: Attribute 2 1
Steve Kennedy wrote:
>
> On Fri, Jun 20, 2003 at 01:56:53PM +0200, Stipe Tolj wrote:
>
> > ok, know I know why:
> > the problem is that your NAS does not deliver an 'Framed-IP-Address'
> > attribute within the acct packet, hence the folllowing inside
> > radius/radius_acct.c:update_tables():
>
>
On Fri, Jun 20, 2003 at 01:56:53PM +0200, Stipe Tolj wrote:
> ok, know I know why:
> the problem is that your NAS does not deliver an 'Framed-IP-Address'
> attribute within the acct packet, hence the folllowing inside
> radius/radius_acct.c:update_tables():
Isn't framed IP used for routing ? (or
OK, I see. I will try to send framed IP from my cisco.
Stipe Tolj wrote:
Hi David,
ok, know I know why:
the problem is that your NAS does not deliver an 'Framed-IP-Address'
attribute within the acct packet, hence the folllowing inside
radius/radius_acct.c:update_tables():
...
client_ip = di
Hi David,
ok, know I know why:
the problem is that your NAS does not deliver an 'Framed-IP-Address'
attribute within the acct packet, hence the folllowing inside
radius/radius_acct.c:update_tables():
...
client_ip = dict_get(pdu->attr, octstr_imm("Framed-IP-Address"));
...
will be of cours
David Chkhartishvili schrieb:
>
> Stipe,
>
> Could you please look at my debug output?
> Radius proxy gets msisdn fro nas correctly, but doesn't include MSISDN
> header.
yes, I'll check. Stay tuned...
Stipe
[EMAIL PROTECTED]
---
W
Stipe,
Could you please look at my debug output?
Radius proxy gets msisdn fro nas correctly, but doesn't include MSISDN
header.
David Chkhartishvili wrote:
Hi List,
I've just tried to use MSISDN feature of kannel. Seems like it doesn't
provide X-WAP-Network-Client-MSISDN header to http server
huangcy wrote:
>
> hi,list:
> when will kannel support wap2.0?
now that's a good question ;)
I guess this depends on how many people there are outside using Kannel
and want to contribute as module maintainer. Which means people that
pick up a certain issue (like Aarno does for PPG) and provi
hi,list:
when will kannel support wap2.0?
Hi List,
I've just tried to use MSISDN feature of kannel. Seems like it doesn't
provide X-WAP-Network-Client-MSISDN header to http server/MMSC. Instead
I see that it transfers X-WAP-Network-Client-IP.
Here is debug log:
2003-06-20 11:47:37 [1] INFO: RADIUS: Got data from NAS
2003-06-20 11:47:3
Hi list,
I just commited this to cvs:
2003-06-20 Stipe Tolj <[EMAIL PROTECTED]>
* Makefile.in: added compilation of RADIUS related files inside
radius/.
* doc/userguide/userguide.xml: new MSISDN provisioning section
describing
the use of the RADIUS accounting proxy thread.
* g
20 matches
Mail list logo