Dave Shield wrote:
Err... yes, probably.
Is the same approach needed in the main 'udpTable_handler' routine,
in the UDPLOCALADDRESS branch?
I don't think so. Snmp walk show it correct. Maybe because address should
be send in network order ?
What about in the other pair of iterators (UDPTABLE_IS_TABLE)
Sorry, I don't have this platforms, and I don't know in what order they
store
there UDP/TCP ADDRESS :(
There are three "special cases": hpux11, solaris2 & WIN32
Then there's an "everything else" case, which starts:
#ifdef linux
#define INP_NEXT_SYMBOL inp_next
#endif
#define UDPTABLE_ENTRY_TYPE struct inpcb
<etc>
But it's *only* the INP_NEXT_SYMBOL that's linux-specific.
Everything else in that block is general.
Oops, sorry, mind jokes %)
You right, I miss this #endif...
Oleg
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
| 
