[ First - *please* don't mail me privately, without copying
any responses to the mailing list. I don't have the time
or inclination to offer private, unpaid, SNMP consultancy.
Keep discussions to the list, where others can both learn
and offer advice. Thanks. ]
> If the issue with ANONYMOUS#4 occurs with the notification of
> dot11Disassociate, then why is there no similar construction with
> the dot11Deauthenticate and dot11AuthenticateFail notifications
> as well?
Yes - they would need to be tweaked in exactly the same manner.
I hadn't spotted those two notifications.
And please not that I'm not saying that this *is* the cause - I'm
just offering it as a distinct possibility, based on the error
message you gave. The only way to find out is to tweak the
MIB and see if the problem goes away.
> As for the indent problem indicated at the bottom of this email,
> the only thing that I can offer is that the message comes during
> indentation of the .c file
OK - I've now tried running "indent ieee802dot11.c" (using the
file that you posted on Tuesday). It turns out that the indent
message is *also* as a result of this same ANONYMOUS#4 problem.
If I tweak the "ANONYMOUS#4" token to read "ANONYMOUS4" wherever
it occurs, then indent is quite happy. I think it must be the
# being wrapped onto a new line, and then interpreted as the start
of a pre-processor directive.
> and this is reported on the command
> line of the terminal window within which I executed mib2c. There
> is no indication on the command line as to where the problem
> occurs. However, given the content of the message, "unexpected
> end of file," I would suspect that the end of the .c file does not
> conform to some standard. For instance, the file may be ended
> with a <cr> instead of a <cr><lf>. In any case, it seems a better
> bet that the error is observed at the end of the .c file, and not at
> some time earlier. This I will attempt to verify, by viewing the
> output of mib2c with and without invocation of the indent facility.
> The result is either that all the file is indented, or only part of
> the file is indented. If all the file is indented, then the cause of
> the error becomes more likely a result of missing terminal
> characters. If the result is that not all the file is indented, then
> the error is from some other cause.
Nope - that's a complete red herring.
It turns out that my original suggestion was correct after all:
>> I'd suggest you try to address the ANONYMOUS#4 problem first,
>> and then see if indent still chokes. If so, then please
>> report back where the indent output is trunctated, and what
>> the pre-indent file looks like at this point.
Dave
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Net-snmp-users mailing list
[EMAIL PROTECTED]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
