Hello Martin -
I suspect this has more to do with trying to use the same UDP port number. You can use the "Port" parameter to specify different port numbers in each instance. BTW - what hardware/software platform are you running on? regards Hugh On Mon, 21 Jan 2002 16:35, Martin Edge wrote: > 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:[EMAIL PROTECTED]> [EMAIL PROTECTED] > Phone: +613 9640 4140 ext. 193 > > "In the end, it's speed, price and customer service." > ----------------------------------------- -- Radiator: the most portable, flexible and configurable RADIUS server anywhere. Available on *NIX, *BSD, Windows 95/98/2000, NT, MacOS X. - Nets: internetwork inventory and management - graphical, extensible, flexible with hardware, software, platform and database independence. === 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.
