Re: RFC: "-@" command line argument to set clientaddr per request/session
Bill Fenner <[email protected]>
| Newsgroups | gmane.network.net-snmp.devel |
|---|---|
| Message-ID | <CAF4SogbwkMvTh7eh_EMOKBdy6kh2hfqv-TYRTf46wEtpLOTfoA@mail.gmail.com> |
On Thu, May 3, 2018 at 1:07 PM, Robert Story <[email protected]> wrote: > On Wed, 2 May 2018 11:49:46 -0400 Bill wrote: > BF> Is it too late to add this? This occurs to me just because it’s > BF> an easier way to test the transports’ support of clientaddr, by > BF> being able to set clientaddr dynamically via the command line, > BF> and I just noticed that this is broken in 5.8. > > This would duplicate functionality.. Pretty much any config option > can be set on the command line using '--TOKEN-VALUE'. e.g. > > > snmpget [...] --clientaddr=192.168.1.111 [...] > Depends on at what level you are looking at the functionality. -@ would set session.localaddr, which is a little different than setting clientaddr. In the sense of "how does my request look" when focusing on the snmpget invocation, it's the same. In the sense of "how do I set the local source for a trapsess", it's different. Since the v1/v2 trap sink commands have gained a "-s" argument, it might be better to call this "-s" too instead of "-@". Bill ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders