(RADIATOR) RADIUS Attrib 28 (Idle-Timeout) default?

[Martin Wallner]

Wellll, 

I like to keep it simple, even if it's getting complicated, as this config is, so I have _two_ AuthBySQL-Clauses, where I have an 'AddIf...' added, for two different realms, everything else is pretty much only complicated in the way I have to rewrite stuff and gather from different sources (the rest of the other realms is mostly Authenticated by LDAP)... 

ARRRRGH. I promptly edited the wrong clause. Came in today, sat down, opened the config file, started to curse after I saw what I wrongly did yesterday, edited the right clause, sent the HUPs to the Radiators, started debug on the CISCO and dialed in..... it promptly worked

Move along, nothing to see here... :-)

There is still the case here with CISCO, that they don't silently discard an attribute they can't interprete on this type of interface (ISDN is terminated on a virtual Serial interface, POTS on a virtual tty), this I will deal out with CISCO, RADIATOR is doing (as usual) fine.... 

Thanks, guys, for the immediate responses.... I was really stuck yesterday, clear case of 'can't see the trees in the forest'...

very embarassed
Martin Wallner

> -----Original Message-----
> From: Hugh Irvine [mailto:hugh at open.com.au] 
> Sent: Montag, 23. Jänner 2006 23:51
> To: Martin Wallner
> Cc: radiator at open.com.au List; Claudio Lapidus
> Subject: Re: (RADIATOR) RADIUS Attrib 28 (Idle-Timeout) default?
> 
> 
> Hello Martin -
> 
> Claudio is correct - Radiator does not add anything to the 
> radius replies without configuration.
> 
> I also agree with Claudio's suggestion that you set up a 
> simple test configuration and add parts of your configuration 
> until you find what is going on.
> 
> regards
> 
> Hugh
> 
> 
> On 24 Jan 2006, at 01:57, Claudio Lapidus wrote:
> 
> > Martin
> >
> > On 1/23/06, Martin Wallner <Martin.Wallner at eunet.co.at> wrote:
> >> My problem is, that RADIATOR seems to send Idle-Timeout=0 in EVERY 
> >> successful Access-Reply, even if it's not configured to... 
> This is a 
> >> misinterpretation of RFC (...)
> >
> >
> > I'm pretty sure that Radiator is not adding that attribute per se,
> > here we have several different implementations of Radiator (very
> > different configurations) and that problem is not shown in any case,
> > this is not default behavior.
> >
> >> From the trace shown, I tend to think that your config is rather
> > complex. Perhaps a way to isolate this problem is to start with a
> > blank configuration (a very simple one) and gradually add 
> elements of
> > your current (problematic) configuration to see where the 
> problem pops
> > out. If that is impractical you may want to sequentially 
> "chop" parts
> > of your current config, trying to determine which branch of the tree
> > is the offending one.
> >
> > good luck
> > cl.
> 
> 
> NB:
> 
> Have you read the reference manual ("doc/ref.html")?
> Have you searched the mailing list archive (www.open.com.au/archives/ 
> radiator)?
> Have you had a quick look on Google (www.google.com)?
> 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.
> -
> CATool: Private Certificate Authority for Unix and Unix-like systems.
> 
> 
> 

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.