El 9 Sep 2001, a las 9:43, Mike McCauley escribió:
> Hello Mariano,
>
> Thanks for reporting this. There was a b ug un Mib.pm that prevented the
> correct OID path bing sent back in the SNMP reply. This apparently causes
> some SNMP clients to think it got no reply at all.
>
> I have attached a new Mib.pm for you to test. If it is OK it wil appear in
> the next release.
Right, now it works, but I see you already released it !!!
on Sunday morning !!! (Saturday night for me)
>
> We apologise for this problem. Thank you for reporting it.
You're definitively welcome... getting a bug fix in 6 hours, (counting the
Australian early morning), and a new release 1.5 hours later, during a
weekend is much more than I ever got from any other software company,
including support contracts with big ones.
BTW, we also bought a year ago (together with the Radiator license), one year
of Radiator Support by mail... We haven't used it even once, since the
support through this mailing list is really superb.
>
> Cheers.
>
> On Sun, 9 Sep 2001 03:44, Mariano Absatz wrote:
> > Hi Mike,
> >
> > Now it (almost) works, the only point is that, apparently, it restarts and
> > doesn't send back an acknowledge to the snmp console that sent the request:
> >
> > Here's the console:
> > #snmpset -t 8 -r 1 -p 16146 192.168.19.1 rw-comm .1.3.6.1.2.1.67.1.1.1.1.4
> > i 2 Timeout: No Response from 192.168.19.1
> >
> >
> > Here's Radiator's log:
> > Sat Sep 8 14:36:50 2001: DEBUG: SNMPAgent: received request from
> > 192.168.1.7, 131, 189128152, rw-comm
> > Sat Sep 8 14:36:52 2001: INFO: Server started: Radiator 2.18.2 on radius1
> >
> >
> >
> > never mind how long the timeout I use (here's 8 secs, but the reset is
> > almost immediate). Any idea? (I'm using 2.18.2)
> >
> > El 7 Sep 2001, a las 9:26, Mike McCauley escribió:
> > > Hi Mariano,
> > >
> > > On Thu, 6 Sep 2001 23:58, Mariano Absatz wrote:
> > > > Well, the point is... it didn't work, Radiator receives the request,
> > > > but doesn't do anything about it.
> > > >
> > > > I tried with the three sets of OID's (the draft ones, RFC2619 &
> > > > RFC2621), but to no avail.
> > > >
> > > > In the requesting machine, I send:
> > > > snmpset -Ir -p 16146 192.168.19.1 rw-comm 1.3.6.1.3.79.1.1.1.4 i 2
> > > > snmpset -Ir -p 16146 192.168.19.1 rw-comm 1.3.6.1.2.1.67.1.1.1.1.4 i
> > > > 2 snmpset -Ir -p 16146 192.168.19.1 rw-comm 1.3.6.1.2.1.67.2.1.1.1.4
> > > > i 2
> > >
> > > Ooos, you need to have a . at the front of the OID, else your snmp
> > > interprets it as a relative OID. Try this: it works for me on 2.18.3:
> > >
> > > snmpset oscar public .1.3.6.1.3.79.1.1.1.4 i 2
> > >
> > > > and I allways get the following output:
> > > > > Error in packet.
> > > > > Reason: (noSuchName) There is no such variable name in this MIB.
> > > > > Failed object:
> > > >
> > > > The trace 4 in the Radiator server says:
> > > > Thu Sep 6 09:56:42 2001: DEBUG: SNMPAgent: received request from
> > > > 192.168.1.7, 131, 293287917, rw-comm
> > > > Thu Sep 6 10:32:13 2001: DEBUG: SNMPAgent: received request from
> > > > 200.x.y.z, 131, 60580895, rw-comm
> > > > Thu Sep 6 10:32:13 2001: WARNING: SNMPAgent: requesting host not
> > > > defined as manager. Request from 200.x.y.z ignored
> > > > Thu Sep 6 10:32:14 2001: DEBUG: SNMPAgent: received request from
> > > > 192.168.1.7, 131, 60580895, rw-comm
> > > > Thu Sep 6 10:34:35 2001: DEBUG: SNMPAgent: received request from
> > > > 192.168.1.7, 131, 1490955430, rw-comm
> > > > Thu Sep 6 10:39:45 2001: DEBUG: SNMPAgent: received request from
> > > > 192.168.1.7, 131, 267748177, rw-comm
> > > > Thu Sep 6 10:41:56 2001: DEBUG: SNMPAgent: received request from
> > > > 192.168.1.7, 131, 1188183886, rw-comm
> > > >
> > > > And it doesn't restart...
> > > >
> > > > What is going wrong?
> > > >
> > > > El 6 Sep 2001, a las 15:07, Mike McCauley escribió:
> > > > > Hi Mariano,
> > > > >
> > > > > On Thu, 6 Sep 2001 07:46, Hugh Irvine wrote:
> > > > > > ---------- Forwarded Message ----------
> > > > > > Subject: (RADIATOR) remote radiator restart
> > > > > > Date: Wed, 5 Sep 2001 14:22:45 -0300
> > > > > > From: "Mariano Absatz" <[EMAIL PROTECTED]>
> > > > > > To: Radiator List <[EMAIL PROTECTED]>
> > > > > >
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > I am running Radiator 2.18.2 on a couple of Sun Netras (Solaris 8)
> > > > > > authenticating against an Oracle database (on yet another Netra).
> > > > > >
> > > > > > We developed a web based front end for administration of the users
> > > > > > in the Oracle database on a Sun Ultra 10 (also Solaris 8) with
> > > > > > Apache and embedded Perl.
> > > > > >
> > > > > > The point is that, for instance, when I try to invoke a restart
> > > > > > script through ssh, I get the following error:
> > > > > >
> > > > > > Doing it so through rsh, it works but it locks the connection (and
> > > > > > anyway, I'd rather not have rshd running on the server.
> > > > > >
> > > > > > On the other hand, the manual states that through the SNMP agent I
> > > > > > can restart Radiator, but I don't know how. Am I missing something?
> > > > > > (I think this would be the cleanest method to do it).
> > > > >
> > > > > you need to set the SNMP variable
> > > > > 1.3.6.1.3.79.1.1.1.4
> > > > >
> > > > > to the value 2, with something like:
> > > > >
> > > > > snmpset your.radius.server.address your_community
> > > > > 1.3.6.1.3.79.1.1.1.4 i 2
> > > > >
> > > > > Note that this does not actually stop the server, it just rereads the
> > > > > config, like with HUP.
> > > > >
> > > > > Cheers.
> > > > >
> > > > > Cheers.
> > > > > ===
> > > > > 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.
>
>
--
Mariano Absatz
El Baby
----------------------------------------------------------
Artificial Intelligence usually beats real stupidity.
===
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.
