buglwIP - A Lightweight TCP/IP stack - Bugs: bug #22070, MIB_OBJECT_WRITE_ONLY not...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #22070: MIB_OBJECT_WRITE_ONLY not implemented in SNMP

Submitted by:  Josh Strinch <mischief>
Submitted on:  Mon 21 Jan 2008 05:08:12 PM UTC  
 
Category:  None Severity:  2 - Minor
Item Group:  Faulty Behaviour Status:  Fixed
Privacy:  Public Assigned to:  Simon Goldschmidt <goldsimon>
Open/Closed:  Closed Planned Release:  None
lwIP version:  CVS Head

( Jump to the original submission)

Fri 13 Feb 2015 08:13:03 PM UTC, comment #7: 

Finally fixed, turns out I just misunderstood the RFC back in 2010...

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Thu 12 Feb 2015 10:22:27 PM UTC, comment #6: 

Back to the original summary: WRITEONLY is not implemented and the current implementation of getnext stops with NOSUCHNAME when iteration reaches a WRITEONLY value...

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Tue 04 May 2010 06:31:08 PM UTC, comment #5: 

Updated summary and status/severity to reflect the changes

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Wed 21 Apr 2010 08:12:25 PM UTC, comment #4: 

Removing the planned release 1.4.0 as I don't really need it and currently don't have the time.

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Mon 25 Jan 2010 05:44:21 PM UTC, comment #3: 

Partly fixed: write-only or not-accessible are still returned by getnext (though not by get any more).

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Sun 03 May 2009 03:45:19 PM UTC, comment #2: 

Oh, and do we need to prevent reading from WRITE_ONLY nodes, too?

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Sat 02 May 2009 04:23:27 PM UTC, comment #1: 

This response is also a little late and I think it's a pity noone from axxon replied so far.

But I guess this is fixed rather easily in snmp_msg_set_event(): just let MIB_OBJECT_WRITE_ONLY pass also in the two checks where we test for MIB_OBJECT_READ_WRITE and that should be it.

Unfortunately I cannot test it without a private MIB and thus I would just check it in unless there is someone seriously against it...

Simon Goldschmidt <goldsimon>
Project AdministratorIn charge of this item.
Mon 21 Jan 2008 05:08:12 PM UTC, original submission:  

MIB_OBJECT_WRITE_ONLY isn't implemented - just READ_ONLY and READ_WRITE.

Symptom is that SET on WRITE_ONLY object always fails with NOSUCHNAME.

Josh Strinch <mischief>

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by kieranm (Updated the item)
  • -email is unavailable- added by goldsimon (Posted a comment)
  • -email is unavailable- added by mischief (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 11 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2015-02-13 goldsimon StatusConfirmed => Fixed
        Open/ClosedOpen => Closed
    2015-02-12 goldsimon SummarySNMP: MIB_OBJECT_WRITE_ONLY is readable for getnext => MIB_OBJECT_WRITE_ONLY not implemented in SNMP
    2013-01-14 goldsimon CategoryContrib => None
    2010-05-04 goldsimon Severity3 - Normal => 2 - Minor
        StatusIn Progress => Confirmed
        SummaryMIB_OBJECT_WRITE_ONLY not implemented in SNMP => SNMP: MIB_OBJECT_WRITE_ONLY is readable for getnext
    2010-04-21 goldsimon Planned Release1.4.0 =>
    2009-08-20 kieranm Planned Release => 1.4.0
    2009-05-02 goldsimon StatusNone => In Progress
        Assigned toNone => goldsimon

    Back to the top


    Powered by Savane 3.5