(RADIATOR) Something for the Wish List

2003-08-28 Thread Brian Morris
Hi folks,

I would like to propose a 'feature' to add to the Radiator wishlist.

How about a feature where, if a customer is not permitted more than one
simultaneous login, that the system allows the second connection to connect,
but also drops the first connection.

This will have two benefits to my specific case...

1.  If a subscriber was logged in at work then went home but forgot to
disconnect from work, he can still connect when he gets home without having
to get us to drop his other connection. (less support requests = happy
customer = happy support staff = happy manager!)

2.  'Leechers' who buy unlimited access accounts then share them with
friends will be booted off whenever they break the rules. (less leechers =
got the bastards = more profit = happy manager!!)

Perhaps a post-auth hook or something could do this.  The actual disconnect
process would be NAS dependant but I am sure it could be done.

Regards,

Brian Morris
(somewhat happy) Manager,
NetSpeed


===
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) Something for the Wish List

2003-08-28 Thread Bret Jordan
That would open a really bad DOS attack.

Bret

Brian Morris wrote:

Hi folks,

I would like to propose a 'feature' to add to the Radiator wishlist.

How about a feature where, if a customer is not permitted more than one
simultaneous login, that the system allows the second connection to connect,
but also drops the first connection.
This will have two benefits to my specific case...

1.  If a subscriber was logged in at work then went home but forgot to
disconnect from work, he can still connect when he gets home without having
to get us to drop his other connection. (less support requests = happy
customer = happy support staff = happy manager!)
2.  'Leechers' who buy unlimited access accounts then share them with
friends will be booted off whenever they break the rules. (less leechers =
got the bastards = more profit = happy manager!!)
Perhaps a post-auth hook or something could do this.  The actual disconnect
process would be NAS dependant but I am sure it could be done.
Regards,

Brian Morris
(somewhat happy) Manager,
NetSpeed
===
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.
 

--
~~~
Bret Jordan   Dean's Office
Computer Administrator   College of Engineering
801.585.3765 University of Utah
   [EMAIL PROTECTED]
~~~


===
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) Something for the Wish List

2003-08-28 Thread Brian Morris

I don't see how (but I would love to find out)

If they must first authenticate successfully before we boot the other one
off then I can't see how it would cause a DOS.  If I am missing something
please correct me - It wouldn't be the first time :-)

Regards,  Brian



- Original Message - 
From: Bret Jordan [EMAIL PROTECTED]
To: Brian Morris [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Thursday, August 28, 2003 1:46 PM
Subject: Re: (RADIATOR) Something for the Wish List


 That would open a really bad DOS attack.

 Bret

 Brian Morris wrote:

 Hi folks,
 
 I would like to propose a 'feature' to add to the Radiator wishlist.
 
 How about a feature where, if a customer is not permitted more than one
 simultaneous login, that the system allows the second connection to
connect,
 but also drops the first connection.
 
 This will have two benefits to my specific case...
 
 1.  If a subscriber was logged in at work then went home but forgot to
 disconnect from work, he can still connect when he gets home without
having
 to get us to drop his other connection. (less support requests = happy
 customer = happy support staff = happy manager!)
 
 2.  'Leechers' who buy unlimited access accounts then share them with
 friends will be booted off whenever they break the rules. (less leechers
=
 got the bastards = more profit = happy manager!!)
 
 Perhaps a post-auth hook or something could do this.  The actual
disconnect
 process would be NAS dependant but I am sure it could be done.
 
 Regards,
 
 Brian Morris
 (somewhat happy) Manager,
 NetSpeed
 
 
 ===
 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.
 
 

 -- 
 ~~~
 Bret Jordan   Dean's Office
 Computer Administrator   College of Engineering
 801.585.3765 University of Utah
 [EMAIL PROTECTED]
 ~~~





===
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) Something for the Wish List

2003-08-28 Thread Hugh Irvine
Hello Brian -

You could probably implement this with a PreClientHook to do what you 
describe.

There are some example hooks in the file goodies/hooks.txt.

regards

Hugh

On Thursday, Aug 28, 2003, at 13:06 Australia/Melbourne, Brian Morris 
wrote:

Hi folks,

I would like to propose a 'feature' to add to the Radiator wishlist.

How about a feature where, if a customer is not permitted more than one
simultaneous login, that the system allows the second connection to 
connect,
but also drops the first connection.

This will have two benefits to my specific case...

1.  If a subscriber was logged in at work then went home but forgot to
disconnect from work, he can still connect when he gets home without 
having
to get us to drop his other connection. (less support requests = happy
customer = happy support staff = happy manager!)

2.  'Leechers' who buy unlimited access accounts then share them with
friends will be booted off whenever they break the rules. (less 
leechers =
got the bastards = more profit = happy manager!!)

Perhaps a post-auth hook or something could do this.  The actual 
disconnect
process would be NAS dependant but I am sure it could be done.

Regards,

Brian Morris
(somewhat happy) Manager,
NetSpeed
===
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.

NB: have you included a copy of your configuration file (no secrets),
together with a trace 4 debug showing what is happening?
--
Radiator: the most portable, flexible and configurable RADIUS server
anywhere. Available on *NIX, *BSD, Windows, 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.