Configurazione Router Pirelli Drg A226m Fastweb
To have a better match with DRG A226M functions, I suggest you to use it with the following network configuration. Using the interneal editor vi, check and edit /etc/config/system file. For more info read switch config.
Configurare Router Fastweb Pirelli Drg A226m
You need to setup a tftp server on some host (I can suggest to use dnsmasq for this) to serve the firmware image to the router. Now just download the image for A226M from You have firmwares for two filesystems (squashfs and jffs2) squashfs is a filesytem that have system files readonly. More stable and less problems. You cannot destroy importan file jffs2 is a file system completly writable. More powerfull but you can destroy system files.
Accesso Router Fastweb
To start as novice I sugegst to use squasfs firmwares. Skip the jffs2 with 64k erase block as the flash use 128k block, anyway using 64k should not give much problem, just some wasted space and some errors messages. Put the chosen image in the right place (see your tftp server configuration), and go to the CFE prompt. I suggest to rename the firmware file downloaded as firmware.bin Now you have to use the flashimage command to load the openwrt image, please don't use the f command. If you configure (with command c) the host ip address you can avoid it in the flashimage argument. CFE flashimage eg.
Flashimage hostip:compressedimagefilename or es: flashimage 192.168.1.100:firmware.bin or es: flashimage firmware.bin That's all, the device will automatically reboot and openwrt will be there Using dnsmasq: dnsmasq -d -enable-tftp -tftp-root=`pwd` -p 0 #fron the directory where firmware is previously downloaded where the 192.168.1.100 is your server tftp After the flashing of new firmware the router will reboot. You can use also TFTP server like tftp32.
Install tftpd32 and put the firmware file (I suggest to rename it as firmware.bin) in the same folder where you installed tftpd32. OpenWrt - First boot. ATM (24 jan 2013) the OpenWrt image is rejected due to wrong CRC in kernel Is this still true today? If this is solved, please update this page accordingly. — tmomas 2015/09/30 15:30 Boot detail with crc error:. Press any key to stop auto run (1 seconds).
Auto run second count down: 0 Trying to boot from previous MAIN image (0x65dba394). Code Address: 0x65DBA394, Entry Address: 0x1970acf7 SGP - Flash Kernel Address: 0xBE020100 SGP - ulImgCrc: 0xD656A53B SGP - Tag-kernelLen: 0x0011FF00 SGP - Flash Kernel Address: 0xBE020100 Linux kernel CRC error. Corrupted image? SGP - Tag Kernel crc: 0xD656A53B - calculated: 0x9D91518A SGP - Decompression Kernel length: 0x91669AEE pucSrc: 0xBE02010C Trying to boot from previous RECOVERY image (0x80010000). Code Address: 0x80010000, Entry Address: 0x80010000 SGP - Flash Kernel Address: 0xBE560100 SGP - ulImgCrc: 0x80DF5773 SGP - Tag-kernelLen: 0x001B008C SGP - Flash Kernel Address: 0xBE560100 SGP - Tag Kernel crc: 0x80DF5773 - calculated: 0x80DF5773 SGP - Decompression Kernel length: 0x0000001C pucSrc: 0xBE56010C Decompression OK!
Entry at 0x80010000 If you receive this error with the test file: openwrt-A226G-cfe-squashfs-cfe.bin I had also prevents this problem and I solved it with this. To have a better match with DRG A226M functions, I suggest you to use it with the following network configuration.
Using the interneal editor vi, check and edit /etc/config/system file. For more info read config. CFE version 1.0.37-8.7 for BCM96358 (32bit,SP,BE) Build Date: lun apr 2 10:48:55 CEST 2007 (gpaolo@buildserver) Copyright (C) 2000-2005 Broadcom Corporation. Boot Address 0xbe000000 Initializing Arena. Initializing Devices. Parallel flash device: name AM29LV320MT, id 0x2201, size 8192KB CPU type 0x2A010: 300MHz, Bus: 133MHz, Ref: 64MHz CPU running TP0 Total memory: 33554432 bytes (32MB) Total memory used by CFE: 0x80401000 - 0x80527ED0 (1208016) Initialized Data: 0x8041D940 - 0x8041F700 (7616) BSS Area: 0x8041F700 - 0x80425ED0 (26576) Local Heap: 0x80425ED0 - 0x80525ED0 (1048576) Stack Area: 0x80525ED0 - 0x80527ED0 (8192) Text (code) segment: 0x80401000 - 0x8041D938 (117048) Boot area (physical): 0x00528000 - 0x00568000 Relocation Factor: I:00000000 - D:00000000 Resetting Secondary CPU.
Board IP address: 192.168.1.1:ffffff00 Host IP address: 192.168.1.100 Gateway IP address: Run from flash/host (f/h): f Default host run file name: vmlinux Default host flash file name: bcm963xxfskernel Boot delay (0-9 seconds): 1 Boot image (0=latest, 1=previous): 0 Board Id (0-6): DWV-S0 Number of MAC Addresses (1-32): 13 Base MAC Address: 02:10:18:xxxxxxxxx PSI Size (1-64) KBytes: 24 Main Thread Number 0 1: 0. Press any key to stop auto run (1 seconds).
Auto run second count down: 1 web info: Waiting for connection on socket 0. CFE VoIP on FXS ports. A226m has a Le88266 VoIP chip onboard providing 2x FXS ports (= 2x ports you can connect analog phones to in order to make calls leveraging VoIP). This functionality is not natively available in OpenWrt, it requires additional drivers. There is an opensource project, called bcm63xx-phone, providing these drivers, and I managed to compile and make it work on this router in combination with Asterisk, tested on both Attitude Adjustment and Barrier Breaker. The developer of the driver directly tested it on a Huawei box, but it also works on A226M. There is no ipk package available at the moment, so you need to compile your own.ipk's package or include them in the image of openwrt.
Once you do this, you will be able to connect an analog phone to the FXS ports and leverage it in combination with a cheap VoIP service provider. If you choose to compile the.ipk's and try to install them on a ready-available openwrt image form repository, be aware that opkg might complain about kernel version not being exaclty the same. Just force installation and it should work. I was able to make phone calls originating from an analog phone connected to the A226M and routed to a VoIP provider using SIP signalling and Asterisk as call manager.