Re: Wrt160nl?

brain0 wrote:

Success! Although I don't have serial console yet, I went for it and flashed. It boots and seems to work, although I didn't test much yet.

which rom are you using?
Can you test the n wifi?

Re: Wrt160nl?

kodex83 wrote:
brain0 wrote:

Success! Although I don't have serial console yet, I went for it and flashed. It boots and seems to work, although I didn't test much yet.

which rom are you using?

What do you mean by "rom"? I flashed a self-built SVN trunk r18422 image with a few tools added over the default configuration.

Can you test the n wifi?

No, I have no other draft-n compatible wifi devices. I only tested wireless in station mode with another g-AP. I seem to get some packet loss when pinging (8% of 200 echo requests), didn't test any big transfers yet.

Re: Wrt160nl?

Okay, tried again. Packet loss is indeed quite high (only tried station mode, haven't tested AP yet).

# iw dev wlan0 link
Connected to xx:xx:xx:xx:xx:xx (on wlan0)
        SSID: marvin
        freq: 2412
        RX: 5528532 bytes (48082 packets)
        TX: 322463 bytes (2097 packets)
        signal: -59 dBm
        tx bitrate: 54.0 MBit/s

Pinging from my laptop to the WRT160NL (both are on the same wireless) results in:

--- 10.23.42.17 ping statistics ---
1136 packets transmitted, 909 received, 19% packet loss, time 1137046ms
rtt min/avg/max/mdev = 1.996/6.298/1015.008/33.596 ms, pipe 2

354 (edited by crydee 2009-11-15 21:24:48)

Re: Wrt160nl?

Compiling my first firmware now based on SVN r18425, takes quite a bit of time wink I selected squashfs only, guess that's all I need to build right? Selected the linksys 160NL profile. Anything else needed to make wireless work?

*edit*
Getting the same packet loss with wireless here

Re: Wrt160nl?

crydee wrote:

Compiling my first firmware now based on SVN r18425, takes quite a bit of time wink I selected squashfs only, guess that's all I need to build right? Selected the linksys 160NL profile. Anything else needed to make wireless work?

*edit*
Getting the same packet loss with wireless here

I opened a bug report, and it is already fixed in r18428. Apparently, upstream linux-wireless developers removed an important memset-call during code cleanup, see
https://dev.openwrt.org/browser/trunk/package/mac80211/patches/550-ath9k_rx_fix.patch?rev=18428

Re: Wrt160nl?

Nice! Thx for the status update brain0

Re: Wrt160nl?

I discovered another weirdness. The /etc/config/network generated by OpenWRT contains this by default:

config switch eth1
        option reset    1
        option enable_vlan 1

config switch_vlan
        option device   eth1
        option vlan     1
        option ports    "0 1 2 3 4 5"

Also, swconfig seems to know only eth1 as a switch, not eth0. However, eth1 is a single ethernet port, while eth0 is supposed to be the switch. Is there a bug in the switch driver that just numbers the ports wrong? Any other ideas why it says eth1?

Re: Wrt160nl?

wyngnut wrote:

I am flashing my WRT160NL with the OpenWRT Trunk from http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-wrt160nl-squashfs.bin

I am following the upgrade instructions per the wiki upgrade code.bin via tftp.

OpenWRT comes on my device.

However, on a secondary boot, I get the following from u-boot:

Restarting system.


U-Boot 1.1.6 (May 12 2009 - 07:52:28)

DRAM:  ar7100_ddr_initial_config(237) enter!
ar7100_ddr_initial_config(269) exit!


U-Boot 1.1.6 (May 12 2009 - 07:52:28)

AP81 (ar7100) U-boot
sri
32 MB
WRT160NL u-boot version: 1.0.0
Top of RAM usable for U-Boot at: 82000000
Reserving 279k for U-Boot at: 81fb8000
Reserving 192k for malloc() at: 81f88000
Reserving 44 Bytes for Board Info at: 81f87fd4
Reserving 36 Bytes for Global Data at: 81f87fb0
Reserving 128k for boot params() at: 81f67fb0
Stack Pointer at: 81f67f98
Now running in RAM - U-Boot at: 81fb8000
id read 0x100000ff
flash size 8MB, sector count = 128
Flash:  8 MB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag7100_enet_initialize...
ag7100 get ethaddr for device eth0
Fetching MAC Address from 0x81feb1e0

--------***** Get the RTL8306SD Manufactory ID=379c *****-------
Reg6: speed=0 nway=1 duplex=0
Reg5: speed=0 nway=0 duplex=0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0 a5=0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
eth0: 00:25:9c:1d:ff:23
eth0 up
eth0
### main_loop entered: bootdelay=1

Hit any key to stop autoboot:  0
## Booting WRT160NL ...
Application code length 0x00280000
Bad CRC: trx.crc32 0xc40e3804 calculate 0x92059ced
check link duplex:Full/speed:100
dup 1 speed 100
Tftpd start listening on port[69]!
Load address: 0x80060000

I'm having the same issue.  However it seems that interrupting the autoboot and then doing a bootwrt, it seems to work.  But autobooting it doesn't seem to go well.

U-Boot 1.1.6 (May 12 2009 - 07:52:28)

DRAM:  ar7100_ddr_initial_config(237) enter!
ar7100_ddr_initial_config(269) exit!


U-Boot 1.1.6 (May 12 2009 - 07:52:28)

AP81 (ar7100) U-boot
sri
32 MB
WRT160NL u-boot version: 1.0.0
Top of RAM usable for U-Boot at: 82000000
Reserving 279k for U-Boot at: 81fb8000
Reserving 192k for malloc()``t: 81f88000
Reserving 44 Bytes for Board Info at: 81f87fd4
Reserving 36 Bytes for Global Data at: 81f87fb0
Reserving 128k for boot params() at: 81f67fb0
Stack Pointer at: 81f67f98
Now running in RAM - U-Boot at: 81fb8000
id read 0x100000ff
flash size 8MB, sector count = 128
Flash:  8 MB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag7100_enet_initialize...
ag7100 get ethaddr for device eth0
Fetching MAC Address from 0x81feb1e0

--------***** Get the RTL8306SD Manufactory ID=379c *****-------
Reg6: speed=0 nway=1 duplex=0
Reg5: speed=0 nway=0 duplex=0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0 a5=0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
eth0: 00:25:9c:1a:28:a5
eth0 up
eth0
### main_loop entered: bootdelay=1

Hit any key to stop autoboot:  0
## Booting WRT160NL ...
Application code length 0x00560000
Bad CRC: trx.crc32 0x2d695acf calculate 0x227a9b4e
check link duplex:Full/speed:100
dup 1 speed 100
Tftpd start listening on port[69]!
Load address: 0x80060000


Abort
TFTP Server Stop
ar7100> reboot

Rebooting...ÿ

U-Boot 1.1.6 (May 12 2009 - 07:52:28)

DRAM:  ar7100_ddr_initial_config(237) enter!
ar7100_ddr_initial_config(269) exit!


U-Boot 1.1.6 (May 12 2009 - 07:52:28)

AP81 (ar7100) U-boot
sri
32 MB
WRT160NL u-boot version: 1.0.0
Top of RAM usable for U-Boot at: 82000000
Reserving 279k for U-Boot at: 81fb8000
Reserving 192k for malloc() at: 81f88000
Reserving 44 Bytes for Board Info at: 81f87fd4
Reserving 36 Bytes for Global Data at: 81f87fb0
Reserving 128k for boot params() at: 81f67fb0
Stack Pointer at: 81f67f98
Now running in RAM - U-Boot at: 81fb8000
id read 0x100000ff
flash size 8MB, sector count = 128
Flash:  8 MB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag7100_enet_initialize...
ag7100 get ethaddr for device eth0
Fetching MAC Address from 0x81feb1e0

--------***** Get the RTL8306SD Manufactory ID=379c *****-------
Reg6: speed=0 nway=1 duplex=0
Reg5: speed=0 nway=0 duplex=0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0 a5=0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
eth0: 00:25:9c:1a:28:a5
eth0 up
eth0
### main_loop entered: bootdelay=1

Hit any key to stop autoboot:  0
ar7100> bootwrt
## Booting WRT160NL ...
## Booting image at bf04003c ...
   Image Name:   MIPS OpenWrt Linux-2.6.30.9
   Created:      2009-11-16  19:09:19 UTC
   Image Type:   MIPS Linux Kernel Image (gzip compressed)
   Data Size:    1189939 Bytes =  1.1 MB
   Load Address: 80060000
   Entry Point:  80060000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
kernel: org len = 1189939, new len = 1245184
No initrd
## Transferring control to Linux (at address 80060000) ...
## Giving linux memsize in bytes, 33554432

Starting kernel ...

Linux version 2.6.30.9 (androsyn@salem) (collect2: ld returned 1 exit status) #1 Mon Nov 16 14:09:12 EST 2009
console [early0] enabled
CPU revision is: 00019374 (MIPS 24Kc)


And then it proceeds to boot correctly from there...It almost seems like a uboot bug..but I'm not quite sure...

-Aaron

Re: Wrt160nl?

Can somebody give me a status update with regard to the automatics builds?  Is there an 'off-the-shelf' image for the WRT160NL yet, with working wireless?  If not, is there any chance another user could supply me a know good binary with wireless?

I've tried compiling my own, but my (Fedora 11) client machine totally locks up (i.e. needs a hard reboot!) while trying to connect via wireless.  Its fine via ethernet.  Its also fine from Windows - either wired or wireless!  Please, see my other post: https://forum.openwrt.org/viewtopic.php?id=22564

Re: Wrt160nl?

paulch wrote:

I've tried compiling my own, but my (Fedora 11) client machine totally locks up (i.e. needs a hard reboot!) while trying to connect via wireless.  Its fine via ethernet.  Its also fine from Windows - either wired or wireless!  Please, see my other post: https://forum.openwrt.org/viewtopic.php?id=22564

Then I guess your client machine is broken and should be fixed, not your image. No matter what your router sends, it should never be able to lock up your computer.

Re: Wrt160nl?

Interesting...

Maybe its this specific version of U-Boot.  I notice that it doesn't have the saveenv command, but it does have the setenv command.

so I can also do
ar7100> setenv bootcmd bootwrt
ar7100> go

This works as well, but doesn't stick across power cycles.  Unfortunately it doesn't look like fw_printenv is in this version of openwrt and with no saveenv we can't set anything.

Ugh, one step closer though.




androsyn wrote:
wyngnut wrote:

I am flashing my WRT160NL with the OpenWRT Trunk from http://downloads.openwrt.org/snapshots/trunk/ar71xx/openwrt-ar71xx-wrt160nl-squashfs.bin

I am following the upgrade instructions per the wiki upgrade code.bin via tftp.

OpenWRT comes on my device.

However, on a secondary boot, I get the following from u-boot:

Restarting system.


U-Boot 1.1.6 (May 12 2009 - 07:52:28)

DRAM:  ar7100_ddr_initial_config(237) enter!
ar7100_ddr_initial_config(269) exit!


U-Boot 1.1.6 (May 12 2009 - 07:52:28)

AP81 (ar7100) U-boot
sri
32 MB
WRT160NL u-boot version: 1.0.0
Top of RAM usable for U-Boot at: 82000000
Reserving 279k for U-Boot at: 81fb8000
Reserving 192k for malloc() at: 81f88000
Reserving 44 Bytes for Board Info at: 81f87fd4
Reserving 36 Bytes for Global Data at: 81f87fb0
Reserving 128k for boot params() at: 81f67fb0
Stack Pointer at: 81f67f98
Now running in RAM - U-Boot at: 81fb8000
id read 0x100000ff
flash size 8MB, sector count = 128
Flash:  8 MB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag7100_enet_initialize...
ag7100 get ethaddr for device eth0
Fetching MAC Address from 0x81feb1e0

--------***** Get the RTL8306SD Manufactory ID=379c *****-------
Reg6: speed=0 nway=1 duplex=0
Reg5: speed=0 nway=0 duplex=0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0 a5=0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
eth0: 00:25:9c:1d:ff:23
eth0 up
eth0
### main_loop entered: bootdelay=1

Hit any key to stop autoboot:  0
## Booting WRT160NL ...
Application code length 0x00280000
Bad CRC: trx.crc32 0xc40e3804 calculate 0x92059ced
check link duplex:Full/speed:100
dup 1 speed 100
Tftpd start listening on port[69]!
Load address: 0x80060000

I'm having the same issue.  However it seems that interrupting the autoboot and then doing a bootwrt, it seems to work.  But autobooting it doesn't seem to go well.

U-Boot 1.1.6 (May 12 2009 - 07:52:28)

DRAM:  ar7100_ddr_initial_config(237) enter!
ar7100_ddr_initial_config(269) exit!


U-Boot 1.1.6 (May 12 2009 - 07:52:28)

AP81 (ar7100) U-boot
sri
32 MB
WRT160NL u-boot version: 1.0.0
Top of RAM usable for U-Boot at: 82000000
Reserving 279k for U-Boot at: 81fb8000
Reserving 192k for malloc()``t: 81f88000
Reserving 44 Bytes for Board Info at: 81f87fd4
Reserving 36 Bytes for Global Data at: 81f87fb0
Reserving 128k for boot params() at: 81f67fb0
Stack Pointer at: 81f67f98
Now running in RAM - U-Boot at: 81fb8000
id read 0x100000ff
flash size 8MB, sector count = 128
Flash:  8 MB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag7100_enet_initialize...
ag7100 get ethaddr for device eth0
Fetching MAC Address from 0x81feb1e0

--------***** Get the RTL8306SD Manufactory ID=379c *****-------
Reg6: speed=0 nway=1 duplex=0
Reg5: speed=0 nway=0 duplex=0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0 a5=0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
eth0: 00:25:9c:1a:28:a5
eth0 up
eth0
### main_loop entered: bootdelay=1

Hit any key to stop autoboot:  0
## Booting WRT160NL ...
Application code length 0x00560000
Bad CRC: trx.crc32 0x2d695acf calculate 0x227a9b4e
check link duplex:Full/speed:100
dup 1 speed 100
Tftpd start listening on port[69]!
Load address: 0x80060000


Abort
TFTP Server Stop
ar7100> reboot

Rebooting...ÿ

U-Boot 1.1.6 (May 12 2009 - 07:52:28)

DRAM:  ar7100_ddr_initial_config(237) enter!
ar7100_ddr_initial_config(269) exit!


U-Boot 1.1.6 (May 12 2009 - 07:52:28)

AP81 (ar7100) U-boot
sri
32 MB
WRT160NL u-boot version: 1.0.0
Top of RAM usable for U-Boot at: 82000000
Reserving 279k for U-Boot at: 81fb8000
Reserving 192k for malloc() at: 81f88000
Reserving 44 Bytes for Board Info at: 81f87fd4
Reserving 36 Bytes for Global Data at: 81f87fb0
Reserving 128k for boot params() at: 81f67fb0
Stack Pointer at: 81f67f98
Now running in RAM - U-Boot at: 81fb8000
id read 0x100000ff
flash size 8MB, sector count = 128
Flash:  8 MB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag7100_enet_initialize...
ag7100 get ethaddr for device eth0
Fetching MAC Address from 0x81feb1e0

--------***** Get the RTL8306SD Manufactory ID=379c *****-------
Reg6: speed=0 nway=1 duplex=0
Reg5: speed=0 nway=0 duplex=0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0 a5=0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
Reg1: a1=7fd9 a2=30e0 a3=15ac a4=30e0
eth0: 00:25:9c:1a:28:a5
eth0 up
eth0
### main_loop entered: bootdelay=1

Hit any key to stop autoboot:  0
ar7100> bootwrt
## Booting WRT160NL ...
## Booting image at bf04003c ...
   Image Name:   MIPS OpenWrt Linux-2.6.30.9
   Created:      2009-11-16  19:09:19 UTC
   Image Type:   MIPS Linux Kernel Image (gzip compressed)
   Data Size:    1189939 Bytes =  1.1 MB
   Load Address: 80060000
   Entry Point:  80060000
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK
kernel: org len = 1189939, new len = 1245184
No initrd
## Transferring control to Linux (at address 80060000) ...
## Giving linux memsize in bytes, 33554432

Starting kernel ...

Linux version 2.6.30.9 (androsyn@salem) (collect2: ld returned 1 exit status) #1 Mon Nov 16 14:09:12 EST 2009
console [early0] enabled
CPU revision is: 00019374 (MIPS 24Kc)


And then it proceeds to boot correctly from there...It almost seems like a uboot bug..but I'm not quite sure...

-Aaron

362

Re: Wrt160nl?

brain0 wrote:
paulch wrote:

I've tried compiling my own, but my (Fedora 11) client machine totally locks up (i.e. needs a hard reboot!) while trying to connect via wireless.  Its fine via ethernet.  Its also fine from Windows - either wired or wireless!  Please, see my other post: https://forum.openwrt.org/viewtopic.php?id=22564

Then I guess your client machine is broken and should be fixed, not your image. No matter what your router sends, it should never be able to lock up your computer.

I've also got a Fedora (though 12, so new-ish kernel) laptop with an iwl3945 and see the same issue. There's no doubt this is a client driver issue, however it works with the stock 160NL firmware, so OpenWrt/hostapd must do something to trigger it. Anyway, that's what we get for running the alpha version of Red Hat Linux tongue

363 (edited by cssc 2009-11-17 09:03:29)

Re: Wrt160nl?

silverblade wrote:

However I do still appear to have the problem with my wireless connection dropping out. Again, the SSID remains visible, the other device (a HTC Magic phone) seems to think it is connected but there's no data transfer. If I disconnect and reconnect (don't need to reboot anything) it works again for a bit.

