Re: Non-standard interfaces in ifTable

2005-02-16 Thread Robert Story
On Tue, 15 Feb 2005 14:59:02 -0500 Jeff wrote: JO Another issue is that some JO ifTypes are not being identified correctly. I have identifed JO the part of the code (the MFD version) where that is an issue JO and hope to put together a patch in the next week or so. Great! We love patches. ;-) --

Re: Non-standard interfaces in ifTable

2005-02-15 Thread cnelson
... As far as future compatibility goes, getting the kernel to recognize your interfaces is the best option. If that's not possible, then you'll have to maintain proprietary patches against net-snmp. Robert, I know you're the expert here but I've got non-standard Interfaces working

Re: Non-standard interfaces in ifTable

2005-02-15 Thread Robert Story
On Tue, 15 Feb 2005 07:47:23 -0500 [EMAIL PROTECTED] wrote: CRC ... CRC As far as future compatibility goes, getting the kernel to CRC recognize your interfaces is the best option. If that's not possible, CRC then you'll have to maintain proprietary patches against net-snmp. CRC CRC Robert,

Re: Non-standard interfaces in ifTable

2005-02-15 Thread cnelson
On Tue, 15 Feb 2005 07:47:23 -0500 [EMAIL PROTECTED] wrote: CRC ... CRC As far as future compatibility goes, getting the kernel to CRC recognize your interfaces is the best option. If that's not possible,CRC then you'll have to maintain proprietary patches against net-snmp. CRC CRC

Re: Non-standard interfaces in ifTable

2005-02-15 Thread Robert Story
On Thu, 10 Feb 2005 10:16:54 -0500 Jeff wrote: JO I have an embedded Linux system with some interfaces that are not JO standard, i.e. the default ifTable implementation isn't getting part JO or all of the information. From looking at the code, it appears that I JO willneed to directly

RE: Non-standard interfaces in ifTable

2005-02-15 Thread Jeff Olhoeft
Thank you, this is exactly what I was looking for. I agree that getting the kernel to report the interfaces correctly is the ideal approach. That will be my prefered approach, but not being familiar with that part of the system, I like having alternative approaches. Another issue is that some

Re: Non-standard interfaces in ifTable

2005-02-14 Thread Robert Story
On Thu, 10 Feb 2005 09:41:18 -0500 Jeff wrote: JO I have an embedded Linux system with some interfaces that are not JO standard, i.e. the default ifTable implementation isn't getting part or JO all of the information. Net-snmp gets the interface information from the kernel. If your embedded

Non-standard interfaces in ifTable

2005-02-10 Thread Jeff Olhoeft
Hello, I have an embedded Linux system with some interfaces that are not standard, i.e. the default ifTable implementation isn't getting part or all of the information. From looking at the code, it appears that I will need to directly modify the source that comes with net-snmp. This will leave me

Re: Non-standard interfaces in ifTable

2005-02-10 Thread cnelson
I have an embedded Linux system with some interfaces that are not standard, i.e. the default ifTable implementation isn't getting part or all of the information. From looking at the code, it appears that I willneed to directly modify the source that comes with net-snmp. ... You can tell

RE: Non-standard interfaces in ifTable

2005-02-10 Thread Jeff Olhoeft
I have an embedded Linux system with some interfaces that are not standard, i.e. the default ifTable implementation isn't getting part or all of the information. From looking at the code, it appears that I willneed to directly modify the source that comes with net-snmp. ... You can

Re: RE: Non-standard interfaces in ifTable

2005-02-10 Thread cnelson
I have an embedded Linux system with some interfaces that are not standard, i.e. the default ifTable implementation isn't getting part or all of the information. From looking at the code, it appears that I willneed to directly modify the source that comes with net-snmp. ...