WRV200 Log - Inbound and Blocked events?

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by ghost_zero5, Jan 5, 2007.

  1. ghost_zero5

    ghost_zero5 LI Guru Member


    I tried using WallWatcher to see inbound or blocked (or just blocked?) events a.s.o. with the WRV200 (v1.0.24-ETSI) BUT I only see outgoing and non blocked events. I tried some secuirty-scans over the Internet and always the same no inbound or even better refused events AND I have enabled to log everything.
    I think that is strange because this is the most interesting thing and exactly that doesn't get logged?

    P.S.: It would also be nice to be able to log things on the router memory for some days and look at that log through the Web-UI. Would be a nice feature I think but it should be just the text log not such a stupid Web-UI-Log as with the WRT54G.
  2. Sfor

    Sfor Network Guru Member

    There were some major changes to the Syslog feature in the 1.0.26 firmware. Yet, the device does not report any blocked traffic events, still.

    The Syslog stops working quite often, and a router reset is necesary to get it going again.

    I do not like the way the log was made, as well. What is the point in a stand alone device not being able to log events without an additional computer running. The same effect could be done with a computer routing network traffic and keeping it's own log entries. This plus a cheaper access point would give the same effect.

    I had two SMC based routers before WRV200. Both were much simpler, yet very reliable and "self syslogging". When the WRV200 is jamming in this or other way (it does it quite often), I'm missing the simplicity and the logging capability of my old routers.
  3. ghost_zero5

    ghost_zero5 LI Guru Member

    Well... There is the mail feature too but I believe that one people won't use for sure. I mean: You get an e-mail for every event that are far too much mails. It would be much better if you would get an e-mail every 24 hours or something like that BUT as soon you have this you could also make a log available via the Web-UI (which would be the best logging feature anyway).

    But well: I don't really need the log that often so that doesn't matter that much BUT the FTP/ICQ-Issue is a bit anoying. Should be fixed ASAP if you ask me... Otherwise I think it is a nice router (at least if you keep the price in mind). Although it needs some firmware work to be done still and the most important is to fix the FTP/ICQ-Issues if you ask me...
  4. Sfor

    Sfor Network Guru Member

    A fully functional log could be a help while looking for the cause of the other issues. That's why the log is the most important feature, now, I believe.
  5. ghost_zero5

    ghost_zero5 LI Guru Member

    Well... Of course it could help :) But I believe fixing connectivity problems should be first. If they can be fixed without a fully functional log :)
  6. Sfor

    Sfor Network Guru Member

    Well. In order for a problem to be fixed, the fimware programmers have to reproduce the problem, first. Right now, there are many issues they can not reproduce (FTP problem included, I think). So, with a log working correctly it would be easier to find out more about what is going on, and perhaps to link an issue with some particular condition.
  7. ghost_zero5

    ghost_zero5 LI Guru Member

    Well strange is that I didn't have the FTP/ICQ-Issue today (so maybe you are right and they are not that easy reproducable, I don't know but before I had that problem every day)... The only thing I did was enable and disable W-LAN on the router once (last night - I only enable W-LAN when I need it) but I did not reboot the router....

    P.S.: Of course, a working log COULD but only could help to fix the problems but not necessarily...
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice