[Ninux-Wireless] Map server link fantasma!
Weila' Mi sto rendendo conto che il map server disegna dei link che non esistono, piu' di quanto immaginassimo... attualmente il server di pisa e' down da ieri pomerigio ma quardando pisa.ninux.org ho visto cambiare lo status dei link diverse volte... come se recuperasse le info da qualche parte ma questo e' impossibile, quindi quei link che disegna sono fantasma ___ Wireless mailing list Wireless@ml.ninux.org http://ml.ninux.org/mailman/listinfo/wireless
[Ninux-Wireless] Fwd: [OpenWrt-Devel] Adding support to a BCM96348 device
Ciao Marco, ciao tutti questa mail spiega come integrare una nuovo router dentro openwrt. E' proprio la domanada a cui spesso capita di rispondere, non ultimo Marco ieri sera. Riporto la mail centrale ma vi consiglio di seguire tutto il trhead. -- Forwarded message -- From: Roger Hardiman ro...@rjh.org.uk Date: 2011/4/2 Subject: Re: [OpenWrt-Devel] Adding support to a BCM96348 device To: OpenWrt Development List openwrt-de...@lists.openwrt.org, carba...@upv.es Carlos, I think you will need to make two changes to OpenWRT to make your board work. I will explain the changes to the source code that will need to be made at the end of the email. However for now there is an easy thing you can do. 1) keep your board set to the board name of 96348GW-10 2) flash the firmware from CFE 3) once the firmware is booted and you have the linux shell, type in this command mtd fix This re-calculates the checksum and stores it in the flash memory. This should then mean that when you next reboot, CFE will not have a checksum error. To make the board supported by OpenWRT all the time, three things are needed 1) the file target/linux/brcm63xx/base-files/etc/uci-defaults/brcm63xx_fixcrc.sh needs to be modified. This file runs once, when the router first boots after flashing firmware. The script then gets erased so it only runs once. You need to change this line bcm63xx/CPVA642 * | bcm63xx/MAGIC *) to say this bcm63xx/CPVA642 * | bcm63xx/MAGIC * | bcm63xx/CPVA502+ * ) 2) in the Linux kernel source is this file arch/mips/bcm63xx/boards/board_bcm963xx.c For testing, you need to edit this file and add in a new board_id. Look for how the 96348GW-10 is defined and copy and paste. The board_name needs to become CPVA502+. Everything else can stay the same. You can then re-compile OpenWRT and test this change. 3) if everything works we need to make a patch file for the change to board_bcm963xx.c and add this to the OpenWRT target source tree so that everyone else building openWRT will get the linux kernel patched with the new board_id. Let me know if you need any help. I’ve just done all these steps for the BT Voyager 2500V (RTA1046) router including the mtd fix Roger -- Roger Hardiman Technical Consultant Optimum Security Services Ltd Mobile 07968 245759 Office 0870 350 2171 Email roger.hardi...@optimum.me.uk -Original Message- From: openwrt-devel-boun...@lists.openwrt.org [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Carlos Baiget Sent: 01 April 2011 20:40 To: OpenWrt Development List Subject: Re: [OpenWrt-Devel] Adding support to a BCM96348 device Hello All, Without really knowing what I was doing, I changed the board id. in CFE from CPVA502+ (default) to 96348GW-10 and OpenWrt booted (openwrt-96348GW-generic-squashfs-cfe.bin from 10.03.1-rc4) At first I had access only from serial console, but after bringing down the br-lan device and giving a valid ip address to eth0 I could connect to LuCI, enable wifi, etc. Problem: After reboot, CRC for image a partition [1] is bad and CFE erases it. (dump below) So most of the hardware is supported by OpenWrt but seems like it is neccesary to create some kind of profile for the particularities of CPVA502+ (original board id). Please could someone point me if i'm on a good path and how I should try to do that? Thank you, Carlos 1-CFE dump after reboot: CFE version 1.0.37-3.6 for BCM96348 (32bit,SP,BE) Build Date: ven lug 21 09:44:42 CEST 2006 (oli...@oliale.telsey.loc) Copyright (C) 2003,2004,2005 Telsey Telecommunications. Boot Address 0xbfc0 Initializing Arena. Initializing Devices. Parallel flash device: name MX29LV320AT, id 0x22a7, size 4096KB 100 MB Full-Duplex (auto-neg) Check consistency for image tag [1]: Image CRC failed. Corrupted image at partition [1]? Calculated CRC 0x5cfa39cb. TAG CRC 0x2722a5a9. Image length 2686724. Erasing tag at partition [1] address 0xbfc1! . Check consistency for image tag [2]: No image found at partition [2] ** Image information not found. ** CPU type 0x29107: 256MHz, Bus: 128MHz, Ref: 32MHz Total memory: 16777216 bytes (16MB) Total memory used by CFE: 0x80401000 - 0x80526FA0 (1204128) Initialized Data: 0x8041E610 - 0x80420480 (7792) BSS Area: 0x80420480 - 0x80424FA0 (19232) Local Heap: 0x80424FA0 - 0x80524FA0 (1048576) Stack Area: 0x80524FA0 - 0x80526FA0 (8192) Text (code) segment: 0x80401000 - 0x8041E60C (120332) Boot area (physical): 0x00527000 - 0x00567000 Relocation Factor: I: - D: Board IP address : 192.168.1.1:ff00 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 : bcm963xx_fs_kernel Boot delay (0-9 seconds) : 1 Board Id Name : 96348GW-10 Psi size in KB : 24 Number of MAC Addresses (1-32) : 8 Base MAC Address : 00:30:ab:00:00:01 Ethernet PHY Type :
Re: [Ninux-Wireless] Fwd: [OpenWrt-Devel] Adding support to a BCM96348 device
OT. ma se un router (netgear) non è presente nella lista... ci sono altre alternative? On 04/06/11 11:11, Claudio wrote: Ciao Marco, ciao tutti questa mail spiega come integrare una nuovo router dentro openwrt. E' proprio la domanada a cui spesso capita di rispondere, non ultimo Marco ieri sera. Riporto la mail centrale ma vi consiglio di seguire tutto il trhead. -- Forwarded message -- From: Roger Hardimanro...@rjh.org.uk Date: 2011/4/2 Subject: Re: [OpenWrt-Devel] Adding support to a BCM96348 device To: OpenWrt Development Listopenwrt-de...@lists.openwrt.org, carba...@upv.es Carlos, I think you will need to make two changes to OpenWRT to make your board work. I will explain the changes to the source code that will need to be made at the end of the email. However for now there is an easy thing you can do. 1) keep your board set to the board name of 96348GW-10 2) flash the firmware from CFE 3) once the firmware is booted and you have the linux shell, type in this command mtd fix This re-calculates the checksum and stores it in the flash memory. This should then mean that when you next reboot, CFE will not have a checksum error. To make the board supported by OpenWRT all the time, three things are needed 1) the file target/linux/brcm63xx/base-files/etc/uci-defaults/brcm63xx_fixcrc.sh needs to be modified. This file runs once, when the router first boots after flashing firmware. The script then gets erased so it only runs once. You need to change this line bcm63xx/CPVA642 * | bcm63xx/MAGIC *) to say this bcm63xx/CPVA642 * | bcm63xx/MAGIC * | bcm63xx/CPVA502+ * ) 2) in the Linux kernel source is this file arch/mips/bcm63xx/boards/board_bcm963xx.c For testing, you need to edit this file and add in a new board_id. Look for how the 96348GW-10 is defined and copy and paste. The board_name needs to become CPVA502+. Everything else can stay the same. You can then re-compile OpenWRT and test this change. 3) if everything works we need to make a patch file for the change to board_bcm963xx.c and add this to the OpenWRT target source tree so that everyone else building openWRT will get the linux kernel patched with the new board_id. Let me know if you need any help. I’ve just done all these steps for the BT Voyager 2500V (RTA1046) router including the mtd fix Roger -- Roger Hardiman Technical Consultant Optimum Security Services Ltd Mobile 07968 245759 Office 0870 350 2171 Email roger.hardi...@optimum.me.uk -Original Message- From: openwrt-devel-boun...@lists.openwrt.org [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Carlos Baiget Sent: 01 April 2011 20:40 To: OpenWrt Development List Subject: Re: [OpenWrt-Devel] Adding support to a BCM96348 device Hello All, Without really knowing what I was doing, I changed the board id. in CFE from CPVA502+ (default) to 96348GW-10 and OpenWrt booted (openwrt-96348GW-generic-squashfs-cfe.bin from 10.03.1-rc4) At first I had access only from serial console, but after bringing down the br-lan device and giving a valid ip address to eth0 I could connect to LuCI, enable wifi, etc. Problem: After reboot, CRC for image a partition [1] is bad and CFE erases it. (dump below) So most of the hardware is supported by OpenWrt but seems like it is neccesary to create some kind of profile for the particularities of CPVA502+ (original board id). Please could someone point me if i'm on a good path and how I should try to do that? Thank you, Carlos 1-CFE dump after reboot: CFE version 1.0.37-3.6 for BCM96348 (32bit,SP,BE) Build Date: ven lug 21 09:44:42 CEST 2006 (oli...@oliale.telsey.loc) Copyright (C) 2003,2004,2005 Telsey Telecommunications. Boot Address 0xbfc0 Initializing Arena. Initializing Devices. Parallel flash device: name MX29LV320AT, id 0x22a7, size 4096KB 100 MB Full-Duplex (auto-neg) Check consistency for image tag [1]: Image CRC failed. Corrupted image at partition [1]? Calculated CRC 0x5cfa39cb. TAG CRC 0x2722a5a9. Image length 2686724. Erasing tag at partition [1] address 0xbfc1! . Check consistency for image tag [2]: No image found at partition [2] ** Image information not found. ** CPU type 0x29107: 256MHz, Bus: 128MHz, Ref: 32MHz Total memory: 16777216 bytes (16MB) Total memory used by CFE: 0x80401000 - 0x80526FA0 (1204128) Initialized Data: 0x8041E610 - 0x80420480 (7792) BSS Area: 0x80420480 - 0x80424FA0 (19232) Local Heap: 0x80424FA0 - 0x80524FA0 (1048576) Stack Area: 0x80524FA0 - 0x80526FA0 (8192) Text (code) segment: 0x80401000 - 0x8041E60C (120332) Boot area (physical): 0x00527000 - 0x00567000 Relocation Factor: I: - D: Board IP address : 192.168.1.1:ff00 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 : bcm963xx_fs_kernel Boot delay (0-9 seconds) : 1 Board Id Name :
[Ninux-Wireless] Dinamic routing con olsr
Salve a tutti,
mi presento, sono Vincenzo dell'Hacklab Cosenza e vi lurko da tempo.
Qui stiamo lavorando ad una rete Ninux che attualmente è in fase
pre-alpha, ovvero di studio e cercare di capire come funziona.
Vado alla questione.
Abbiamo configurato 3 router Linksys WRT54GL con l'ultima Freifunk, con
questi indirizzamenti
MAC *2D7F
IP LAN 192.168.1.1
IP WAN 192.168.11.1 GW 192.168.11.2
IP WIFI 10.10.10.1
MAC *2FFB
IP LAN 192.168.2.1
IP WAN 192.168.12.1 GW 192.168.12.2
IP WIFI 10.10.10.2
MAC *DB0B
IP LAN 192.168.3.1
IP WAN 192.168.13.1 GW 192.168.13.2
IP WIFI 10.10.10.3
Ogni router potenzialmente ha un GW verso l'esterno, che può essere UP o
meno.
I tre router sono connessi tra loro tramite Wifi in modalità ad-hoc,
come da manuale e comunicano senza problemi.
Il protocollo olsr funziona e i 3 router creano la mesh, quindi
configurando un solo gateway si può navigare dalle 3 LAN.
Ciò che ancora non siamo riusciti a far funzionare è l'aggiornamento
automatico delle route quando cambia gateway, ovvero se un GW sparisce
ma ce n'è un altro disponibile in rete.
Il problema è che il router non si accorge che il suo GW è down e la
rete va riconfigurata a mano.
Nel campo HNA4 di ogni router abbiamo messo
0.0.0.0/0; 192.168.X.1; 192.168.1X.1
con X in {1,2,3}
purtroppo non abbiamo trovato documentazione per questo caso e siamo
fermi da alcune settimane su questo
Ogni suggerimento è ben accetto :)
Grazie
Vincenzo
___
Wireless mailing list
Wireless@ml.ninux.org
http://ml.ninux.org/mailman/listinfo/wireless
Re: [Ninux-Wireless] Map server link fantasma!
ti mando in privato info per fare debug Saverio Il 06 aprile 2011 10:43, Gioacchino Mazzurco gmazzurc...@gmail.com ha scritto: Weila' Mi sto rendendo conto che il map server disegna dei link che non esistono, piu' di quanto immaginassimo... attualmente il server di pisa e' down da ieri pomerigio ma quardando pisa.ninux.org ho visto cambiare lo status dei link diverse volte... come se recuperasse le info da qualche parte ma questo e' impossibile, quindi quei link che disegna sono fantasma ___ Wireless mailing list Wireless@ml.ninux.org http://ml.ninux.org/mailman/listinfo/wireless ___ Wireless mailing list Wireless@ml.ninux.org http://ml.ninux.org/mailman/listinfo/wireless
[Ninux-Wireless] [OT] Jerry Polemica - Nerds
http://www.youtube.com/watch?v=_DynwZe1dHENR=1feature=fvwp Jonathan A ___ Wireless mailing list Wireless@ml.ninux.org http://ml.ninux.org/mailman/listinfo/wireless
