Re: clients.conf problem
Try a fresh CVS checkout or tonight's CVS snapshot and see if this corrects your problems. Looks like there was a byte ordering problem when sanitizing the client entry based on the netmask. This would only have affected people with little-endian machines. --Mike Alan DeKok wrote: "dev_null" <[EMAIL PROTECTED]> wrote: Strange, I don't know why it won't work to me. Ok. Never mind. Try from a fresh CVS checkout, and don't change anything other than the "clients". If it's still a problem, it might be the inet_pton() functions on your system. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: clients.conf problem
"dev_null" <[EMAIL PROTECTED]> wrote: > Strange, I don't know why it won't work to me. > Ok. Never mind. Try from a fresh CVS checkout, and don't change anything other than the "clients". If it's still a problem, it might be the inet_pton() functions on your system. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: clients.conf problem
Strange, I don't know why it won't work to me. Ok. Never mind. Thanks - Original Message Follows - > I've tested that config, and ones with 500K clients. They all work > for me. > > Alan DeKok. > -- Naručite svoj XXLadsl - instalacija i modem i dalje za samo 1 kn! Postanite i vi korisnik ultra brzog Interneta! http://www.iskon.biz/xxladsl - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: clients.conf problem
"dev_null" <[EMAIL PROTECTED]> wrote: > The only way it works is when including both and only 10.20.1.0/24 & > 10.20.1.100 but it wont' work if a third client is added. :( I've tested that config, and ones with 500K clients. They all work for me. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: clients.conf problem
Michael Griego <[EMAIL PROTECTED]> wrote: > There has been some reworking of the clients code recently in CVS. I > haven't looked at it much yet as it was done by Alan, but, as with all > of the CVS tree, it's still considered unstable code. I did some preliminary tests, but I'll try this case to see if there's a problem. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: clients.conf problem
There has been some reworking of the clients code recently in CVS. I haven't looked at it much yet as it was done by Alan, but, as with all of the CVS tree, it's still considered unstable code. --Mike dev_null wrote: Hello, I tried what you said but the server ignored both localhost & 10.20.1.x requests. Could this be a bug in the 20050818 snapshot? The only way it works is when including both and only 10.20.1.0/24 & 10.20.1.100 but it wont' work if a third client is added. :( - Original Message Follows - I have a hunch... How many clients are in your clients.conf file? Is it just those two or do you have any more? Are those the *first* two clients? If you only have two clients, and its the two you listed there, try putting the localhost (127.0.0.1) client declaration in first followed by the 10.20.1.0/24 client declaration (leave out the 10.20.1.100 client declaration) and see if that works. --Mike - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: Re: clients.conf problem
Hello, I tried what you said but the server ignored both localhost & 10.20.1.x requests. Could this be a bug in the 20050818 snapshot? The only way it works is when including both and only 10.20.1.0/24 & 10.20.1.100 but it wont' work if a third client is added. :( - Original Message Follows - > I have a hunch... > > How many clients are in your clients.conf file? Is it just those two or > do you have any more? Are those the *first* two clients? > > If you only have two clients, and its the two you listed there, try > putting the localhost (127.0.0.1) client declaration in first followed > by the 10.20.1.0/24 client declaration (leave out the 10.20.1.100 client > declaration) and see if that works. > > --Mike -- Naručite svoj XXLadsl - instalacija i modem i dalje za samo 1 kn! Postanite i vi korisnik ultra brzog Interneta! http://www.iskon.biz/xxladsl - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: clients.conf problem
I have a hunch...
How many clients are in your clients.conf file? Is it just those two or
do you have any more? Are those the *first* two clients?
If you only have two clients, and its the two you listed there, try
putting the localhost (127.0.0.1) client declaration in first followed
by the 10.20.1.0/24 client declaration (leave out the 10.20.1.100 client
declaration) and see if that works.
--Mike
dev_null wrote:
Hello,
thanks for helping me :)
Well, you have "shortname" spelt incorrectly for a start.
Sorry, that's not a copy/past from clients.conf, there it's correct. My fault
when typing this mail.
Have you run the server in debug mode so that you can see exactly what
it is doing, and where it is dropping the request?
radiusd -X
Yes. But got only this:
...
Nothing to do. Sleeping until we see a request.
rad_recv: Access-Request packet from host 10.20.1.100 port 3846, id=7, length=48
Ignoring request from unknown client 10.20.1.100 port 3846
--- Walking the entire request list ---
When testing with "radtest testuser pass 10.20.1.5 1812 shared_secret"
with a clients.conf including only:
client 10.20.1.100 {
secret= shared_secret
shortname = WLAN
}
The strange thing is, as I mentioned before, that it works (only) when
including both:
client 10.20.1.0/24 {
secret= shared_secret
shortname = WLAN
}
and
client 10.20.1.100 {
secret= shared_secret
shortname = WLAN
}
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: clients.conf problem
Hello,
thanks for helping me :)
> Well, you have "shortname" spelt incorrectly for a start.
Sorry, that's not a copy/past from clients.conf, there it's correct. My fault
when typing this mail.
> Have you run the server in debug mode so that you can see exactly what
> it is doing, and where it is dropping the request?
> radiusd -X
Yes. But got only this:
...
Nothing to do. Sleeping until we see a request.
rad_recv: Access-Request packet from host 10.20.1.100 port 3846, id=7, length=48
Ignoring request from unknown client 10.20.1.100 port 3846
--- Walking the entire request list ---
When testing with "radtest testuser pass 10.20.1.5 1812 shared_secret"
with a clients.conf including only:
client 10.20.1.100 {
secret= shared_secret
shortname = WLAN
}
The strange thing is, as I mentioned before, that it works (only) when
including both:
client 10.20.1.0/24 {
secret= shared_secret
shortname = WLAN
}
and
client 10.20.1.100 {
secret= shared_secret
shortname = WLAN
}
--
Naručite svoj XXLadsl - instalacija i modem i dalje za samo 1 kn!
Postanite i vi korisnik ultra brzog Interneta! http://www.iskon.biz/xxladsl
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: clients.conf problem
Well, you have "shortname" spelt incorrectly for a start.
Have you run the server in debug mode so that you can see exactly what
it is doing, and where it is dropping the request?
radiusd -X
cheers,
Mike
dev_null wrote:
Hello,
I can't get clients.conf confiugure and it have a very strange behavior (at
least to me). The
problem is the following:
1.If clients.conf contains
client 10.20.1.0/24 {
secret = shared_secret
sortname = WLAN
}
It ignores all the incoming connections:
Ignoring request from unknown client 10.20.1.100 port 3846
2.If I put both
client 10.20.1.0/24 {
secret = shared_secret
sortname = WLAN
}
and
client 10.20.1.100 {
secret = shared_secret
sortname = WLAN
}
It accepts the requests from 10.20.1.100
3.If I put only
client 10.20.1.100 {
secret = shared_secret
sortname = WLAN
}
It ignores all connections including 10.20.1.100
4.If I add another client to the 2nd case it ignores all the connections.
Can anyone help me understand where I'm wrong?
I would like to make it accept all the connections from the APs in the net
10.20.1.* or 10.20.*.* in
a WiFi network.
I'm running freeradius-snapshot-20050818 on RH9.
Thanks
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
clients.conf problem
Hello,
I can't get clients.conf confiugure and it have a very strange behavior (at
least to me). The
problem is the following:
1.If clients.conf contains
client 10.20.1.0/24 {
secret = shared_secret
sortname = WLAN
}
It ignores all the incoming connections:
Ignoring request from unknown client 10.20.1.100 port 3846
2.If I put both
client 10.20.1.0/24 {
secret = shared_secret
sortname = WLAN
}
and
client 10.20.1.100 {
secret = shared_secret
sortname = WLAN
}
It accepts the requests from 10.20.1.100
3.If I put only
client 10.20.1.100 {
secret = shared_secret
sortname = WLAN
}
It ignores all connections including 10.20.1.100
4.If I add another client to the 2nd case it ignores all the connections.
Can anyone help me understand where I'm wrong?
I would like to make it accept all the connections from the APs in the net
10.20.1.* or 10.20.*.* in
a WiFi network.
I'm running freeradius-snapshot-20050818 on RH9.
Thanks
--
Naručite svoj XXLadsl - instalacija i modem i dalje za samo 1 kn!
Postanite i vi korisnik ultra brzog Interneta! http://www.iskon.biz/xxladsl
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: clients.conf problem
"Tobias Amon" <[EMAIL PROTECTED]> wrote: > I have a new installation of freeradius 0.8.1 Do NOT use 0.8.1! Use 1.0.0. If there's no package for your OS, try 0.9.3. > testing with "radtest username userpassword 127.0.0.1 0 XXX" is no > problem but testing with "radtest username userpassword 10.44.3.222 > 0 XXX" does not work Are you sure you're using the right port? This isn't generally a RADIUS problem. It's a network problem. Use network tools to see where the packets are going. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
AW: clients.conf problem
Hello,
I got a solution, but i donÄt know i fit fits your problem.
I changed the values at the false clients.conf . The clients.conf-file used by the
server
is in the /usr/local/etc/raddb/ directory . if not in your case try finding a
clients.conf file
useing "find -name clients.conf" at the console
Adding the right lines the made the server working.
But now my Cisco 350 AP does not "talk" to the server.
Thats another problem, but i'm oing to fix it
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] im Auftrag von John Wry
Gesendet: Mo 16.08.2004 13:55
An: [EMAIL PROTECTED]
Cc:
Betreff: Re: clients.conf problem
hello tobias,
I'm having the exact problem. Not sure how to help, I have posted
questions but have no answers yet.
radtest test test localhost 0 testing123 works fine, but my dialup
users don't.
please let me know if you get something. I'll notify you of updates.
Thanks.
John Wry
On Monday, August 16, 2004, at 07:50 AM, Tobias Amon wrote:
> Hello,
>
> i'm trying to run a freeradius-server on Suse 7.0
> I have a new installation of freeradius 0.8.1
>
> I changed the clients.conf and useres Files
> I added "client 10.44.3.222{ secret = XXX nastype = other }" to
> clients.conf
> and "username userpassword Password = "XXX" " to users
> I did not Change the radiusd.conf
>
> testing with "radtest username userpassword 127.0.0.1 0 XXX" is no
> problem
> but testing with "radtest username userpassword 10.44.3.222 0 XXX"
> does not work
> testing with NTRadPing from another machine (Client also added to
> clients.conf) does not work
>
> where does the server take the clients?
> what is wrong?
>
>
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
<>
Re: clients.conf problem
hello tobias,
I'm having the exact problem. Not sure how to help, I have posted
questions but have no answers yet.
radtest test test localhost 0 testing123 works fine, but my dialup
users don't.
please let me know if you get something. I'll notify you of updates.
Thanks.
John Wry
On Monday, August 16, 2004, at 07:50 AM, Tobias Amon wrote:
Hello,
i'm trying to run a freeradius-server on Suse 7.0
I have a new installation of freeradius 0.8.1
I changed the clients.conf and useres Files
I added "client 10.44.3.222{ secret = XXX nastype = other }" to
clients.conf
and "username userpassword Password = "XXX" " to users
I did not Change the radiusd.conf
testing with "radtest username userpassword 127.0.0.1 0 XXX" is no
problem
but testing with "radtest username userpassword 10.44.3.222 0 XXX"
does not work
testing with NTRadPing from another machine (Client also added to
clients.conf) does not work
where does the server take the clients?
what is wrong?
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
clients.conf problem
Hello,
i'm trying to run a freeradius-server on Suse 7.0
I have a new installation of freeradius 0.8.1
I changed the clients.conf and useres Files
I added "client 10.44.3.222{ secret = XXX nastype = other }" to clients.conf
and "username userpassword Password = "XXX" " to users
I did not Change the radiusd.conf
testing with "radtest username userpassword 127.0.0.1 0 XXX" is no problem
but testing with "radtest username userpassword 10.44.3.222 0 XXX" does not work
testing with NTRadPing from another machine (Client also added to clients.conf) does
not work
where does the server take the clients?
what is wrong?
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
