Logging with DD-WRT

From DD-WRT Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 01:55, 8 May 2008 (edit)
Soulstace (Talk | contribs)

← Previous diff
Revision as of 11:59, 23 August 2008 (edit) (undo)
Soulstace (Talk | contribs)
m (added to basic tut)
Next diff →
Line 46: Line 46:
[[dmesg command]] [[dmesg command]]
-[[Category: English documentation]]+[[Category: English documentation]][[Category: Basic tutorials]]

Revision as of 11:59, 23 August 2008



DD-WRT uses the syslog and klog daemons to log system, kernel, and firewall events. This can be useful for troubleshooting purposes, or just to keep an eye on how your router/network is behaving.


Logging is probably disabled by default. To enable it:

  1. Enable Syslogd under the Services tab.
    • If you wish to send logs to a remote system, enter the IP address of that machine which is also running a syslog utility (it needs an open network socket in order to accept logs being sent by the router).
  2. To log firewall events, go to the Security tab and enable the appropriate options. (Note: this doesn't function in micro)

That's all there is to it. DD-WRT should now be logging...either locally to /tmp/var/log/messages, or remotely to the IP address you specified earlier.

Recommended tools

Here are some utilities you may wish to check out if you're logging remotely:

syslog-ng (CYGWIN)
Kiwi Syslog

Linux already has syslogd built in.

Displaying logs in your web browser

create a symbolic link in /tmp/www

ln -s /tmp/var/log/messages /tmp/www/log.html

now go to:

(credits to kuthulu for that tip)

micro versions

Micro versions have a stripped down version of BusyBox, so it might not include the ln command used above. In that case, you can use a different method to view the logs from within your browser, shown below.

Issue the following command from the Web Interface -> Commands section (or via Telnet):

cat /tmp/var/log/messages

As noted in the Setup section, the logfile in micro currently does not show any firewall events, unfortunately.

See Also

dmesg command