(RADIATOR) Authlog
Is it okay to use this: (stock Emerald log stuff) To push errors into the Emerald Radlogs table? Then just assign the error logging to it? I am having trouble getting it to work. Ideas? === 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) Maxsessions
Is there a way to enforce MaxSessions across different Clients? I have a problem with people using the same login in San Francisco and Los Angeles. By and large, they both are dealt with by the Default Client and Default handler.. so I thought it would keep a database of this okay. Does Radiator keep a separate session list per client or handler? If you run, you'll only die tired... === 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) Framed IP differences?
Greetings! I am told by my Tech support Monkeys that customers calling in have a different IP than the one showing up in the Call Logs. Uhh.. did I miss a step? My authentication takes place as AuthBy FILE on the primary server, and the others AuthBY RADIUS to that server unless the connections die, then they AuthBy FILE to their own local copies. The Accounting records go straight from the NAS into the Emerald billing system, so Radiator doesn't do a thing with them. Whats up with different IPs? Why wouldn't the NAS just hand one off and shoot the record into the database? === 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) Auth Question
I have sent up a Radiator box to AuthBy Radius and fall back to text. This it does. I have a question.. The Default realm is very simple, as all the "settings" live in the other clauses. Identifier Checklocal AuthBy CheckProxy My question is this: Is it okay to use the same for all other realms? Identifier Checklocal AuthBy CheckProxy In the same radius.cfg? - "We sleep safe in our beds because rough men stand ready in the night to visit violence on those who would do us harm." George Orwell === 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) Identical Clients
I'd like to set up a client clause for each type of NAS with the Identical clients picking up the same for same types. How would this look? - "We sleep safe in our beds because rough men stand ready in the night to visit violence on those who would do us harm." George Orwell === 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) MaxSessions
MaxSessions won't work under text right? Don't I need a master online calls table of somekind? Can I use authby radius and authby text, but check accounting on Emerald's calls table? - "We sleep safe in our beds because rough men stand ready in the night to visit violence on those who would do us harm." George Orwell === 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) Framed-IP of 0.0.0.0
Yes. I have seen this before prior to using Radiator in some of my NASes. We also have some Ascends. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of William Hernandez Sent: Wednesday, September 12, 2001 07:16 To: Radiator Subject: (RADIATOR) Framed-IP of 0.0.0.0 Hello everyone, We're using 2.18.2. Recently we started to see FRAMEDIPADDRESS of 0.0.0.0 in RADONLINE. These records create a problem when checking for Simultaneous-Use. Is this a problem with the Ascend NASes that we use? Thanks in advance, William === 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.
(RADIATOR) Clients in handlers?
Is there a way to make Radiator prefer certain clients? What I am trying to do is have the handler be identified by a region, in this case a city. Hence the handler for say Los Angeles would then have the NAS clients for LA built into it. I would like it the Los Angeles Radiator server to primarily serve the Los Angeles NAS groups, and secondarily handle the others. Can't this be done with an Authby Loadbalance? === 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) Is this possible?
Is it possible to write a handler using "NAS-Address-Port-List %D/portlist" or something to say build a default route for a port (say port 25) to only route to a particular mail server? This would prevent spam via open relays on other servers. Suggestions? === 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) Trace levels?
This does not seem to be working.. although the other day I setup a PasswordLogFileName in DEFAULT and that worked just fine. I am trying to cut a log of the users on the one Client/Handler for debugging. Is it because my trace levels are low? Identifier Log1 Filename %L/Log1logfile LogSuccess 1 LogFailure 1 FailureFormat %Y%m%d %H:%M:%S (%q) %C Port: %{NAS-Port} %1 U: %U P: %P Realm: %R SuccessFormat %Y%m%d %H:%M:%S (%q) %C Port: %{NAS-Port} %1 U: %U P: %P Realm: %R Used in conjunction with: Secret My-Secret DupInterval 1 Identifier A-Access Filename %D/A-AccessUsers DefaultReply Service-Type=Framed-User,Framed-Protocol=PPP,Framed-IP-Netmask=255.255.255.0 ,Port-Limit=1,Session-Timeout=21600,Idle-Timeout =3600 CaseInsensitivePasswords AuthLog Log1 PasswordLogFileName %L/Log1Logfile === 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) DefaultReply
Is it valid to use a variable like this? Where the DefaultReply string is in a file in %D? RewriteUsername tr/A-Z/a-z/ RewriteUsername s/\s+//g Filename %D/users DefaultReply %D/Reply CaseInsensitivePasswords # Log accounting to a detail file AcctLogFileName %L/detail AuthLog CustomLog === 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) Ignore case?
In working up the rewrite of user names, is there a way just to ignore case? I have used some of the others with success. PS -got the custom log messages working except that %X and %Z show up literally. -Todd === 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) Custom Errors?
I have something like this in radius.cfg for a client... # Access Client for Fred Secret The-Secret DupInterval 1 Identifier 0-Access Filename %D/0users It works fine.. but I was wondering if I could spit out a separate type of message from the system. Instead of the normal: Fri Aug 17 16:04:22 2001: INFO: Access rejected for bubba: Bad Password Fri Aug 17 16:04:30 2001: INFO: Access rejected for albert: Bad Password Fri Aug 17 16:04:33 2001: INFO: Access rejected for freddy: Bad Password Fri Aug 17 16:05:06 2001: INFO: Access rejected for cheese: Bad Password On this Client / Handler it would be nice to know if they came in from the 0-Access group. Is there a way? === 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) Okay.. what did I miss? (RewriteUsername)
I am trying to rewrite usernames on Realms.. I have tried moving the statement about in or out of the Authby.. either way I get this: I thought the manual said you could use it in a Realm, or Handler? Did I miss something (again) ? ERR: Unknown keyword 'RewriteUsername' Example: RewriteUsername s/^([^@]+).*/$1/ Filename %D/users === 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) Dictionary files
Well to assign dictionary files in client or in handlers that have clients.. %D/DictionaryFile dictionary.ascend settings... # Same Modem type settings... Next handler would be say dictionary.usr === 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) Dictionary files
Is it "legal" to assign dictionary files within client statements? === 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) Auth By Emerald Question
I noticed the SQL query in the authenticator for Emerald looks at the sa.login or the sa.shell fields in the SubAccounts table. Question: If I have a login say of "fred" in the sa.login field, would it be okay to stuff the realm login into the Shell field? We don't issue shell accounts, so it would be a fairly simple query (we use the ma.Referredby field to determine various acquisitions we have done) -so parsing the realm this way would be easy. So if sa.login = "fred" and sa.shell = "[EMAIL PROTECTED]" would this solve realming without having to set up a handler for a realm? === 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) problem about radiator server
That is essentially the same error I am getting, only it isn't recognising localhost, either as "localhost" or as 127.0.0.1 -even though there is an entry for it in radius.cfg === 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) Auth by Text Questions
I just had Radiator dropped into my lap this last week amidst other things. I must be missing a REAL OBVIOUS issue, but I can't get my Radiator to auth off of a file. This is on a Linux box with the rpm file for the install. The file is traditional in that it points the logfiles and gets the users file from the normal spots. The files are there. In radius.cfg is where I have the case of the "DUH"s going on. The only Authby Text clause I have is at the bottom (the standard DEFAULT) and have added above it Client lists of the modems sending the requests. Those I sorted by location and type, so they swap out dictionaries as needed. That is about all I did. Radiator starts okay, but won't authenticate off localhost (yes, built that entry.. once as in the example "localhost" and redone as 127.0.0.1. I looked over the logs, it seems to start, but then doesn't complete. So my long verbose note here is to ask if my brain is kludged in the understanding of the way to set up a radius.cfg file. File information (logs and users file) Client lists with features Authby Text issues End of file. Suggestions? - Inreach Internet Systems Department === 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.