Anurag> [...] However, configuring it to port 161 fails, with
Anurag> permission denied. The application I am testing sends
Anurag> requests on port 161. Is their a way of being able to get at
Anurag> those requests and respond to them?
well, this sounds you are running your application on a unix platform
as a normal user.
on a unix platform there is root permission necessary to open ports
below 1024 (or maybe 1000).
this may be realized by launching the application as the root user, or
by setting the s-uid bit for execution and setting ownership of the
application to root (this may not work, if your unix flaviour does not
accept suid permissions for scripts).
well, like `permission denied' says, it's a permission problem.
Anurag> I know for traps, we can have multiple sessions configured on
Anurag> port 162, and all will be able to get the message. Is their
Anurag> any simmilar mechanism for responding to gets?
to be able to receive traps with the tnm extension there is a
multiplexer named straps for scotty v2.x or nmtrapd for scotty v3.x.
this multiplexer is only a nonplus solution for the access problem to
ports below ~ 100 on unix platforms and about the exclusiv access to
ports.
Anurag> Or is their any other way I can set up an agent to respond to
Anurag> gets being sent out to port 161 by an application (running on
Anurag> the same machine).
no. on a unix platform there is root permission necessary to access
port 161 (however there are different ways to ensure this).
Erik
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.