As there were again some ath9k, madwifi and iw changes I posted a ramdisk build of 18596 at ftp://ftp.maddes.net/openwrt/trunk/orio … 6/ramdisk/

(Last edited by maddes.b on 7 Apr 2010, 19:37)

As I wrote the post I remembered mentioning something about padding the img file to bin so I have done it, sorry for bothering you in advance. Found it here and did it accordingly.
The recovery utility asks only for *.BIN not accepting *.IMG. I have done it with FW version 2.0.0.20 and now I have again flashed to 18148, jdt downloading luci.... Will see if it will panic again when PPPoE is set.

Thanks for help, appreciate it!!

(Last edited by bourne on 29 Nov 2009, 14:47)

Remember that there have been wifi/wlan issues for some weeks, the older build 17264 from my ftp space is the last solid I released for testing.

Thanks for the heads up. I enabled Wifi and it is working. Atleast with no security set. I am trying to find how to make PPPoE working now. Probably I messed the config before trying to do PPPoE connection and WiFi in the same time.

I have installed 17264,however luci stopped working after downgrade. I did firsboot but now it is updating packages from your ftp. How can I set it to download packages from OWRT?

From SSh PuTTY when I try to edit the /etc/opkg.conf it says permission denied.

EDIT: I managed with vi.

(Last edited by bourne on 29 Nov 2009, 17:01)

So, I managed to get it to work, though PPPoE drops somewhat often. Nevertheless, WiFi is working, reporting 54Mb/s with WPA2 enabled. I used 17264 build as you have recommended, so far so good.

Thanks for the help!

@ Maddes.b I got my cable today so I have tried your newest build 18596 but I can not test it properly as when I try to activate wifi router restarts.
Is there any chance to get the squashfs.img so I can test it?

I have to report that build 17264 is working flawlessly so far. I thought there were some problems in the beginning as the link was dropping but so far it is working great. I have also enabled n  mode and it is reporting 130 Mbps. I enabled Turbo also but I don't know if this is of any help.

I am using LuCI as my interface of choice, tried X-Wrt also but there seems to be some troube with packages. For some reason it is failing to download packages that it is requesting from web interface (bandwithd, for example) and after installation of the X-wrt I have to edit the opkg.conf as it messes up the X-Wrt repo somehow.

(Last edited by bourne on 1 Dec 2009, 17:38)

Bourne and Maddes:  Kudos to you for all the hard work you are putting into this!  This is my first attemp to using wrt firmware, and i am already a fan!

Question:  I updated the build from 2 weeks back onto my WNR854T and other than the wifi, its been working very good.  Is build 17264 able to get wifi for WNR854T working as well, or is it just for WNR350.  Also, since sysupgrade is not working for WNR854T, is TFTP the best alternative?

Thanks in advance...

@bourne:
That's why I'm currently only releasing ramdisk builds. If a build crashes, then it is not a good idea to flash it from the squashfs image.
Right now there are some crashes (so called "kernel panics") on encrypted wifi/wlan.
Just created a ramdisk build of 18615.

@nd_1000 / nilfred:
Thanks, but major credit goes to Kaloz from the OpenWrt developers, Leonard from Marvel plus DirkNL, StrikerNL from this forum.
I published all 17264 images for the Marvell Orion CPU, therefore: yes, you can test that build for WNR854T.
Can not say if WNR854T has also wifi/wlan problems with the latest builds. Maybe Nilfred can tell you more about this.

And yes TFTP is the most robust way to flash. Flashing inside Linux works (read page 12 and onwards) but you have to check a lot of stuff.

Update:
Currently rebuilding 17264 with sysupgrade support for WRT350 and WNR854T. Will take 12-14 hours.

(Last edited by maddes.b on 1 Dec 2009, 21:02)

I want to create a complete repository for WRT350N and other Orion-CPU-based routers, right now I would try to create it for build 17264.
Please mail(!) me if you would prefer this build, or would prefer another.
Please mail me via the mail link under my name - don't spam this thread. Your mail address will be visiable to me, if you want to be anonymous then PM me.

