On 2013-07-09 at 10:18, Matthew Newton (m...@leicester.ac.uk) wrote:
> Julian,
>
> On Mon, Jul 08, 2013 at 03:10:31PM -0700, Julian Macassey wrote:
> > I'm just trying to do a bog standard username and
> > password for OS X and Linux users on laptops - Plus the
>
On 2013-07-09 at 00:52, Alan DeKok (al...@deployingradius.com) wrote:
> Julian Macassey wrote:
> > So, I put it back in. I took it out earlier as 1. I
> > couldn't connect with it. 2. My understanding from reading the
> > docs was that pap alone would do the job.
On 2013-07-08 at 22:16, Matthew Newton (m...@leicester.ac.uk) wrote:
> On Mon, Jul 08, 2013 at 01:49:47PM -0700, Julian Macassey wrote:
> > I have a Netgear WiFi router set up for WPA2 Enterprise.
> > It is pointed at a freeradius server. I am trying to use the
> > use
I have a Netgear WiFi router set up for WPA2 Enterprise.
It is pointed at a freeradius server. I am trying to use the
username and password of that server to authenticate. It fails
consistenty with:
[pap] WARNING! No "known good" password found for the user.
Authentication may fail becaus
On 2013-06-24 at 18:38, a.l.m.bu...@lboro.ac.uk (a.l.m.bu...@lboro.ac.uk) wrote:
> Hi,
>
> > Chain INPUT (policy ACCEPT)
> > target prot opt source destination
> > ACCEPT tcp -- 0.0.0.0/00.0.0.0/0tcp
> > dpt:1812
>
> you see this - TCP
>
> read a
On 2013-06-24 at 13:24, John Dennis (jden...@redhat.com) wrote:
> On 06/24/2013 12:18 PM, Julian Macassey wrote:
> > I added in /etc/freeradius/clients.conf:
> >
> > client plumgrid-ldap1 {
> > # # secret and password are mapped through the
On 2013-06-24 at 18:06, a.l.m.bu...@lboro.ac.uk (a.l.m.bu...@lboro.ac.uk) wrote:
> Hi,
>
> > > Always start simple. Run radtest on the RADIUS server box
> > > using 127.0.0.1 ... THEN move to running against it from other
> > > systems once you've verified all authentication etc is working
> >
On 2013-06-22 at 16:41, Alan Buxey (a.l.m.bu...@lboro.ac.uk) wrote:
>
> Always start simple. Run radtest on the RADIUS server box
> using 127.0.0.1 ... THEN move to running against it from other
> systems once you've verified all authentication etc is working
Works on localhost.
On 2013-06-22 at 01:20, Olivier Beytrison (oliv...@heliosnet.org) wrote:
> On 21.06.2013 22:21, Julian Macassey wrote:
>
>
> in your config you didn't configure any other client than 127.0.0.1
> you're sending your request to 192.168.10.14 which mean it's over th
On 2013-06-22 at 01:23, Roberto Ortega Ramiro (roberto.ort...@esj.es) wrote:
> Hi, You have 2 modules ldap, one is ldap and the other is including
> configuration file /etc/freeradius/modules/ldap-orig
> Put /etc/freeradius/modules/ldap-orig out of modules directory.
Done. As per the doc
On 2013-06-21 at 16:41, John Dennis (jden...@redhat.com) wrote:
>
> Looking at this more carefully also make sure port 1812 is open
That was my first guess. I asked the guy who set up the
servers if they were open and he assured me they were.
But my tests, just re-tried, show th
On 2013-06-21 at 16:48, John Dennis (jden...@redhat.com) wrote:
> The radius server is not seeing any client requests and your client is
> not getting a response from the server, either you've got the wrong
> address for the radius server or more likely your firewall is block
> their communication
On 2013-06-21 at 16:34, John Dennis (jden...@redhat.com) wrote:
> >
> > What am I missing? It won't complain and it won't work.
> >
>
> You've failed to provide the complete debug output, something which is
> stated as being required nearly every day on this list. This means we
> can't see how
I am tring to get freeradius working with ldap.
The ldap server is on the same LAN as the RADIUS server.
The local user test works.
I have configured all files I can think are pertinent.
In debug mode, I get:
root#> freeradius -X
}
listen {
type = "auth"
ipaddr = 127.
14 matches
Mail list logo
