[WLANware] Re-2: Freifunk AP keien IP beim Boot

Marc V. admin at vmtek.de
Mon Mar 28 20:57:58 CEST 2011


Falls es Hilft ist hier mal die Ausgabe vom Boot:

CFE version 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: Fri Dec 12 02:01:12 CST 2003 (vlinux at Test)
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.

Initializing Arena.
Initializing Devices.
et0: Broadcom BCM47xx 10/100 Mbps Ethernet Controller 3.50.21.0
CPU type 0x29007: 200MHz
Total memory: 0x2000000 bytes (32MB)

Total memory used by CFE:  0x8032B9F0 - 0x80430EF0 (1070336)
Initialized Data:          0x8032B9F0 - 0x8032DB40 (8528)
BSS Area:                  0x8032DB40 - 0x8032EEF0 (5040)
Local Heap:                0x8032EEF0 - 0x8042EEF0 (1048576)
Stack Area:                0x8042EEF0 - 0x80430EF0 (8192)
Text (code) segment:       0x80300000 - 0x80309420 (37920)
Boot area (physical):      0x00431000 - 0x00471000
Relocation Factor:         I:00000000 - D:00000000

Device eth0:  hwaddr 00-90-4C-60-04-00, ipaddr 192.168.5.79, mask 255.255.255.224
        gateway not set, nameserver not set
Reading :: Failed.: Timeout occured
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: .. 3704 bytes read
Entry at 0x80001000
Closing network.
Starting program at 0x80001000
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "cfe"
0x00040000-0x001f0000 : "linux"
0x000b3c9c-0x00190000 : "rootfs"
mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
0x001f0000-0x00200000 : "nvram"
0x00190000-0x001f0000 : "OpenWrt"
Using /lib/modules/2.4.30/ff-diag.o
diag boardtype: 00000446
diag wap54g-v2 detected
Using /lib/modules/2.4.30/switch-core.o
Using /lib/modules/2.4.30/switch-robo.o
Probing device eth0: No Robo switch in managed mode found
Probing device eth1: No such device
Probing device eth2: No such device
Probing device eth3: No such device
insmod: init_module: switch-robo: No such device
Using /lib/modules/2.4.30/switch-adm.o
BFL_ENETADM not set in boardflags. Use force=1 to ignore.
insmod: init_module: switch-adm: No such device
Unlocking mtd4
init started:  BusyBox v1.01 (2010.08.29-10:07+0000) multi-call binary
kernel.panic = 3
vm.pagetable_cache = 0 0
net.ipv4.conf.all.arp_ignore = 1
net.ipv4.conf.default.arp_ignore = 1
net.ipv4.conf.all.rp_filter = 1
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.default.send_redirects = 0
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.icmp_ignore_bogus_error_responses = 1
net.ipv4.ip_forward = 1
net.ipv4.tcp_fin_timeout = 30
net.ipv4.tcp_frto = 1
net.ipv4.tcp_keepalive_time = 120
net.ipv4.tcp_syncookies = 1
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_westwood = 1
Using /lib/modules/2.4.30/wl.o
Warning: loading wl will taint the kernel: no license
  See http://www.tux.org/lkml/#export-tainted for information about tainted modules
eth1: Broadcom BCM4320 802.11 Wireless Controller 3.90.37.0
Using /lib/modules/2.4.30/crondog.o
CRONDOG: Timer margin: 600 sec
Using /lib/modules/2.4.30/wlcompat.o
device br0 is a bridge device itself; can't enslave a bridge device to a bridge device.
SIOCSIFHWADDR: Operation not supported
Error: either "local" is duplicate, or "/27" is a garbage.
arping: connect
RTNETLINK answers: Network is unreachable
Error: either "local" is duplicate, or "/27" is a garbage.
arping: connect
RTNETLINK answers: Network is unreachable
### WARNING eth1: proto disabled not supported
Starting firewall...
Starting udhcpd...
Starting olsrd...
Terminated
Thu Dec 31 12:00:00 UTC 2009
Starting olsr prio...

Please press Enter to activate this console.


BusyBox v1.01 (2010.08.29-10:07+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 (       ).-----.-----.-----.)  )  )  ).----.)  )
 (   -   ))  _  )  -__)     ))  )  )  ))   _))   _)
 (_______))   __)_____)__)__))________))__)  )____)
          )__) F R E I F U N K  F I R M W A R E

root at Marcs-AP:/# ifconfig
[Install freifunk-openwrt-compat for /sbin/ifconfig]
+ exec ip addr
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,PROMISC,UP> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:90:4c:60:04:00 brd ff:ff:ff:ff:ff:ff
3: tunl0 at NONE: <NOARP> mtu 1480 qdisc noop
    link/ipip 0.0.0.0 brd 0.0.0.0
4: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:90:4c:60:04:00 brd ff:ff:ff:ff:ff:ff
5: br0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
root at Marcs-AP:/#



        processed by David.fx 
Subject: [WLANware] Re-2: Freifunk AP keien IP beim Boot (28-Mrz-2011 20:45)
From:    Marc V. <admin at vmtek.de>
To:      WLAN-Hard+


Also im Webinterface ists bei LAN eingetragen und im NVRAM hab ichs nicht gesetzt, da stehts einfach so drin.
Manuell setzen auf br0 geht ja, bis zum neustart.

Ich hab die Version 2 mit den 2MB Intel Flash.


Original Message        processed by David.fx 
Subject: Re: [WLANware] Freifunk AP keien IP beim Boot (28-Mrz-2011 20:42)
From:    Thomas Hempe <freifunk at thomashempe.de>
To:      WLAN-Hard+


Ah sicher dass du die IP für das richtige interface gesetzt hast und das WAN interface muss glaub ich aus gemacht werden ich hatte anfangs auch ein paar kleine Probleme. Welche Version vom WAP54G hast du ? 


Am 28.03.2011 um 20:40 schrieb Marc V.:


Moin Freifunk Community,

ich habe auf meinen Linksys WAP54G die Freifunk Firmware installiert.
Jetzt habe ich das Problem, dass der AP beim Booten keine IP zugewiesen bekommt.
Ich muss immer über die Serielle Konsole die ip setzen.
Im nvram und im Webinterface ist die IP aber richtig drin.

Mfg,
Marc V.
_______________________________________________
WLANware mailing list
WLANware at freifunk.net
Abonnement abbestellen? -> https://freifunk.net/mailman/listinfo/wlanware

Weitere Infos zu den freifunk.net Mailinglisten und zur An- und Abmeldung unter http://freifunk.net/mailinglisten

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.freifunk.net/pipermail/wlanware-freifunk.net/attachments/20110328/815f801f/attachment.html>


More information about the WLANware mailing list