(Last edited by maddes.b on 1 Dec 2009, 21:05)

@nd_100: O_o I am the last person here that should be thanked, I just tried the almost_done build few days back. As Maddes said, major credit goes to Kaloz, Leonard, DirkNL, StrikerNL, and all the early testers willing to help. And Maddes, of course. Without him and his will to keep track on the changes, applying and compiling them for testing, we would have hard time with crappy Linksys

Thanks Maddes!

@nd_100: Please read this tread (at least). Stock WNR854T wifi is unsupported, but as it's Mini-PCI, can be exchanged by a well supported one. Needed mwl8k driver is unfinished.

I have x-wrt official package repositories, 160~190 Mb each, if someone is interested for:
r17427
r17980
r18042
r18161
r18327
r18433
r18454
r18456
r18580

@maddes.b: +1 r17264. Could we have a fork? Some changes after that are completely harmless.

@ maddes.b I have tried following ramdisk builds:

17357, 17399, 17456, 17562, 17650.

17358 did not have ramdisk image so I skipped on that one.

wifi is working on all off them for me but n is not working. I tested on my xp machine and all are reporting 54Mbps.

On the build I ave installed configuration for WiFi is following:

config 'wifi-device' 'wlan0'
        option 'type' 'mac80211'
        option 'country' 'cn'
        option 'hwmode' '11ng'
        option 'maxassoc' ''
        option 'distance' ''
        option 'diversity' ''
        option 'txantenna' ''
        option 'rxantenna' ''
        option 'disabled' '0'
        option 'antenna' ''
        option 'channel' '9'

config 'wifi-iface'
        option 'device' 'wlan0'
        option 'network' 'lan'
        option 'mode' 'ap'
        option 'hidden' '0'
        option 'isolate' '0'
        option 'txpower' ''
        option 'bgscan' '0'
        option 'wds' '0'
        option 'key1' ''
        option 'key2' ''
        option 'key3' ''
        option 'key4' ''
        option '80211h' ''
        option 'compression' ''
        option 'bursting' ''
        option 'ff' ''
        option 'wmm' ''
        option 'xr' ''
        option 'ar' ''
        option 'turbo' '1'
        option 'macpolicy' 'none'
        option 'maclist' ''
        option 'encryption' 'psk2'
        option 'key' '***********'
        option 'ssid' 'OW_test'

Adding following lines did not make any difference:

        list 'ht_capab' 'HT40-'
        list 'ht_capab' 'SHORT-GI-40'
        list 'ht_capab' 'DSSS_CCK-40'

one question: Does setting option 'encryption' 'psk2' or 'psk2/aes' make any difference?
XP is connecting as PSK2/AES in both configurations.

This will be a "sticky" post to keep track of the mac80211 changes (due to the current wlan/wifi issues), so please bookmark it (same as you did with #300, didn't you?).

Explanations: (as of r19183)
WPA[1] is normally TKIP encryption, and was inofficially updated to CCMP (AES) encryption.
WPA2 is the official implementation of CCMP (AES) encryption.
WEP is totally unsecure and unsupported by OpenWrt's hostapd script.
Linux Wireless info, HostAPd homepage

The files in OpenWrt that handle wireless are lib/wifi/mac80211.sh and lib/wifi/hostapd.sh, plus sbin/wifi for general functions.
a) lib/wifi/mac80211.sh
Checks for lower case of *wep* or *psk*|*wpa*
b) lib/wifi/hostapd.sh
Checks for wpa2*|*psk2* and sets CCMP only, or *mixed* and sets CCMP+TKIP, otherwise TKIP only
Then checks for encryption overrides: *tkip+aes|*tkip+ccmp sets CCMP+TKIP, *tkip sets TKIP only, and *aes|*ccmp sets CCMP only

