OpenWrt merupakan firmware open source untuk embedded device yang menggunakan metode packaging agar device dapat dikustomisasi sesuai keinginan.

Metode instalasi OpenWrt ini hampir sama dengan FONERA. Instalasi OpenWrt ini cukup aman, mengingat fimware asli dapat dikembalikan lagi jika sudah tidak ingin menggunakan OpenWrt lagi. Untuk detailnya lihat di sini.

Firmware OpenWrt untuk EOC-2610 yang berbasis pada Atheros WiSOC yaitu:

• Vmlinux
• Rootfs

Langkah-langkah:

1. Atur ip address komputer pada subnet 192.168.1.0/24, misal 192.168.1.20 netmask 255.255.255.0.
2. Persiapkan TFTP Server, untuk Windows dapat menggunakan TFTPD32. Jika anda menggunakan Ubuntu install paket atftpd dengan: sudo apt-get install atftpd.
3. Taruh kedua file firmware OpenWrt pada rootdir TFTP server. Untuk windows, rootdir dapat diatur setelah menjalankan TFTPD32. Untuk Ubuntu, rootdir atftpd server ada di /var/lib/tftpboot (membutuhkan akses root).
4. Download utiliti command line untuk RedBoot. Untuk windows download di http://numpang.bkdjombang.com/files/windows/engenius/RedBoot.zip, dan untuk Ubuntu download di http://numpang.bkdjombang.com/files/ubuntu/RedBoot.tar.gz. Ekstrak arsip tersebut ke suatu folder. Untuk Ubuntu, anda perlu juga menginstall putty dengan: sudo apt-get install putty.
5. Matikan device, kemudian jalankan utility redboot.cmd/redboot.sh dari arsip pada langkah 4. Kemudian nyalakan kembali device, tunggu hingga jendela putty menampilkan prompt RedBoot>. Jika putty tidak menampilkan prompt tersebut, anda perlu mengulang-ulang langkah ini.
6. Ketik perintah-perintah berikut (yang berhuruf tebal):

   RedBoot> ip_address -l 192.168.1.1/24 -h 192.168.1.20
   IP: 192.168.1.1/255.255.255.0, Gateway: 0.0.0.0
   Default server: 192.168.1.20
   RedBoot> load -r -b %{FREEMEMLO} openwrt-atheros-vmlinux.lzma
   Using default protocol (TFTP)
   Raw file loaded 0x80041000-0x80100fff, assumed entry at 0x80041000
   RedBoot> fis init -f
   About to initialize [format] FLASH image system - continue (y/n)? y
   *** Initialize FLASH Image System
   ... Erase from 0xa8030000-0xa87e0000: ...........................................................................................................................
   ... Erase from 0xa87e0000-0xa87f0000: .
   ... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
   RedBoot> fis create256 -r 0x80041000 -e 0x80041000 vmlinux.bin.l7
   ... Erase from 0xa8030000-0xa80f0000: ............
   ... Program from 0x80041000-0x80101000 at 0xa8030000: ............
   ... Erase from 0xa87e0000-0xa87f0000: .
   ... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
   RedBoot> fis free
     0xA80F0000 .. 0xA87E0000

7. Perintah fis free di atas digunakan untuk mengkalkulasi ukuran rootfs pada flash, mengingat ukuran kernel/vmlinux dapat berbeda-beda terlebih lagi jika anda meng-kompilasi dan meng-konfigurasi sendiri fimware OpenWrt. Catat alamat awal dan akhir kemudian kalkulasi ukuran rootfs menggunakan calculator. Pada contoh di atas ukuran rootfs = 0xA87E0000 – 0xA80F0000 = 0×6F0000 (parameter -l). Catat juga alamat awal untuk flashing rootfs = 0xA80F0000 (parameter -f). Kemudian lanjutkan dengan perintah-perintah berikut (INGAT, SESUAIKAN PERINTAH-PERINTAH INI SESUAI DENGAN KALKULASI DI ATAS):

   RedBoot> load -r -b %{FREEMEMLO} openwrt-atheros-root.squashfs
   Using default protocol (TFTP)
   Raw file loaded 0x80041000-0x801e0fff, assumed entry at 0x80041000
   RedBoot> fis create256 -f 0xa80f0000 -l 0x6f0000 -e 0 rootfs
   ... Erase from 0xa80f0000-0xa87e0000: ...............................................................................................................
   ... Program from 0x80041000-0x801e1000 at 0xa80f0000: ..........................
   ... Erase from 0xa87e0000-0xa87f0000: .
   ... Program from 0x80ff0000-0x81000000 at 0xa87e0000: .
   RedBoot> reset

8. Device kemudian reboot, coba ping ke ip 192.168.1.1, dan jika sudah tersambung ke ip tersebut, gunakan telnet untuk mengakses shell dan berikan perintah passwd untuk mengganti password device.
9. Langkah selanjutnya anda tinggal mengkonfigurasi device. Secara default Kamikaze 8.09 sudah menyertakan antarmuka web LuCI. Cukup buka browser ke alamat http://192.168.1.1/. Jika anda familiar dengan shell linux, anda bisa menggunakan SSH untuk mengkonfigurasi OpenWrt.
10. Dokumentasi konfigurasi OpenWrt lebih lanjut dapat dilihat di http://wiki.openwrt.org/doc/configuring.

Sebagai informasi tambahan, saat ini masih ada beberapa kekurangan OpenWrt pada EOC-2610 yaitu:

• Perintah reboot tidak berfungsi (berfungsi ketika hanya lan saja yang aktif, ketika pertama kali sesudah instalasi, setelah wireless aktif perintah tersebut tidak berfungsi – client mode).
• Tx Power tidak sama dengan firmware asli dari EnGenius (maksimal 19dBm, power offset tidak tersedia).

Wireless Distributed System (WDS) คือระบบที่เชื่อมต่อด้วย Access Point หลายตัวภายใต้ Protocol 802.11 ให้สามารถแลกเปลี่ยนข้อมูลระหว่างกันได้ แทนการใช้ Network Backbone ที่ใช้สายแบบที่เป็นตามปรกติทั่วไป ซึ่งแตกต่างจากวิธีอื่น คือใช้วิธีพินิจ MAC Address ของ Package ที่ส่งผ่าน

การเชื่อมต่อระหว่าง Access Point อ้างผ่าน MAC Address และแต่ละ Access Point ต้องมี Channel, Encryption Method เดียวกัน โดยการทำงานอาจพูดได้ว่าเป็น Repeater & Bridge แต่ก็มีข้อเสียคือ Throughput จะลดลงไปครึ่งหนึ่ง

ระหว่าง OpenWrt & DD-Wrt ไม่สามารถใช้ WDS ร่วมกันได้

