Re: (RADIATOR) Caller ID
Seriously, change the usernames and passwords. How do you know they won't use them from another phone number? You are setting yourself up for pain and suffering. Just my $0.02 cheers Mike McCauley wrote: On Apr 15, 2:54pm, Richard Hawley wrote: Subject: Re: (RADIATOR) Caller ID But if I wanted radiator to reject ANY username and password coming from one phone number, the easiest way would be a handler, correct? For example, a former employee who knows several usernames and passwords is trying to logon for free. Nasty. To prevent that from his/her phone number, I would need to use a handler, no? Yes, I think so. Dont forget that the way radiator choses between Realms, DEFAULT Realms, regexp Realms and Handlers may not be immediately obvious, so make sure you test it. Cheers. ..Rich Mike McCauley wrote: On Apr 14, 10:29am, Richard Hawley wrote: Subject: Re: (RADIATOR) Caller ID So if I want to reject one particular phone number and I am using an SQL Subscribers table, how would I go about that without using handlers? I have a feeling I would be forced to use a handler, no? No, you could put this in the affected user(s): username Password=,Calling-Station-Id=/^(?!12345)/ That will reject if the calling station id _is_ 12345 Hope that helps. Cheers. ..Rich Mike McCauley wrote: Hi Anton, Yes, you can set up Radiator to authenticate or reject based on Calling-Station-Id, same as any other check item. You could also use Calling-Station-Id in a Handler clause to choose the auth method to use: Handler Calling-Station-Id=12345 AuthBy ... /Handler Cheers. On Apr 13, 4:11pm, Anton Sparrius wrote: Subject: (RADIATOR) Caller ID [ Attachment (text/plain): 595 bytes Character set: Windows-1252 plain text ] -- End of excerpt from Anton Sparrius Hi, We normally dont worry about the CallerID, but is it possible to not allow a call if it comes from a certain phone number, regardless of what the username is?? Or is this more of a NAS thing? Regards, Anton Sparrius Chief Operations Officer -- Mike McCauley [EMAIL PROTECTED] Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW 24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au Phone +61 3 9598-0985 Fax +61 3 9598-0955 Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, external, etc etc on Unix, Win95/8, NT, Rhapsody === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. -- Richard W. Hawley - Network Engineer CyberZone Internet Services http://www.cyberzone.net [EMAIL PROTECTED] -- End of excerpt from Richard Hawley -- Mike McCauley [EMAIL PROTECTED] Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW 24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au Phone +61 3 9598-0985 Fax +61 3 9598-0955 Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, external, etc etc on Unix, Win95/8, NT, Rhapsody -- Richard W. Hawley - Network Engineer CyberZone Internet Services http://www.cyberzone.net [EMAIL PROTECTED] -- End of excerpt from Richard Hawley -- Mike McCauley [EMAIL PROTECTED] Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW 24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au Phone +61 3 9598-0985 Fax +61 3 9598-0955 Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, external, etc etc on Unix, Win95/8, NT, Rhapsody === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. -- Shori Pty Ltd / Barry W Anderson \ / / Senior Consultant \\\' , / // [EMAIL PROTECTED]\\\//, _/ //, \_-//' / //, http://www.shori.com\ /// //` / \\\`__/_ 42 Munich Drive
Re: (RADIATOR) Lost Stop Records
Mike, I believe there may be a problem here - an ISP I am familiar with uses portmasters (and an inferior radius server ;-)) and they are always complaining about lost stop records. I haven't had a chance to look into it (and haven't been asked), but consider this confirmation that the problem has been seen in the wild. cheers, Barry Mike McCauley wrote: On Apr 16, 12:32pm, Paul Thornton wrote: Subject: (RADIATOR) Lost Stop Records Hi, Does anyone know why I am sometimes not receiving a STOP record for when a user disconnects (for whatever reason). We are using the radius detail logs for accounting purposes, but with this being an intermittent problem our accounting program doesn't record them logging out. This in turn causes another program (Time Watcher) to keep deducting credit. Not good for our records and definately not good for the user. I have basically had to create a script (very resource hungry) which uses smtp to retreive the latest user list from 15 PortMasters and then verify this list, with what our database shows. There is always one or two that should not be there :( I guess the most common cause of missing Stop packets in your detail file is if your NAS crashes or is restarted. You will never get a Stop for the users who were on the NAS at the time. Other possibilities are: 1. Flakey network. That doesnt sound likely, as you would probably have other more serious problems than this. 2. Firmware problem in your NAS, though I havent had any similar reports from this cause for PMs. 3. Anyone else think of anything? Hope that helps. Cheers. -- Mike McCauley [EMAIL PROTECTED] Open System Consultants Pty. LtdUnix, Perl, Motif, C++, WWW 24 Bateman St Hampton, VIC 3188 Australia http://www.open.com.au Phone +61 3 9598-0985 Fax +61 3 9598-0955 Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, external, etc etc on Unix, Win95/8, NT, Rhapsody === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. -- Shori Pty Ltd / Barry W Anderson \ / / Senior Consultant \\\' , / // [EMAIL PROTECTED]\\\//, _/ //, \_-//' / //, http://www.shori.com\ /// //` / \\\`__/_ 42 Munich Drive /,)-^ _\` \\\ Keilor Downs, Victoria(/ \\ / \\\ Australia 3038 // //\\\ --((`-((`- === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
(RADIATOR) Lost Stop Records
Howdy, Thanks for the great response. We have used 2 other variations of radius including the Livingston Radius and the problem has always been there, so I have emailed Lucent as it would appear to be a Hardware problem. If I get some positive feed back, I'll let you all know! Cheers, Paul Thornton. ,- __ -, DOVE AUSTRALIA SYSADMIN TEAM / \___/ /__ _ _/ \ / _ / _ / _ \ |/ / -_) _ \ Account queries: [EMAIL PROTECTED] /.- \_,_/\___/___/\__/-.\ Tech Support: [EMAIL PROTECTED] A U S T R A L I A Sales queries: [EMAIL PROTECTED] http://dove.net.auAdmin queries: [EMAIL PROTECTED] === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) replyattr and fixed ip's
Hi I've changed my table defs to include a coulmn for FRAMEDIPADDRESS etc, and also changed the radius config file , but I get an error, for fixed IP customers still. ERR: Bad Attribute=value pair: 193.218.160.249 And then it drops the user. Iqbal === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
Re: (RADIATOR) Re: your mail
interesting. Do you all feel its a good idea to "lowercase and chop" all usernames like this, and just let the user have "[EMAIL PROTECTED]" incorrectly in their dial up config, or do you think its better to correct for it? I think the RewriteUsername would cut down alot of tech support calls, and really its harmless so long as its only their dialup config that is braindead and not their mail config etc. I think it's not a good idea. Remeber that the password will not be touched, so if your customer forgot to turn off caps lock, the authentication will fail anyway, and support calls will happen. Cheers, Ricardo Freire === To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
