Question : Deciphering log files

Hi:

As usual, the Linksys folks know less about their equipment than my grandmother (and she's no longer with us).

Realizing that no device is perfect, I've stayed with the Linksys product line because of their heavy Cisco influence.  Recently I've been working with the WRV54G, the wireless VPN router.  It has problems.  Sometimes it just "freezes" the way a desktop would freeze if you could see it with monitor, keyboard and mouse.  To fix the issue, I was given Beta firmware, which after I installed, fixed one problem and caused another.  So I enabled the logs.  They are all noise to me.  Can someone help me make some intelligent sense out of them?

Sample: (note..I snipped out actual IP addresses)

Wed Feb 16 11:59:44 2005
Error resolving hostname: "0.0.0.0/0"
Wed Feb 16 11:59:44 2005
estream_read_call_func:512: socket 21 read_func closed connection 1
Wed Feb 16 11:59:44 2005
Error resolving hostname: "0.0.0.0/0"
Wed Feb 16 11:59:44 2005
estream_read_call_func:512: socket 43 read_func closed connection 1
Wed Feb 16 11:59:44 2005
estream_read_call_func:512: socket 42 read_func closed connection 1
Wed Feb 16 11:59:44 2005
Error resolving hostname: "0.0.0.0/0"
Wed Feb 16 11:59:44 2005
DNS: trying forwarder 208.57.0.10.
Wed Feb 16 11:59:44 2005
DNS: trying forwarder 208.57.0.10.
Wed Feb 16 11:59:43 2005
DNS: trying forwarder 208.57.0.10.
Wed Feb 16 11:59:43 2005
Error resolving hostname: ""
Wed Feb 16 11:58:52 2005
estream_read_call_func:512: socket 6 read_func closed connection 1
Wed Feb 16 11:58:52 2005
estream_read_call_func:512: socket 7 read_func closed connection 1
Wed Feb 16 11:58:52 2005
estream_read_call_func:512: socket 8 read_func closed connection 1
Wed Feb 16 11:58:31 2005
RGFW-IN: ACCEPT (UDP IP omitted for security reasons:500->(IP omitted for security reasons):500 on ixp1) [700,45875201]

At the time this log was generated, the log was fine.  In fact, there seems to be no problems at all with the device.  But I am having problems with the content filtering.  If I enable it, the network performance slows to early dialup speeds.

It is impossible to find someone at Linksys with whom to have an intelligent conversation.  You can never talk to their product managers.

Answer : Deciphering log files

The problem you are having is probalby becouse new beta firmware is unoptimized for filtering and becouse of that it's slow (that's why it's beta).
LinkSys won't tell you about this for sure, but it ain't their fault (you should wait for final ver), but freezing the device with old (production) ones is their fault.
Persons with same (or similiar problems):
http://www.linksysinfo.org/modules.php?name=Forums&file=viewtopic&t=2742
http://www.dslreports.com/forum/remark,8318940
I would try to make it working with non-beta firmware rather than solving this issue.

Decipher:
Error resolving hostname - This is a DNS resolver. When you type www.google.com you've got web server ip address that is used to communicate with. This is called resolving.
DNS: trying forwarder - Probalby a secondary DNS server which packets is formwarded if the first one didn't resolve.
estream_read_call_func - Some internal function. Probalby has something to do with IPSec. Nothing funny anyway.