Thanks, I have just changed the NasType for my windows clients to "Ping" - at least it is better than nothing :-)
Regards, Tunde I. ----- Original Message ----- From: "Andreas Stollar" <[EMAIL PROTECTED]> To: "Ayotunde Itayemi" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, September 10, 2002 4:37 PM Subject: Re: Antwort: (RADIATOR) Re: *GhostSessions Problem > Hello, > > I was having a similar problem using "DefaultSimultaneousUse 1" in my > config. I mostly blame our outsourced dial up vendor, who uses a chaotic > mess of different NAS devices, so stop records did not always get > received, and using either snmp or finger only worked for half of the > NAS's out there. We were having a support nightmare with users not being > allowed to dial up because Radiator had an active session. As a last > resort I started using "NasType Ping" under my DEFAULT client. This has > turned out almost perfect. Ok, so someone with a firewall that blocks icmp > traffic will be able to get multiple sessions now, but this is minor > compared to the amount of happy customers now no longer calling tech > support. > > Andreas Stollar > Speakeasy, Inc. Sr. System Administrator > > On Tue, 10 Sep 2002, Ayotunde Itayemi wrote: > > > Date: Tue, 10 Sep 2002 09:51:35 +0100 > > From: Ayotunde Itayemi <[EMAIL PROTECTED]> > > To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> > > Subject: Re: Antwort: (RADIATOR) Re: *GhostSessions Problem > > > > > > ----- Original Message ----- > > From: "Ayotunde Itayemi" <[EMAIL PROTECTED]> > > To: "Hugh Irvine" <[EMAIL PROTECTED]> > > Sent: Tuesday, September 10, 2002 9:51 AM > > Subject: Re: Antwort: (RADIATOR) Re: *GhostSessions Problem > > > > > > > Hi Hugh, > > > > > > I know you have said before that there is no way to query windows for > > online > > > clients > > > using SNMP. This is just to the "house" in general. Is there anyone out > > > there with > > > workable solutions for windows? > > > > > > Regards, > > > Tunde I. > > > > > > ----- Original Message ----- > > > From: "Hugh Irvine" <[EMAIL PROTECTED]> > > > To: "Christian Rautscher" <[EMAIL PROTECTED]> > > > Cc: <[EMAIL PROTECTED]> > > > Sent: Tuesday, September 10, 2002 8:34 AM > > > Subject: Re: Antwort: (RADIATOR) Re: *GhostSessions Problem > > > > > > > > > > > > > > Hello Christian - > > > > > > > > As I discussed in a previous mail, Radiator can use the NasType > > > > parameter in the Client clause(s) to enforce strict session limit > > > > checking with the NAS equipement being used, as long as the NAS can be > > > > queried successfully. > > > > > > > > Unfortunately, we cannot provide solutions for all types of NAS and all > > > > versions of NAS software, so it becomes a matter of trial and error for > > > > Radiator users to work out how to make things work in their own > > > > environment. We have provided a number of NasType modules and the source > > > > code for all of them is in the "Radius/Nas" directory. > > > > > > > > The only thing I can suggest is that you test the query that Radiator > > > > tries to run by hand to see what result you get, and if it is not > > > > correct then you will need to verify what is wrong in the code and > > > > correct it. It may also be the case that you need a different version of > > > > the SNMP code for example, or that your NAS needs to be configured to > > > > respond correctly to the query that Radiator tries to send. > > > > > > > > Note that we do not have any NAS equipment ourselves and we rely on > > > > customers to do their own testing. Many customers have done exactly this > > > > and contributed their code, most of which is what is found in the > > > > Radiator distribution. > > > > > > > > This is a vexing problem, I know, but there is little I can do to help > > > > you. > > > > > > > > regards > > > > > > > > Hugh > > > > > > > > > > > > On Tuesday, September 10, 2002, at 04:22 PM, Christian Rautscher wrote: > > > > > > > > > > > > > > Hello Hugh, > > > > > i did post it already in the Mailing List last week, but i > > > > > got no reply. That's why i thought, as we did buy a 7-station-licence > > > > > of Radiator i could send it to the support list, and hope > > > > > that somebody will response me there :) > > > > > > > > > > You cannot help me or? I mean can you give me at least a little > > > > > hint, how the problem could be resolved. ;) > > > > > > > > > > Happy working, > > > > > regards, > > > > > Christian > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hugh Irvine <[EMAIL PROTECTED]>@open.com.au am 10.09.2002 03:58:06 > > > > > > > > > > Gesendet von: [EMAIL PROTECTED] > > > > > > > > > > > > > > > An: "Christian Rautscher" <[EMAIL PROTECTED]> > > > > > Kopie: [EMAIL PROTECTED] (Blindkopie: Christian > > Rautscher/RUN/RAIFF) > > > > > > > > > > Thema: (RADIATOR) Re: *GhostSessions Problem > > > > > > > > > > > > > > > > > > > > Hello Christian - > > > > > > > > > > I have posted this to the Radiator mailing ([EMAIL PROTECTED]) list > > > > > for you. > > > > > > > > > > You should post these questions to the Radiator list, not the support > > > > > list. > > > > > > > > > > regards > > > > > > > > > > Hugh > > > > > > > > > > > > > > > On Monday, September 9, 2002, at 07:30 PM, Christian Rautscher wrote: > > > > > > > > > >> Hello Hugh, hi everybody, > > > > >> > > > > >> i'd like to ask if some1 could help me with the quite "famous" > > > > >> Problem of the "ghost-sessions" in Radiator-DB. > > > > >> > > > > >> P.es. > > > > >> > > > > >> AccessServer works fine. Connecting clients will be registered in > > > > >> the Radonline-DB of Radiator with their SessionStart-Entry. Now lets > > > > >> assume that at a certain point, due to networking failure or other > > > > >> reason > > > > >> Radiator and AccessServer aren't able to comunicate to each other > > > > >> anymore. > > > > >> > > > > >> Now we assume that Client A and B are disconnecting themselves right > > at > > > > >> this moment. > > > > >> PROBLEM: NAS doesn't send Stop-Session-Entry to Radiator, so for > > > > >> Radiator that > > > > >> client is still online. > > > > >> > > > > >> Now let's assume that the communication Problem between Radiator and > > > > >> NAS > > > > >> has been > > > > >> solved, and client A would like to re-enter. But isn't able, because > > > > >> of > > > > >> the > > > > >> configuration of Radiator the client exceeds the its allowed > > > > >> simulateous > > > > >> Permission of 1. > > > > >> > > > > >> As i've already tried with the Nas-Type Attribute but somehow it > > won't > > > > >> work > > > > >> as it should. > > > > >> > > > > >> As i noticed that this kind of problem appeared quite often in this > > > > >> mailing-list i hope that > > > > >> someone may be able to help me. > > > > >> > > > > >> Thank you just in advance, > > > > >> Christian > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > > > > > > > > -- > > > > > 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. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > 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. > > > > > > === > 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.