Technorati : dd-wrt, openwrt, wds, wireless
Del.icio.us : dd-wrt, openwrt, wds, wireless

ไว้ set เวลาใน Wireless Router OpenWRT platform

• /etc/TZ ไว้ set time zone
• opkg install ntpdate หรือ ntpclient
• ลองดูกับ server : time.navy.mi.th

http://martybugs.net/wireless/openwrt/timesync.cgi

Technorati : openwrt, time synchronization
Del.icio.us : openwrt, time synchronization

ตากที่ trunk 17802 ได้อ้างไว้ว่าพึ่งเพิ่มเติมมาได้ไม่กี่เดือนคือ

make kernel_menuconfig

ควรลองดูเพราะทุกที make menuconfig จะสามารถเลือกได้แค่ package ที่ต้องการใน firmware เท่านั้น

Technorati : openwrt
Del.icio.us : openwrt

Quante volte vi siete trovati a girare per casa in cerca del vostro segnale wifi?
Quante volte avreste desiderato abbattere quella maledetta parete di tufo/pietra ottocentesca di casa vostra che riduce drasticamente le probabilità di navigare in wireless per tutta la casa?
Quante volte avete desiderato espandere il vostro wifi oltre i confini delle striminzite antennine del vostro Alice Gate di Telecozz?
Bene ora potete!

Universal Repeater

Bene, tralasciando questa ridicola introduzione e venendo al dunque ho ottenuto un comodo ripetitore di segnale configurando il mio WRT54GL con pochi passaggi.
La situazione in cui ci troviamo è tipo quella riportata in figura.

Ampliare la rete wifi con un repeater

Per prima cosa è necessario (se si vuole utilizzare la WPA-PSK impostata di default da Telecom) scaricare i seguenti pacchetti direttamente su OpenWrt.

root@OpenWrt:~# ipkg install wpa-supplicant
root@OpenWrt:~# ipkg install hostapd
root@OpenWrt:~# ipkg install zlib
root@OpenWrt:~# ipkg install libopenssl

Per poter visionare cosa avete sul sistema usate questo

root@OpenWrt:~# ipkg list_installed
base-files-atheros-2.6 - 10-9078 -
bridge - 1.0.6-1 -
busybox - 1.4.2-2 -
dnsmasq - 2.39-1 -
dropbear - 0.50-2 -
hostapd - 0.5.7-1 -
hotplug2 - 0.9+r102-2 -
iptables - 1.3.7-1 -
kernel - 2.6.21.5-atheros-1 -
kmod-madwifi - 2.6.21.5+r2568-20070710-atheros-2 -
kmod-ppp - 2.6.21.5-atheros-1 -
kmod-pppoe - 2.6.21.5-atheros-1 -
libgcc - 4.1.2-10 -
libopenssl - 0.9.8e-1 -
mtd - 5 -
ppp - 2.4.3-8 -
ppp-mod-pppoe - 2.4.3-8 -
uclibc - 0.9.28-10 -
udevtrigger - 106-1 -
wireless-tools - 29-1 -
wpa-supplicant - 0.5.7-1 -
zlib - 1.2.3-4 -
Done.

Se i pacchetti che avete sono + o – questi possiamo andare oltre…
Passiamo ora alla configurazione delle interfacce. In primo luogo modifichiamo la network lan

root@OpenWrt:~# vi /etc/config/network

#### LAN configuration
config interface lan
option type bridge
option ifname eth0.0
option proto static
option ipaddr 192.168.1.111
option netmask 255.255.255.0

Poi passiamo alla parte wireless

root@OpenWrt:~# vi /etc/config/wireless

config wifi-device wl0
option type broadcom
option channel 11 # lo stesso canale della wifi di Alice

config wifi-iface
option device wl0
option network lan
option mode ap
option ssid RepeaterWifi # il nome della wifi del repeater


config wifi-iface
option device wl0
option network lan
option mode sta
option ssid Alice-12345678 # il nome della rete wifi da ripetere
option encryption 'psk'
option key 'xxxxxxxxxxxxxxxxxxxxx'

Fatto ciò dovresta avere un bel ripetitore wifi!!

Objetivo

utilizar un linksys WRT54GLcon OpenWRT como repetidor de señal y de esta forma ampliar la zona de cobertura de la señal wireless. con una SSID propia.

Topologia

Requisitos

1. Router (Vecino) configurado en modo AP (access point)
2. Conocer el modo wireless del Router (Vecino) puede ser B, G, B+G(Mixed) para esto puedes usar wireshark en caso tal que no tengas acceso a la configuracion del router (No se esplicara en este post como hacer esto).
3. Conocer la Clave WEP o WAP del router vecino en caso que tenga. si no la conoces puedes usar aircrack-ng (No se esplicara en este post como hacer esto).
4. router linksys WRT54GLcon firmware openWRT (No se esplicara en este post como cambiar el firmware).

Manos a la obra!

vamos a configurar el Linksys como repetidor para tal fin vamos hacer lo sigueinte

• Conectarnos al Linksys por cable UTP directo (LAN)
• En el navegador web abrimos la sigueinte direccion: 192.168.1.1
• Pinchamos en Setup

Nos pide usuario y clave

• Escribimos el usuario y clave correspondiente (por omision es user: root , password: admin)

En Setup->Basic Setup

• configuramos el servidor DHCP  a activo.
• signamos una IP para la nueva red (Debe ser diferente a la que nos dal el Router Vecino)

ahora vamos a wireless->Bassic Settings y configuramos:

• Wireless Mode = Repeater
• Wireless Network Mode=B, G, Mixed segun sea el caso del router Vecino
• SSID=vecino (el ssid del router fuente)
• Creamos una Virtual Interface
• SSID Virtual=Mi-Hogar (el ssid que tu le quieras poner)

Lo ultimo es la seguridad inalámbrica (encriptación) en caso que aplique, para tal caso vamos a wireless->Wireless Security

• Security Mode=El modo del Router Vecino (WAP/WEP)
• WPA Algorithms=el metodo de encriptacion que use el router Vecino(TKIP,AES,ETC) (importante usar el mismo metodo)
• WPA Shared Key=la clave del router vecino
• si quieres configurar seguridad para tu conecixion lo haces en la parte de virtual interfaces

Y listo ya tenemos wifi en nuestro hogar con el patrocinio de nuestro vecino.

si tienes la oportunidad de desabilitar el firewall del router Vecino puede ser bueno para evitar problemas

upgrade firmware Senao EOC5610Kantor akhirnya mengabulkan untuk pembelian perangkat wireless baru Senao EOC5610. Mulanya sih mau menggunakan dd-wrt. Tapi aduh… ternyata firmware satu ini gratisnya cuman untuk perangkat2 semacam Linksys, tapi kalo untuk Senao? Bayar bung!!