To set the different encryptions in their default way use one of this lines:
uci set wireless.@wifi-iface[0].encryption=psk-mixed  # WPA-PSK with TKIP and WPA2-PSK with CCMP (AES)
uci set wireless.@wifi-iface[0].encryption=psk2  # WPA2 with CCMP (AES)
uci set wireless.@wifi-iface[0].encryption=psk  # WPA[1] with TKIP

Additionally for PSK mode: if the passphrase is a 64 chars long key then it is used as a hex key.

For hwmode the following possibilities exist: (lib\wifi\hostapd.sh)
11bg, 11a, 11b, 11g, 11na, 11ng

Issues:
After 17264 some older drivers could not connect to OpenWrt, big problem with rarely updated devices like Smartphones, etc.
Additionally there must be a mac address in the config, this may not be the case if you kept/copied the config from a previous build.
Somewhere after 18000 there are kernel panics when starting the network or a device connects (last test: 19265).
There's a ticket for this issue: #5815
It turned out that only release builds have this problem, a mini build does work.
The problematic package is kmod/Network Support/kmod-ipsec.

Test with 19265:

* mini+tun build:
11g with G device (Dell Latitude D630, Intel Pro Wireless 3945ABG, Driver 12.2.0.0)
  none: +
  wep: not supported by hostapd script
       would be key management WEP104 or WEP40, instead of TKIP or CCMP
  wpa1-psk: ++
  wpa2-psk: ++
  wpa-mixed-psk: ++

11ng with G device (Dell Latitude D630, Intel Pro Wireless 3945ABG, Driver 12.2.0.0)
"Per the draft standard, wpa2 is required for 802.11n."
  none: +
  wep: not supported by hostapd script
       would be key management WEP104 or WEP40, instead of TKIP or CCMP
  wpa1-psk: not allowed due to N mode
  wpa2-psk: +
  wpa-mixed-psk: only WPA2, no connection with WPA1 TKIP (from Laptop or Smartphone)


* release build:
11g with G device (Dell Latitude D630, Intel Pro Wireless 3945ABG, Driver 12.2.0.0)
  none: kernel panic

Currently not working on the list, it is complete up to the time I started creating it.

