RE: Support for tcp with IPv6

2005-05-31 Thread Srini Kode (skode)
Hi, Our requirement needs the net-snmp-5.1 to support udp & tcp for both ipv4 and ipv6. Accordingly I used the options udp:161 and tcp:161 to start snmp daemon. It comes up fine. But in addition to the above 2 options, for ipv6 support I added 2 more options: udp6:161 and tcp6:161. The snmp daem

compiling module; conflicting function names

2005-05-31 Thread Matthew Boehm
Hi all. I am one of many side programmers for Asterisk, the open source PBX. (www.asterisk.org) Many months ago, someone tried to write a module for Asterisk that would allow direct SNMP querying of many different "guages"; such as number of current SIP calls, number of Zap calls, etc... I'm tryi

re: implicit declaration of function "strtok_r"

2005-05-31 Thread Bruce Shaw
Some more detail on this issue: When I check config.log, CVS MAIN shows a check for strtok_r and later ac_cv_func_strtok_r=yes. Make doesn't raise any particular issue. 5.0.10.rc2 shows the same thing but make seems to generate a whole lot of extra noise on the issue eg. mibII/interfaces.c: In

Re: Fwd: Linux 2.6 IPv6 interface "ip6tnl0"

2005-05-31 Thread Gunnar Lindberg
Ah, I see. if_type_from_name(); I'm not sure how much one should depend on how that code currently is written , but as is - strncmp() - it will work just fine with if_unit="" and if_name="eth2:3". Otherwise, one could use a slightly more complicated split algorithm: o Backwards while ['0'-

Re: Fwd: Linux 2.6 IPv6 interface "ip6tnl0"

2005-05-31 Thread Dave Shield
On Tue, 2005-05-31 at 09:13, Gunnar Lindberg wrote: > I guess you code writers can tell why (if) this is a bad idea, but > my 0.01c is to skip the if_unit stuff completely > The only usage of if_unit I find is strncat() and string_append_int() > and both work well with the above. It's not the u

Fwd: Linux 2.6 IPv6 interface "ip6tnl0"

2005-05-31 Thread Gunnar Lindberg
A few days ago I posted the mail below. Problem: : ip6tnl0 : ^ : ! split into <6tnl0> by the current code in Interface_Scan_Init(). One immediate comment was that my fix (below) would break some interface names e.g: o eth2:3 o eth3.4 This is true, but it's in fact true for