Terpaksa harus putar otak, coba upgrade firmware via web interfacenya malah routernya gak bisa diakses! Ini kok macet… Sampai pusing dan stress… Lha gimana lagi, ini punya kantor. Kalo rusak ya ikut ganti, mana gak murah lagi.

Senao EOC5610 menggunakan bootloader yang dinamakan redboot. Ini sedikit rumit dan perlu trik karena begitu router gagal loading firmwarenya, router tidak bisa diakses. Jadi sebelum router loading firmwarenya, kita cegat dulu di bootloadernya. (macam penjahat aja ya?, pakai dicegat segala..)

Browse kesana kemari akhirnya ketemu juga tutorialnya, tapi rumit. Akhirnya setelah mencoba, aku kompilasi lagi tutorialnya menjadi seperti ini:

Ini menggunakan windows, untuk Linux ada tutorialnya di http://wiki.x-wrt.org/index.php/Kamikaze_Installation

1. Download firmware OpenWrt versi X-Wrt (tampilan web interface nya lebih baik) disini http://x-wrt.org/install.html

2. Pilih aja yang Kamikaze, cari versi terbaru.

3. Karena Senao EOC5610 menggunakan atheros, jadi pilih sub folder atheros – default (kalo udah bisa flashing, bisa coba jenis lain)

4. Anda membutuhkan 2 macam file:

- openwrt-atheros-root.squashfs ==> ini filesystemnya

- openwrt-atheros-vmlinux.lzma ==> ini kernelnya

5. Anda harus menggunakan putty, taruhlah di folder misalnya di D:\putty

6. Nah, bagaimana kalo anda merasa jagoan ngetik? ada waktu kira2

1,8 detik untuk masuk ke putty dan memasukkan perintah ^C (CTRL C) baru

anda akan masuk ke prompt dari RedBoot. Tapi bisa menggunakan cara

paling mudah ini yaitu dengan membuat script.

7. Lalu buka notepad, lalu copy script ini dan taruh di folder yang sama dengan putty (D:\putty), simpan dengan nama redboot.bat

rem echo off:startrem ————————————————

ping 192.168.1.1 -n 1 -w 1 >NUL

IF ERRORLEVEL 1 goto start

rem putty

rem ————————————————

break

putty.exe telnet://192.168.1.1:9000 -m redboot.txt

exit

8. Buka notepad lagi dan buat file dengan nama redboot.txt, Letakkan di folder yang sama dengan putty, dan redboot.bat. Isinya adalah :

^C

9. Untuk transfer image file, anda membutuhkan program kecil yang bernama tftpd. Extract di D:\tftpd. Download tftpd disini http://tftpd32.jounin.net

10. Persiapan hampir selesai.. Taruh 2 file image tadi di folder yang sama dengan putty (biar mudah saja, karena tftpd kadang komplain karena penamaan file yang terlalu panjang)

11. Atur IP komputer anda ke 192.168.1.21

12. Pasang kabel jaringan ke Senao EOC5610 dan komputer, jalankan dulu file redboot.bat, baru kemudian hidupkan router anda.

13. Beberapa detik kemudian anda akan dibawa ke shell dari redboot. Perintah berikutnya anda ketik di shell dari RedBoot. Tulisan berwarna merah adalah perintahnya, sedangkan yang berwarna biru adalah hasilnya pada shell Redboot.

RedBoot>

14. Konfigurasikan alamat IP dari RedBoot dan tftp komputer anda

RedBoot> ip_address -l 192.168.1.1 -h 192.168.1.21

15. Loading kernel dan flashing kernel

RedBoot> fis init

About to initialize [format] FLASH image system – continue (y/n)? y*** Initialize FLASH Image System… Erase from 0xbe7e0000-0xbe7f0000: .

… Program from 0×81fe0400-0×81ff0400 at 0xbe7e0000: .

RedBoot> load -r -b 0×80041000 openwrt-atheros-vmlinux.lzma

Using default protocol (TFTP)Raw file loaded 0×80041000-0×80100fff, assumed entry at 0×80041000

16. Buat image dari kernel

RedBoot>fis create -r 0×80041000 -e 0×80041000 vmlinux.bin.l7

… Erase from 0xbe030000-0xbe0f0000: …………… Program from 0×80041000-0×80101000 at 0xbe030000: …………… Erase from 0xbe7e0000-0xbe7f0000: .

… Program from 0×81fe0400-0×81ff0400 at 0xbe7e0000: .

17. Cek tempat kosong dari router

RedBoot>fis free

0xBE0F0000 .. 0xBE7E0000

Setelah itu, pakai kalkulator (windows) atau bc (Linux) , lalu hitung ini:

BE7E0000-BE0F0000

Di perangkat saya, hasilnya adalah 6F0000. Ini adalah besar kapasitas sisa.

18. Loading rootfs

RedBoot>load -r -b %{FREEMEMLO} openwrt-atheros-root.squashfs

Using default protocol (TFTP)Raw file loaded 0×80000400-0×801a03ff, assumed entry at 0×80000400

19. Buat filesistem root (rootfs). Ingat langkah ke empat, pada perangkat saya 6F0000

RedBoot>fis create -l 0×6F0000 rootfs

… Erase from 0xbe0f0000-0xbe7e0000: …………………………………………………………………………………………………… Program from 0×80000400-0×801a0400 at 0xbe0f0000: ……………………….. Erase from 0xbe7e0000-0xbe7f0000: .

… Program from 0×81fe0400-0×81ff0400 at 0xbe7e0000: .

20. Tulis bootscript ke bootloader

RedBoot> fconfig boot_script true

boot_script: Setting to true

RedBoot> fconfig boot_script_data

boot_script_data:Enter script, terminate with empty line>> fis load -l vmlinux.bin.l7

>> exec

>>

Update RedBoot non-volatile configuration – continue (y/n)? y

… Erase from 0xbe7e0000-0xbe7f0000: .

… Program from 0×81fe0400-0×81ff0400 at 0xbe7e0000: .

21. Reboot router

RedBoot> reset

Tunggu sebentar, kalo masih belum loading, cabut powernya dan nyalakan lagi.

Langkah ini bisa anda gunakan untuk flash firmware apa saja ke router yang menggunakan RedBoot. Pastikan saat flashing firmware, tidak ada gangguan listrik. Kalo sama sekali gagal masuk ke bootloader dan tidak bisa di-ping, berarti router anda rusak (bricked). Coba cari di paman Google untuk de-bricking lagi. Kalo masih gagal, ya buat aja sebagai hiasan meja.

for english version. Download upgrade firmware Senao EOC5610

