(RADIATOR) Odd Issue with SNMPAgent

Martin Edge martin.edge at phoneware.net.au
Sun Jan 20 23:35:20 CST 2002


Hey Guys,
 
Something I noticed last night while playing ...
 
I have a radius server which runs two copies of Radiator
 
Both copies run on separate bound IP's on the machine..
 
When running SNMPAgent using :
 
# enable SNMP handling
<SNMPAgent>
        Port xxxxxx
        ROCommunity xxxxxxx
        BindAddress 202.160.128.46
</SNMPAgent>

and 
 
# enable SNMP handling
<SNMPAgent>
        Port xxxxx
        ROCommunity xxxxx
        BindAddress 202.160.128.43
</SNMPAgent>
 
The first one loads, but when loading the second, I get an error saying it is unable to bind to the IP, assuming that the first one is binding to everything, instead of the IP it was told to bind too..
 
Using SNMP_Session-0.90 + Radiator 2.19
 
Has this been seen before?
Martin

 
-----------------------------------------
Martin Edge
Technical Services Co-ordinator
Phoneware Online
eMail:  <mailto:Martin.Edge at phoneware.net.au> Martin.Edge at phoneware.net.au
Phone: +613 9640 4140 ext. 193
 
"In the end, it's speed, price and customer service."
-----------------------------------------
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20020121/8085b6e9/attachment.html>


More information about the radiator mailing list