MAC80211-related changes after 17264: (checked up to 18617)
a) direct changes to package/mac80211
17265 - [mac80211] Update to compat-wireless-2009-08-15
17266 - [mac80211] update openfw to 5.2
17267 - [mac80211] Build modules only if realy needed.
17275 - [mac80211] also exclude usb_unpoison_urb
17276 - [mac80211] Do not build the mac80211 module in the kernel.
17277 - [mac80211] increase release number
17280 - [mac80211] add deadlock fix patch
17326 - [mac80211] upgrade to 2008-08-20 and clean up some unnecessary patching to config.mk, which frequently causes rejects on new versions
17327 - [mac80211] remove support for compat-wireless-old
17328 - [mac80211] fix ath5k dma size workaround for ar71xx.
17331 - [mac80211] add missing config override
17335 - [mac80211] speed up build by reducing the makefile shell calls, fix forced disable of rfkill
17336 - [mac80211] disable b43 lp-phy support for now
17337 - [mac80211] fix a typo in the compat-wireless build speedup patch
17339 - [mac80211] reorganize compat code to make cfg80211 load without usb
17340 - [mac80211] b43: disable pio and pcmcia support
17341 - [mac80211] fix a race condition in the cfg80211 scanning code
17457 - [mac80211] fix module loading with kernel 2.6.27
17541 - [mac80211] add menuconfig option for enabling debug support via debugfs
17754 - [mac80211] Do not depend on rfkill. With kernel 2.6.31 cfg80211 is build with rfkill if it was build.
17755 - [mac80211] Do not build some modules as they are not needed
17760 - [mac80211] Add ar9170usb driver
17821 - [mac80211] merge Pat Erley's mac80211.sh from openwrt-devel@ with many cleanups and other changes by nbd. adds support for multiple interfaces, tested with ath9k
17824 - [mac80211] fix typo in ifname setup, suppress error messages of interface enumeration commands
17825 - [mac80211] autodetect the default phy mode based on 11n and freq capabilities
17828 - [mac80211] ath: add a compile time option that gives the user full control over regulatory settings (disabled by default for now)
17982 - [mac80211] libertas: use driver from compat-wireless instead of OpenWrt (deprecated) one
17986 - [mac80211] fix typos in KernelPackage/libertas
18023 - [mac80211] upgrade to latest compat-wireless, fix ad-hoc interface setup
18024 - [mac80211] fix autochannel / fixed channel selection, add commands for unencrypted sta mode
18025 - [mac80211] fix encryption fallback for sta mode, add frequency/bssid selection support
18030 - [mac80211] fix ibss join/create
18031 - [mac80211] fix rt2800pci, tx ack timeout is now hardcoded
18034 - [mac80211] fix a warning during interface bringup when using autochannel
18040 - [mac80211] fix download url
18065 - [mac80211] fix ath5k compile on 2.6.28 and earlier
18258 - [mac80211] fix hostapd frame injection in mac80211, backport 9b1ce526eb917c8b5c8497c327768130ee683392
18283 - [kernel] add preliminary 2.6.32 support (patch)
18293 - [mac80211] fill some important capabilities into ht_capab in the hostapd config
18294 - [mac80211] update to 2009-11-03
18317 - [mac80211] fix up the download location for the updated mac80211 version
18338 - [mac80211] b43: work around a locking issue, might fix #5996
18351 - [mac80211] fix wifi detect with 11n cards that have multiple bands
18355 - [mac80211] fix wpa in client mode
18356 - [mac80211] implement wds sta support (wds ap support work in progress, needs hostapd changes)
18363 - [mac80211] fix a bug in broadcast handling of wds sta interfaces
18377 - [mac80211] fix a race condition when bringing up wds sta interfaces on the ap
18379 - [mac80211] disable powersave on the sta by default (for performance reasons)
18412 - [mac80211] add config option to enable Atheros wireless debugging
18415 - [mac80211] update to 2009-11-13 and add some of my new performance improvement patches.ixes excessive cpu usage of hostapd in ap mode, should also fix the ath9k memleak.
18427 - [mac80211] sync with changes to patches submitted upstream
18428 - [mac80211] ath9k: fix massive packet loss issue introduced by upstream cleanups
18429 - [mac80211] ath9k: work-in-progress patch to adapt ath9k to the mac80211 rate control api
18430 - [mac80211] add some missing patch chunks that were accidentally left out in the previous commit
18431 - [mac80211] adjust patches based on upstream feedback
18433 - [mac80211] ath: use GFP_DMA for rx buffer allocations to fix allocation errors on ixp4xx devices with more than 64 MB RAM
18436 - [mac80211] use platform_data on PCI devices in ath9k
18444 - [mac80211] ath9k: split up and adjust rc cleanup patch according to upstream feedback, also fix tx status reporting for minstrel compatibility
18445 - [mac80211] ath9k: fix bisectability of rc patches
18452 - [mac80211] ath9k: fix compiler warning without debug enabled
18465 - [mac80211] update to compat-wireless 2009-11-21
18503 - [mac80211] ath9k: add a few debugfs files to access the chainmasks and registers
18504 - [mac80211] do not build b44
18505 - [mac80211] separate ath9k debugfs support from ath9k debugging, use the mac80211 debugfs config option to enable it
18525 - [mac80211] ath: only use GFP_DMA on ixp4xx
18537 - [mac80211] disable 2GHz band for 5GHz only devices
18562 - [mac80211] select channel 36 by default on 5GHz only devices
18563 - [mac80211] update ath9k patch
18567 - [mac80211] fix a typo in the mac80211.sh
18577 - [mac80211] fix default channel selection in mac80211.sh
18580 - [mac80211] update p54usb firmware to 2.13.24.0.lm87.arm
18582 - [mac80211] remove trailing whitespaces in mac80211.sh
18583 - [mac80211] fix detection of multiple mac80211 devices
18584 - [mac80211] use mac address from platform data if present on ath9k
18600 - [mac80211] fix up wds sta mode after r18591 (= [iw] Update iw to version 0.9.18)
18615 - [mac80211] ix p54usb firmware installation