ยิ่งลงยิ่งมันส์ .. ipkg จำนวนมาก, application บน x86 open-source ทั้งหลายถูก port มาเพื่อให้สามารถใช้งานได้กับ router cpu mip .. แต่น่าเสียดายพื้นที่อันจำกัดของ Flash memory ที่ storage ข้อมูลของเรา ดังนั้นจึงต้องเพิ่มกันหน่อย ..

มาทำ Compact Flash (CF) ให้เป็น Root file system กัน

รายละเอียด

usb storage : howto

boot from external media : howto

package on external media : howto

http://oldwiki.openwrt.org/OpenWrtDocs%282f%29KamikazeConfiguration%282f%29BootFromExternalMediaHowTo.html

https://forum.openwrt.org/viewtopic.php?pid=94804

http://www.nslu2-linux.org/wiki/OpenWRT/BootFromUsbDevice

Boot Configuration (Kamikaze)

Make it executable:

chmod +x /etc/init.d/pivotroot

Then install the modules, for Kamikaze 7.07 or later (Kernel 2.6), use

ipkg install kmod-fs-ext2 kmod-fs-ext3

Test to see if pivotroot works:

/etc/init.d/pivotroot
df -h

You may safely ignore errors saying “

insmod: cannot insert ...

” If pivotroot worked, then df will show that your USB storage is mounted on “/” (root). Now reboot.

reboot

after that edit /etc/init.d/rcS — แก้ใหม่ทั้ง file

#!/bin/sh
# Copyright (C) 2006 OpenWrt.org
if test $2 == "boot" ; then
/etc/init.d/pivotroot          fi
{
        for i in /etc/rc.d/$1*; do
                $i $2 2>&1
        done
} | logger -s -p 6 -t '' &

now your System should Startup nicely either from USB or from internal Flash if the USB-disk is not available.

*** ข้อสำคัญ อยู่ที่ sleep เพื่อรอให้ อุปกรณ์รับรู้ถึงการต่อ USB .. บางทีอาจต้องรอเป็น 10s
แต่เท่าที่ลอง สำหรับ kernel 2.4 ใช้เวลา(=4s) น้อยกว่า kernel 2.6
(หรือก็อาจเป็นได้ว่า Card reader ช้ากว่ากัน ??)

Technorati : openwrt, storage
Del.icio.us : openwrt, storage

สำหรับ OpenWRT รุ่น Code Name ว่า Kamikaze 8.09 นั้น สามารถเลือกที่จะติดตั้ง (Flash Firmware) ให้กับ Router ได้เลยโดยไม่จำเป็นต้อง Compile Firmware : “Image File” เองโดยสามารถ Download ได้จาก http://downloads.openwrt.org/

แต่พอประสบปัญหาเรื่อง ไม่สามารถใช้งาน Softare บางตัวที่ได้มาจากการ ipkg -> Pacage Manager ของ OpenWRT

ทำให้ตัดสินใจทดลอง Download Source Code มาแก้ไข แล้ว Compile ใหม่ .. ถึงอย่างนั้น ทำไปทำมา แค่ Source Code แท้ยัง Compile ไม่ผ่านเลย .. ทำไม ?!?

หลังจากลองผิดลองถูกอยู่นาน ทำให้ได้วิธีดังนี้ (Tip: ไม่ควร login เป็น root และเวลา make ควรใช้คำสั่ง make V=99 เพื่อตรวจสอบความผิดพลาดได้ )

การสร้าง Firmware เอง

1. ทำการ download source code ทั้ง kamikaze และ package เสริม มาไว้บนเครื่องก่อน ซึ่งจะเป็นต้องใช้คำสั่ง

svn co svn://svn.openwrt.org/openwrt/branches/8.09

svn co svn://svn.openwrt.org/openwrt/branches/8.09_package

ทั้งนี้ ได้ทำการทดลองนำ svn co svn://svn.openwrt.org/openwrt/trunk/ และ svn.openwrt.org/openwrt/packages/ มาใช้แล้วแต่ compile ไม่ผ่าน ยังหาสาเหตุไม่ได้

2. ให้เข้าไปที่ 8.09/package โดย

cd 8.09/package

3. ทำการเพิ่ม Package 8.09_package โดย Link 8.09_package ที่ได้ให้อยู่ใน directory ข้างต้น

ln -sf ../../8.09_package/*/* .

ซึ่งข้อควรระวังก็คือ ไม่ควร ln -sf ../../8.09_package . เพราะว่า ในการ compile จะประสบปัญหาว่า package บางตัวที่ต้องการ link ไป package อื่นจะหากันไม่เจอ เพราะไม่ยอมมองแบบ Hierachy

4. ที่ 8.09 directory ให้เริ่ม compile โดยทำการ config image, package ที่เลือก (ให้คำนึงถึง dependency ด้วย) ..

make menuconfig

สังเกตว่า การ collecting packages ใน 8.09/package จะสามารถทำการได้ครบถ้วนทีเดียว ถึงแม้ เราจะ ln -sf ../../8.09_package มาทั้งชั้นก็ตาม .. แต่ปัญหาจำเกิด ตามมาตอน make … ดังนั้นต้อง ln -sf ../../8.09_package/*/* เท่านั้น !!!!

แนะนำคือ ควรเลือก ให้เข้ากับ Platform ที่ใช้ เช่น Asus Premium V2 ควรใช้ .. อ่านได้จาก Net

จากนั้นเริ่มสร้าง Firmware (image) และ ipkg ทั้งหมด

make

ผลที่ได้ .. ภาวนา และข้อสำคัญคือ ต้องเชื่อมต่อ Internet เพื่อขณะ compile จะมีการ download source code เพิ่มเติมด้วย

Note

- สำหรับการ *.ipk จะอยู่ใน 8.09/bin/mipsel/package

- บาง ISP จะทำการ Block SVN port ทำให้ไม่สามารถ check out “kamikaze” ได้

อ้างอิง

http://hanez.org/openwrt-building-software-packages.html

http://wiki.openwrt.org/oldwiki/openwrtdocs/packages

http://wiki.openwrt.org/oldwiki/buildingpackageshowto

https://forum.openwrt.org/viewtopic.php?pid=31794#p31794

Mi è arrivata grazie a Michelangelo la nuova Fonera 2.0n.

Vediamo subito di cosa si tratta.

Aspetto esterno

La nuova Fonera 2.0n è cresciuta nelle dimensioni. Ora misura 16×3x10 cm , circa un 40% in più del volume della precedente Fonera 2.0 .

La porta USB è ora frontale ,  le porte lan passano da 1 a 4 e le antenne diventano 2.

