Hey all,
2.0.0 Beta1 is nearly 2 months old now and we should move on. 2 months
are already too long, so the only thing I plan to add for an actual
release is:
- make TCPIP_CORE_LOCKING the default (todo: implement mutexes for the
win32 port)
- fix the timing issues (patches #7855, #8712, #899
Hi Marco,
there is only one callback, it supplies the OID of the object that has been
written. We found this to be more suitable then adding a callback per
written object, because we think you usually do not have that many writable
elements.
You can use snmp_oid_compare() for OID comparison.
C
Thank you Noam.
I am not using raw api's TCP part. (raw api is disabled at lwipopts.h). Raw Api
has beautiful web server example that covers everything (SSI, post, dynamic
files). I couldn't find an example like that for netconn. So i get parts that i
am copying codes that doing that staff from
Hi Dirk,
Thanks for pointing this out. I will try to provide a patch to introduce
varbinds to snmp traps again.
I have another question regarding SNMP. I see you added the option to execute a
callback function after a succeeded set request.
How should this callback mechanism be used? For exa
Peter Haagerup wrote:
> the fields "max" and "err" in the MEM UDP_PCB section contains the number
> 4294967295 (2^32 - 1) which is strange
That's really strange: 'err' is only increased but never decreased.
Also, by default, the stats counters are u16_t, not u32_t.
I don't expect disabling UDP to
pe...@sensohive.com wrote:
> In the lwIP log file, I see that around the time when it stops working, the
> fields "max" and "err" in the MEM UDP_PCB
> section contains the number 4294967295 (2^32 - 1) which is strange, since
> these fields are 0, 1 or 2 in the long period
> where there is no pro