Hi,
Thank you guys. Looks like I overlooked the difference in runtime
environment. For real use I have still installed Ethereal, and
Wireshark is indeed run from build directory only.
Sorry for the noise. I hope someone can help me further in main main
issue about filling display columns from dis
On Sat, Jan 27, 2007 at 12:36:55AM +0100, Andrej Mikus wrote:
> I notice that wireshark emits unconditionally warning mentioning that
> it Could not find the radius directory.
I assume that you are running Wireshark from its build directory without
having a version installed? Guy recently adde
On 1/27/07, Andrej Mikus <[EMAIL PROTECTED]> wrote:
> Thanks for comments.
>
> Of course, I removed the message to stop coming out after I realized
> that it is coming before preferences.
>
> Creating file in my system does not address this problem for others.
Yep but Others usually install either
Thanks for comments.
Of course, I removed the message to stop coming out after I realized
that it is coming before preferences.
Creating file in my system does not address this problem for others.
Elegant solution would be perhaps to postpone reading the directory until
it is really needed.
Alt
The radius dictionary gets loaded way before preferences are
evaluated. Giving no warning and then having the packets undecoded
isn't elegant.
Your patch suppresses the error altoghether which is not a nice solution.
What you can do is just add a dummy radius dir and a dummy dictionary:
$ cd $W
Team,
I notice that wireshark emits unconditionally warning mentioning that it
Could not find the radius directory.
I do not think that radius dictionary is needed for operation in all
environments, is is possible to move this output to some kind of
diagnostics mode?
Based on my search, it appea