Nel pannello posteriore , come si puo’ notare , è comparso un interruttore per lo spegnimento della wifi e un bottone del quale non ho capito le funzionalità . Per intuito direi che è un pulsante a doppia funzione , se premuto a lungo effettua un reset dell’unità , se premuto una volta sola attiva la funzione WPS per permettere l’accoppiamento di apparecchi wireless in autoapprendimento WPA/WPA2.

L’alimentazione è fornita da un trasformatore wall plug da 12 volts 1.0A . I consumi dovrebbero quindi essere intorno ai 10 watt.

Nella scatola non è presente la consueta patch ethernet quindi ricordatevi di averne una sottomano prima di aprire la scatola ed effettuare l’installazione altrimenti rimarrete tutta la sera a guardare i led che si accendono senza poter usare la Fonera

Specifiche Tecniche

L’hardware è basato su chip ralink RT3052F a 300 Mhz

Il chip in questione fornisce la parte AP in 802.11 b/g/n , 5 porte 10/100 switch e interfaccia per USB OTG, RGMII, SPI, PCM, I2C e UART.

A corredo troviamo un supporto di memoria ram da 64 Mb

Il sistema operativo è un openwrt kamikaze 8.09.1 pesantemente adattato da Fon , sia per la parte del consueto captive portal/heartbeat , sia per il supporto al chip Ralink , non direttamente supportato da OpenWRT.

L’interfaccia utente si raggiunge via web collegandosi attraverso la LAN cablata o la WLAN Myplace all’indirizzo 192.168.10.1 , la password di default è “admin”.

Si tratta di un’interfaccia basata sul Luci project di freifunk , già vista sulla fonera 2.0.

Di fabbrica la fonera 2.0n era flashata con il firmware 2.2.5.0 flipper enduser , la release stabile al momento in cui sto scrivendo.

Per accedere alla console in ssh ho flashato l’ultima release per sviluppatori , la 2.3.0.0 RC1 DEV che si puo’ prelevare da http://download.fonosfera.org/RC/ , scegliendo l’immagine compressa in tgz e caricandola direttamente dall’interfaccia web.

Qui la nuova fonerina mi ha subito impressionato , compiendo l’intera operazione di reflash in 3,5 minuti.

I benefici del processore assai più vispo del precedente e forse di una memoria flash più veloce sono molto evidenti .

L’interfaccia web è veloce , reattiva , intuitiva e completa , con settaggi avanzati anche per l’utente più navigato.

Ecco le schermate più significative dell’interfaccia d’amministrazione.

Welcome page

admin panel

firmware update

Configurazione Plugins (qui nella schermata Twitter plugin )

Impressioni d’uso

Il primo aggettivo  che viene in mente usando la nuova fonera 2.0n è : veloce !

Dall’accensione impiega solo 25 secondi per alzare entrambe le WLAN  , già pronte con il dhcp , il chilli per l’autenticazione e il corretto routing e firewall. E’ senza dubbio merito del nuovo processore e della dotazione di ram.

Di fabbrica la Fonera 2.0n è preimpostata con una chiave WPA di 10 caratteri piuttosto complessa ( numeri e lettere , maiuscole e minuscole ) e in modalità mista b/g/n .

Non ho potuto provare per ora le performance della wireless in draft n , in quanto non sono ancora in possesso di un’apparecchiatura wireless 802.11N , ma come per tutti i dispositivi consumer presenti sul mercato non mi aspetto di ottenere un transfer rate maggiore di 50Mbit/s . Purtroppo anche se i nuovi chip fanno progressi non sono ancora in grado di sostenere velocità maggiori.

La portata del segnale è nella norma ed è stabile ed efficace , sia sulla wlan criptata che sulla wlan pubblica.

Una delle novità introdotte dalla Fonera 2.0n è la possibilità di disabilitare completamente la parte radio tramite l’interruttore on/off posteriore oppure semplicemente escludere la wlan pubblica , trasformando la fonera in un qualsiasi router wifi consumer.

Quest’ultima caratteristica secondo me ci dice qualcosa circa la rinnovata filosofia di Fon , forse.

Se ti do la possibilità di disattivare la funzione più importante del mio dispositivo , quella inerente allo sharing fra la community , significa che la mia aspirazione è quella di diventare (anche) un produttore hardware .

E non è una cosa sbagliata, credo . Sul mercato si trovano decine di prodotti simili alla nuova fonera 2.0n  ma quasi tutti con un firmware limitato che offre poche possibilità all’utente smanettone , obbligandolo ad usare software di terze parti.

Questo dispositivo nasce con già a bordo Openwrt , sviluppato e seguito costantemente da un team di hacker di prim’ordine ed è aperto ad ogni personalizzazione. Io dico che se il prezzo retail si assesterà sui 69 euro potrebbe dare del filo da torcere ai big , Netgear e Linksys in prima fila.

Altra grossa novità sono i plugin uploader e il file sharing.

Queste funzioni però meritano una prova approfondita che mi appresto a fare nei prossimi giorni .

Mi aspetto che se messa sotto stress la fonera 2.0n cominci a fare  il fiato grosso

Staremo a vedere !

Hier nun ein paar Impressionen des Dashboards von La Fonera 2.0n.

Ich habe meinen Fonera 2.0n bekommen. Ein wunderschönes Gerät und ie Firmware ist echt ein Traum. Ich kann durch die Kiste einen kompletten Rechner abschalten. Ich schreibe die Tage ausführlich darüber. Hier noch ein Screenshot vom Dashboard.

Dashboard vom FONERA 2.0N

Okay, so if you haven’t yet, please read my last blog post.

Twitter has this great API that makes it super easy to “tweet” (I can’t believe I just used the word tweet). The coolest thing is, you hardly need any extra software, which is a huge plus, especially on the Ubiquiti Nanostation which only has 16 MB of RAM and 4 MB of flash. I read this great guide that uses cURL. Unfortunately, when I tried to install cURL on my Ubiquiti, opkg tried to install a couple MB to my flash; way too much. Curl was not feasible given my limited hardware.

Fortunately, there’s a smaller program that can accomplish the same thing: wget. OpenWRT already has wget installed, but it’s a smaller version of wget that doesn’t have everything we need (it’s actually part of BusyBox).

Now, one of the reasons that cURL is so large is because it wants SSL. We don’t need that, so we can install the package wget-nossl.

root@OpenWrt:~# opkg install wget-nossl -force-overwrite

The -force-overwrite is required or it’ll complain that wget is already installed:

* Package wget-nossl wants to install file /usr/bin/wget
But that file is already provided by package * busybox

Anyway, once we’ve got wget installed, we can post a message to Twitter like this:

wget --http-user=wifispaught --http-password=password --post-data=status="test!" http://twitter.com/statuses/update.xml

