*** Release Candidate 3 ***

The OpenWrt Team is pleased to announce the third and last release
candidate (RC3) of the next stable release, codenamed Backfire. Testing
of this build will help refine the code in preparation of the final
release.

Binaries can be downloaded at
http://downloads.openwrt.org/backfire/10.03-rc3/

OpenWrt Trunk has now been branched and named "backfire" within the
repository.
The Backfire branch source code can be checked out at
svn://svn.openwrt.org/openwrt/branches/backfire/

Changes since Backfire RC2:
* support for Infineon Danube/TwinPass (ifxmips)
* support for Intel Tolapai SoC (ep80579)
* experimental ImageBuilder files back again and available
* new /etc/openwrt_release machine-readable file with detailed release
  informations

Known Issues:
* Encounters of spurious log messages every second on some brcm-2.4 &
  brcm47xx installs
* Kernel modules missing on ixp4xx
* There have been reports that sysupgrade can fail on brcm-2.4 and
  brcm47xx under certain conditions

More detailed information available at
https://dev.openwrt.org/milestone/Backfire%2010.03-rc3

Special thanks to marcant.net for offering buildbot assistance   

Yours truly,
--
The release management team
Andy Boyett & Nicolas Thill

For bcrm47xx The image builder is missing (Ticket #7051)

(Last edited by guymarc on 3 Apr 2010, 11:01)

There appear to be no wifi drivers in the WNDR3700 jjfs2 image. No wifi interfaces are detected.
Found the same issue in RC1 and RC2.

output for command "wifi":

PHY for wifi device radio0 not found
PHY for wifi device radio1 not found
PHY for wifi device radio0 not found
PHY for wifi device radio1 not found

Installing kmod-ath9 fixed that... now just getting the 5GHz radio to work..

(Last edited by hijglander on 3 Apr 2010, 14:02)

You need to install kmod-ath9k.

Please note that this does not that  b43 driver hangs Asus WL-500gP v2!!

Enabling wireless will hang your router and force you to install new firmware.

For more information see:
https://dev.openwrt.org/ticket/6907

This also seems to be the case with previous 10.03 RC:s

Thnx, that worked indeed.. but only for the 2,4GHz radio. The 5GHz radio generated an error message something like not being able to select the proper channel (tried channels from 36 to 56) because the hardware doesn't support it.

Has this slipped off the radar? No reaction for the past 3 weeks is strange.
https://dev.openwrt.org/ticket/6719

I'll try later today but I expect the problem to be still there, I saw nothing relevant in the changelog.
Will update with fresh info, then.

EDIT (fresh info):
on WRT54GS_v4, rc3 still suffers from the same issue when WAN is PPTP: the router cannot reach the modem (i.e., PPTP server) since no route exists. Adding an alias or a new interface as described in the bug above does not work because the IP is briefly added to eth0.1 during boot then removed, isolating the modem from the router.

I worked around the issue by changing the modem configuration to bridged and using PPPoE on OpenWRT. Works nicely.

(Last edited by aboaboit on 4 Apr 2010, 16:55)

Hello,

I've tested the backfire 10.03 rc3 or more exactly r20675 on my Linksys WRT54G v3.1. I compiled it with kernel 2.6 and Luci without any problem. After having it installed on my device I tested the following:
- Access point without encryption: OK
- Access point with WPA encryption: OK
- Access point with WPA2 encryption: OK
- Client mode (access point with WPA encryption): OK
- SD card reader: NOT OK

Conclusion: The broadcom wireless driver for the 2.6 kernel fulfills my needs, but I was unable to mount a SD card, has anyone already done this successfully?

I'll checkout trunk and retry everything with a 2.4 kernel, especially the gpio SD card interface.

Regards, Gilles

You need the block-mount & block-hotplug packages. Then use /etc/config/fstab for configuration. If you like to install packages on the SD card in an easy way you have to build an image with block-extroot package included in the SquashFS.

The SD card is detected by the mmc-over-gpio driver?

(Last edited by Dogge on 4 Apr 2010, 18:47)

Hello Dogge,

No the card is not detected, dmesg shows the following:
mmc_spi: Unknown symbol spi_register_driver
mmc_spi: Unknown symbol spi_sync
mmc_spi: Unknown symbol spi_bus_type
mmc_spi: Unknown symbol spi_setup
spi_bitbang: Unknown symbol spi_unregister_master
spi_bitbang: Unknown symbol spi_register_master
spi_gpio_old: Unknown symbol spi_bitbang_stop
spi_gpio_old: Unknown symbol spi_alloc_master
spi_gpio_old: Unknown symbol spi_new_device
spi_gpio_old: Unknown symbol spi_bitbang_start
gpiommc: Unknown symbol config_group_init
gpiommc: Unknown symbol configfs_unregister_subsystem
gpiommc: Unknown symbol configfs_register_subsystem
gpiommc: Unknown symbol config_item_init_type_name
gpiommc: Unknown symbol spi_gpio_next_id

The following packages are installed on the device:
- kmod-mmc - 2.6.32.10-1
- kmod-mmc-over-gpio - 2.6.32.10-4
- kmod-mmc-spi - 2.6.32.10-1
- kmod-spi-bitbang - 2.6.32.10-1
- kmod-spi-gpio-old - 2.6.32.10-1
- luci-app-mmc-over-gpio - 0.9+svn6006-1

Regards, Gilles

'opkg list_installed' and 'lsmod'

The output of the two commands:

root@OpenWrt:~# opkg list_installed
base-files - 42-r20675
block-hotplug - 0.1.0-1
block-mount - 0.1.0-1
busybox - 1.16.1-1
cfdisk - 2.13.0.1-4
crda - 1.1.0-2
ddns-scripts - 1.0.0-6
dnsmasq - 2.52-2
dropbear - 0.52-4
firewall - 1-10
hotplug2 - 1.0-beta-1
iptables - 1.4.6-2
iptables-mod-conntrack - 1.4.6-2
iptables-mod-conntrack-extra - 1.4.6-2
iptables-mod-filter - 1.4.6-2
iptables-mod-imq - 1.4.6-2
iptables-mod-ipopt - 1.4.6-2
iptables-mod-nat - 1.4.6-2
iw - 0.9.19-1
kernel - 2.6.32.10-1
kmod-b43 - 2.6.32.10+2010-03-24-6
kmod-b43legacy - 2.6.32.10+2010-03-24-6
kmod-cfg80211 - 2.6.32.10+2010-03-24-6
kmod-crc-ccitt - 2.6.32.10-1
kmod-crc-itu-t - 2.6.32.10-1
kmod-crc7 - 2.6.32.10-1
kmod-crypto-aes - 2.6.32.10-1
kmod-crypto-arc4 - 2.6.32.10-1
kmod-crypto-core - 2.6.32.10-1
kmod-diag - 2.6.32.10-6
kmod-fs-ext3 - 2.6.32.10-1
kmod-fs-mbcache - 2.6.32.10-1
kmod-fs-vfat - 2.6.32.10-1
kmod-ipt-conntrack - 2.6.32.10-1
kmod-ipt-conntrack-extra - 2.6.32.10-1
kmod-ipt-core - 2.6.32.10-1
kmod-ipt-filter - 2.6.32.10-1
kmod-ipt-imq - 2.6.32.10-1
kmod-ipt-ipopt - 2.6.32.10-1
kmod-ipt-nat - 2.6.32.10-1
kmod-ipt-nathelper - 2.6.32.10-1
kmod-mac80211 - 2.6.32.10+2010-03-24-6
kmod-mmc - 2.6.32.10-1
kmod-mmc-over-gpio - 2.6.32.10-4
kmod-mmc-spi - 2.6.32.10-1
kmod-nls-base - 2.6.32.10-1
kmod-nls-cp437 - 2.6.32.10-1
kmod-nls-iso8859-1 - 2.6.32.10-1
kmod-ppp - 2.6.32.10-1
kmod-pppoe - 2.6.32.10-1
kmod-sched - 2.6.32.10-1
kmod-spi-bitbang - 2.6.32.10-1
kmod-spi-gpio-old - 2.6.32.10-1
kmod-switch - 2.6.32.10-2
kmod-textsearch - 2.6.32.10-1
libc - 0.9.30.1-42
libgcc - 4.3.3+cs-42
libiptc - 1.4.6-2
liblua - 5.1.4-6
libncurses - 5.7-2
libnl-tiny - 0.1-1
librt - 0.9.30.1-42
libuci - 12012009.5-1
libuci-lua - 12012009.5-1
libxtables - 1.4.6-2
lua - 5.1.4-6
luci - 0.9+svn6013-1
luci-admin-core - 0.9+svn6013-1
luci-admin-full - 0.9+svn6013-1
luci-admin-mini - 0.9+svn6013-1
luci-app-ddns - 0.9+svn6013-1
luci-app-firewall - 0.9+svn6013-1
luci-app-initmgr - 0.9+svn6013-1
luci-app-mmc-over-gpio - 0.9+svn6006-1
luci-app-ntpc - 0.9+svn6013-1
luci-app-qos - 0.9+svn6013-1
luci-cbi - 0.9+svn6013-1
luci-core - 0.9+svn6013-1
luci-http - 0.9+svn6013-1
luci-i18n-english - 0.9+svn6013-1
luci-ipkg - 0.9+svn6013-1
luci-lmo - 0.9+svn6013-1
luci-nixio - 0.9+svn6013-1
luci-sgi-cgi - 0.9+svn6013-1
luci-sys - 0.9+svn6013-1
luci-theme-base - 0.9+svn6013-1
luci-theme-openwrt - 0.9+svn6013-1
luci-uci - 0.9+svn6013-1
luci-uvl - 0.9+svn6013-1
luci-web - 0.9+svn6013-1
mtd - 12
ntpclient - 2007_365-4
nvram - 5
opkg - 513-1
ppp - 2.4.4-5
ppp-mod-pppoe - 2.4.4-5
qos-scripts - 1.2.1-2
tc - 2.6.29-1-2
uci - 12012009.5-1
udevtrigger - 106-1
uhttpd - 7
wireless-tools - 29-4
wpad-mini - 20100309-1
root@OpenWrt:~# lsmod
Module                  Size  Used by    Not tainted
mmc_block               7216  0
mmc_core               40000  1 mmc_block
nf_nat_tftp              432  0
nf_conntrack_tftp       2400  1 nf_nat_tftp
nf_nat_irc               864  0
nf_conntrack_irc        2592  1 nf_nat_irc
nf_nat_ftp              1360  0
nf_conntrack_ftp        4896  1 nf_nat_ftp
xt_HL                   1280  0
xt_hl                    928  0
xt_MARK                  496 15
ipt_ECN                 1376  0
xt_CLASSIFY              496  0
xt_time                 1632  0
xt_tcpmss               1008  0
xt_statistic             800  0
xt_mark                  512 15
xt_length                688  5
ipt_ecn                  992  0
xt_DSCP                 1536  0
xt_dscp                 1040  0
xt_IMQ                   704  1
imq                     3008  0
xt_string                880  0
xt_layer7              10752  2
ipt_MASQUERADE           992  1
iptable_nat             2304  1
nf_nat                 11824  5 nf_nat_tftp,nf_nat_irc,nf_nat_ftp,ipt_MASQUERADE,iptable_nat
xt_CONNMARK              768  2
xt_recent               5888  0
xt_helper                816  0
xt_conntrack            2144  0
xt_connmark              640  0
xt_connbytes            1216  0
xt_NOTRACK               672  0
iptable_raw              656  1
xt_state                 800  3
nf_conntrack_ipv4       7808 10 iptable_nat,nf_nat
nf_defrag_ipv4           608  1 nf_conntrack_ipv4
nf_conntrack           42912 18 nf_nat_tftp,nf_conntrack_tftp,nf_nat_irc,nf_conntrack_irc,nf_nat_ftp,nf_conntrack_ftp,xt_layer7,ipt_MASQUERADE,iptable_nat,nf_nat,xt_CONNMARK,xt_helper,xt_conntrack,xt_connmark,xt_connbytes,xt_NOTRACK,xt_state,nf_conntrack_ipv4
pppoe                  10208  0
pppox                   1312  1 pppoe
ipt_REJECT              1984  2
xt_TCPMSS               1952  1
ipt_LOG                 4640  0
xt_comment               464  0
xt_multiport            1904  5
xt_mac                   576  0
xt_limit                1152  1
iptable_mangle           992  1
iptable_filter           768  1
ip_tables               8864  4 iptable_nat,iptable_raw,iptable_mangle,iptable_filter
xt_tcpudp               1856 13
x_tables                9840 35 xt_HL,xt_hl,xt_MARK,ipt_ECN,xt_CLASSIFY,xt_time,xt_tcpmss,xt_statistic,xt_mark,xt_length,ipt_ecn,xt_DSCP,xt_dscp,xt_IMQ,xt_string,xt_layer7,ipt_MASQUERADE,iptable_nat,xt_CONNMARK,xt_recent,xt_helper,xt_conntrack,xt_connmark,xt_connbytes,xt_NOTRACK,xt_state,ipt_REJECT,xt_TCPMSS,ipt_LOG,xt_comment,xt_multiport,xt_mac,xt_limit,ip_tables,xt_tcpudp
ext3                   95888  0
jbd                    44144  1 ext3
ppp_async               9040  0
ppp_generic            21200  3 pppoe,pppox,ppp_async
slhc                    5360  1 ppp_generic
vfat                    8016  0
fat                    45456  1 vfat
b43legacy              98752  0
b43                   154688  0
nls_iso8859_1           2848  0
nls_cp437               4384  0
mac80211              212368  2 b43legacy,b43
ts_fsm                  2656  0
ts_bm                   1456  0
ts_kmp                  1344  0
nls_base                4960  4 vfat,fat,nls_iso8859_1,nls_cp437
mbcache                 4160  0
crc7                     720  0
crc_itu_t                992  0
crc_ccitt                976  1 ppp_async
cfg80211              129088  3 b43legacy,b43,mac80211
compat_firmware_class     5920  2 b43legacy,b43
compat                   432  0
arc4                     816  2
aes_generic            31056  0
deflate                 1328  0
ecb                     1328  2
cbc                     2016  0
switch_robo             4048  0
switch_core             5200  1 switch_robo
diag                    7504  0
root@OpenWrt:~#

Regards, Gilles

Seems all normal. No idea what could be wrong...

ImageBuilders are now available (except for ixp4xx & brcm63xx), feedback welcome !
--
-{Nico}

How do I find the Imagebuild for ar71xx rc3?

thank you
john  isaacson

Cancel the request.
I found it right after I asked.

thanks;
john isaacson

Does anyone know if support for the SheevaPlug (Marvell Kirkwood) utilizes the hardware AES/SHA1?

By the by... how do you check if the acceleration is used or not? I have the relevant modules loaded, the SoC in the Asus WL-500gPv1 is supposed to have a working crypto core (at least, it shows up in dmesg)... but which cold, hard facts can I check?

Today I've tested my SD interface with the 2.4 kernel (brcm-2.4 revision 20716). I'm still unable to use the interface but the problems are different, it's possible to write the partition table and create a FAT32 filesystem which is usable on my desktop but once I try to mount the card I get the following:

/etc/init.d/sdcard start
sdcard - Card detected and initialized
mount: mounting /dev/sdcard/part1 on /sdcard failed: Invalid argument
sdcard - Unable to mount /dev/sdcard/part1 on /sdcard

/etc/init.d/sdcard status
sdcard - Started
Card Type      : SD
Spec Version   : 1.10
Card Size      : 974 MB
Block Size     : 512 bytes
Num. of Blocks : 1995264
Voltage Range  : 2.7-3.6
Manufacture ID : 03
Application ID : ?h
Product Name   : SD01G
Revision       : 8.5
Serial Number  : 00f004d7
Manu. Date     : Nov 2006

To be sure that the interface is not damaged I reflashed 8.09.2 brcm-2.4. Both, kmod-broadcom-mmc and the kmod-broadcom-sdhc SDHC/MMHC Card driver, work without any problem. By the way, what is the difference between both modules?

Regards, Gilles

(Last edited by Roodemol on 5 Apr 2010, 22:04)

I've tested this release on a WRT54G v3.1 and I didn't succeed in configuring a WDS interface.

Using

config wifi-iface
        option device wlan0
        option network lan
        option mode wds
        option ssid <my ssid>
        option encryption none
        option bssid <other ap's bssid>

produces wlan0(cfg057442): Invalid mode, ignored.

Looking at the /lib/wifi/mac80211.sh script, I've also tried:

config wifi-iface
        option device wlan0
        option network lan
        option mode sta
        option wds 1
        option ssid <my ssid>
        option encryption none
        option bssid <other ap's bssid>

with no more success.

Any tip I'd have missed?

Thanks in advance.

Yes, the mac80211 wds mechanism is different. You basically define a normal ap / sta link and add "option wds 1" on both sides in the wifi iface section.

Hi,

What does this mean for those of us who own the WL-500W ? Does it mean we can't use Backfire because of the fact that b43 doesn't yet support the Brcm 4321 wireless chip ?

Regards,

Zinahe A.

Erm... I fail to see the the whole picture. Is there somewhere an example of such a configuration for /etc/config/wireless?

BTW, is this mac80211 wds compatible with other WRT54G running kamikaze brcm-2.4?

Hello,
my problem is now solved. It's now working with kernel 2.6, I'm not sure where exactly I made an error in my previous essay, probably an error in /etc/config/mmc_over_gpio. Nevertheless I have the impression that reading and writing to the card was faster with 8.09.2 kmod-broadcom-sdhc SDHC/MMHC Card driver. Is there something similar to "/etc/init.d/sdhc test".

Kind regards, Gilles

I am trying to use an old PC as router/file server. I have been trying to use OpenWrt. Backfire 10.03-rc3 does not recognize my Asus nx1101 gigabit ethernet card. It worked in Debian when I installed the ipg kernel module, but I did not find this package for OpenWrt. Is there a way to make this card to work in latest Backfire?
Thanks.