> inet_aton only groks IPv4 addresses :). Additional logic needs to
> be added to parse out the address via inet_addr -- I would introduce
> another argument (say 'A' instead of 'a'?) for IPv6 addresses so that
> way there's a clean method for dealing with IPv4 vs IPv6 (some
> revamping will need to occur because IPv6 addresses must be
> IPV6-TC::Ipv6Address types, for instance, from what I can see etc).
> I'll see if I can whip up a patch later on tonight because I know
> this is going to be a snag for my group in a couple of months :/..
> Thanks,
> -Garrett
Thank you very much for the assistance Garrett. Now that I've gone back and
re-read my comments I see that I didn't mention it, but I was also thinking
that new argument would be appropriate. Since an IPv6 address is accepted as
the trap destination AND there's argument that lets you pass in a readable IPv4
address argument it seems like an ommision that there's not an argument that
lets you pass in a readable IPv6 address argument.
I'd be happy to help you test the patch. :-) I'm running Linux 5.5.1.
------------------------------------------------------------------------------
AppSumo Presents a FREE Video for the SourceForge Community by Eric
Ries, the creator of the Lean Startup Methodology on "Lean Startup
Secrets Revealed." This video shows you how to validate your ideas,
optimize your ideas and identify your business strategy.
http://p.sf.net/sfu/appsumosfdev2dev
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