Now let’s see if we can’t add a Spot to the mix.

StreamConnection serialStream = (StreamConnection) Connector.open("edemoserial://usart?baudrate=9600&databits=8&stopbits=1&parity=none");
OutputStream out = serialStream.openOutputStream();
out.write(("wget --http-user=wifispaught --http-password=mypassword --post-data=status=\"Hello, world!\" http://twitter.com/statuses/update.xml\n").getBytes());

Okay, we need some code to run on the Ubiquiti side of things:

root@OpenWrt:~# head -n 1 /dev/ttyS0 | ash

This will read a line off of the serial connection (ttyS0), and then pipe the output into ash (a simple shell included with BusyBox). Since the SunSPOT is sending the wget command, there’s no need to do any parsing or logic.

Now I’ve got a SunSPOT posting to Twitter via wifi.

If you’re interested, here’s the twitter feed of the spot.

En la página del grupo LUGRo-Mesh se encuentran disponibles las pruebas realizadas sobre una serie de nodos que ya están operativos y prestando servicios.

Hemos podido comprobar de manera fehaciente el desempeño del firmware Nightwing en condiciones reales.

Según nuestras estadísticas, desde el 13 de junio al 13 de Julio se ha filtrado el acceso, a los usuarios de la Red LUGRo-Mesh , de más de 2.200 sitio de Malware.

Mediante políticas de filtrado y la utilización de OpenDNS , se ha impedido que los usuarios que utilizan la Red LUGRo-Mesh, para el acceso a Internet, puedan ser infectados por posible Malware proveniente de más 2.213 sitios los cuales han sido bloqueados.

La Red LUGRo-Mesh posee, al día de hoy, más de 100 usuarios y 7 hostpots operativos en la ciudad utilizando el firmware Nightwing. Se espera llegar a 10 a fín del mes de Julio.

En promedio se han agregado más de 30 usuarios por mes.

I recently switched some of my domains to Joker.com. One of the nice things Joker has is capability to dynamically update DNS records.  I was going to use ez-ipupdate, but my OpenWRT router did not have enough free memory to install the package.

It rummaging through FAQ on Joker website it turns out I can update entries using wget in a cron job as well. All it takes is to set up cron entry that looks something like this:

0 * * * * wget "http://svc.joker.com/nic/update?username=BLAH&password=BLAH&hostname=myhost.example.com" > /dev/null 2>&1

Username and password are supplied by Joker when setting up DDNS.

Oggi scrivo per tutti gli sfortunati possessori di questo fantastico router ADSL, ebbene sì! Vi illustrerò come salvare gli € spesi per questo baracchino, cambiando il firmware (quello originale è pessimo e buggato) e risolvendo il problema del surriscaldamento che causa i frequenti blocchi riscontrati soprattutto in condizioni di alto carico di rete.

Ecco come si presenta la cavia, prima di diventare il frankenstein informatico di turno...

La procedura non richiede di aprire il router, ed è relativamente facile. Per installare OpenWrt bisognerà modificare le partizioni della flash, tramite il server FTP modificato del bootloader ADAM2. In caso voleste ripristinare il vecchio firmware, dovrete ripartizionare la flash coi valori originari (che io non mi sono segnato! ma sono facilmente individuabili nel programma CICLaMaB) per poi ricaricare l’immagine del firmware D-Link. Detto questo passiamo ai fatti!

Analisi tecnica

Questa etichetta riporta modello e revisione su cui ho fatto i miei esperimenti

System-on-a-Chip:

Modello: Texas Instruments AR7 TNETD7300
Processore: MIPS 4KEc 32-Bit RISC @150MHz

RAM:

Modello: Hynix HY57V281620
Capacità: 16MB

Flash:

Modello: Spansion S29AL032090
Capacità: 4MB

Switch:

Modello: Infineon ADM6996M

Ecco i vari componenti principali

Immagine OpenWrt

Per riflashare l’apparato avrete bisogno dell’immagine dell’ultima versione di OpenWrt (attualmente la 8.09.1) che potete trovare qui:
http://downloads.openwrt.org/kamikaze/8.09.1/ar7/openwrt-ar7-squashfs.bin

In ogni caso, se avete un po’ di dimestichezza vi consiglio di compilarvi la vostra immagine custom, scaricandovi l’ultima revision del trunk e includendo i pacchetti che vi servono. In questo modo i pacchetti rientreranno nella partizione compressa sola lettura squashfs e risparmierete spazio… installandoli in un secondo momento con opkg andrete a consumare memoria preziosa sulla partizione scrivibile jffs2!

Io ho preferito farmi la mia personalizzata, e ci ho incluso i pacchetti per il client DNS dinamico, il client NTP e l’interfaccia web X-Wrt. Per farlo, dovrete dare questi comandi nella directory in cui compilate OpenWrt:

scripts/feeds install updatedd
scripts/feeds install ddns-scripts
scripts/feeds install ntpclient
scripts/feeds install webif

E poi selezionarli (con l’asterisco) nel menu di configurazione per poi lanciare la compilazione vera e propria:

make menuconfig
make world -j3

L’opzione -j3 è molto utile se avete un processore multi-core o multi-threaded. In caso contrario non utilizzatela.

La console FTP di ADAM2

Prima di cominciare ricordatevi di non toccare la partizione mtd2, in quanto contiene il bootloader ADAM2 stesso… se lo toccaste rischiereste di rendere il vostro router non avviabile, richiedendo un ripristino via cavo JTAG. Uomo avvisato…!
Per modificare le partizioni della flash e scriverla, vi occorrerà stabilire una connessione FTP all’indirizzo IP del bootloader. Il nostro D-Link DSL-524T all’accensione rimane in ascolto per qualche secondo sull’indirizzo 5.8.8.8, prima di avviare il sistema operativo.
Bene, detto ciò, modificate l’indirizzo del vostro PC e impostateci qualcosa tipo 5.8.8.9/24 giusto per trovarvi nella stessa subnet. Ora con una console posizionatevi nella cartella dove avete salvato l’immagine del firmware. Avviate il router e due/tre secondi dopo lanciate il comando:

ftp 5.8.8.8

A questo punto, se è andato tutto bene vi verrà chiesto di inserire l’username e la password che sono entrambi adam2. In caso contrario, riavviate il router e riprovate a connettervi!

Ripartizionare

Una volta in console, dovremo inserire qualche comando per ottenere la seguente tabella di partizioni:

Per farlo, digitate i seguenti comandi:

quote "SETENV mtd0,0x90086B80,0x903f0000" (fs)
quote "SETENV mtd1,0x90010000,0x90086B80" (kernel)
quote "SETENV mtd4,0x90010000,0x903f0000" (fs+kernel)

Flashare

