On Tue, 2004-08-10 at 12:35 -0400, Ted Kaczmarek wrote:
> On Tue, 2004-08-10 at 09:34 -0400, Ted Kaczmarek wrote:
> > Process snmpd (pid: 1930, stackpage=ee6cb000)
> > Stack: ee6cbf04 00000001 00000000 c2f5f980 b5d5dab3 00000000 00000000
> > 00000000
> >        000089f0 ee7d7e00 ee6cbf54 00000000 c01f9230 ee7d7e00 ee6cbf54
> > 000089f0
> >        ee6cbf54 000089f0 00000001 ee6cbf54 c01f9447 ee6cbf54 000089f0
> > 00000020
> > Call Trace:   [<c01f9230>] dev_ifsioc [kernel] 0x3d0 (0xee6cbf24))
> > [<c01f9447>] dev_ioctl [kernel] 0x1a7 (0xee6cbf44))
> > [<c01f0486>] sock_ioctl [kernel] 0x26 (0xee6cbf84))
> > [<c01571a9>] sys_ioctl [kernel] 0xc9 (0xee6cbf94))
> > [<c010953f>] system_call [kernel] 0x33 (0xee6cbfc0))
> > 
> > 
> > This is on a RH9 with Openswan 2.1.4-1  and net-snmp-5.0.9-2.90.1.
> > 
> > This of any value?
> > Or gdb output required as well, I still owe you guys one :-)
> > 
> > Ted
> > 
> http://www.gibraltar.at/pipermail/debian-openswan/2004-July/000019.html
> 
> Someone else seeing simillar issue.
> 
> Sorry about replying to my own post but sometimes it makes sense :-)
> 
> Ted

Problem occurs when snmpd tries to figure out transmission speed for the

interfaces:

<agent/mibgroup/mibII/interfaces.c>
...
if (ioctl(fd, 0x8947, &ifr) >= 0) {
     new_ioctl_nums = 1;
} else if (ioctl(fd, SIOCDEVPRIVATE, &ifr) >= 0) {
     new_ioctl_nums = 0;
... 

So, it first tries SIOCGMIIREG ioctl; if that doesn't work, it falls 
back to SIOCDEVPRIVATE which seems to have been previously used for this

purpose.

ipsec however uses SIOCDEVPRIVATE completely differently:

/* attach a virtual ipsec? device to a physical device */
#define IPSEC_SET_DEV (SIOCDEVPRIVATE)


==> Result: ipsec bombs out trying to handle SIOCDEVPRIVATE ioctl for 
(already configured) ipsec0.

which leaves us with the question: what's the right fix?
        a) remove the fallback SIOCDEVPRIVATE call from snmpd
        b) add a SIOCGMIIREG ioctl to ipsec
        c) handle the spurious SIOCDEVPRIVATE ioctl more gracefully in
ipsec.

I've just verified that removing the fallback to SIOCDEVPRIVATE from 
snmp works as a fix, no more problems with openswan+snmp daemon. What I 
can't say if this might impact snmpd functionality when used with older 
kernels/drivers that implement only SIOCDEVPRIVATE.

Hijacked from a reply to an Openswan post. 
Credit to Martin Bene.

Ted





-------------------------------------------------------
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-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

Reply via email to