Other than that, it all seems to be working great.

I have precisely the same issue. When I start the wifi on my HTC Hero, it  connects just fine to my WRT160NL(still with the stock firmware..haven't got the time to put together a level shifter and gain serial access:/ ), the signal strength  indicates excellent, I can browse the net for some time and than all of a sudden - the connection is being lost. At the same time however, two other netbooks are connected via the same WRT160NL and have no connectivity issues.

The same HTC Hero works file with WRT54GL(v1.1).

The two routers(54GL and 160NL) does not share uplink,location or whatsoever the 160NL is at home and the 54GL is at the office

I would say that must be something related closely to the HTC firmware and/or possibly to the 160NL hardware..after all this only seem to happen when connecting an HTC(Android 1.5) phone via the WRT160NL!

It would be great if anyone can share any thoughts on this:)

364 (edited by paulch 2009-11-17 20:15:43)

Re: Wrt160nl?

brain0 wrote:

it should never be able to lock up your computer.

I totally agree, and this was exactly what I first thought (and why I posted on the Fedora forum too).  However, an OpenWRT router should also not send bad data, or perform in any strange non-standard way.  As my Fedora install works with all other routers I've ever tried (easily 10+), there also seems to be a problem on the OpenWRT end.

mark wrote:

I've also got a Fedora (though 12, so new-ish kernel) laptop with an iwl3945 and see the same issue. There's no doubt this is a client driver issue, however it works with the stock 160NL firmware, so OpenWrt/hostapd must do something to trigger it. Anyway, that's what we get for running the alpha version of Red Hat Linux tongue