Ora la tabella di partizioni è pronta.  Potete scrivere l’immagine di OpenWrt con:

quote "MEDIA FLSH"
binary
debug
hash
put "openwrt-ar7-squashfs.bin" "c mtd4"
quote REBOOT
quit

Se non vi restituisce codici di errore avete finito… Altrimenti in caso di errore strambo (a me ha dato un codice 550, che mi ha impedito di caricare il file sulla partizione mtd4) provate ad usare il software CICLaMaB: basta inserirci l’indirizzo del bootloader e il path del file immagine “unico” che volete scrivere e premere il tasto “connetti”. A questo punto modificate le partizioni con il tasto apposito in modo da rispecchiare i valori riportati nella tabella in alto (forse c’è anche un preset chiamato “OpenWrt AR7 Port” che dovrebbe avere dei buoni valori) e infine premete il tasto per flashare il router. Non preoccupatevi se vi da errore al comando “quote REBOOT”, nonostante questa notifica tutto è andato come doveva.
Ora aspettate qualche minuto, l’unità si riavvierà e da subito noterete che il led status lampeggia in modo diverso da prima: durante il boot in modo veloce e, una volta avviato, lampeggia in stile heartbeat.

Primo avvio di OpenWrt

Ora manca solo la parte più semplice!
Eseguite l’accesso in telnet e configurate la vostra password col comando passwd. Ora chiudete la connessione telnet e riapritene una ssh ed eseguite le modifiche ai file di configurazione!

Configurazione networking e ADSL

Per configurare il modem col protocollo PPPoE ed incapsulamento LLC, fate in modo che il vostro file /etc/config/network somigli a quello riportato qui:

root@DSL-524T:~# cat /etc/config/network 

config 'interface' 'loopback'
    option 'ifname' 'lo'
    option 'proto' 'static'
    option 'ipaddr' '127.0.0.1'
    option 'netmask' '255.0.0.0'

config 'interface' 'lan'
    option 'type' 'bridge'
    option 'ifname' 'eth0'
    option 'proto' 'static'
    option 'netmask' '255.255.255.0'
    option 'nat' '1'
    option 'ipaddr' '192.168.1.1'
    option 'macaddr' ''
    option 'ip6addr' ''
    option 'gateway' ''
    option 'ip6gw' ''
    option 'dns' ''

config atm-bridge
    option unit     0
    option encaps   llc
    option vpi      8
    option vci      35

config interface wan
    option ifname   nas0
    option proto    pppoe
    option username aliceadsl
    option password aliceadsl

Avvio automatico connessione ADSL

Per far sì che il modem si connetta automaticamente all’avvio, dovete fare una piccola modifica al fie /etc/init.d/network. Sostituite all’interno della funzione boot() l’ultima istruzione: al posto di /sbin/wifi up scrivete start.
Dovrebbe risultare qualcosa del genere:

boot() {
    ...
    setup_switch
    [ -s /etc/config/wireless ] || \
        /sbin/wifi detect > /etc/config/wireless
    start
}

Ora salvate e riavviate. Una volta che il led status è in heartbeat e il led ADSL è acceso fisso provate a pingare un indirizzo internet… se ottenete risposta avete finito… altrimenti… ricontrollate i file di configurazione!

Interfaccia Web X-Wrt

Per qualsiasi altra configurazione, potete affidarvi all’interfaccia X-Wrt. Inserite nel browser l’idirizzo IP del vostro router, alla richiesta di username inserite root e come password quella che avete impostato col comando passwd alla prima connessione telnet. L’interfaccia è molto intuitiva, se siete arrivati fin qui non c’è bisogno che ve la spieghi!!!

Dissipatore per la CPU

Per abbassare le temperature della calorosa CPU, ho recuperato un dissipatore da un transistor MOSFET e l’ho appiccicato con una goccia di colla e 2 strisce di pasta termoconduttiva al SoC. Avevo notato che anche lo switch ADM6996M scaldava, ma ho deciso di non aggiungerci un dissipatore… probabilmente questo componente è costruito con un processo produttivo meno recente e di dimensioni maggiori, per cui dovrebbe risentire meno del calore.

Vi riporto un paio di foto del piccolo mod effettuato al router:

La CPU con colla e pasta termoconduttiva

Ecco la CPU con il dissipatore applicato

LED Mod

Dato che i LED verdi del router sono invisibili di giorno, ma soprattutto dalla postazione dove mi trovo di solito, ho provveduto a dissaldare il LED di status e a sostituirlo con uno ad alta luminosità azzurro, recuperato da una RB411 colpita da un fulmine… l’effetto finale è ottimo!

Il nuovo led status azzurro, ora suffiicentemente visibile anche di giorno!

Stanotte controllerò se è troppo luminoso o se mi permette di dormire!

Bibliografia

1. La pagina di Linux MIPS su TI AR7
2. La pagina OpenWrt OldWiki dedicata al DSL-524T
3. CICLaMaB Che Iddio Ce La Mandi Buona

I have a Linksys WRT54GL router at home. I had DD-WRT installed on it, and used it as a home wireless access point, router and IPv6 6to4 gateway. So far it was working flawlessly, until I changed my ISP to Sunrise.

After the switch, I started having a weird PPPoE related issue where the router would redial the connection every 30 minutes. There was no elegant solution available, and the unelegant solution wasn’t good enough.

I decided to be a macho and install OpenWRT. I’ve read on the Internet that I should be prepared to spend some time configuring it manually without expecting a good web interface.

It was a very pleasant surprise to find a very nice web administration interface, not as nice as DD-WRT, but it allowed me to configure more aspects of the router behavior. PPPoE with Sunrise just works, and the OpenWRT distribution feels more like a full-blown desktop/server distribution, with package management and all. I just love it.

• Comunidades Wireless:
  

Ile Sans Fil

Lugro-Mesh

Rosario Argentina

• OpenWrt:

http://openwrt.org/

• WifiDog:

• http://dev.wifidog.org/

• Implementación de puntos de acceso gratuito WiFi utilizando Software Libre:

Documentación

• Mesh Networking:

http://en.wikipedia.org/wiki/Mesh_networking

• The Public Wireless Internet Project

Awesome post title… anyway,

This is how I built a powerful Wi-Fi ADSL router, using my ALIX2D3 (previously running PFsense), a spare USB ADSL modem (Trust MD-3100) and a CM9 atheros-based miniPCI card.

Requirements

• ADSL modem (Conexant based for this howto)
• Average Linux knowledge
• vi editor familiarity
• USB CF card reader

Installing OpenWrt on CF card for ALIX boards

