OpenWrt Forum Archive

Topic: Wrt160nl?

The content of this topic has been archived between 9 Mar 2018 and 6 May 2018. Unfortunately there are posts – most likely complete pages – missing.

@memozny,

I have to admit, I have no 802.11N clients in my house only plain ABG.  Sorry I cannot help on this point, at this time.  I have ordered an Intel 5100 to put in my Samsung Q1 Ultra but it may be a week or two before I get around to installing it.

I have attempted to edit entry for WRT160NL following this template:

http://wiki.openwrt.org/inbox/trialtemplate

It's good to see some attempt to standardize the hardware pages.

Please contribute to this page:

http://wiki.openwrt.org/inbox/wrt160nl

(Last edited by vincentfox on 17 Aug 2009, 18:07)

I've also been able to get this up and running, but no luci webif for some reason!

Thanks!  I actually thought of this as well but the problem is that I don't have internet access through the router... yet.  I need to setup one of the ports as a bridge first to receive internet connection from another router that is acting as a client and receiving the connection via wireless.

jonisign wrote:

Thanks!  I actually thought of this as well but the problem is that I don't have internet access through the router... yet.  I need to setup one of the ports as a bridge first to receive internet connection from another router that is acting as a client and receiving the connection via wireless.

You can't just hook it up with an ethernet cable until you set it up?

Nope, I live next to a dorm at my university so I can only get internet through the wireless... One of my routers is in client mode and I'm trying to set this one to relay that signal via wireless...

It does not appear to me, that the failsafe mode is working.  I filed ticket 5727 about it.

I don't see that at least with snapshot of trunk 17264, that there is any module:

root@OpenWrt:~# cat /proc/devices
Character devices:
  1 mem
  4 ttyS
  5 /dev/tty
  5 /dev/console
  5 /dev/ptmx
 10 misc
 13 input
 90 mtd
108 ppp
128 ptm
136 pts

Block devices:
259 blkext
 31 mtdblock
root@OpenWrt:~#

I also see that power LED remains in blinking mode, filed ticket 5725 about that.

(Last edited by vincentfox on 19 Aug 2009, 08:59)

jonisign wrote:

I've also been able to get this up and running, but no luci webif for some reason!

Are you certain luci is installed?  What is in the /www directory?

vincentfox wrote:
jonisign wrote:

I've also been able to get this up and running, but no luci webif for some reason!

Are you certain luci is installed?  What is in the /www directory?

Luci always blocked my telnet/ssh access, the first admin password setting was always needed using Luci. I personally prefer this to xwrt.

Got it, thanks!

Hi

How can i start run my wireless network ?

nnuser wrote:

Hi

How can i start run my wireless network ?

Check the output of uci show wireless.

So my router showed up today. I did order the DKU-5B and it should be here in a day or two. I may mess around with getting the serial going over RJ45 in the next day.
Currently running the stock firmware. Can't wait to get Kamikaze on this thing!

So it looks like the snapshot build is safe to upload from a stock firmware via the Web GUI? Dare I do it before I get the serial hooked up? smile

- SMiTTY

(Last edited by SMiTTY on 20 Aug 2009, 04:10)

Trunk r17324 fixed (by juhosg) the issue with power LED.

Still no working failsafe mode.

Serial is always recommended I don't think there's any "rescue" tricks you can do.  See the Broadcom platforms had a window during bootloader where it would accept TFTP so you could always fix it if you tried a number of times even without serial.

Poking around with GPIO now will post again a bit later when I have buttons doing something....

(Last edited by vincentfox on 20 Aug 2009, 06:51)

So it looks like at present the trunk doesn't know the buttons as RESET or SES/WPS just as BTN_0 and BTN_1.
I created a script for fun to test pushing the buttons:

mkdir /etc/hotplug.d/button
cd /etc/hotplug.d/button
touch 00-test
chmod 755 00-test
vi 00-test

The script contained this simple code:

if [ "$BUTTON" = "BTN_0" ]; then
        if [ "$ACTION" = "pressed" ]; then
                echo "pressed reset">>/tmp/button
        fi
elif [ "$BUTTON" = "BTN_1" ]; then
        if [ "$ACTION" = "pressed" ]; then
                echo "pressed wps">>/tmp/button
        fi
fi

Then I just ran tail -f /tmp/button and could watch the results.

I cannot work out how to make the LED change state, there is no /proc/diag directory.

(Last edited by vincentfox on 20 Aug 2009, 07:43)