... with an OpenWRT router!  There must be an issue on the OpenWRT side too - and I'm willing to put in some work to try and track it down.  So, can anyone point me in the direction of where to look for wireless logs on the OpenWRT server, and/or post some links to get me on track with how the OpenWRT brings the wireless up and accepts connections?  All I know is clientside!

EDIT:  Just had a reply from the Fedora people, saying its more likely to be a user configuration bug and maybe related to IPv6.  Here's the link to that forum topic: http://forums.fedoraforum.org/showthread.php?t=233917.

Thanks,
Paul.

Re: Wrt160nl?

paulch wrote:

EDIT:  Just had a reply from the Fedora people, saying its more likely to be a user configuration bug and maybe related to IPv6.  Here's the link to that forum topic: http://forums.fedoraforum.org/showthread.php?t=233917.

It's off-topic here, but I will still say it: That is pure bullshit. If your computer crashes or locks up, it is ALWAYS a kernel bug. Whatever you do to your computer, however you configure it, whatever device you connect it to, it must NEVER crash - and if it does it is by definition the kernel's fault.

Re: Wrt160nl?

So doing some more research, I think the people that have working openwrt on the WRT160NL have u-boot 1.1.5 and the newer devices (which don't work) have u-boot 1.1.6.  I looked at the Linksys site and found WRT160NL_1.00.01.17.tar.gz in their Open Source section, unfortunately this has my version of u-boot. 

Anybody have the u-boot 1.1.5 binary that I could downgrade to OR an older WRT160NL release from the linksys site?

Thanks!


wyngnut wrote:

Interesting...

Maybe its this specific version of U-Boot.  I notice that it doesn't have the saveenv command, but it does have the setenv command.

so I can also do
ar7100> setenv bootcmd bootwrt
ar7100> go

This works as well, but doesn't stick across power cycles.  Unfortunately it doesn't look like fw_printenv is in this version of openwrt and with no saveenv we can't set anything.

Ugh, one step closer though.

Re: Wrt160nl?

Anyone gotten the n wifi to work yet?
Had some issues with LuCI webinterface - loosing css on every second reload of a page etc. (cleared browser cache, tried 3 browsers, cleared /tmp files related to LuCI on the router, removed the packages through opkg, reininstalled them..) Switched to X-Wrt webif for now sad

368

Re: Wrt160nl?

crydee wrote:

Anyone gotten the n wifi to work yet?
Had some issues with LuCI webinterface - loosing css on every second reload of a page etc. (cleared browser cache, tried 3 browsers, cleared /tmp files related to LuCI on the router, removed the packages through opkg, reininstalled them..) Switched to X-Wrt webif for now sad

Not sure if this was what fixed it for me, but I switched to pre-compiled LUA in the LuCI config section (among with a bunch of other changes) and the problem seems to be gone. I can upload my config in case you want to compare other points to yours.

Re: Wrt160nl?

Hi Mark - if you could do that, it'd be great smile

Re: Wrt160nl?

wyngnut wrote:

So doing some more research, I think the people that have working openwrt on the WRT160NL have u-boot 1.1.5 and the newer devices (which don't work) have u-boot 1.1.6.

# strings /dev/mtdblock0 | grep U-Boot
U-Boot 1.1.5 (Apr  6 2009 - 13:54:11)

So I guess I am very luck then? This device is brand-new, maybe it has been in stock for a long time before I ordered it.

371

Re: Wrt160nl?

crydee wrote:

Hi Mark - if you could do that, it'd be great smile

Here you go: http://pastebin.com/f5cfa88a9

372

Re: Wrt160nl?

Hi guys, first I would like to thank vincentfox for early exploration with this device and to Kamikaze developers (specially juhosg and nbd for platform support and ath9k driver fixes respectively, and obviously big thanks to ath9k developers too!).

Just to report that 802.11N is working beatifully in this device, tested with an Asus EeePC 1000 with a Ralink 2860PCI device I get locked on 135Mbps and iperf of 80Mbps both ways using default config.

Restricting to 20Mhz channels and without fancy stuff (SHORT-GI-40 and DSSS_CCK-40) I get 50Mbps.
With plain 802.11g I get 25Mbps.

I transfer several GB of data and no mem leaks and rock solid.

Indeed great progress, thank you!

Re: Wrt160nl?

Hello, does OpenWRT currently support USB memories plugged to WRT160NL? Can they be shared to network?

Re: Wrt160nl?

lkaino wrote:

Hello, does OpenWRT currently support USB memories plugged to WRT160NL? Can they be shared to network?

By default, OpenWRT automatically mounts them when you plug them in, in case the filesystem driver is installed (I hate that and disable that in my builds). About sharing on the network, I plan to use lighttpd to allow downloads and use the USB storage as the document and file storage. I guess you could install samba or nfsd to share the files too.

Re: Wrt160nl?

brain0 wrote:
lkaino wrote:

Hello, does OpenWRT currently support USB memories plugged to WRT160NL? Can they be shared to network?

By default, OpenWRT automatically mounts them when you plug them in, in case the filesystem driver is installed (I hate that and disable that in my builds). About sharing on the network, I plan to use lighttpd to allow downloads and use the USB storage as the document and file storage. I guess you could install samba or nfsd to share the files too.

Soungs good, thanks for the info. I'm interested in running a bittorrent client in WRT160NL which would use the USB storage as a place to store the data. This way I wouldn't need to have otherwise unnecessary computer running.

Looking forward on running OpenWRT on my router smile.