Boot your favourite Linux distribution. If you don’t have one try Ubuntu LiveCD: it loads in RAM and leave you data untouched.
Plug your CF card in your USB CF reader, and plug it in your USB connector. If your CF card isn’t formatted, your Linux may auto-mount the card’s partitions; if so, unmount them.
Type in terminal as root (may need su or sudo command):

fdisk -l

In the list of disks shown, identify your CF card and write down its name, the device size should help you (tip: assuming /dev/sda as your first sata disk, CF card should be named /dev/sdb).
Now download from here the 8.09.1 (lastest at the time of writing) version of OpenWrt x86 image.
All we need to do now, is to copy the image over the CF card.
WARNING: if you use the wrong device name for the next command, you may wipe out all your hard disk data.
Assuming your CF card device name /dev/sdX type this:

dd if=openwrt-x86-ext2.image of=/dev/sdX

Wait some time, and the command should end printing a report of written blocks. Now start GParted or your favourite partition editor, and grow the ext2 partition of your card up to fill the empty space.

Installing LuCI or X-Wrt web interface

OK, it is pretty useless for what we’re doing, but with a 1GB CF card, why not waste some space for a cool web interface??? Choose one of the following:

#1 LuCI:

opkg update
opkg install luci-admin-full

And then add all the luci-app-*** packages you want to simplify your applications management.

#2 X-Wrt:

echo "src X-Wrt http://downloads.x-wrt.org/xwrt/kamikaze/8.09/x86/packages" >> /etc/opkg.conf
opkg update
opkg remove -recursive luci-* //NOTE: only if you have previously installed LuCI
opkg install webif

Configuring ADSL modem

Install needed USB kernel modules:

opkg update
opkg install kmod-usb-atm-cxacru kmod-usb2 kmod-usb-uhci

Download and put the ADSL modem firmware (cxacru-fw.bin) in /lib/firmware/.
Plug in the USB modem, and type:

dmesg | tail

Keep checking the output of this command, until you’ll get the “ADSL Line: up” state:

cxacru 1-1:1.0: receive of cm 0x90 failed (-104)
cxacru 1-1:1.0: found firmware cxacru-fw.bin
ATM dev 0: ADSL state: stopped
ATM dev 0: ADSL line: down
ATM dev 0: ADSL state: running
ATM dev 0: ADSL line: initializing
ATM dev 0: ADSL line: down
ATM dev 0: ADSL line: attempting to activate
ATM dev 0: ADSL line: down
ATM dev 0: ADSL line: attempting to activate
ATM dev 0: ADSL line: training
ATM dev 0: ADSL line: attempting to activate
ATM dev 0: ADSL line: training
ATM dev 0: ADSL line: channel analysis
ATM dev 0: ADSL line: up (7584 kb/s down | 480 kb/s up)

Configuring WAN interface

Now we’ll set up the WAN using the ppp0 interface that will be created by pppd.
The following configuration works for my ISP (Telecom Italia) edit it with your ISP parametes.

uci set network.wan=interface
uci set network.wan.proto=pppoa
uci set network.wan.ifname=ppp0
uci set network.wan.encaps=vc
uci set network.wan.vpi=8
uci set network.wan.vci=35
uci set network.wan.username=aliceadsl
uci set network.wan.password=aliceadsl
uci set network.wan.peerdns=1
uci commit network
/etc/init.d/network restart

Now the ppp0 interface should come up and you’ll be able to reach internet.

ADSL sync wait script

The only problem is that on startup, before upping the WAN interface, the system must wait for the ADSL line to come up. I solved this problem with this simple script that start on boot, wait for ADSL sync and then restart the OpenWrt network. It is a modified version of the one you find in Reference #2 at the bottom of this post.
Create the file /etc/init.d/adsl and paste this script in it:

#!/bin/sh /etc/rc.common
# ADSL start script

START=98

boot() {
 exsist=0
 sync=0
 until [[ -e /proc/net/atm/cxacru\:0 ]]
 do
 if [[ $exsist = '0' ]]
 then
 echo "InitAdsl Waiting cxacru.fw loading"
 exsist=1
 fi
 done
 echo "InitAdsl Firmware loaded"
 end=0
 while [[ $end = '0' ]]
 do
 if [[ $sync = '0' ]]
 then
 echo "InitAdsl Waiting sync"
 sync=1
 fi
 if [[ `grep Line /proc/net/atm/cxacru\\:0 | cut -d' ' -f2` = 'up' ]]
 then
 end=1
 /etc/init.d/network restart
 echo "InitAdsl Sync done"
 fi
 done
}

Save the file and type on terminal:

/etc/init.d/adsl enable

Now reboot your router. Everything should work automagically. My router in 3 minutes is connected and providing natted internet service to the dhcp clients.

Configuring wireless interface

TODO!

References

1. LuCI Reference
2. Modem sync wait script from MandrakeItalia.org
3. Various infos taken from Paolo Minazzi’s page
4. PC Engines’ ALIX boars

Desde que se hizo el llamado para incorporar nodos a la red Lugro-Mesh ya son 8 los nuevos nodos que están programados en la ciudad de Rosario.
Nos pone muy contentos que existan personas que piensan como nosotros sobre la importancia del acceso a la información y que quieran participar de un proyecto tan ambicioso como el que tenemos. Lograr que Rosario tenga acceso libre a Internet en cada rincón.

El desarrollo del firmware Nightwing nos está permitiendo contar con una base solida para formar la red de equipos que servirán de soporte para la red.
Esperemos poder seguir sumando gente y nodos. Mientras, el mapa de Rosario ya empieza a tener más actividad.

Install smartmontools from the repository.

thinkpad:~# aptitude install smartmontools

Enable SMART monitoring on the SATA drive.

thinkpad:~# smartctl -s on  -d ata /dev/sda

Check the health of the drive.

thinkpad:~# smartctl -d ata -H /dev/sda
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

Run a short self test on the drive and check the test log.

thinkpad:~# smartctl -t short /dev/sda
thinkpad:~# smartctl -l selftest /dev/sda
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%      4156         -

In order to configure smartd to monitor the hard disk, enable it in /etc/default/smartmontools.

# uncomment to start smartd on system startup
start_smartd=yes

Set the schedule and monitoring options by editing /etc/smartd.conf. Comment out all the DEVICESCAN lines and add a line for the main hard drive.

# First (primary) ATA/IDE hard disk.  Monitor all attributes, enable
# automatic online data collection, automatic Attribute autosave, and
# start a short self-test every day between 2-3am, and a long self test
# Saturdays between 3-4am. Send mail on SMART failures
/dev/sda -a -o on -S on -s (S/../.././02|L/../../6/03) -m naveen@localhost

Start the smart daemon.

thinkpad:~# /etc/init.d/smartmontools restart
 * Restarting S.M.A.R.T. daemon smartd                        [ OK ]