Archiwum dla Kwiecień 2010

08
Kwi
10

rsyslog captures wrt54gl tomato’s logs

1. Edit the /etc/rsyslogd.conf file for allowing the rsyslog server to accept logs from UDP (port 514), by uncommenting the following lines:

# provides UDP syslog reception
$ModLoad imudp
$UDPServerRun 514

By default, rsyslogd will treat the remote logs as if they were local ones (meaning, among other things, the entries will end up in the same logfiles where the local logs are stored). In my setup, I found convenient to override that behaviour and instead place all the logs from my router in a different file:

2. (Optional) Create the file /etc/rsyslogd.d/openwrt.conf with the following contents:

:source, isequal, "myrouter.mydomain" /var/log/mylogfile.log
:source, isequal, "myrouter.mydomain" ~

The first line logs the entries coming from „myrouter.mydomain” (can be expressed as an IP as well) into /varlog/mylogfile.log, while the second one prevents any further processing of the entry by discarding it (note the final tilde ~). A more complete description of the different configuration options [1] and example configurations [2] can be found on the rsyslogd man pages and wiki.

Hope it helps someone.

[1] http://www.rsyslog.com/doc-rsyslog_conf.html
[2] http://wiki.rsyslog.com/index.php/Configuration_Samples

This tutorial was wrote by diego.mics on openwrt forum
08
Kwi
10

ssh on wrt54gl with tomato

  1. Login to your AccessPoint
  2. Click Administration->Admin access
  3. Set
  • Enable at Startup YES
  • Remote Access YES
  • Remote Port 2222
  • Port 22
  • Allow Password Login NO
  • Authorized Keys – you have to generete this with ssh-keygen outside

Here is how to generate authorized key:

ssh-keygen -t rsa

Cat and paste the *pub key to the Authorized Keys field and click SAVE.

…give it a litle bit of time…sip some (admin’s) coffee…

All you have to do is:

ssh -p 2222 root@192.168.1.1 

Happy ssh-ing 🙂

08
Kwi
10

Tomato on WRT54GL Linksys

  1. Download Tomato sofrware, from here.
  2. Log into you Access Point and go to: Administration-> Firmware Upgrade.
  3. Load WRT54G_WRT54GL.bin and click UPGRADE.
  4. Drink some (admin’s)coffee…and wait for it….
  5. Enjoy
06
Kwi
10

RAID5 failed to run set md2

Subject: RAID md2 failed to run
also
mdadm: failed to RUN_ARRAY /dev/md2 Invalid argument

solution:
1. Check the mdadm configuration: /etc/mdadm/mdadm.conf (or just /etc/mdadm.conf) and see what kind of devices are present in the array /dev/md2
cat /etc/mdadm/mdadm.conf
2. Stop the failed array
mdadm -S /dev/md2
3. Assemble the array
mdadm --assemble --force /dev/md2 /dev/sdc5 /dev/sdd5 /dev/sda5 /dev/sdb5
4. Reboot




Google Adsense

kalendarz

Kwiecień 2010
Pon T Śr T Pt S S
« Sty   Maj »
 1234
567891011
12131415161718
19202122232425
2627282930