On 08/14/2013 09:25 PM, McNutt, Justin M. wrote:
One other thing with multiple interfaces: RHEL 6 comes with some
anti-spoofing features in the kernel enabled by default. I'm afraid
As I noted elsewhere in the thread, the terms to google for this are
martians and rp filter, and you are
From: Phil Mayers p.may...@imperial.ac.uk
If radiusd -X isn't reporting *anything*, then it's not reaching
FreeRADIUS, which means some part of the network stack is dropping it.
If you're sure your iptables are correct, google linux log martians and
linux rp filter. RHEL6 has different
Hi all
I'm trying to setup a very basic test server using FreeRADIUS (running on
Ubuntu 12.04) that uses PEAP with the example certificates generated by
FreeRADIUS.
I keep running into a variety of fairly basic problems.
After running freeradius -X I get this error message.
Couldn't open
ultaman khoo wrote:
I have faced an issue with NAS IP Changes
RADIUS assumes that NAS IPs don't change. If they do, you are running
a VERY unusual system.
causes radius accouting insert
instead of update, this has causes an issue with the reporting wenever
the NAS IP changes, for example
Darlington, Andrew wrote:
I’m trying to setup a very basic test server using FreeRADIUS (running
on Ubuntu 12.04) that uses PEAP with the example certificates generated
by FreeRADIUS.
See http://deployingradius.com It has a detailed guide for EAP / PEAP.
Couldn't open
Hi Alan,
Thanks for your response.
Initially FreeRadius would not start and I did get an error indicating
that the remote_secret_reject module failed to load. There was no reason
given even with -XXX. I found since then that I was missing a brace.
Now I can get FreeRadius to start. I still seem
Sigh. I broke the cardinal rule of the list _again_.
I'Ll grab a full debug log now.
Sorry for the spam.
Dave Aldwinckle
On 2013-08-13 11:22 AM, Alan DeKok al...@deployingradius.com wrote:
David Aldwinckle wrote:
Is there a way that I can deny a specific realm when an access request
is
David Aldwinckle wrote:
Initially FreeRadius would not start and I did get an error indicating
that the remote_secret_reject module failed to load. There was no reason
given even with -XXX. I found since then that I was missing a brace.
Now I can get FreeRadius to start. I still seem to be
Thanks for the fast reply.
See http://deployingradius.com It has a detailed guide for EAP / PEAP.
I'm actually following that one, it's very helpful, however I keep running into
problems that aren't covered.
You're running it as a normal user, and the file is owned by root (or
another
Hi,
I'm trying to setup a very basic test server using FreeRADIUS (running on
Ubuntu 12.04) that uses PEAP with the example certificates generated by
FreeRADIUS.
out of the box, freeRADIUS works - you just need, for testing
to add your user/pass to the 'users' file and your NAS to
Hi,
Initially FreeRadius would not start and I did get an error indicating
that the remote_secret_reject module failed to load. There was no reason
given even with -XXX. I found since then that I was missing a brace.
Now I can get FreeRadius to start. I still seem to be missing something
hi,
check permissions/owner etc of /etc/freeradius and the contents
alan
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On 15/08/13 14:30, Darlington, Andrew wrote:
Couldn't open /etc/freeradius/acct_users for reading: Permission denied
Errors reading /etc/freeradius/acct_users
/etc/freeradius/modules/files[7]: Instantiation failed for module files
/etc/freeradius/sites-enabled/inner-tunnel[124]: Failed to load
Hi
Thanks for all the replies!
Going through all the permissions of the various files freeradius complained
about fixed it like Phil Mayers and Alan said.
I also fixed the radtest problem. This just need to have freeradius restarted
normally.
I'm now working on PEAP with an Ubuntu client
ultaman khoo wrote:
I have faced an issue with NAS IP Changes
RADIUS assumes that NAS IPs don't change. If they do, you are running
a VERY unusual system.
Do you mean it doesnt conform to the radius acct RFC standard in this case?
if im get it right the FR3.0 should have take care of the NAS
btw the nas ip changes is due to NAS system supplying the radius acct
has failover to the backup unit, radius acct is then supply from there. so
it get change
On Fri, Aug 16, 2013 at 7:39 AM, ultaman khoo ultaman.k...@gmail.comwrote:
ultaman khoo wrote:
I have faced an issue with NAS IP
ultaman khoo wrote:
btw the nas ip changes is due to NAS system supplying the radius acct
has failover to the backup unit, radius acct is then supply from there.
so it get change
It's still garbage.
The FreeRADIUS SQL queries assume that one NAS sends all of the
accounting traffic for
17 matches
Mail list logo
