From: SourceForge.net <no...@so...> - 2008-09-11 20:25:14
|
Patches item #700681, was opened at 2003-03-09 22:38 Message generated for change (Comment added) made by hardaker You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=312694&aid=700681&group_id=12694 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed >Resolution: Accepted Priority: 2 Private: No Submitted By: Stephen J. Friedl (sjfriedl) >Assigned to: Wes Hardaker (hardaker) Summary: Enable limited UDP broadcast support Initial Comment: I realize that the whole idea of doing SNMP broadcast may be anathema to many, but this was a real need on a real project so we spent some time to figure it out for use with async SNMP This patch enables the setting of UDP broadcast on an SNMP session. The equipment I'm talking to initially has no IP address, and this is the only way of performing configuration that suits our purposes (these are JetDirect-like print servers). The code itself is pretty self-contained, but it's likely that somebody else will pick another value for the "next" flag in the SNMP_FLAGS_xxx series unless this gets picked up by the main team. It's also likely that my hack is sub-optimal. If nothing else, it would be helpful if the SNMP_FLAGS_UDP_BROADCAST value could at least be entered as a placeholder. We did some digging to extend broadcast support to the cmdline tools, but this was much more work: we'd have had to change the whole workings to use async, and this looked like a really bad idea. -- Steve ---------------------------------------------------------------------- >Comment By: Wes Hardaker (hardaker) Date: 2008-09-11 13:25 Message: I've modified it to bring it up to spec with the trunk line and applied it. ---------------------------------------------------------------------- Comment By: Thomas Anders (tanders) Date: 2007-10-04 23:20 Message: Logged In: YES user_id=848638 Originator: NO Not yet. Feel free to update the patch accordingly. ---------------------------------------------------------------------- Comment By: Wayne F. Tackabury (waytac) Date: 2007-10-04 15:18 Message: Logged In: YES user_id=189900 Originator: NO Did this ever get carried forward in the 5.4 dev branch or on any subsequent release? ---------------------------------------------------------------------- Comment By: Thomas Anders (tanders) Date: 2006-01-15 23:34 Message: Logged In: YES user_id=848638 According to yesterday's IRC talk, Stephen is looking into updating this patch for CVS MAIN (5.4.dev). ---------------------------------------------------------------------- Comment By: David Peer (davidpeer) Date: 2006-01-15 23:23 Message: Logged In: YES user_id=1310219 in version 5.3 i didn't find any async_response handler. what can i do? ( beside writing my own handler ) ---------------------------------------------------------------------- Comment By: David Peer (davidpeer) Date: 2006-01-15 02:51 Message: Logged In: YES user_id=1310219 did you tried it on v 3? I couldn't find in the snmp_session struct the field: sess_template.callback = asynch_response ---------------------------------------------------------------------- Comment By: Thomas Anders (tanders) Date: 2006-01-12 03:35 Message: Logged In: YES user_id=848638 Without having looked at the patch yet: Has this been tested with SNMPv3? SNMPv3 discovery may need special attention. And again: we'd need a patch against CVS MAIN to consider adding this functionality. ---------------------------------------------------------------------- Comment By: Thomas Anders (tanders) Date: 2005-08-29 16:20 Message: Logged In: YES user_id=848638 Can you resubmit this against CVS MAIN? ---------------------------------------------------------------------- Comment By: Stephen J. Friedl (sjfriedl) Date: 2003-03-23 15:05 Message: Logged In: YES user_id=730166 While using NET-SNMP on a Sun, it seems that the patch required a bit more than the change for Linux. Uploading a patch for 5.0.8 that we're using now in production code. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=312694&aid=700681&group_id=12694 |