(RADIATOR) FYI: SNMP errors for win32
Hi, Someone else may find this useful. For Win32 environments, we use either net-snmp (v5.0.8) (or ucd-snmp v4.2.3). The errors returned by snmpwalk may be slightly different to that preconfigured in SNMP.pm in Radiator v3.5. For example, instead of "No Response", we get "Timeout". A minor change is required to SNMP.pm in this case. Regards. Achint. P.S: The behaviour of the "-P e" toggle is the exact opposite in net-snmp, as compared to ucd-snmp. Perhaps a bug in v5.0.8. === 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) Malformed Packet requests
Hello, Thanks for all your previous replies. Just another issue I need some help with. Im getting a Malformed request packet warning in my radiator logs. Any ideas why would this happen? I don't have an Attribute 0 defined in my dictionary. A sample packet trace is attached. Cheers. Achint. ---> Mon Aug 19 15:50:54 2002: WARNING: Malformed request packet: Vendor 5586 Attribute 0 with length 1: ignored Mon Aug 19 15:50:54 2002: DEBUG: Packet dump: *** Received from 192.168.193.2 port 1812 Code: Accounting-Request Identifier: 241 Authentic: <151>W<182><231>/Ze<176><135><130>i<204>qD<133>o Attributes: Acct-Status-Type = Start Acct-Delay-Time = 0 Acct-Authentic = RADIUS Event-Timestamp = 1029736339 Acct-Interim-Interval = 60 NAS-IP-Address = 192.168.193.2 User-Name = "new_user" Acct-Session-Id = " 2949346" L2TP-Tunnel-If-Index = 73 L2TP-Tunnel-Local-Sid = 77 ISP-LNS-Name = "r1.nwton" Tier-Of-Service = Business Unknown = --> === 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) SQL Database failover.
Title: Message Hi, Just a quick question. I've got a pretty straightforward configuration here. I have my radius servers pointed to 2 SQL databases. When database A goes down, Radiator switches over to database B. This works fine. My question is, is there anyway to go back to database A when it returns to operational? The current behaviour is to stay put at database B until it goes down too. FailureBackoffTime doesnt work in this way. Any ideas. Thanks. Achint.
(RADIATOR) Major Bug in radiator patches
Just a quick note, in case no one has discovered this yet. In Rdict.pm, $vendor is redefined as a local variable, which causes incorrect vendor attribute and value mapping. > error sub valNumToName { my ($self, $attrnum, $valnum, $vendor) = @_; my $vendor += 0; . . } < fix sub valNumToName { my ($self, $attrnum, $valnum, $vendor) = @_; $vendor += 0; . . } Cheers. Achint. === 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.