On 2014-03-27 20:43, Heikki Vatiainen wrote:
> On 03/27/2014 05:22 PM, Hartmaier Alexander wrote:
>
>> Did you have time to work on this feature?
> We have worked on EAP-SIM, Diameter and other RADIUS functionality, but
> not this. It's still on the ideas to explore list, though.
>
>> I've started
Heikki, thanks for the tip.
I've written the following.
Config file part:
OriginHost mm2.ims..xx
OriginRealm ims..xx
Port 3870
SupportedVendorIds DictVendors
PostDiaToRadiusConversionHook file:"%D/dia_to_radius_hook.pl"
dia_to_radius_ho
Hi Elmar,
I'm afraid that this problem has nothing do to with radiator or with different
architecture. I've realised that the same problem is between radsecproxy <->
radsecproxy (version 1.6.5 on DEBIAN). It is exactly like you described.
The only chance to notice this behaviour is to check the
On 03/28/2014 11:50 AM, Arthur wrote:
> dia_to_radius_hook.pl:
> sub
> {
> my $d=${$_[0]};
> my $p=${$_[1]};
>
> my $subscription = $p->get_attr('Subscription-Id-Data');
> $subscription =~ s/^sip://g;
> $p->add_attr('User-Name', $subscription);
> &main::log($main::LOG_DEBU
On 03/27/2014 12:01 AM, Markus Moeller wrote:
> Thank you for testing. That is not good news. I was intending to
> use wired 802.1x and a restart means switches may need to failover to
> the secondary Radius server especially if you want to do frequent CRL
> check and may disrupt clients whe
