Re: (dialup_admin) snmpfinger program pays no attention to naslist.conf
On Thu, 17 Mar 2005, Nick Bright wrote:
Also executing "Check NAS validity" fails for every NAS, I looked at the
PHP and it's trying to do "gethostbyname($selected_nas), where the name
is an IP address. Is that why it's failing, because I used IP's instead
of hostnames? Maybe that factors in to why user_finger.php3 is doing
funky stuff?
Also fixed in CVS, Thanks.
Running "Check Nas Validity" now results in:
Fatal error: Call to undefined function: check_ip() in
/usr/local/dialup_admin/htdocs/nas_admin.php3 on line 48
Fixed, thanks
Another error on stats.php3, too (it wasn't doing this before):
Fatal error: Cannot redeclare time2str() (previously declared in
/usr/local/dialup_admin/lib/functions.php3:2) in
/usr/local/dialup_admin/lib/functions.php3 on line 2
If I change line 16 from
require('../lib/functions.php3');
to
require_once('../lib/functions.php3');
it goes back to doing what it was doing before this CVS release,
spitting out a bunch of errors like this:
Fixed also.
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 117
These warnings should be gone now.
--
Kostas Kalevras Network Operations Center
[EMAIL PROTECTED] National Technical University of Athens, Greece
Work Phone: +30 210 7721861
'Go back to the shadow' Gandalf
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: (dialup_admin) snmpfinger program pays no attention to naslist.conf
On Mon, 2005-03-14 at 05:58, Kostas Kalevras wrote:
> On Thu, 10 Mar 2005, Nick Bright wrote:
>
> > To hop back to this question, updating to the latest CVS made
> > user_finger.php3 behave quite a bit differently.
> >
> > Now when I go to that page, I get a listing for every NAS from the
> > database, but there is no information for the NAS unless there is also
> > information in naslist.conf
> >
> > Shouldn't it just use the information from SQL if the nas table is
> > there, and completely ignore/not use naslist.conf? It seems a little
> > redundant to put the information into two locations.
>
> dialupadmin will use all information that is available. That means that it
> will
> also use any information present in naslist.conf. In any case, it was a bug
> and
> hopefully fixed in CVS.
"Online Users" is showing the correct NAS information now
>
> >
> > *shrug* maybe I'm just doing something wrong? That's pretty likely ;)
> >
> > Another odd thing is that on nas_admin.php3, all my NAS's are showing
> > type "other" in the dropdown, though they are set for various things in
> > the database (including: other, max40xx, and usrhiper). When I try to
> > modify the setting through dialup_admin, it doesn't change in the
> > dropdown, but it does change in the database. Seems like the dropdown
> > isn't reading properly.
>
> Also fixed in CVS, Thanks.
Yup, fixed. Thanks :)
>
> >
> > Also executing "Check NAS validity" fails for every NAS, I looked at the
> > PHP and it's trying to do "gethostbyname($selected_nas), where the name
> > is an IP address. Is that why it's failing, because I used IP's instead
> > of hostnames? Maybe that factors in to why user_finger.php3 is doing
> > funky stuff?
>
> Also fixed in CVS, Thanks.
Running "Check Nas Validity" now results in:
Fatal error: Call to undefined function: check_ip() in
/usr/local/dialup_admin/htdocs/nas_admin.php3 on line 48
Another error on stats.php3, too (it wasn't doing this before):
Fatal error: Cannot redeclare time2str() (previously declared in
/usr/local/dialup_admin/lib/functions.php3:2) in
/usr/local/dialup_admin/lib/functions.php3 on line 2
If I change line 16 from
require('../lib/functions.php3');
to
require_once('../lib/functions.php3');
it goes back to doing what it was doing before this CVS release,
spitting out a bunch of errors like this:
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 117
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 120
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 123
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 117
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 120
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 123
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 117
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 120
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 123
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 117
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 120
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 123
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 117
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 120
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 123
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 117
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 120
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 123
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 117
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 120
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 123
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 117
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 120
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 123
Warning: Cannot use a scalar value as an array in
/usr/local/dialup_admin/htdocs/stats.php3 on line 117
Warnin
Re: (dialup_admin) snmpfinger program pays no attention to naslist.conf
Kostas Kalevras <[EMAIL PROTECTED]> wrote: > Downloading through cvs is clearly described in > http://www.freeradius.org/development.html#cvs > > There's no module dialup_admin and i don't think there's a > /cvsroot/dialup-admin It's still on sourceforge. But that hasn't been used for dialup_admin in a number of years. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: (dialup_admin) snmpfinger program pays no attention to naslist.conf
On Mon, 2005-03-14 at 16:43, Kostas Kalevras wrote: > On Mon, 14 Mar 2005, Nick Bright wrote: > > > Wow, WTF. I downloaded the latest CVS and _everything_ is all jacked up. > > I'm pretty sure I'm not doing something correctly (I don't use CVS > > much). . . > > > > I did: > > > > shell> cvs > > -d:pserver:[EMAIL PROTECTED]:/cvsroot/dialup-admin > > login > > > > * When prompted for a password simply press the Enter Key > > > > shell> cvs -z3 > > -d:pserver:[EMAIL PROTECTED]:/cvsroot/dialup-admin > > co dialup_admin > > > > The resulting version is missing files, doesn't contain many of the > > default configuration files, and just basically doesn't work. > > > > wtf? Is this not the right way to get the CVS? Should I be getting the > > CVS of freeradius and taking the dialup_admin directory out of there? > > Downloading through cvs is clearly described in > http://www.freeradius.org/development.html#cvs > > There's no module dialup_admin and i don't think there's a > /cvsroot/dialup-admin > > So please read that page and try again. dialup_admin is included in the > radiusd > module. Yeah, that's weird. I was able to get stuff by executing the commands above (which I got from a mailing list post, by the way). . . Anyways, the method in the URL above worked fine. Thanks. > > > > > - Nick Bright > > Terraworld, Inc > > > > On Mon, 2005-03-14 at 05:58, Kostas Kalevras wrote: > >> On Thu, 10 Mar 2005, Nick Bright wrote: > >> > >>> To hop back to this question, updating to the latest CVS made > >>> user_finger.php3 behave quite a bit differently. > >>> > >>> Now when I go to that page, I get a listing for every NAS from the > >>> database, but there is no information for the NAS unless there is also > >>> information in naslist.conf > >>> > >>> Shouldn't it just use the information from SQL if the nas table is > >>> there, and completely ignore/not use naslist.conf? It seems a little > >>> redundant to put the information into two locations. > >> > >> dialupadmin will use all information that is available. That means that it > >> will > >> also use any information present in naslist.conf. In any case, it was a > >> bug and > >> hopefully fixed in CVS. > >> > >>> > >>> *shrug* maybe I'm just doing something wrong? That's pretty likely ;) > >>> > >>> Another odd thing is that on nas_admin.php3, all my NAS's are showing > >>> type "other" in the dropdown, though they are set for various things in > >>> the database (including: other, max40xx, and usrhiper). When I try to > >>> modify the setting through dialup_admin, it doesn't change in the > >>> dropdown, but it does change in the database. Seems like the dropdown > >>> isn't reading properly. > >> > >> Also fixed in CVS, Thanks. > >> > >>> > >>> Also executing "Check NAS validity" fails for every NAS, I looked at the > >>> PHP and it's trying to do "gethostbyname($selected_nas), where the name > >>> is an IP address. Is that why it's failing, because I used IP's instead > >>> of hostnames? Maybe that factors in to why user_finger.php3 is doing > >>> funky stuff? > >> > >> Also fixed in CVS, Thanks. > >> > >> -- > >> Kostas KalevrasNetwork Operations Center > >> [EMAIL PROTECTED] National Technical University of Athens, Greece > >> Work Phone:+30 210 7721861 > >> 'Go back to the shadow'Gandalf > >> > >> - > >> List info/subscribe/unsubscribe? See > >> http://www.freeradius.org/list/users.html > > -- > > - Nick Bright > > Terraworld, Inc > > 888-332-1616 x315 > > http://home.terraworld.net > > > > > > - > > List info/subscribe/unsubscribe? See > > http://www.freeradius.org/list/users.html > > > > -- > Kostas Kalevras Network Operations Center > [EMAIL PROTECTED] National Technical University of Athens, Greece > Work Phone: +30 210 7721861 > 'Go back to the shadow' Gandalf > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- - Nick Bright Terraworld, Inc 888-332-1616 x315 http://home.terraworld.net - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: (dialup_admin) snmpfinger program pays no attention to naslist.conf
On Mon, 14 Mar 2005, Nick Bright wrote: Wow, WTF. I downloaded the latest CVS and _everything_ is all jacked up. I'm pretty sure I'm not doing something correctly (I don't use CVS much). . . I did: shell> cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dialup-admin login * When prompted for a password simply press the Enter Key shell> cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/dialup-admin co dialup_admin The resulting version is missing files, doesn't contain many of the default configuration files, and just basically doesn't work. wtf? Is this not the right way to get the CVS? Should I be getting the CVS of freeradius and taking the dialup_admin directory out of there? Downloading through cvs is clearly described in http://www.freeradius.org/development.html#cvs There's no module dialup_admin and i don't think there's a /cvsroot/dialup-admin So please read that page and try again. dialup_admin is included in the radiusd module. - Nick Bright Terraworld, Inc On Mon, 2005-03-14 at 05:58, Kostas Kalevras wrote: On Thu, 10 Mar 2005, Nick Bright wrote: To hop back to this question, updating to the latest CVS made user_finger.php3 behave quite a bit differently. Now when I go to that page, I get a listing for every NAS from the database, but there is no information for the NAS unless there is also information in naslist.conf Shouldn't it just use the information from SQL if the nas table is there, and completely ignore/not use naslist.conf? It seems a little redundant to put the information into two locations. dialupadmin will use all information that is available. That means that it will also use any information present in naslist.conf. In any case, it was a bug and hopefully fixed in CVS. *shrug* maybe I'm just doing something wrong? That's pretty likely ;) Another odd thing is that on nas_admin.php3, all my NAS's are showing type "other" in the dropdown, though they are set for various things in the database (including: other, max40xx, and usrhiper). When I try to modify the setting through dialup_admin, it doesn't change in the dropdown, but it does change in the database. Seems like the dropdown isn't reading properly. Also fixed in CVS, Thanks. Also executing "Check NAS validity" fails for every NAS, I looked at the PHP and it's trying to do "gethostbyname($selected_nas), where the name is an IP address. Is that why it's failing, because I used IP's instead of hostnames? Maybe that factors in to why user_finger.php3 is doing funky stuff? Also fixed in CVS, Thanks. -- Kostas Kalevras Network Operations Center [EMAIL PROTECTED] National Technical University of Athens, Greece Work Phone: +30 210 7721861 'Go back to the shadow' Gandalf - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- - Nick Bright Terraworld, Inc 888-332-1616 x315 http://home.terraworld.net - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- Kostas Kalevras Network Operations Center [EMAIL PROTECTED] National Technical University of Athens, Greece Work Phone: +30 210 7721861 'Go back to the shadow' Gandalf - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: (dialup_admin) snmpfinger program pays no attention to naslist.conf
Wow, WTF. I downloaded the latest CVS and _everything_ is all jacked up. I'm pretty sure I'm not doing something correctly (I don't use CVS much). . . I did: shell> cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/dialup-admin login * When prompted for a password simply press the Enter Key shell> cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/dialup-admin co dialup_admin The resulting version is missing files, doesn't contain many of the default configuration files, and just basically doesn't work. wtf? Is this not the right way to get the CVS? Should I be getting the CVS of freeradius and taking the dialup_admin directory out of there? - Nick Bright Terraworld, Inc On Mon, 2005-03-14 at 05:58, Kostas Kalevras wrote: > On Thu, 10 Mar 2005, Nick Bright wrote: > > > To hop back to this question, updating to the latest CVS made > > user_finger.php3 behave quite a bit differently. > > > > Now when I go to that page, I get a listing for every NAS from the > > database, but there is no information for the NAS unless there is also > > information in naslist.conf > > > > Shouldn't it just use the information from SQL if the nas table is > > there, and completely ignore/not use naslist.conf? It seems a little > > redundant to put the information into two locations. > > dialupadmin will use all information that is available. That means that it > will > also use any information present in naslist.conf. In any case, it was a bug > and > hopefully fixed in CVS. > > > > > *shrug* maybe I'm just doing something wrong? That's pretty likely ;) > > > > Another odd thing is that on nas_admin.php3, all my NAS's are showing > > type "other" in the dropdown, though they are set for various things in > > the database (including: other, max40xx, and usrhiper). When I try to > > modify the setting through dialup_admin, it doesn't change in the > > dropdown, but it does change in the database. Seems like the dropdown > > isn't reading properly. > > Also fixed in CVS, Thanks. > > > > > Also executing "Check NAS validity" fails for every NAS, I looked at the > > PHP and it's trying to do "gethostbyname($selected_nas), where the name > > is an IP address. Is that why it's failing, because I used IP's instead > > of hostnames? Maybe that factors in to why user_finger.php3 is doing > > funky stuff? > > Also fixed in CVS, Thanks. > > -- > Kostas Kalevras Network Operations Center > [EMAIL PROTECTED] National Technical University of Athens, Greece > Work Phone: +30 210 7721861 > 'Go back to the shadow' Gandalf > > - > List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html -- - Nick Bright Terraworld, Inc 888-332-1616 x315 http://home.terraworld.net - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: (dialup_admin) snmpfinger program pays no attention to naslist.conf
On Thu, 10 Mar 2005, Nick Bright wrote: To hop back to this question, updating to the latest CVS made user_finger.php3 behave quite a bit differently. Now when I go to that page, I get a listing for every NAS from the database, but there is no information for the NAS unless there is also information in naslist.conf Shouldn't it just use the information from SQL if the nas table is there, and completely ignore/not use naslist.conf? It seems a little redundant to put the information into two locations. dialupadmin will use all information that is available. That means that it will also use any information present in naslist.conf. In any case, it was a bug and hopefully fixed in CVS. *shrug* maybe I'm just doing something wrong? That's pretty likely ;) Another odd thing is that on nas_admin.php3, all my NAS's are showing type "other" in the dropdown, though they are set for various things in the database (including: other, max40xx, and usrhiper). When I try to modify the setting through dialup_admin, it doesn't change in the dropdown, but it does change in the database. Seems like the dropdown isn't reading properly. Also fixed in CVS, Thanks. Also executing "Check NAS validity" fails for every NAS, I looked at the PHP and it's trying to do "gethostbyname($selected_nas), where the name is an IP address. Is that why it's failing, because I used IP's instead of hostnames? Maybe that factors in to why user_finger.php3 is doing funky stuff? Also fixed in CVS, Thanks. -- Kostas Kalevras Network Operations Center [EMAIL PROTECTED] National Technical University of Athens, Greece Work Phone: +30 210 7721861 'Go back to the shadow' Gandalf - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: (dialup_admin) snmpfinger program pays no attention to naslist.conf
To hop back to this question, updating to the latest CVS made
user_finger.php3 behave quite a bit differently.
Now when I go to that page, I get a listing for every NAS from the
database, but there is no information for the NAS unless there is also
information in naslist.conf
Shouldn't it just use the information from SQL if the nas table is
there, and completely ignore/not use naslist.conf? It seems a little
redundant to put the information into two locations.
*shrug* maybe I'm just doing something wrong? That's pretty likely ;)
Another odd thing is that on nas_admin.php3, all my NAS's are showing
type "other" in the dropdown, though they are set for various things in
the database (including: other, max40xx, and usrhiper). When I try to
modify the setting through dialup_admin, it doesn't change in the
dropdown, but it does change in the database. Seems like the dropdown
isn't reading properly.
Also executing "Check NAS validity" fails for every NAS, I looked at the
PHP and it's trying to do "gethostbyname($selected_nas), where the name
is an IP address. Is that why it's failing, because I used IP's instead
of hostnames? Maybe that factors in to why user_finger.php3 is doing
funky stuff?
On Thu, 2005-03-10 at 08:50, Kostas Kalevras wrote:
> On Thu, 10 Mar 2005, Nick Bright wrote:
>
> > On Thu, 2005-03-10 at 08:33, Nick Bright wrote:
> >> Since I'm using the version of dialup_admin from the 1.0.2 release of
> >> freeradius (with freeradius 1.0.1), would you suggest updating the whole
> >> thing to the latest CVS?
>
> You can probably just update the user_finger.php3. But it's much better to
> just
> update the whole dialupadmin
>
> >
> > Clarification of my own email (hehe), I mean update dialup_admin to the
> > latest CVS, not the whole freeradius package.
> >
> >> I'm also curious, why is naslist.conf used, instead of reading the
> >> information from the "nas" table in sql?
>
> In recent versions of dialupadmin the nas table is also used if it is set. If
> you find a lib/sql/nas_list.php3 file then you have such a version.
>
> >>
> >> On Wed, 2005-03-09 at 15:57, Kostas Kalevras wrote:
> >>> On Wed, 9 Mar 2005, Nick Bright wrote:
> >>>
> I have a rather large naslist.conf file, all configured to use
> finger_type database. However, snmpfinger insists upon querying each and
> every one as a cisco nas (they aren't, and i don't even have SNMP
> priviledges on most of them).
> >>>
> >>> Yes, there's a bug in user_finger.php3. Please do a cvs update on the
> >>> file and
> >>> things should work. Or you can just set general_finger_type to whatever
> >>> value
> >>> (apart from snmp) and still get the same results.
> >>>
> >>> Thanks for noting that.
> >>>
>
> My naslist.conf file is "generated" by manipulating some spreadsheet
> stuff, so the lines for each nas aren't grouped together. I don't know
> if that is causing a problem or not.
>
> However, my configuration for each nas is something like this:
>
> nasX_name: nameofnas.%{general_domain}
> nasX_model: Useful Description
> nasX_type: other
> nasX_port_num: 4096
> nasX_community: rocomm
> nasX_finger_type: database
>
> The only variable here is the nasX_type field, which could be: other,
> usrhiper, or lucent
>
> The port_num field is appropriate for the NAS, or 4096 if it's a proxy
> provider (outsourced dialup)
>
> All nases are set for finger_type "database", so they shouldn't even be
> firing off snmpfinger at all . . .
>
> --
> - Nick Bright
> Terraworld, Inc
> 888-332-1616 x315
> http://home.terraworld.net
>
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>
> >>>
> >>> --
> >>> Kostas Kalevras Network Operations Center
> >>> [EMAIL PROTECTED] National Technical University of Athens, Greece
> >>> Work Phone: +30 210 7721861
> >>> 'Go back to the shadow' Gandalf
> >>>
> >>> -
> >>> List info/subscribe/unsubscribe? See
> >>> http://www.freeradius.org/list/users.html
> > --
> > - Nick Bright
> > Terraworld, Inc
> > 888-332-1616 x315
> > http://home.terraworld.net
> >
> >
> > -
> > List info/subscribe/unsubscribe? See
> > http://www.freeradius.org/list/users.html
> >
>
> --
> Kostas Kalevras Network Operations Center
> [EMAIL PROTECTED] National Technical University of Athens, Greece
> Work Phone: +30 210 7721861
> 'Go back to the shadow' Gandalf
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
--
- Nick Bright
Terraworld, Inc
888-332-1616 x315
http://home.terraworld.net
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: (dialup_admin) snmpfinger program pays no attention to naslist.conf
I updated to the latest CVS of dialup_admin, and am getting this error when I click on "statistics": Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 117 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 120 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 123 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 117 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 120 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 123 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 117 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 120 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 123 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 117 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 120 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 123 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 117 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 120 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 123 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 117 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 120 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 123 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 117 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 120 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 123 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 117 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 120 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 123 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 117 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 120 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 123 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 132 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 133 Warning: Cannot use a scalar value as an array in /usr/local/dialup_admin/htdocs/stats.php3 on line 134 Warning: Division by zero in /usr/local/dialup_admin/htdocs/stats.php3 on line 136 Warning: Division by zero in /usr/local/dialup_admin/htdocs/stats.php3 on line 137 Warning: Division by zero in /usr/local/dialup_admin/htdocs/stats.php3 on line 138 I'll try to figure it out, but I thought I'd send it over in case it was a bug or something. - Nick On Thu, 2005-03-10 at 08:50, Kostas Kalevras wrote: > On Thu, 10 Mar 2005, Nick Bright wrote: > > > On Thu, 2005-03-10 at 08:33, Nick Bright wrote: > >> Since I'm using the version of dialup_admin from the 1.0.2 release of > >> freeradius (with freeradius 1.0.1), would you suggest updating the whole > >> thing to the latest CVS? > > You can probably just update the user_finger.php3. But it's much better to > just > update the whole dialupadmin > > > > > Clarification of my own email (hehe), I mean update dialup_admin to the > > latest CVS, not the whole freeradius package. > > > >> I'm also curious, why is naslist.conf used, instead of reading the > >> information from the "nas" table in sql? > > In recent versions of dialupadmin the nas table is also used if it is set. If > you find a lib/sql/nas_list.php3 file then you have such a version. > > >> > >> On Wed, 2005-03-09 at 15:57, Kostas Kalevras wrote: > >>> On Wed, 9 Mar 2005, Nick Bright wrote: > >>> > I have a rather large naslist.conf file, all configured to use > finger_type database. However, snmpfinger insists upon querying each and > every one as a cisco nas (they aren't, and i don't even have SNMP > priviledges on most of them). > >>> > >>> Yes, there's a bug in user_finger.php3. Please do a cvs update on the > >>> file and > >>> things should work. Or you can just set general_fin
Re: (dialup_admin) snmpfinger program pays no attention to naslist.conf
On Thu, 10 Mar 2005, Nick Bright wrote:
On Thu, 2005-03-10 at 08:33, Nick Bright wrote:
Since I'm using the version of dialup_admin from the 1.0.2 release of
freeradius (with freeradius 1.0.1), would you suggest updating the whole
thing to the latest CVS?
You can probably just update the user_finger.php3. But it's much better to just
update the whole dialupadmin
Clarification of my own email (hehe), I mean update dialup_admin to the
latest CVS, not the whole freeradius package.
I'm also curious, why is naslist.conf used, instead of reading the
information from the "nas" table in sql?
In recent versions of dialupadmin the nas table is also used if it is set. If
you find a lib/sql/nas_list.php3 file then you have such a version.
On Wed, 2005-03-09 at 15:57, Kostas Kalevras wrote:
On Wed, 9 Mar 2005, Nick Bright wrote:
I have a rather large naslist.conf file, all configured to use
finger_type database. However, snmpfinger insists upon querying each and
every one as a cisco nas (they aren't, and i don't even have SNMP
priviledges on most of them).
Yes, there's a bug in user_finger.php3. Please do a cvs update on the file
and
things should work. Or you can just set general_finger_type to whatever value
(apart from snmp) and still get the same results.
Thanks for noting that.
My naslist.conf file is "generated" by manipulating some spreadsheet
stuff, so the lines for each nas aren't grouped together. I don't know
if that is causing a problem or not.
However, my configuration for each nas is something like this:
nasX_name: nameofnas.%{general_domain}
nasX_model: Useful Description
nasX_type: other
nasX_port_num: 4096
nasX_community: rocomm
nasX_finger_type: database
The only variable here is the nasX_type field, which could be: other,
usrhiper, or lucent
The port_num field is appropriate for the NAS, or 4096 if it's a proxy
provider (outsourced dialup)
All nases are set for finger_type "database", so they shouldn't even be
firing off snmpfinger at all . . .
--
- Nick Bright
Terraworld, Inc
888-332-1616 x315
http://home.terraworld.net
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
--
Kostas Kalevras Network Operations Center
[EMAIL PROTECTED] National Technical University of Athens, Greece
Work Phone: +30 210 7721861
'Go back to the shadow' Gandalf
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
--
- Nick Bright
Terraworld, Inc
888-332-1616 x315
http://home.terraworld.net
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
--
Kostas Kalevras Network Operations Center
[EMAIL PROTECTED] National Technical University of Athens, Greece
Work Phone: +30 210 7721861
'Go back to the shadow' Gandalf
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: (dialup_admin) snmpfinger program pays no attention to naslist.conf
On Thu, 2005-03-10 at 08:33, Nick Bright wrote:
> Since I'm using the version of dialup_admin from the 1.0.2 release of
> freeradius (with freeradius 1.0.1), would you suggest updating the whole
> thing to the latest CVS?
Clarification of my own email (hehe), I mean update dialup_admin to the
latest CVS, not the whole freeradius package.
> I'm also curious, why is naslist.conf used, instead of reading the
> information from the "nas" table in sql?
>
> On Wed, 2005-03-09 at 15:57, Kostas Kalevras wrote:
> > On Wed, 9 Mar 2005, Nick Bright wrote:
> >
> > > I have a rather large naslist.conf file, all configured to use
> > > finger_type database. However, snmpfinger insists upon querying each and
> > > every one as a cisco nas (they aren't, and i don't even have SNMP
> > > priviledges on most of them).
> >
> > Yes, there's a bug in user_finger.php3. Please do a cvs update on the file
> > and
> > things should work. Or you can just set general_finger_type to whatever
> > value
> > (apart from snmp) and still get the same results.
> >
> > Thanks for noting that.
> >
> > >
> > > My naslist.conf file is "generated" by manipulating some spreadsheet
> > > stuff, so the lines for each nas aren't grouped together. I don't know
> > > if that is causing a problem or not.
> > >
> > > However, my configuration for each nas is something like this:
> > >
> > > nasX_name: nameofnas.%{general_domain}
> > > nasX_model: Useful Description
> > > nasX_type: other
> > > nasX_port_num: 4096
> > > nasX_community: rocomm
> > > nasX_finger_type: database
> > >
> > > The only variable here is the nasX_type field, which could be: other,
> > > usrhiper, or lucent
> > >
> > > The port_num field is appropriate for the NAS, or 4096 if it's a proxy
> > > provider (outsourced dialup)
> > >
> > > All nases are set for finger_type "database", so they shouldn't even be
> > > firing off snmpfinger at all . . .
> > >
> > > --
> > > - Nick Bright
> > > Terraworld, Inc
> > > 888-332-1616 x315
> > > http://home.terraworld.net
> > >
> > >
> > > -
> > > List info/subscribe/unsubscribe? See
> > > http://www.freeradius.org/list/users.html
> > >
> >
> > --
> > Kostas Kalevras Network Operations Center
> > [EMAIL PROTECTED] National Technical University of Athens, Greece
> > Work Phone: +30 210 7721861
> > 'Go back to the shadow' Gandalf
> >
> > -
> > List info/subscribe/unsubscribe? See
> > http://www.freeradius.org/list/users.html
--
- Nick Bright
Terraworld, Inc
888-332-1616 x315
http://home.terraworld.net
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: (dialup_admin) snmpfinger program pays no attention to naslist.conf
Since I'm using the version of dialup_admin from the 1.0.2 release of
freeradius (with freeradius 1.0.1), would you suggest updating the whole
thing to the latest CVS?
I'm also curious, why is naslist.conf used, instead of reading the
information from the "nas" table in sql?
On Wed, 2005-03-09 at 15:57, Kostas Kalevras wrote:
> On Wed, 9 Mar 2005, Nick Bright wrote:
>
> > I have a rather large naslist.conf file, all configured to use
> > finger_type database. However, snmpfinger insists upon querying each and
> > every one as a cisco nas (they aren't, and i don't even have SNMP
> > priviledges on most of them).
>
> Yes, there's a bug in user_finger.php3. Please do a cvs update on the file
> and
> things should work. Or you can just set general_finger_type to whatever value
> (apart from snmp) and still get the same results.
>
> Thanks for noting that.
>
> >
> > My naslist.conf file is "generated" by manipulating some spreadsheet
> > stuff, so the lines for each nas aren't grouped together. I don't know
> > if that is causing a problem or not.
> >
> > However, my configuration for each nas is something like this:
> >
> > nasX_name: nameofnas.%{general_domain}
> > nasX_model: Useful Description
> > nasX_type: other
> > nasX_port_num: 4096
> > nasX_community: rocomm
> > nasX_finger_type: database
> >
> > The only variable here is the nasX_type field, which could be: other,
> > usrhiper, or lucent
> >
> > The port_num field is appropriate for the NAS, or 4096 if it's a proxy
> > provider (outsourced dialup)
> >
> > All nases are set for finger_type "database", so they shouldn't even be
> > firing off snmpfinger at all . . .
> >
> > --
> > - Nick Bright
> > Terraworld, Inc
> > 888-332-1616 x315
> > http://home.terraworld.net
> >
> >
> > -
> > List info/subscribe/unsubscribe? See
> > http://www.freeradius.org/list/users.html
> >
>
> --
> Kostas Kalevras Network Operations Center
> [EMAIL PROTECTED] National Technical University of Athens, Greece
> Work Phone: +30 210 7721861
> 'Go back to the shadow' Gandalf
>
> -
> List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
--
- Nick Bright
Terraworld, Inc
888-332-1616 x315
http://home.terraworld.net
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Re: (dialup_admin) snmpfinger program pays no attention to naslist.conf
On Wed, 9 Mar 2005, Nick Bright wrote:
I have a rather large naslist.conf file, all configured to use
finger_type database. However, snmpfinger insists upon querying each and
every one as a cisco nas (they aren't, and i don't even have SNMP
priviledges on most of them).
Yes, there's a bug in user_finger.php3. Please do a cvs update on the file and
things should work. Or you can just set general_finger_type to whatever value
(apart from snmp) and still get the same results.
Thanks for noting that.
My naslist.conf file is "generated" by manipulating some spreadsheet
stuff, so the lines for each nas aren't grouped together. I don't know
if that is causing a problem or not.
However, my configuration for each nas is something like this:
nasX_name: nameofnas.%{general_domain}
nasX_model: Useful Description
nasX_type: other
nasX_port_num: 4096
nasX_community: rocomm
nasX_finger_type: database
The only variable here is the nasX_type field, which could be: other,
usrhiper, or lucent
The port_num field is appropriate for the NAS, or 4096 if it's a proxy
provider (outsourced dialup)
All nases are set for finger_type "database", so they shouldn't even be
firing off snmpfinger at all . . .
--
- Nick Bright
Terraworld, Inc
888-332-1616 x315
http://home.terraworld.net
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
--
Kostas Kalevras Network Operations Center
[EMAIL PROTECTED] National Technical University of Athens, Greece
Work Phone: +30 210 7721861
'Go back to the shadow' Gandalf
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
(dialup_admin) snmpfinger program pays no attention to naslist.conf
I have a rather large naslist.conf file, all configured to use
finger_type database. However, snmpfinger insists upon querying each and
every one as a cisco nas (they aren't, and i don't even have SNMP
priviledges on most of them).
My naslist.conf file is "generated" by manipulating some spreadsheet
stuff, so the lines for each nas aren't grouped together. I don't know
if that is causing a problem or not.
However, my configuration for each nas is something like this:
nasX_name: nameofnas.%{general_domain}
nasX_model: Useful Description
nasX_type: other
nasX_port_num: 4096
nasX_community: rocomm
nasX_finger_type: database
The only variable here is the nasX_type field, which could be: other,
usrhiper, or lucent
The port_num field is appropriate for the NAS, or 4096 if it's a proxy
provider (outsourced dialup)
All nases are set for finger_type "database", so they shouldn't even be
firing off snmpfinger at all . . .
--
- Nick Bright
Terraworld, Inc
888-332-1616 x315
http://home.terraworld.net
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