Ah OK starting to work out the LED business, structured under /sys/class/leds there are subdirectories for each LED.  You can set triggers and brightness of LED etc.   Simplest example:

root@OpenWrt:/sys/devices/platform/leds-gpio/leds/wrt160nl:blue:power# pwd
/sys/class/leds/wrt160nl:blue:power
root@OpenWrt:/sys/devices/platform/leds-gpio/leds/wrt160nl:blue:power# ls
brightness      max_brightness  trigger
device          subsystem       uevent
root@OpenWrt:/sys/devices/platform/leds-gpio/leds/wrt160nl:blue:power# echo "0" > brightness

This makes the power LED blink since that is it's "off" state.

vincentfox wrote:

Ah OK starting to work out the LED business, structured under /sys/class/leds there are subdirectories for each LED.  You can set triggers and brightness of LED etc.   Simplest example:

root@OpenWrt:/sys/devices/platform/leds-gpio/leds/wrt160nl:blue:power# pwd
/sys/class/leds/wrt160nl:blue:power
root@OpenWrt:/sys/devices/platform/leds-gpio/leds/wrt160nl:blue:power# ls
brightness      max_brightness  trigger
device          subsystem       uevent
root@OpenWrt:/sys/devices/platform/leds-gpio/leds/wrt160nl:blue:power# echo "0" > brightness

This makes the power LED blink since that is it's "off" state.

Setting brightness would be very nice. Those blue LED's are BRIGHT in my bedroom at night. LOL!!! My wife always complains. :-P

vincentfox wrote:
nnuser wrote:

Hi

How can i start run my wireless network ?

Check the output of uci show wireless.

Can you tell me step-by-step how can i start my Access Point.

nnuser wrote:

Can you tell me step-by-step how can i start my Access Point.

Cut and paste the output of "uci show wireless" and I'd be willing to step through it from that.

mordak wrote:

Setting brightness would be very nice. Those blue LED's are BRIGHT in my bedroom at night. LOL!!! My wife always complains. :-P

On is 255.  I didn't test whether intermediate values would dim it, but I suspect not.
You could easily enough write a script so when you press the WPS button on top it
turns off the power LED though.

vincentfox wrote:
nnuser wrote:

Can you tell me step-by-step how can i start my Access Point.

Cut and paste the output of "uci show wireless" and I'd be willing to step through it from that.

root@OpenWrt:~# uci show wireless
root@OpenWrt:~#

nnuser wrote:

root@OpenWrt:~# uci show wireless
root@OpenWrt:~#

What firmware did you install? A snapshot or self-compiled?  I got this result once when I installed a firmware of my own that lacked wireless modules.

Here's what output should look like (roughly):

root@hazel:~# uci show wireless
wireless.wlan0=wifi-device
wireless.wlan0.type=mac80211
wireless.wlan0.disabled=0
wireless.wlan0.channel=6
wireless.@wifi-iface[0]=wifi-iface
wireless.@wifi-iface[0].device=wlan0
wireless.@wifi-iface[0].network=lan
wireless.@wifi-iface[0].mode=ap
wireless.@wifi-iface[0].ssid=MYSSID
wireless.@wifi-iface[0].encryption=psk2
wireless.@wifi-iface[0].key=BLAHBLAH

Which I set values I need with "uci set (blah)" followed by "uci commit".
If you have no file in /etc/config/wireless I suspect you don't have the
modules for WiFi.  Do you even have the device itself?  Look at kernel
boot messages with dmesg, or at ifconfig -a

(Last edited by vincentfox on 20 Aug 2009, 17:39)

nnuser wrote:
vincentfox wrote:
nnuser wrote:

Can you tell me step-by-step how can i start my Access Point.

Cut and paste the output of "uci show wireless" and I'd be willing to step through it from that.

root@OpenWrt:~# uci show wireless
root@OpenWrt:~#

I have the same problem. Using kamikaze r17250.

Got my USB-> Serial today. Says CA-42 on the USB side. I imagine I just cut the other end off and find TX, RX and ground?

My Linux laptop sees it.

[  328.585430] pl2303 2-2:1.0: pl2303 converter detected
[  328.596765] usb 2-2: pl2303 converter now attached to ttyUSB0
[  328.596788] usbcore: registered new interface driver pl2303
[  328.596791] pl2303: Prolific PL2303 USB to serial adaptor driver


- SMiTTY

(Last edited by SMiTTY on 21 Aug 2009, 00:39)