b) outside changes related to mac80211
17276 - [mac80211] Do not build the mac80211 module in the kernel.
17280 - [mac80211] fix for commit r17276
17296 ? [kernel] use 2.6.30.5
17311 ? [madwifi] refresh patches
17312 ? [madwifi] add powersave fixes based on patches by Steven Luo (#4376)
17314 ? [madwifi] add patch for building all modules (except for the HAL) into a single module. removes support for onoe and amrr.
17315 ? [madwifi] remove support for the madwifi upstream release, it doesn't work on newer kernels and it's not very reliable anyway
17316 ? [madwifi] remove version selection support
17431 ? [madwifi] fix another unconverted netdev_ops issue
17510 ? [madwifi] add a configuration for uapsd (unscheduled automatic powersave delivery), turn it off by default
17545 ? [madwifi] fix several noderef and ibss merge issues that led to memory leaks and high system load
17546 ? [madwifi] replace an implicit memcpy with an explicit one (cosmetic fix)
17549 ? [kernel] update to 2.6.30.6
17554 ? [madwifi] bump some revisions and update copyrights
17576 ? [madwifi] remove an unimportant part of the ibss node handling fix, which led to a regression in ap-to-ap wds operation
17578 ? [madwifi] fix a wds related race condition
17592 ? [madwifi] fix iwconfig tx power display
17602 ? [kernel] update to latest 2.6.27 and 2.6.30 kernels
17687 ? [madwifi] fix maximum txpower display
17688 ? [madwifi] fix sta mode reconnect when roaming between different aps of the same essid
17689 ? [madwifi] fix beacon slot handling and add support for more than 4 vaps (useful for wds per-sta interfaces)
17690 ? [madwifi] fix a theoretical tx buffer leak
17691 ? [madwifi] fix bugs in the calibration triggers
17804 ? [kernel] upgrade to 2.6.30.8
17823 ? [hostapd] initialize wme to sane values
17953 ? [madwifi] madwifi cannot be compiled on cobalt which has a different mips cpu abi
17960 ? [madwifi] add HAL_TARGET mapping for kirkwood board
18001 ? [madwifi] we cannot build madwifi for octeon since there is no mips64r2 hal target
18045 ? [madwifi] beacon timer fixes
18046 ? [madwifi] fix race condition on ibss init
18048 ? [madwifi] fix another ibss crash
18050 ? [madwifi] more ad-hoc fixes
18051 ? [hostapd] do not configure wme when using madwifi - fixes wpa/wpa2 association problems
18052 ? [madwifi] fix various noderef/memleak issues
18053 ? [madwifi] remove the 10HZ timer for updating rate control statistics
18054 ? [madwifi] merge fixes from trunk
18055 ? [madwifi] add antenna gpio support for nanostation loco2
18107 ? [hostapd] make compilation of the hostap driver conditional - saves 10k uncompressed
18108 ? [wireless-tools] reduce binary size by ~13k by removing unused/obsolete features
18112 ? [madwifi] reduce the size of the multicall tool binary
18126 ? [kernel] update to 2.6.30.9
18290 ? [madwifi] fix a crash bug related to refcounting of bss nodes
18293 - [hostapd] fill some important capabilities into ht_capab in the hostapd config
18358 - [hostapd] use the new build variants feature to clean up the makefile
18360 - [hostapd] update to latest git, remove openssl dependency for hostapd-full, it works with internal crypto now
18364 - [hostapd] implement wds ap support
18365 - [hostapd] automatically add wds sta interfaces of an ap to the right bridge
18377 - [hostapd] fix a race condition when bringing up wds sta interfaces on the ap
18378 ? [wireless-tools] re-enable support for enabling/disabling powersave
18404 - [hostapd] fix HT40 BSS scan checks
18405 - [hostapd] fix endian bugs in STA HT capability handling
18417 - [hostapd] fix build of hostapd-utils
18464 - [hostapd] only build opkg packages for the requested build variant (or any if no variant was specified for the package)
18497 - [hostapd] fix rebuild checks
18602 - [hostapd] replace the wme_* config variables with wmm_* ones
18606 - [hostapd] update to latest git, fixes ampdu settings in the beacon HT IE

This is a preparation for creating a current build with the old mac80211 package of 17264.
But for this to work correctly all outside changes have to be known, evaluated and maybe reversed.

Here's how to setup the source code for a recent build with an old mac80211 package: (see post #300 for my information on how to compile it yourself).

# extra folder for all downloads (stays untouched on 'make distclean')
mkdir ~/downloads/

# create folder for this special build
mkdir ~/kernel_mac80211/
cd ~/kernel_mac80211/

# create link to download folder
ln -s ../downloads/ dl

# initial checkout
svn checkout svn://svn.openwrt.org/openwrt/trunk/ .

# change mac80211 to old revision
cd package/mac80211/
svn update -r 17264
cd ../..

(Last edited by maddes.b on 3 Apr 2010, 17:23)

Re-created ramdisk and squashfs builds of 17264 have been published on my ftp space with the main packages.
Only change in main is the updated sysupgrade support for WNR845T and WRT350Nv2.

A compilation with all packages of 17264 (plus updated packages of OpenSSL, OpenVPN, SSLH, etherwake) went fine and is fully uploaded.

Compilation with a complete current feed package (r18617) plus updated packages of dnsmasq, dropbear, opkg went fine and is fully uploaded.
Tested successfully SSH, OpenVPN, both also via SSLH, etherwake, also via X-Wrt interface, ntpclient, PPPOE/DSL, Wifi/WLAN WPA2-PSK/AES.

(Last edited by maddes.b on 7 Apr 2010, 19:38)

For swapping card out of my wnr854t, would any of the following 2 cards work:

Intel WiFi Link 5100
Atheros AR5008

Any other card that will work right out of the gate instead of having to recompile something? 
Thanks in advance.  I tried searching the forums to see if this information is already been discussed but i didnt find anything specific...

I have to correct myself on one thing:

        list 'ht_capab' 'HT40-'
        list 'ht_capab' 'SHORT-GI-40'
        list 'ht_capab' 'DSSS_CCK-40'

does make a difference, speed goes up.

I have reflashed to the latest 17264 and I have updated hostapd too before I have added the 'list' options.

btw it works flawlessly, 17264.

@nd_100, I think that with change of card you need to recompile the kernel, but am not sure. Maybe someone more experienced can answer this.

The WRT350N comes with an AR5008 (consisting of Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81) so that should work fine.

Sorry for interrupt, but i want to ask whether I can use the file
openwrt-wrt350nv2-squashfs.padded.img
directly upgrade form the webGUI of the WRT350n V2 router

thanks

What WebGUI?
If stock firmware, then no. You need a webupgrade image.
If OpenWrt, then this would work. If sysupgrade support is already included then you do not need a padded image.

Btw it is recommended to really read the complete thread (at least from page 10 on), so you know what problems and issues currently exist. For example post #614 above and there are more.
Plus read the Wiki and Docs to know how to configure your router via uci, otherwise you will be lost and your router is rendered useless.

(Last edited by maddes.b on 8 Dec 2009, 01:24)

@maddes: I did give a try to your latest "enhanced" 17264 build.
For me it is not the way to go as from a wifi perspective, this version is quite worse compared to the latest stable you had (18148): it is a nightmare for my smartphone to keep connected :-(
So I wanted to switch back to 18148 which is not perfect but better (I made a local copy a few weeks ago) but... sysupgrade seems broken in the latest 17264:

# sysupgrade -v ftp://192.168.1.11/public/openwrt/maddes/build_18148/squashfs/openwrt-wrt350nv2-squashfs.img
File does not exist.
Image check 'platform_check_image' failed.

(Of course a wget with the exact same url is ok.)

Edit1:
For the bad wifi:
I've managed to get decent performances by:
- installing hostapd from optware trunk rather than from maddes build.
- manually editing /lib/wifi/hostapd.sh to add some more parameters as they were not handled through uci or the /etc/config/wireless file

ieee80211d=1
dtim_period=1
ignore_broadcast_ssid=1
ap_max_inactivity=1800

I think that most of the above paremeters are just to deal with how I want my wifi network to operate and should'nt play any role with regards to performance. Anyway, there's no way to set them up with uci.

-  using some specific wireless parameters (with uci):

wireless.wlan0.ht_capab=[HT40-][SHORT-GI-40][DSSS_CCK-40]
wireless.wlan0.hwmode=11ng

Edit2:
Finaly, I have too many wifi stability issues with 17264, so I reverted to 18148... (if one can say it reverts from 17264 to 18148 :D, yeah I'm back in the future :D :D)
For the broken sysupgrade, just wget the image in /tmp and then sysupgrade from the local file in /tmp.

(Last edited by operron on 8 Dec 2009, 22:13)

If i am using the stock firmware, is there any methods that can be done in order to use OpenWrt?
sorry i don't know much about the other ways to flash the router

@slxar: maddes already answered you: You need a webupgrade image.
What may be not obvious if you just jumped in this thread is: where the hell do I find a webugrade image ? Hence maddes recommendation to get through the whole thread... yeah painful but very valuable.
So, having said that, the latest webugrade image (as the time of writing this) is here.

Operron is right there's a left over from testing.
After some more testing it is not possible to do a sanity check on files from ftp/http spaces.
Therefore please download to /tmp and sysupgrade from there.

Latest version:

# use default "image" for PART_NAME
# use default for platform_do_upgrade()

platform_check_image() {
    [ "${ARGC}" -gt 1 ] && { echo 'Too many arguments. Only flash file expected.'; return 1; }

    local hardware=`sed -n /Hardware/s/.*:.//p /proc/cpuinfo`
    local magic="$(get_magic_word "$1")"

    case "${hardware}" in
     # hardware with padded uImage + padded rootfs
     'Netgear WNR854T' | 'Linksys WRT350N v2')
        [ "${magic}" != '2705' ] && {
            echo "Invalid image type ${magic}."
            return 1
        }
        # special cases
        [ "${hardware}" == 'Linksys WRT350N v2' ] && {
            # checks can only be done with directly available files
            [ ! -f "$1" ] && {
                local filename=`basename $1`;
                echo "Due to necessary checks please download \"${filename}\" via wget to /tmp and upgrade from there.";
                return 1;
            }
            # WRT350Nv2 eRcOmM sanity check, if 0x00750000-0x0075FFFF would be overwritten or erased
            local checksize=$(( 0x00750000 ))
            local size=`ls -l "$1" | awk '{ print $5 }'`
            [ ${size} -gt ${checksize} ] && {
                local bytes=`hexdump -v -e '1/1 "%02X"' -s $(( 0x0075FFE8 )) -n 8 "$1"`
                [ "${bytes}" != '6552634F6D4D0000' ] && {
                    echo "Flash image would kill eRcOmM identifier for WRT350N v2. Not flashing."
                    return 1
                }
            }
        }
        return 0
        ;;
    esac

    echo "Sysupgrade is not yet supported on ${hardware}."
    return 1
}

(Last edited by maddes.b on 11 Dec 2009, 12:56)

sorry about that,my english is too bad for understanding the posts but i have read the whole thread before i wrote the posts
Frankly speaking, thanks for you help and i will try it ASAP

Sorry for another question, how can i access to the web interface after flashing the router?
also some more question about routing
how can i set to have port forwarding and also access via lan device?
for example computer A got port 80 open but computer B can't access when typing the IP it just shows 404 error
sorry for my foolish question and English but it is in urgency

(Last edited by slxar on 9 Dec 2009, 17:04)