Re: (RADIATOR) Re: DefaultLeasePeriod
Hello Brian - I can't see any easy way around this, other than to write some custom queries, or perhaps a stored procedure in the database. Or alternatively, what about setting up the address pools on the NAS? regards Hugh On Tuesday, August 20, 2002, at 05:32 AM, Brian Morris wrote: I think in the case of DSL clients though this is not quite correct. We have several 000's of DSL clients but only about 25% of them are online at any one time. Sure they CAN be permanent, but they usually are not. It is a waste of IP space to allocate a static IP to all of them. In some business cases it is even desirous not to allocate them a static IP - but rather make it an 'additional' purchase ;-) We have sometimes run into a problem where if the NAS fails, or the customers DSL router messes up and tries to login hundreds of times a minute we soon run out of available IP addresses in RADPOOL - upon inspection of RADPOOL it shows that the same user has dozens or more ip addresses allocated to them with a state of (1). It would be good if there was some method of clearing these up - currently, we run a script which sets the state of all but the most receint allocation to (0) for any user with more than one entry in RADPOOL. (We don't allow simultaneous logins on our DSL service) Has anyone else has similar problems and/or found a solution? Regards, Brian. - Original Message - From: Hugh Irvine To: Ayotunde Itayemi Cc: [EMAIL PROTECTED] Sent: Monday, August 19, 2002 11:48 PM Subject: Re: (RADIATOR) Re: DefaultLeasePeriod Hello Tunde - By definition a customer with a permanent connection would not use a dynamic address. You should allocate such users static addresses instead. regards Hugh NB: I am travelling this week, so there may be delays in our correspondence. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence.
(RADIATOR) Re: DefaultLeasePeriod
Hello Tunde - The IP address in the address pool is marked as available when the DefaultLeasePeriod expires. There is no relationship between the Session-Timeout on the NAS and the DefaultLeasePeriod for the IP address allocation. You will have to manage any relationship that you wish to have with your configuration. regards Hugh On Monday, August 19, 2002, at 06:09 PM, Ayotunde Itayemi wrote: Hi Hugh, Hi All, What happens when the DefaultLeasePeriod (say 86400 = 1 day) expires? Does the user get disconnected and the IP allocated to him/her reclaimed? Or is the user (correctly) allowed to stay connected? Let's assume that the checkattribute of the clients specifies that he/she can stay on for the whole day (Service-Type = Framed-User,Time ="Al-2400",Simultaneous-Use = 1) Regards, Tunde I. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence.
Re: (RADIATOR) Re: DefaultLeasePeriod
Hi Hugh, One, I assume the checkattribute ( Service-Type = Framed-User,Time ="Al-2400",Simultaneous-Use = 1) implies "always-on 24-7-365" access for the user? My aim is to allow clients with DSL access (alwayson-24-7-365)to remain on without radiatiorreclaiming the IP address allocated to themwhile they are still connected. What combination of attributes do you think can handle clients with DSL access (alwayson-24-7-365) and dial-up access so that the IP address is not reclaimed for the DSL clients while they are still connected - and still reclaim the IP addresses allocated to the dial-up/DSL clients when they disconnect by themselves from the NASes? Would setting the Defaultleaseperiod to "infinity" ( :-) or say a year, and leaving the LeaseReclaimInterval set to (say) a day handle the kind of configuration I mentioned above? That is, correctly reclaim the IPaddresses for clients when they are disconnected (by NAS, attributes, etc) and also not reclaim the IP addresses allocated to clients that are still online. Regards, Tunde Itayemi. - Original Message - From: Hugh Irvine To: Ayotunde Itayemi Cc: [EMAIL PROTECTED] Sent: Monday, August 19, 2002 12:31 PM Subject: (RADIATOR) Re: DefaultLeasePeriod Hello Tunde -The IP address in the address pool is marked as available when the DefaultLeasePeriod expires.There is no relationship between the Session-Timeout on the NAS and the DefaultLeasePeriod for the IP address allocation. You will have to manage any relationship that you wish to have with your configuration.regardsHughOn Monday, August 19, 2002, at 06:09 PM, Ayotunde Itayemi wrote: Hi Hugh, Hi All,What happens when the DefaultLeasePeriod(say 86400 = 1 day) expires?Does the user get disconnected and the IP allocated to him/her reclaimed?Or is the user (correctly) allowed to stay connected?Let's assume that the checkattribute of the clients specifies that he/shecan stay on for the whole day (Service-Type = Framed-User,Time ="Al-2400",Simultaneous-Use = 1)Regards,Tunde I.-- Radiator: the most portable, flexible and configurable RADIUS serveranywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.-Nets: internetwork inventory and management - graphical, extensible,flexible with hardware, software, platform and database independence.
RE: (RADIATOR) Re: DefaultLeasePeriod
Does anyone know how to set up clients, NAS etc to make the client use a DHCP server at the ISP? Is it as simple as doing a normal DHCP configuration in the client, and then set up your DHCP server? Or do you have to configure the NAS as well? Because such a setup would allow the client to renew its own IP address according to the lease time configured in the DHCP server. /Ingvar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Hi Hugh, One, I assume the checkattribute ( Service-Type = Framed-User,Time =Al-2400,Simultaneous-Use = 1) implies always-on 24-7-365 access for the user? My aim is to allow clients with DSL access (alwayson-24-7-365) to remain on without radiatior reclaiming the IP address allocated to them while they are still connected. What combination of attributes do you think can handle clients with DSL access (alwayson-24-7-365) and dial-up access so that the IP address is not reclaimed for the DSL clients while they are still connected - and still reclaim the IP addresses allocated to the dial-up/DSL clients when they disconnect by themselves from the NASes? Would setting the Defaultleaseperiod to infinity ( :-) or say a year, and leaving the LeaseReclaimInterval set to (say) a day handle the kind of configuration I mentioned above? That is, correctly reclaim the IPaddresses for clients when they are disconnected (by NAS, attributes, etc) and also not reclaim the IP addresses allocated to clients that are still online. Regards, Tunde Itayemi. - Original Message - From: Hugh Irvine mailto:[EMAIL PROTECTED] To: Ayotunde Itayemi mailto:[EMAIL PROTECTED] Cc: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Sent: Monday, August 19, 2002 12:31 PM Subject: (RADIATOR) Re: DefaultLeasePeriod Hello Tunde - The IP address in the address pool is marked as available when the DefaultLeasePeriod expires. There is no relationship between the Session-Timeout on the NAS and the DefaultLeasePeriod for the IP address allocation. You will have to manage any relationship that you wish to have with your configuration. regards Hugh On Monday, August 19, 2002, at 06:09 PM, Ayotunde Itayemi wrote: Hi Hugh, Hi All, What happens when the DefaultLeasePeriod (say 86400 = 1 day) expires? Does the user get disconnected and the IP allocated to him/her reclaimed? Or is the user (correctly) allowed to stay connected? Let's assume that the checkattribute of the clients specifies that he/she can stay on for the whole day (Service-Type = Framed-User,Time =Al-2400,Simultaneous-Use = 1) Regards, Tunde I. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Re: DefaultLeasePeriod
Hello Tunde - By definition a customer with a permanent connection would not use a dynamic address. You should allocate such users static addresses instead. regards Hugh On Monday, August 19, 2002, at 10:10 PM, Ayotunde Itayemi wrote: Hi Hugh, One, I assume the checkattribute ( Service-Type = Framed-User,Time ="Al-2400",Simultaneous-Use = 1) implies "always-on 24-7-365" access for the user? My aim is to allow clients with DSL access (alwayson-24-7-365) to remain on without radiatior reclaiming the IP address allocated to them while they are still connected. What combination of attributes do you think can handle clients with DSL access (alwayson-24-7-365) and dial-up access so that the IP address is not reclaimed for the DSL clients while they are still connected - and still reclaim the IP addresses allocated to the dial-up/DSL clients when they disconnect by themselves from the NASes? Would setting the Defaultleaseperiod to "infinity" ( :-) or say a year, and leaving the LeaseReclaimInterval set to (say) a day handle the kind of configuration I mentioned above? That is, correctly reclaim the IPaddresses for clients when they are disconnected (by NAS, attributes, etc) and also not reclaim the IP addresses allocated to clients that are still online. Regards, Tunde Itayemi. - Original Message - From: Hugh Irvine To: Ayotunde Itayemi Cc: [EMAIL PROTECTED] Sent: Monday, August 19, 2002 12:31 PM Subject: (RADIATOR) Re: DefaultLeasePeriod Hello Tunde - The IP address in the address pool is marked as available when the DefaultLeasePeriod expires. There is no relationship between the Session-Timeout on the NAS and the DefaultLeasePeriod for the IP address allocation. You will have to manage any relationship that you wish to have with your configuration. regards Hugh On Monday, August 19, 2002, at 06:09 PM, Ayotunde Itayemi wrote: Hi Hugh, Hi All, What happens when the DefaultLeasePeriod (say 86400 = 1 day) expires? Does the user get disconnected and the IP allocated to him/her reclaimed? Or is the user (correctly) allowed to stay connected? Let's assume that the checkattribute of the clients specifies that he/she can stay on for the whole day (Service-Type = Framed-User,Time ="Al-2400",Simultaneous-Use = 1) Regards, Tunde I. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence.
Re: (RADIATOR) Re: DefaultLeasePeriod
Hello Ingvar - No I have never seen such a thing. This is because the end client device must start a session (usually PPP) *before* it can send TCP/UDP packets. regards Hugh On Monday, August 19, 2002, at 11:41 PM, Ingvar Berg (EAB) wrote: Does anyone know how to set up clients, NAS etc to make the client use a DHCP server at the ISP? Is it as simple as doing a normal DHCP configuration in the client, and then set up your DHCP server? Or do you have to configure the NAS as well? Because such a setup would allow the client to renew its own IP address according to the lease time configured in the DHCP server. /Ingvar -Original Message- From:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Hi Hugh, One, I assume the checkattribute ( Service-Type = Framed-User,Time =Al-2400,Simultaneous-Use = 1) implies always-on 24-7-365 access for the user? My aim is to allow clients with DSL access (alwayson-24-7-365) to remain on without radiatior reclaiming the IP address allocated to them while they are still connected. What combination of attributes do you think can handle clients with DSL access (alwayson-24-7-365) and dial-up access so that the IP address is not reclaimed for the DSL clients while they are still connected - and still reclaim the IP addresses allocated to the dial-up/DSL clients when they disconnect by themselves from the NASes? Would setting the Defaultleaseperiod to infinity ( :-) or say a year, and leaving the LeaseReclaimInterval set to (say) a day handle the kind of configuration I mentioned above? That is, correctly reclaim the IPaddresses for clients when they are disconnected (by NAS, attributes, etc) and also not reclaim the IP addresses allocated to clients that are still online. Regards, Tunde Itayemi. - Original Message - From: Hugh Irvine mailto:[EMAIL PROTECTED] To: Ayotunde Itayemi mailto:[EMAIL PROTECTED] Cc: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Sent: Monday, August 19, 2002 12:31 PM Subject: (RADIATOR) Re: DefaultLeasePeriod Hello Tunde - The IP address in the address pool is marked as available when the DefaultLeasePeriod expires. There is no relationship between the Session-Timeout on the NAS and the DefaultLeasePeriod for the IP address allocation. You will have to manage any relationship that you wish to have with your configuration. regards Hugh On Monday, August 19, 2002, at 06:09 PM, Ayotunde Itayemi wrote: Hi Hugh, Hi All, What happens when the DefaultLeasePeriod (say 86400 = 1 day) expires? Does the user get disconnected and the IP allocated to him/her reclaimed? Or is the user (correctly) allowed to stay connected? Let's assume that the checkattribute of the clients specifies that he/she can stay on for the whole day (Service-Type = Framed-User,Time =Al-2400,Simultaneous-Use = 1) Regards, Tunde I. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
RE: (RADIATOR) Re: DefaultLeasePeriod
Just thought that it would be A Nice Thing, if the NAS could act as a DHCP relay, and leave it to the client and the DHCP server to do this the standard way. (A Nice Thing usually exists already, and can be found, you just have to know where to search ;-). /Ingvar -Original Message- From: Hugh Irvine [mailto:[EMAIL PROTECTED]] Hello Ingvar - No I have never seen such a thing. This is because the end client device must start a session (usually PPP) *before* it can send TCP/UDP packets. regards Hugh On Monday, August 19, 2002, at 11:41 PM, Ingvar Berg (EAB) wrote: Does anyone know how to set up clients, NAS etc to make the client use a DHCP server at the ISP? Is it as simple as doing a normal DHCP configuration in the client, and then set up your DHCP server? Or do you have to configure the NAS as well? Because such a setup would allow the client to renew its own IP address according to the lease time configured in the DHCP server. /Ingvar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Hi Hugh, One, I assume the checkattribute ( Service-Type = Framed-User,Time =Al-2400,Simultaneous-Use = 1) implies always-on 24-7-365 access for the user? My aim is to allow clients with DSL access (alwayson-24-7-365) to remain on without radiatior reclaiming the IP address allocated to them while they are still connected. What combination of attributes do you think can handle clients with DSL access (alwayson-24-7-365) and dial-up access so that the IP address is not reclaimed for the DSL clients while they are still connected - and still reclaim the IP addresses allocated to the dial-up/DSL clients when they disconnect by themselves from the NASes? Would setting the Defaultleaseperiod to infinity ( :-) or say a year, and leaving the LeaseReclaimInterval set to (say) a day handle the kind of configuration I mentioned above? That is, correctly reclaim the IPaddresses for clients when they are disconnected (by NAS, attributes, etc) and also not reclaim the IP addresses allocated to clients that are still online. Regards, Tunde Itayemi. - Original Message - From: Hugh Irvine mailto:[EMAIL PROTECTED] To: Ayotunde Itayemi mailto:[EMAIL PROTECTED] Cc: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Sent: Monday, August 19, 2002 12:31 PM Subject: (RADIATOR) Re: DefaultLeasePeriod Hello Tunde - The IP address in the address pool is marked as available when the DefaultLeasePeriod expires. There is no relationship between the Session-Timeout on the NAS and the DefaultLeasePeriod for the IP address allocation. You will have to manage any relationship that you wish to have with your configuration. regards Hugh On Monday, August 19, 2002, at 06:09 PM, Ayotunde Itayemi wrote: Hi Hugh, Hi All, What happens when the DefaultLeasePeriod (say 86400 = 1 day) expires? Does the user get disconnected and the IP allocated to him/her reclaimed? Or is the user (correctly) allowed to stay connected? Let's assume that the checkattribute of the clients specifies that he/she can stay on for the whole day (Service-Type = Framed-User,Time =Al-2400,Simultaneous-Use = 1) Regards, Tunde I. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Re: DefaultLeasePeriod
Hi Hugh, Okay you are right. But what if I would like to ensure that the max time a client can stay on is a day? That is, even the "always-on" clients get disconnected at least once everyday? In such a case, what would my checkattributes and replyattributes be? Regards, Tunde I. - Original Message - From: Hugh Irvine To: Ayotunde Itayemi Cc: [EMAIL PROTECTED] Sent: Monday, August 19, 2002 2:48 PM Subject: Re: (RADIATOR) Re: DefaultLeasePeriod Hello Tunde -By definition a customer with a permanent connection would not use a dynamic address.You should allocate such users static addresses instead.regardsHughOn Monday, August 19, 2002, at 10:10 PM, Ayotunde Itayemi wrote: Hi Hugh,One, I assume the checkattribute ( Service-Type = Framed-User,Time ="Al-2400",Simultaneous-Use = 1)implies "always-on 24-7-365" access for the user?My aim is to allow clients with DSL access (alwayson-24-7-365)to remain on without radiatiorreclaiming theIP address allocated to themwhile they are still connected.What combination of attributes do you think can handle clients with DSL access (alwayson-24-7-365) and dial-upaccess so that the IP address is not reclaimed for the DSL clients while they are still connected - and still reclaimthe IP addresses allocated to the dial-up/DSL clients when they disconnect by themselves from the NASes?Would setting the Defaultleaseperiod to "infinity" ( :-) or say a year, and leaving the LeaseReclaimInterval set to(say) a day handle the kind of configuration I mentioned above? That is, correctly reclaim the IPaddresses for clientswhen they are disconnected (by NAS, attributes, etc) and also not reclaim the IP addresses allocated to clientsthat are still online.Regards,Tunde Itayemi.- Original Message -From: Hugh IrvineTo: Ayotunde ItayemiCc: [EMAIL PROTECTED]Sent: Monday, August 19, 2002 12:31 PMSubject: (RADIATOR) Re: DefaultLeasePeriodHello Tunde -The IP address in the address pool is marked as available when the DefaultLeasePeriod expires.There is no relationship between the Session-Timeout on the NAS and the DefaultLeasePeriod for the IP address allocation. You will have to manage any relationship that you wish to have with your configuration.regardsHughOn Monday, August 19, 2002, at 06:09 PM, Ayotunde Itayemi wrote:Hi Hugh, Hi All,What happens when the DefaultLeasePeriod(say 86400 = 1 day) expires?Does the user get disconnected and the IP allocated to him/her reclaimed?Or is the user (correctly) allowed to stay connected?Let's assume that the checkattribute of the clients specifies that he/shecan stay on for the whole day (Service-Type = Framed-User,Time ="Al-2400",Simultaneous-Use = 1)Regards,Tunde I.--Radiator: the most portable, flexible and configurable RADIUS serveranywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.-Nets: internetwork inventory and management - graphical, extensible,flexible with hardware, software, platform and database independence.-- Radiator: the most portable, flexible and configurable RADIUS serveranywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X.-Nets: internetwork inventory and management - graphical, extensible,flexible with hardware, software, platform and database independence.
RE: (RADIATOR) Re: DefaultLeasePeriod
Hello Ingvar, I think perhaps it will depend heavily on the capabilities of the NAS itself to do such a thing. If you are talking Cisco here, the NAS has all the same capabilities as a standard router. At least I can recall a setup we did once in the past where we allowed DHCP broadcast queries to leak from one LAN across a serial link and on the other side, to the DHCP server. There was a command named 'ip helper address' I think, don't recall very well, though. Perhaps this is a starting point for your quest :) Now, if you are talking about other NAS brands here, I won't be able to help. regards, cl. From: Ingvar Berg (EAB) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: (RADIATOR) Re: DefaultLeasePeriod Date: Mon, 19 Aug 2002 16:18:26 +0200 Just thought that it would be A Nice Thing, if the NAS could act as a DHCP relay, and leave it to the client and the DHCP server to do this the standard way. (A Nice Thing usually exists already, and can be found, you just have to know where to search ;-). /Ingvar -Original Message- From: Hugh Irvine [mailto:[EMAIL PROTECTED]] Hello Ingvar - No I have never seen such a thing. This is because the end client device must start a session (usually PPP) *before* it can send TCP/UDP packets. regards Hugh On Monday, August 19, 2002, at 11:41 PM, Ingvar Berg (EAB) wrote: Does anyone know how to set up clients, NAS etc to make the client use a DHCP server at the ISP? Is it as simple as doing a normal DHCP configuration in the client, and then set up your DHCP server? Or do you have to configure the NAS as well? Because such a setup would allow the client to renew its own IP address according to the lease time configured in the DHCP server. /Ingvar -Original Message- From:[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Hi Hugh, One, I assume the checkattribute ( Service-Type = Framed-User,Time =Al-2400,Simultaneous-Use = 1) implies always-on 24-7-365 access for the user? My aim is to allow clients with DSL access (alwayson-24-7-365) to remain on without radiatior reclaiming the IP address allocated to them while they are still connected. What combination of attributes do you think can handle clients with DSL access (alwayson-24-7-365) and dial-up access so that the IP address is not reclaimed for the DSL clients while they are still connected - and still reclaim the IP addresses allocated to the dial-up/DSL clients when they disconnect by themselves from the NASes? Would setting the Defaultleaseperiod to infinity ( :-) or say a year, and leaving the LeaseReclaimInterval set to (say) a day handle the kind of configuration I mentioned above? That is, correctly reclaim the IPaddresses for clients when they are disconnected (by NAS, attributes, etc) and also not reclaim the IP addresses allocated to clients that are still online. Regards, Tunde Itayemi. - Original Message - From: Hugh Irvine mailto:[EMAIL PROTECTED] To: Ayotunde Itayemi mailto:[EMAIL PROTECTED] Cc: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Sent: Monday, August 19, 2002 12:31 PM Subject: (RADIATOR) Re: DefaultLeasePeriod Hello Tunde - The IP address in the address pool is marked as available when the DefaultLeasePeriod expires. There is no relationship between the Session-Timeout on the NAS and the DefaultLeasePeriod for the IP address allocation. You will have to manage any relationship that you wish to have with your configuration. regards Hugh On Monday, August 19, 2002, at 06:09 PM, Ayotunde Itayemi wrote: Hi Hugh, Hi All, What happens when the DefaultLeasePeriod (say 86400 = 1 day) expires? Does the user get disconnected and the IP allocated to him/her reclaimed? Or is the user (correctly) allowed to stay connected? Let's assume that the checkattribute of the clients specifies that he/she can stay on for the whole day (Service-Type = Framed-User,Time =Al-2400,Simultaneous-Use = 1) Regards, Tunde I. -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message
Re: (RADIATOR) Re: DefaultLeasePeriod
Hello Claudio, Hello Ingvar - As mentioned in my previous mail, DHCP as a protocol uses UDP, which assumes that you already have a properly configured and operating IP stack in place. This is obviously not the case in most cases when Radiator is handling an access request for PPP for example, because the result of the radius authentication will result in the link being set up. As Ingvar already knows, we have implemented the AuthBy DYNADDRESS/AddressAllocator DHCP combination to allow a DHCP server to be used for address allocation in response to a radius request. If as Claudio describes, you are wanting to do DHCP over an already established link, then you can use DHCP request forwarding using Cisco's selective forwarding configuration. regards Hugh On Tuesday, August 20, 2002, at 02:08 AM, Claudio Lapidus wrote: Hello Ingvar, I think perhaps it will depend heavily on the capabilities of the NAS itself to do such a thing. If you are talking Cisco here, the NAS has all the same capabilities as a standard router. At least I can recall a setup we did once in the past where we allowed DHCP broadcast queries to leak from one LAN across a serial link and on the other side, to the DHCP server. There was a command named 'ip helper address' I think, don't recall very well, though. Perhaps this is a starting point for your quest :) Now, if you are talking about other NAS brands here, I won't be able to help. regards, cl. From: Ingvar Berg (EAB) [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: RE: (RADIATOR) Re: DefaultLeasePeriod Date: Mon, 19 Aug 2002 16:18:26 +0200 Just thought that it would be A Nice Thing, if the NAS could act as a DHCP relay, and leave it to the client and the DHCP server to do this the standard way. (A Nice Thing usually exists already, and can be found, you just have to know where to search ;-). /Ingvar -Original Message- From: Hugh Irvine [mailto:[EMAIL PROTECTED]] Hello Ingvar - No I have never seen such a thing. This is because the end client device must start a session (usually PPP) *before* it can send TCP/UDP packets. regards Hugh On Monday, August 19, 2002, at 11:41 PM, Ingvar Berg (EAB) wrote: Does anyone know how to set up clients, NAS etc to make the client use a DHCP server at the ISP? Is it as simple as doing a normal DHCP configuration in the client, and then set up your DHCP server? Or do you have to configure the NAS as well? Because such a setup would allow the client to renew its own IP address according to the lease time configured in the DHCP server. /Ingvar -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Hi Hugh, One, I assume the checkattribute ( Service-Type = Framed-User,Time =Al-2400,Simultaneous-Use = 1) implies always-on 24-7-365 access for the user? My aim is to allow clients with DSL access (alwayson-24-7-365) to remain on without radiatior reclaiming the IP address allocated to them while they are still connected. What combination of attributes do you think can handle clients with DSL access (alwayson-24-7-365) and dial-up access so that the IP address is not reclaimed for the DSL clients while they are still connected - and still reclaim the IP addresses allocated to the dial-up/DSL clients when they disconnect by themselves from the NASes? Would setting the Defaultleaseperiod to infinity ( :-) or say a year, and leaving the LeaseReclaimInterval set to (say) a day handle the kind of configuration I mentioned above? That is, correctly reclaim the IPaddresses for clients when they are disconnected (by NAS, attributes, etc) and also not reclaim the IP addresses allocated to clients that are still online. Regards, Tunde Itayemi. - Original Message - From: Hugh Irvine mailto:[EMAIL PROTECTED] To: Ayotunde Itayemi mailto:[EMAIL PROTECTED] Cc: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Sent: Monday, August 19, 2002 12:31 PM Subject: (RADIATOR) Re: DefaultLeasePeriod Hello Tunde - The IP address in the address pool is marked as available when the DefaultLeasePeriod expires. There is no relationship between the Session-Timeout on the NAS and the DefaultLeasePeriod for the IP address allocation. You will have to manage any relationship that you wish to have with your configuration. regards Hugh On Monday, August 19, 2002, at 06:09 PM, Ayotunde Itayemi wrote: Hi Hugh, Hi All, What happens when the DefaultLeasePeriod (say 86400 = 1 day) expires? Does the user get disconnected and the IP allocated to him/her reclaimed? Or is the user (correctly) allowed to stay connected? Let's assume that the checkattribute of the clients specifies that he/she can stay on for the whole day (Service-Type
Re: (RADIATOR) Re: DefaultLeasePeriod
I think in the case of DSL clients though this is not quite correct. We have several 000's of DSL clients but only about 25% of them are online at any one time. Sure they CAN be permanent, but they usually are not. It is a waste of IP space to allocate a static IP to all of them. In some business cases it is even desirous not to allocate them a static IP - but rather make itan 'additional' purchase ;-) We have sometimes run into a problem where if the NAS fails, or the customers DSL router messes up and tries to login hundreds of times a minute we soon run out of available IP addresses in RADPOOL - upon inspection of RADPOOL it shows that the same user has dozens or more ip addresses allocated to them with a state of (1). It would be good if there was some method of clearing these up - currently, we run a script which sets the state of all but the most receint allocation to (0) for any user with more than one entry in RADPOOL. (We don't allow simultaneous logins on our DSL service) Has anyone else has similar problems and/or found a solution? Regards, Brian. - Original Message - From: Hugh Irvine To: Ayotunde Itayemi Cc: [EMAIL PROTECTED] Sent: Monday, August 19, 2002 11:48 PM Subject: Re: (RADIATOR) Re: DefaultLeasePeriod Hello Tunde -By definition a customer with a permanent connection would not use a dynamic address.You should allocate such users static addresses instead.regardsHugh
