Fong,
Please send replies ONLY to [EMAIL PROTECTED]

The net-snmp developers have plainly stated before that they
do not have large IPv6 network to test against.  This means that 
if you don't learn ways to provide better problem reports for
the issues which you have, you won't be pleased with the service
you receive.  All pardons due to the nature of volunteering one's
time without pay apply especially to you for your valuable time.

During the process you might even identify the problem yourself,
and create a patch!  THAT will result in faster service.

  1. Create a bug report.  Keep initial description short and concise.
     Use the bug report to hold all the information you will collect,
     since e-mail archive is not suitable for problem tracking.

     For each description you add, please take the time to
     mention the software version that you are describing, the platform
     that you build or run the software from.

     Please build using just the sources provided by the Net-SNMP
     project, where that is possible.  This helps to verify that the
     problem is ours, and not yours!

  2. You will be in a better position to test and report if
     you build from a machine that has no SNMP packaged.
     And, you can control the configuration used with confidence.

  3. For each version that you test,
     Identify the "configure" options used.
     Save the "configure" output and "make" output.
     Note that some outputs are sent to standard error, too.

  4. Create a log using 'snmpd -m "" -M "" -D ALL -f -Lf log'
      [ -m/M with blank value filters MIB parsing from the log]

  5. READ the log.  Yes, it is verbose.  It might even
     tell you what is not parsed correctly, etc.

  6. Attach the files you created in steps 3 and 4 to the bug report,
      identifying the net-snmp version that you used.  Include a log
      of commands that were invoked that "talk to" the agent.

  7. Cleanly remove the installed files in preparation for the next build.

  8. For version 5.0.9, repeat steps 2 through 7.
  9. Download 5.1.2 release, repeat steps 2 through 7.
 10. Extract the CVS main branch sources, repeat steps 2 through 7.
 11. Be patient.  Be prepared.  Be happy.

Best Regards,
-Mike Slifcak

> 
> From: "Fong Tsui" <[EMAIL PROTECTED]>
>  
> I have tried v5.1.2.rc2, it still can't launch as 
> snmpd udp:161,tcp:161,udp6:161,tcp6:161
> 


>-----Original Message----- 
>       
> Is there a patch which can solve this issue: launch IPv6 and IPv4 together?
>   snmpd udp:161,tcp:161,udp6:161,tcp6:161
>       
> At this moment, I can not update to v5.1.2 version. I am using 5.0.9 and hope to 
> solve this.
>               
>       
>       -----Original Message-----
>       From: Robert Story (Coders) [mailto:[EMAIL PROTECTED]
>       
>       On Fri, 6 Aug 2004 10:56:43 -0700 Fong wrote:
>       FT> Is it a known issue there is a problem to launch Ipv6 and ipv4
>       FT> together?
>       
>       It works in the main line CVS, so I'd guess it should work in 5.1.2 as well.
>       
>       FT> It seems it only gets the first type of trapsport. I am using 5.0.9.
>       
>       FT> Any help is appreciated.
>       
>       Did you configure with ipv6 support? Does ipv6 work by itself?
>       
>       --
>       Robert Story; NET-SNMP Junkie <http://www.net-snmp.org/> 
> <irc://irc.freenode.net/#net-snmp>
>       Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>
>       




-------------------------------------------------------
SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to