Re: [PATCH] [CFT] [RFC] [WIP] Next series

Replying to David Chkhartishvili:
> I also would like mention, that current radius implementetion not always 
> working properly. Sometimes we get incorrect mappings and as a result clients 
> get other clients MSISDN's. That situation is fatal when services are 
> dependent on MSIDN, for example MMS.
> From my point of view, Paul's implementetion is more cleaner. But there is 
> also disadvantage: hard dependency to FreeRadius. 

I think we can overcome this.
Interface is very simple (actually, we are storing map
framed-ip-address->msisdn, thats all) and I think I can write module
for any major free radius implementation floating around which allows
modules.

But this approach still have problems. Both wapboxes and radius need
coherent access to same filesystem. In most cases it can be achieved
only on locally mounted fs. (hp-ux is non-coherent even on local fs,
but I need to check berkeley db sources to see are they actually
worked around this).

Another solution would be - to write some kind of network service,
maybe - add it to bearerbox, which will relay to many wapboxes,
probably on different machines, required msisdn information - by
request from wapbox or even unconditionally with each datagram.

I hope I will continue to work in this direction just after I will do
some more testing on different platforms and under real-world load :)

-- 
Paul P 'Stingray' Komkoff Jr // http://stingr.net/key <- my pgp key
 This message represents the official view of the voices in my head