Let's suppose that there is also an attacker
(a disglunted employee maybe?), who knows about this bug and decides
to
attack my FreeRadius servers, so he starts sending these
specially crafted packets to each server and since the two servers
have
the same bug, both of them would die upon
Hi Robin,
Have FreeRadius mirror the Access-Accept (plus reply-attributes) of your
Mikrotik radius server. You should be able to do a tcpdump (or snoop if
it's on Solaris) to see the authentication messaging. Perhaps your
Mikrotik radius server is setting some network-level parameters in the
You could try this method ...
Don't 'strip' the realm and store complete usernames in your users file
(or database).
So your username would be j...@business or b...@communication.
Regards,
Jason
-Original Message-
From:
time is appreciated. Thanks again for the
response.
Regards,
Jason
--- Alan DeKok [EMAIL PROTECTED] wrote:
Jason Hodges wrote:
...
Here are the debug results:
radius_xlat: '0210xxx'
radius_xlat: Running registered xlat function of
module exec for string
'/usr/local/freeradius
Greetings. First I'd like to thank everyone who works
on this project. Freeradius is amazing.
For our issue, I have browsed the online
documentation, faq, and mailing lists.
We have a need to alter the accounting records that we
proxy to another company. The attribute that we need
to rewrite
5 matches
Mail list logo
