Hi all I am using two radius servers for our DSL clients. but our client has ip conflict issue. it looks like the first radius issues the ip to the A DSL client. but seondary radius doesn't know this ip already allocated and issue this ip to B DSL client. Then two clients have the same ip address and cause the ip conflict. How can we avoid this problem? Thank you ____________________________________________________________________________________ Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. http://farechase.yahoo.com/promo-generic-14795097
ann kok wrote:
it looks like the first radius issues the ip to the A DSL client. but seondary radius doesn't know this ip already allocated and issue this ip to B DSL client.
You've configured two different RADIUS servers to allocate the same IP to two different people? Why?
How can we avoid this problem?
Each server should have it's own IP pool. IP pools should not be shared between servers. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
Hi Alan Thank you for your mail We are using a LNS this time We are using 2 radius servers. When one radius is down, 2nd radius can help for authenticate Regarding to separate ip spool eg: radius 1. ip from x.x.x.2 - x.x.x.127 radius 2. ip from x.x.x.128 to x.x.x.254 if the radius1 is used up the ip, ls the client automatically asking the radius2 to get the ip? Thank you --- Alan DeKok <aland@deployingradius.com> wrote:
ann kok wrote:
it looks like the first radius issues the ip to the A DSL client. but seondary radius doesn't know this ip already allocated and issue this ip to B DSL client.
You've configured two different RADIUS servers to allocate the same IP to two different people? Why?
How can we avoid this problem?
Each server should have it's own IP pool. IP pools should not be shared between servers.
Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
____________________________________________________________________________________ Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html
ann kok wrote:
Regarding to separate ip spool eg: radius 1. ip from x.x.x.2 - x.x.x.127 radius 2. ip from x.x.x.128 to x.x.x.254
if the radius1 is used up the ip, ls the client automatically asking the radius2 to get the ip?
No. But you can configure radius1 to proxy the request to radius2 if the IP pool on radius1 is completely allocated. Alan DeKok. -- http://deployingradius.com - The web site of the book http://deployingradius.com/blog/ - The blog
On Wed 11 Apr 2007, ann kok wrote:
Hi all
I am using two radius servers for our DSL clients.
but our client has ip conflict issue.
it looks like the first radius issues the ip to the A DSL client. but seondary radius doesn't know this ip already allocated and issue this ip to B DSL client.
Then two clients have the same ip address and cause the ip conflict.
How can we avoid this problem?
Any of the following: * Don't use the same pool range on 2 servers (What made you think that this would work?) * Use a share storage backend (sqlippool with shared database) -- Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc
You could use the same ip pool across two NAS servers if you were only using one radius server to assign IPs. I recommend you either make one radius server handle only one NAS, so the ip pools don't collide, or used rlm_sqlipool across them both as Peter pointed out. Jan On 12/04/07, Peter Nixon <listuser@peternixon.net> wrote:
On Wed 11 Apr 2007, ann kok wrote:
Hi all
I am using two radius servers for our DSL clients.
but our client has ip conflict issue.
it looks like the first radius issues the ip to the A DSL client. but seondary radius doesn't know this ip already allocated and issue this ip to B DSL client.
Then two clients have the same ip address and cause the ip conflict.
How can we avoid this problem?
Any of the following: * Don't use the same pool range on 2 servers (What made you think that this would work?) * Use a share storage backend (sqlippool with shared database)
--
Peter Nixon http://www.peternixon.net/ PGP Key: http://www.peternixon.net/public.asc - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
participants (4)
-
Alan DeKok -
ann kok -
Jan Mulders -
Peter Nixon