Topic: D-Link DIR-600 A1 or Frys FR-54RTR

I'm new to OpenWRT.

I spent the last couple days playing with it, and I want to share my findings
about the Frys Wireless G Router (FR-54RTR) which is a rebadged D-Link
DIR-600 A1.  (The FCC ID is KA2DIR600A1.)

I started by upgrading the firmware to the 1.01 version released by D-Link.
(I'm not sure if this step can be skipped.)

ftp://ftp.dlink.com/Gateway/dir600/Firmware/dir600_firmware_101NA.zip

To install the D-Link firmware, I performed the 30-30-30 reset which
exposed the "D-LINK Firmware Upgrade System" on http://192.168.0.1/

After uploading the 1.01 firmware via the firmware upgrade pages,
I was able to update the firmware to a snapshot of OpenWRT from
http://downloads.openwrt.org/snapshots/trunk/ar71xx/

I used the snapshot from "09-Feb-2010 11:37":
openwrt-ar71xx-dir-600-a1-squashfs-universal.bin

The one problem I couldn't get past is that the driver for eth1 (ag71xx) kept
crashing on me when I tried to upload more than a few KBytes of data to the
WAN.  I'm hoping this is the same issue being diagnosed on the Mikrotik
RB450G.

This crash would require a reboot to clear.

ar71xx-wdt: enabling watchdog timer
------------[ cut here ]------------
WARNING: at net/sched/sch_generic.c:261 0x801f8674()
NETDEV WATCHDOG: eth1 (ag71xx): transmit queue 0 timed out
Modules linked in: nf_nat_tftp nf_conntrack_tftp nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ipt_MASQUERADE iptable_nat nf_nat xt_NOTRACK iptable_raw xt_state nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack pppoe pppox ipt_REJECT xt_TCPMSS ipt_LOG xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables ppp_async ppp_generic slhc crc_ccitt leds_gpio button_hotplug gpio_buttons input_polldev input_core
Call Trace:[<80068304>] 0x80068304
[<80068304>] 0x80068304
[<8007cc98>] 0x8007cc98
[<801f8674>] 0x801f8674
[<8007cd18>] 0x8007cd18
[<801e3dbc>] 0x801e3dbc
[<801f8674>] 0x801f8674
[<8009549c>] 0x8009549c
[<8007a3a4>] 0x8007a3a4
[<801f8510>] 0x801f8510
[<80087380>] 0x80087380
[<80070b24>] 0x80070b24
[<800824bc>] 0x800824bc
[<8008259c>] 0x8008259c
[<8006082c>] 0x8006082c
[<80091b00>] 0x80091b00
[<80060a00>] 0x80060a00
[<8006b59c>] 0x8006b59c
[<8006c8fc>] 0x8006c8fc
[<80060a20>] 0x80060a20
[<802cda48>] 0x802cda48
[<802cd3a8>] 0x802cd3a8

When running the D-Link firmware, I would have file transfers
to the WAN stall after a couple hundred meg.  The transfer would
die, but I didn't need to reboot the router for new connections
to work.

Otherwise, the performance of OpenWRT seemed to be on par with
the D-Link.

================================================================================
Performance numbers

For each test I transferred about 100-200 MB at a time with SCP.
Numbers are just to show that other than uploads to WAN,
performance was comparable.

OpenWRT firmware KAMIKAZE (bleeding edge, r19557)

1.9 MB/s download (from wan) wireless 11ng (g) - 40-50% util
2.7 MB/s download (from lan) wireless 11ng (g) - 40-50% util
2.7 MB/s upload (to lan) wireless 11ng (g) - 30-40% util

6.1 MB/s  switch (port 1 to 3)
10.5 MB/s download (from wan) (80% CPU utilization)

D-Link firmware 1.01NA

1.9 MB/s download (from wan) wireless 11ng (g)
2.6 MB/s upload (to wan) wireless 11ng (g)
    transferred 1635MB in 10:35; didn't stall

2.7 MB/s download (from lan) wireless 11ng (g)
2.5 MB/s upload (to lan) wireless 11ng (g)

2.7 MB/s download (from lan) wireless 11ng (g) WPA2-AES
2.5 MB/s upload (to lan) wireless 11ng (g) WPA2-AES

5.4 MB/s  switch (port 1 to 4)
5.7 MB/s  switch (port 1 to 3)
8.6 MB/s download (from wan)
11 MB/s [until it stalls] upload (to wan)
================================================================================

Linux version 2.6.32.7 (buildbot@faraday) (gcc version 4.3.3 (GCC) ) #1 Tue Feb 9 11:34:20 UTC 2010
prom: fw_arg0=00000007, fw_arg1=a1f6ffb0, fw_arg2=a1f70460, fw_arg3=00000004
MyLoader: sysp=bf005e00, boardp=df00d700, parts=b007700f
bootconsole [early0] enabled
CPU revision is: 00019374 (MIPS 24Kc)
Atheros AR7240 rev 2, CPU:350.000 MHz, AHB:175.000 MHz, DDR:350.000 MHz
Determined physical RAM map:
 memory: 02000000 @ 00000000 (usable)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
  Normal   0x00000000 -> 0x00002000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0: 0x00000000 -> 0x00002000
On node 0 totalpages: 8192
free_area_init_node: node 0, pgdat 802cba80, node_mem_map 81000000
  Normal zone: 64 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 8128 pages, LIFO batch:0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
Kernel command line: rootfstype=squashfs,yaffs,jffs2 noinitrd console=ttyS0,115200 board=DIR-600-A1 mtdparts=spi0.0:192k(u-boot)ro,64k(nvram)ro,896k(kernel),2816k(rootfs),64k(mac)ro,64k(art)ro,3712k@0x40000(firmware)
PID hash table entries: 128 (order: -3, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Writing ErrCtl register=00000000
Readback ErrCtl register=00000000
Memory: 29348k/32768k available (2090k kernel code, 3420k reserved, 390k data, 152k init, 0k highmem)
SLUB: Genslabs=7, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Hierarchical RCU implementation.
NR_IRQS:56
Calibrating delay loop... 232.65 BogoMIPS (lpj=1163264)
Mount-cache hash table entries: 512
devtmpfs: initialized
NET: Registered protocol family 16
MIPS: machine is D-Link DIR-600 rev. A1
registering PCI controller with io_map_base unset
bio: create slab <bio-0> at 0
PCI: fixup device 0000:00:00.0
pci 0000:00:00.0: reg 10 64bit mmio: [0x000000-0x00ffff]
pci 0000:00:00.0: supports D1
pci 0000:00:00.0: PME# supported from D0 D1 D3hot
pci 0000:00:00.0: PME# disabled
PCI: mapping irq 48 to pin1@0000:00:00.0
Switching to clocksource MIPS
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
NET: Registered protocol family 1
squashfs: version 4.0 (2009/01/31) Phillip Lougher
Registering mini_fo version $Id$
JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
yaffs Feb  9 2010 11:29:43 Installing. 
msgmni has been set to 57
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
console [ttyS0] enabled, bootconsole disabled
Atheros AR71xx SPI Controller driver version 0.2.4
m25p80 spi0.0: w25x32 (4096 Kbytes)
7 cmdlinepart partitions found on MTD device spi0.0
Creating 7 MTD partitions on "spi0.0":
0x000000000000-0x000000030000 : "u-boot"
0x000000030000-0x000000040000 : "nvram"
0x000000040000-0x000000120000 : "kernel"
0x000000120000-0x0000003e0000 : "rootfs"
mtd: partition "rootfs" set to be root filesystem
mtd: partition "rootfs_data" created automatically, ofs=249000, len=197000 
0x000000249000-0x0000003e0000 : "rootfs_data"
0x0000003e0000-0x0000003f0000 : "mac"
0x0000003f0000-0x000000400000 : "art"
0x000000040000-0x0000003e0000 : "firmware"
ag71xx_mdio: probed
eth0: Atheros AG71xx at 0xba000000, irq 5
eth1: Atheros AG71xx at 0xb9000000, irq 4
Atheros AR71xx hardware watchdog driver version 0.1.0
ar71xx-wdt: timeout=15 secs (max=24)
TCP westwood registered
NET: Registered protocol family 17
Bridge firewalling registered
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
devtmpfs: mounted
Freeing unused kernel memory: 152k freed
gpio-buttons driver version 0.1.2
input: gpio-buttons as /devices/platform/gpio-buttons/input/input0
Button Hotplug driver version 0.3.1
eth0: link up (1000Mbps/Full duplex)
Registered led device: dir-600-a1:green:power
Registered led device: dir-600-a1:amber:power
Registered led device: dir-600-a1:blue:wps
mini_fo: using base directory: /
mini_fo: using storage directory: /jffs
eth0: link down
eth0: link up (1000Mbps/Full duplex)
device eth0 entered promiscuous mode
br-lan: port 1(eth0) entering forwarding state
eth1: link up (100Mbps/Full duplex)
PPP generic driver version 2.4.2
ip_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 24
nf_conntrack version 0.5.0 (460 buckets, 1840 max)
CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
ar71xx-wdt: enabling watchdog timer
root@OpenWrt:/# cat /proc/cpuinfo 
system type             : Atheros AR7240 rev 2
machine                 : D-Link DIR-600 rev. A1
processor               : 0
cpu model               : MIPS 24Kc V7.4
BogoMIPS                : 232.65
wait instruction        : yes
microsecond timers      : yes
tlb_entries             : 16
extra interrupt vector  : yes
hardware watchpoint     : yes, count: 4, address/irw mask: [0x0000, 0x0168, 0x0af0, 0x09c8]
ASEs implemented        : mips16
shadow register sets    : 1
core                    : 0
VCED exceptions         : not available
VCEI exceptions         : not available

root@OpenWrt:/# cat /proc/meminfo 
MemTotal:          29500 kB
MemFree:           18484 kB
Buffers:            1032 kB
Cached:             3644 kB
SwapCached:            0 kB
Active:             3680 kB
Inactive:           2432 kB
Active(anon):       1496 kB
Inactive(anon):        0 kB
Active(file):       2184 kB
Inactive(file):     2432 kB
Unevictable:           0 kB
Mlocked:               0 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:          1448 kB
Mapped:              876 kB
Shmem:                60 kB
Slab:               3248 kB
SReclaimable:        764 kB
SUnreclaim:         2484 kB
KernelStack:         240 kB
PageTables:          184 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:       14748 kB
Committed_AS:       3744 kB
VmallocTotal:    1048372 kB
VmallocUsed:         612 kB
VmallocChunk:    1041148 kB
root@OpenWrt:/# 

root@OpenWrt:/tmp# lspci 
00:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)

Re: D-Link DIR-600 A1 or Frys FR-54RTR

I upgraded to 2/17/2010's snapshot and was still seeing the same problems. (r19655)

On the DD-WRT board, chirho mentioned that he wasn't having problems with
the WAN port, so I started playing around with different settings.
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=410466#410466

First, because my router was between 2 machines that do GigE, I put
10/100 switches on both sides, but that didn't fix anything.

Then I tried playing with a simple tc htb setup and was able to constrain
traffic to 50Kbps (with an rsync backup over ssh) for hours.

Finally, I started playing with MTU.  I found that if I set MTU between 1440
and 1500, I could crash the wan interface with a ping flood where packet data
== MTU.  I have seen it crash under a ping flood between 1410 and 1440.

I have not yet seen it crash due to a ping flood at 1400, but I did just
crash it with an scp session.  With scp I'm stressing it by copying a 1.5 GB
file repeatedly at about 10.5 MB/s.  This seems to put the cpu at about 95%
utilization; most of it in "sirq".

If I then rate limit it to 5 MB/s with a simple tc htb setup like below,
processor utilization hovers around 60% (nearly all "sirq").

opkg install tc_2.6.29-1-1_ar71xx.ipk 
opkg install kmod-sched_2.6.32.8-1_ar71xx.ipk 

# the rest of this would work well in /etc/rc.local
insmod /lib/modules/2.6.32.8/sch_htb.ko
INTERFACE=eth1
RATE=5MBps
tc qdisc del dev $INTERFACE root
tc qdisc add dev $INTERFACE root handle 1: htb default 1
tc class add dev $INTERFACE parent 1: classid 1:1 htb rate $RATE ceil $RATE

To set MTU, edit /etc/config/network, add the line, "option mtu      1400"
under "config interface wan". 

Then reboot.  The wan interface just seems to hang if you change the MTU on
the WAN and just by issue "/etc/init.d/network restart".

Re: D-Link DIR-600 A1 or Frys FR-54RTR

Currently (05/14/2010 - 05/18/2010), Fry's Electronics is celbrating its 25th Anniversary and has this FR-54RTR router onsale for $12. Hopefully, more people will get this device to hack with OpenWRT to resolve the issue faster.

Mazi

Re: D-Link DIR-600 A1 or Frys FR-54RTR

monte wrote:

After uploading the 1.01 firmware via the firmware upgrade pages,
I was able to update the firmware to a snapshot of OpenWRT from
http://downloads.openwrt.org/snapshots/trunk/ar71xx/

I used the snapshot from "09-Feb-2010 11:37":
openwrt-ar71xx-dir-600-a1-squashfs-universal.bin

Hmmm ..., interestingly I could not locate the openwrt-ar71xx-dir-600-a1-squashfs-universal.bin firmware from the above link. Can you please confirm this?

OTOH, I compiled my own AR7 firmware and here is the list of generated firmware with no openwrt-ar71xx-dir-600-a1-squashfs-universal.bin firmware:

openwrt-ar71xx-generic-dir-600-a1-jffs2-factory.bin
openwrt-ar71xx-generic-dir-600-a1-jffs2-sysupgrade.bin
openwrt-ar71xx-generic-dir-600-a1-squashfs-factory.bin
openwrt-ar71xx-generic-dir-600-a1-squashfs-sysupgrade.bin
openwrt-ar71xx-generic-rootfs.tar.gz
openwrt-ar71xx-generic-root.jffs2-128k
openwrt-ar71xx-generic-root.jffs2-64k
openwrt-ar71xx-generic-root.squashfs
openwrt-ar71xx-generic-root.squashfs-4k
openwrt-ar71xx-generic-uImage-gzip.bin
openwrt-ar71xx-generic-uImage-lzma.bin
openwrt-ar71xx-generic-vmlinux.bin
openwrt-ar71xx-generic-vmlinux.elf
openwrt-ar71xx-generic-vmlinux.gz
openwrt-ar71xx-generic-vmlinux.lzma
Mazi

Re: D-Link DIR-600 A1 or Frys FR-54RTR

mazilo wrote:

Hmmm ..., interestingly I could not locate the openwrt-ar71xx-dir-600-a1-squashfs-universal.bin firmware from the above link. Can you please confirm this?

If you are loading via the emergency D-Link boot loader (30-30-30 reset) you should use this one:
openwrt-ar71xx-generic-dir-600-a1-squashfs-factory.bin

I'm not sure when they changed names.

Re: D-Link DIR-600 A1 or Frys FR-54RTR

monte wrote:
mazilo wrote:

Hmmm ..., interestingly I could not locate the openwrt-ar71xx-dir-600-a1-squashfs-universal.bin firmware from the above link. Can you please confirm this?

If you are loading via the emergency D-Link boot loader (30-30-30 reset) you should use this one:
openwrt-ar71xx-generic-dir-600-a1-squashfs-factory.bin

Thanks. I tried that firmware and looks like it bricked my device. OTOH, when I flashed my unit with a self-built OpenWRT from SVN trunk, the device didn't behave very stable and traffics through WAN got blocked after an hour or so up running. Also, I have noticed no httpd daemon through the ps utility. Looks like there is much need be done before this device will run OpenWRT.

Mazi

Re: D-Link DIR-600 A1 or Frys FR-54RTR

I used the built-in web interface on the FR-54RTR to update it to http://downloads.openwrt.org/backfire/10.03/ar71xx/openwrt-ar71xx-fr-54rtr-squashfs-factory.bin

it rebooted and passes traffic just fine.  the LEDs do not work, but that's OK.

the FR-54RTR rocks!  on sale for $12, it has 32MB RAM, 4MB flash, a serial port, and maybe I can use the GPIOs on the LEDs for something else.

Re: D-Link DIR-600 A1 or Frys FR-54RTR

there is a wqy to flash the W25x32vf?, got it brick too

Re: D-Link DIR-600 A1 or Frys FR-54RTR

cls wrote:

I used the built-in web interface on the FR-54RTR to update it to http://downloads.openwrt.org/backfire/10.03/ar71xx/openwrt-ar71xx-fr-54rtr-squashfs-factory.bin

An interesting about this FR-54RTR firmware is there is nowhere to be found on OpenWRT SVN trunk, yet. Perhaps, developers have not updated the SVN trunk to include a support for FR-54RTR router.

Mazi

Re: D-Link DIR-600 A1 or Frys FR-54RTR

The problem with "NETDEV WATCHDOG: eth1 (ag71xx): transmit queue 0 timed out" can be fixed by setting MTU to 1400 on wan port:

vi /etc/config/network

in the "config interface wan" add    
option mtu    1400

I've found this solution from http://wiki.openwrt.org/toh/tp-link/tl-wr941nd and it worked perfectly for me.

Re: D-Link DIR-600 A1 or Frys FR-54RTR

koolcho wrote:

The problem with "NETDEV WATCHDOG: eth1 (ag71xx): transmit queue 0 timed out" can be fixed by setting MTU to 1400 on wan port:
.

It doesn't make the problem go away; it just makes it much less likely to occur.

Re: D-Link DIR-600 A1 or Frys FR-54RTR

Today, I did an SVN update to r21517 to my local OpenWRT SVN source. I did a make menuconfig to include uhttp + LuCI packages. Then, I successfully compiled/installed the OpenWRT SVN firmware to my FR-54RTR WiFi router. Now, my FR-54RTR WiFi router is up running with a LuCI GUI. The reason I included GUI is I want to configure this WiFi router as a client so that it can be used by my friend to connect to a WiFi server provided by the apartment complex where she currently is a tenant. If anyone out here knows how to configure a WiFi router do achieve this task, I sure will appreciate some helps on this.

Mazi

Re: D-Link DIR-600 A1 or Frys FR-54RTR

mazilo wrote:

The reason I included GUI is I want to configure this WiFi router as a client so that it can be used by my friend to connect to a WiFi server provided by the apartment complex where she currently is a tenant. If anyone out here knows how to configure a WiFi router do achieve this task, I sure will appreciate some helps on this.

I posted notes on how to do this on dd-wrt.com's forums a while back (using OpenWrt).

http://www.dd-wrt.com/phpBB2/viewtopic. … p;start=30

I haven't checked to see if the dhcp issue mentioned in the post has been fixed.

I wanted to try this out myself...

opkg update
opkg install wpa-supplicant


/etc/config/wireless:

config wifi-device  radio0
        option type     mac80211
        option channel  auto
        option macaddr  00:26:5a:ce:6c:63
        option hwmode   11g
#       option htmode   HT20
#       list ht_capab   SHORT-GI-40
#       list ht_capab   DSSS_CCK-40
        # REMOVE THIS LINE TO ENABLE WIFI:
        option disabled 0

config wifi-iface
        option device   radio0
        option network  wan
        option mode     sta
        option ssid     AccessPointSSID
        option encryption psk
        option key      'example password'

I set channel to "auto", but you can probably hardcode it.
Change network to "wan".
Change mode to "sta". (It's short for "station".)
Change ssid to the ssid of the access point you wish to talk to.

I noticed problems with wireless coming up (as a client)
when using dhcp; I found no problems when I set it to static.

If you do this, you need to set ifname to wlan0, otherwise
routing will be messed up. The DNS server I chose is one
of Google's open DNS servers.

/etc/config/network:

config 'interface' 'wan'
        option 'ifname' 'wlan0'
        option 'macaddr' '00265ACE6C64'
        option 'proto' 'static'
        option 'mtu' '1400'
        option 'ipaddr' '192.168.7.10'
        option 'netmask' '255.255.255.0'
        option 'gateway' '192.168.7.1'
        option 'dns' '8.8.4.4'

14 (edited by mazilo 2010-05-25 00:59:24)

Re: D-Link DIR-600 A1 or Frys FR-54RTR

monte wrote:

I haven't checked to see if the dhcp issue mentioned in the post has been fixed.

I wanted to try this out myself...

opkg update
opkg install wpa-supplicant


/etc/config/wireless:

config wifi-device  radio0
        option type     mac80211
        option channel  auto
        option macaddr  00:26:5a:ce:6c:63
        option hwmode   11g
#       option htmode   HT20
#       list ht_capab   SHORT-GI-40
#       list ht_capab   DSSS_CCK-40
        # REMOVE THIS LINE TO ENABLE WIFI:
        option disabled 0

config wifi-iface
        option device   radio0
        option network  wan
        option mode     sta
        option ssid     AccessPointSSID
        option encryption psk
        option key      'example password'

I set channel to "auto", but you can probably hardcode it.
Change network to "wan".
Change mode to "sta". (It's short for "station".)
Change ssid to the ssid of the access point you wish to talk to.

I noticed problems with wireless coming up (as a client)
when using dhcp; I found no problems when I set it to static.

If you do this, you need to set ifname to wlan0, otherwise
routing will be messed up. The DNS server I chose is one
of Google's open DNS servers.

/etc/config/network:

config 'interface' 'wan'
        option 'ifname' 'wlan0'
        option 'macaddr' '00265ACE6C64'
        option 'proto' 'static'
        option 'mtu' '1400'
        option 'ipaddr' '192.168.7.10'
        option 'netmask' '255.255.255.0'
        option 'gateway' '192.168.7.1'
        option 'dns' '8.8.4.4'

I have no idea how you managed to get the above scripts working on an FR-54RTR WiFi router flashed with an OpenWRT BackFire firmware. When I tried it, there is no WiFi as shown below ( the output from ifconfig showed no wlan0 device):

Connected to 192.168.1.1.
Escape character is '^]'.
 === IMPORTANT ============================
  Use 'passwd' to set your login password
  this will disable telnet and enable SSH
 ------------------------------------------


BusyBox v1.15.3 (2010-04-06 03:14:11 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 Backfire (10.03, r20728) --------------------------
  * 1/3 shot Kahlua    In a shot glass, layer Kahlua 
  * 1/3 shot Bailey's  on the bottom, then Bailey's, 
  * 1/3 shot Vodka     then Vodka.
 ---------------------------------------------------
root@OpenWrt:/# ifconfig
br-lan    Link encap:Ethernet  HWaddr 00:26:5A:F4:6C:14  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:86 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:5193 (5.0 KiB)  TX bytes:4412 (4.3 KiB)

eth0      Link encap:Ethernet  HWaddr 00:26:5A:F4:6C:14  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:96 errors:0 dropped:0 overruns:0 frame:0
          TX packets:41 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7417 (7.2 KiB)  TX bytes:5615 (5.4 KiB)
          Interrupt:5 

lan1      Link encap:Ethernet  HWaddr 00:26:5A:F4:6C:14  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:96 errors:0 dropped:0 overruns:0 frame:0
          TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:5689 (5.5 KiB)  TX bytes:4572 (4.4 KiB)

lan2      Link encap:Ethernet  HWaddr 00:26:5A:F4:6C:14  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lan3      Link encap:Ethernet  HWaddr 00:26:5A:F4:6C:14  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lan4      Link encap:Ethernet  HWaddr 00:26:5A:F4:6C:14  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@OpenWrt:/#

Here is the output from opkg list that shows all packages installed on my FT-54RTR WiFi router:

root@OpenWrt:/# opkg list
base-files - 42-r20728
busybox - 1.15.3-2
crda - 1.1.0-2
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-nat - 1.4.6-2
iw - 0.9.19-1
kernel - 2.6.32.10-1
kmod-button-hotplug - 2.6.32.10-1
kmod-cfg80211 - 2.6.32.10+2010-03-24-5
kmod-crc-ccitt - 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-input-core - 2.6.32.10-1
kmod-input-gpio-buttons - 2.6.32.10-1
kmod-input-polldev - 2.6.32.10-1
kmod-ipt-conntrack - 2.6.32.10-1
kmod-ipt-core - 2.6.32.10-1
kmod-ipt-nat - 2.6.32.10-1
kmod-ipt-nathelper - 2.6.32.10-1
kmod-leds-gpio - 2.6.32.10-1
kmod-mac80211 - 2.6.32.10+2010-03-24-5
kmod-ppp - 2.6.32.10-1
kmod-pppoe - 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
libnl-tiny - 0.1-1
libuci - 12012009.5-1
libuci-lua - 12012009.5-1
libxtables - 1.4.6-2
lua - 5.1.4-6
luci - 0.9.0-1
luci-admin-core - 0.9.0-1
luci-admin-full - 0.9.0-1
luci-admin-mini - 0.9.0-1
luci-app-firewall - 0.9.0-1
luci-app-initmgr - 0.9.0-1
luci-cbi - 0.9.0-1
luci-core - 0.9.0-1
luci-http - 0.9.0-1
luci-i18n-english - 0.9.0-1
luci-ipkg - 0.9.0-1
luci-lmo - 0.9.0-1
luci-nixio - 0.9.0-1
luci-sgi-cgi - 0.9.0-1
luci-sys - 0.9.0-1
luci-theme-base - 0.9.0-1
luci-theme-openwrt - 0.9.0-1
luci-uci - 0.9.0-1
luci-uvl - 0.9.0-1
luci-web - 0.9.0-1
mtd - 12
opkg - 513-2
ppp - 2.4.4-5
ppp-mod-pppoe - 2.4.4-5
swconfig - 5
uci - 12012009.5-1
udevtrigger - 106-1
uhttpd - 7
wireless-tools - 29-4
wpa-supplicant - 20100309-1
root@OpenWrt:/#

Failing that, I compiled my own and flashed the OpenWRT SVN firmware to my FR-54RTR WiFi router to find out the same problem.

Mazi

15 (edited by mazilo 2010-05-25 01:00:09)

Re: D-Link DIR-600 A1 or Frys FR-54RTR

Now that I reflashed my FR-54RTR unit with a self-built OpenWRT SVN firmware + the /etc/config/network + /etc/config/wireless files from you, the output of ifconfig has shown the wlan0 hardware; however, my device still can't find out any WiFi signals, even it is sitting on the same table next to a WiFi router source. At the moment, I am completely clueless. sad

Connected to 192.168.1.1.
Escape character is '^]'.
 === IMPORTANT ============================
  Use 'passwd' to set your login password
  this will disable telnet and enable SSH
 ------------------------------------------


BusyBox v1.16.1 (2010-05-20 21:09:28 EDT) built-in shell (ash)
Enter 'help' for a list of built-in commands.

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 KAMIKAZE (bleeding edge, r21517) ------------------
  * 10 oz Vodka       Shake well with ice and strain
  * 10 oz Triple sec  mixture into 10 shot glasses.
  * 10 oz lime juice  Salute!
 ---------------------------------------------------
root@OpenWrt:/# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                 2048      2048         0 100% /rom
tmpfs                    14772        52     14720   0% /tmp
tmpfs                      512         0       512   0% /dev
root                      2048      2048         0 100% /tmp/root
mini_fo:/tmp/root         2048      2048         0 100% /tmp/root
/dev/mtdblock4             852        64       788   8% /overlay
mini_fo:/overlay          2048      2048         0 100% /
root@OpenWrt:/# ifconfig
br-lan    Link encap:Ethernet  HWaddr 00:26:5A:F4:6C:14  
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10164 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6310 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:632622 (617.7 KiB)  TX bytes:633386 (618.5 KiB)

eth0      Link encap:Ethernet  HWaddr 00:26:5A:F4:6C:14  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10176 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6311 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:816432 (797.2 KiB)  TX bytes:659669 (644.2 KiB)
          Interrupt:5 

lan1      Link encap:Ethernet  HWaddr 00:26:5A:F4:6C:14  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:10176 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6310 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:633264 (618.4 KiB)  TX bytes:658626 (643.1 KiB)

lan2      Link encap:Ethernet  HWaddr 00:26:5A:F4:6C:14  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lan3      Link encap:Ethernet  HWaddr 00:26:5A:F4:6C:14  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lan4      Link encap:Ethernet  HWaddr 00:26:5A:F4:6C:14  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr 00:26:5A:F4:6C:14  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

root@OpenWrt:/#
Mazi

Re: D-Link DIR-600 A1 or Frys FR-54RTR

mazilo wrote:

Now that I reflashed my FR-54RTR unit with a self-built OpenWRT SVN firmware + the /etc/config/network + /etc/config/wireless files from you, the output of ifconfig has shown the wlan0 hardware; however, my device still can't find out any WiFi signals, even it is sitting on the same table next to a WiFi router source. At the moment, I am completely clueless. sad

Sorry, I'm not really setup to troubleshoot at the moment.

Is there anything in the output from logread?

Also, what happens if you issue "wifi down", then "wifi up"?

Re: D-Link DIR-600 A1 or Frys FR-54RTR

monte wrote:
mazilo wrote:

Now that I reflashed my FR-54RTR unit with a self-built OpenWRT SVN firmware + the /etc/config/network + /etc/config/wireless files from you, the output of ifconfig has shown the wlan0 hardware; however, my device still can't find out any WiFi signals, even it is sitting on the same table next to a WiFi router source. At the moment, I am completely clueless. sad

Sorry, I'm not really setup to troubleshoot at the moment.

At least, you are doing better than me. I don't use any WiFi. So, my knowledge on WiFi is 0.

Is there anything in the output from logread?

The following is the excerpt from logread.

root@OpenWrt:/# logread
May 24 17:25:00 OpenWrt syslog.info syslogd started: BusyBox v1.16.1
May 24 17:25:00 OpenWrt user.info kernel: squashfs: version 4.0 (2009/01/31) Phillip Lougher
May 24 17:25:00 OpenWrt user.warn kernel: Registering mini_fo version $Id$
May 24 17:25:00 OpenWrt user.info kernel: JFFS2 version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
May 24 17:25:00 OpenWrt user.info kernel: msgmni has been set to 57
May 24 17:25:00 OpenWrt user.info kernel: io scheduler noop registered
May 24 17:25:00 OpenWrt user.info kernel: io scheduler deadline registered (default)
May 24 17:25:00 OpenWrt user.info kernel: Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
May 24 17:25:00 OpenWrt user.info kernel: serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
May 24 17:25:00 OpenWrt user.info kernel: console [ttyS0] enabled, bootconsole disabled
May 24 17:25:00 OpenWrt user.info kernel: loop: module loaded
May 24 17:25:00 OpenWrt user.info kernel: Atheros AR71xx SPI Controller driver version 0.2.4
May 24 17:25:00 OpenWrt user.info kernel: m25p80 spi0.0: w25x32 (4096 Kbytes)
May 24 17:25:00 OpenWrt user.notice kernel: 7 cmdlinepart partitions found on MTD device spi0.0
May 24 17:25:00 OpenWrt user.notice kernel: Creating 7 MTD partitions on "spi0.0":
May 24 17:25:00 OpenWrt user.notice kernel: 0x000000000000-0x000000030000 : "u-boot"
May 24 17:25:00 OpenWrt user.notice kernel: 0x000000030000-0x000000040000 : "nvram"
May 24 17:25:00 OpenWrt user.notice kernel: 0x000000040000-0x000000120000 : "kernel"
May 24 17:25:00 OpenWrt user.notice kernel: 0x000000120000-0x0000003e0000 : "rootfs"
May 24 17:25:00 OpenWrt user.notice kernel: mtd: partition "rootfs" set to be root filesystem
May 24 17:25:00 OpenWrt user.info kernel: mtd: partition "rootfs_data" created automatically, ofs=30B000, len=D5000 
May 24 17:25:00 OpenWrt user.notice kernel: 0x00000030b000-0x0000003e0000 : "rootfs_data"
May 24 17:25:00 OpenWrt user.notice kernel: 0x0000003e0000-0x0000003f0000 : "mac"
May 24 17:25:00 OpenWrt user.notice kernel: 0x0000003f0000-0x000000400000 : "art"
May 24 17:25:00 OpenWrt user.notice kernel: 0x000000040000-0x0000003e0000 : "firmware"
May 24 17:25:00 OpenWrt user.info kernel: Atheros(R) L2 Ethernet Driver - version 2.2.3
May 24 17:25:00 OpenWrt user.info kernel: Copyright (c) 2007 Atheros Corporation.
May 24 17:25:00 OpenWrt user.info kernel: ag71xx_mdio: probed
May 24 17:25:00 OpenWrt user.info kernel: eth0: Atheros AG71xx at 0xba000000, irq 5
May 24 17:25:00 OpenWrt user.debug kernel: eth0: using fixed link parameters
May 24 17:25:00 OpenWrt user.info kernel: eth1: Atheros AG71xx at 0xb9000000, irq 4
May 24 17:25:00 OpenWrt user.debug kernel: eth1: using fixed link parameters
May 24 17:25:00 OpenWrt user.info kernel: Atheros AR71xx hardware watchdog driver version 0.1.0
May 24 17:25:00 OpenWrt user.debug kernel: ar71xx-wdt: timeout=15 secs (max=24)
May 24 17:25:00 OpenWrt user.info kernel: Registered led device: dir-600-a1:green:power
May 24 17:25:00 OpenWrt user.info kernel: Registered led device: dir-600-a1:amber:power
May 24 17:25:00 OpenWrt user.info kernel: Registered led device: dir-600-a1:blue:wps
May 24 17:25:00 OpenWrt user.info kernel: IPv4 over IPv4 tunneling driver
May 24 17:25:00 OpenWrt user.info kernel: GRE over IPv4 tunneling driver
May 24 17:25:00 OpenWrt user.info kernel: TCP westwood registered
May 24 17:25:00 OpenWrt user.info kernel: NET: Registered protocol family 17
May 24 17:25:00 OpenWrt user.notice kernel: Distributed Switch Architecture driver version 0.1
May 24 17:25:00 OpenWrt user.info kernel: eth0[0]: detected a Atheros AR7240 built-in switch
May 24 17:25:00 OpenWrt user.info kernel: dsa slave smi: probed
May 24 17:25:00 OpenWrt user.info kernel: 802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
May 24 17:25:00 OpenWrt user.info kernel: All bugs added by David S. Miller <davem@redhat.com>
May 24 17:25:00 OpenWrt user.info kernel: lib80211: common routines for IEEE802.11 drivers
May 24 17:25:00 OpenWrt user.debug kernel: lib80211_crypt: registered algorithm 'NULL'
May 24 17:25:00 OpenWrt user.debug kernel: lib80211_crypt: registered algorithm 'WEP'
May 24 17:25:00 OpenWrt user.debug kernel: lib80211_crypt: registered algorithm 'CCMP'
May 24 17:25:00 OpenWrt user.debug kernel: lib80211_crypt: registered algorithm 'TKIP'
May 24 17:25:00 OpenWrt user.warn kernel: VFS: Mounted root (squashfs filesystem) readonly on device 31:3.
May 24 17:25:00 OpenWrt user.info kernel: Freeing unused kernel memory: 152k freed
May 24 17:25:00 OpenWrt user.warn kernel: Please be patient, while OpenWrt loads ...
May 24 17:25:00 OpenWrt user.info kernel: gpio-buttons driver version 0.1.2
May 24 17:25:00 OpenWrt user.info kernel: input: gpio-buttons as /devices/platform/gpio-buttons/input/input0
May 24 17:25:00 OpenWrt user.info kernel: Button Hotplug driver version 0.4.0
May 24 17:25:00 OpenWrt user.info kernel: eth0: link up (1000Mbps/Full duplex)
May 24 17:25:00 OpenWrt user.warn kernel: jffs2_scan_eraseblock(): End of filesystem marker found at 0x2000
May 24 17:25:00 OpenWrt user.warn kernel: jffs2_build_filesystem(): unlocking the mtd device... done.
May 24 17:25:00 OpenWrt user.warn kernel: jffs2_build_filesystem(): erasing all blocks after the end marker... done.
May 24 17:25:00 OpenWrt user.info kernel: mini_fo: using base directory: /
May 24 17:25:00 OpenWrt user.info kernel: mini_fo: using storage directory: /overlay
May 24 17:25:00 OpenWrt user.info kernel: eth0: link down
May 24 17:25:01 OpenWrt user.info kernel: eth0: link up (1000Mbps/Full duplex)
May 24 17:25:02 OpenWrt user.notice rdate: No usable time server for loopback found
May 24 17:25:03 OpenWrt user.info kernel: device lan1 entered promiscuous mode
May 24 17:25:03 OpenWrt user.info kernel: device eth0 entered promiscuous mode
May 24 17:25:03 OpenWrt user.notice rdate: No usable time server for eth found
May 24 17:25:03 OpenWrt user.info kernel: lan1: link up, 100Mb/s, full duplex
May 24 17:25:03 OpenWrt user.info kernel: device lan2 entered promiscuous mode
May 24 17:25:03 OpenWrt user.info kernel: br-lan: port 1(lan1) entering forwarding state
May 24 17:25:04 OpenWrt user.info kernel: device lan3 entered promiscuous mode
May 24 17:25:04 OpenWrt user.info kernel: device lan4 entered promiscuous mode
May 24 17:25:04 OpenWrt user.info kernel: Generic kernel compatibility enabled based on linux-next next-20100113
May 24 17:25:05 OpenWrt user.info kernel: cfg80211: Calling CRDA to update world regulatory domain
May 24 17:25:06 OpenWrt user.notice rdate: No usable time server for lan found
May 24 17:25:06 OpenWrt user.info kernel: cfg80211: World regulatory domain updated:
May 24 17:25:06 OpenWrt user.info kernel:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
May 24 17:25:06 OpenWrt user.info kernel:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 24 17:25:06 OpenWrt user.info kernel:     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
May 24 17:25:06 OpenWrt user.info kernel:     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
May 24 17:25:06 OpenWrt user.info kernel:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 24 17:25:06 OpenWrt user.info kernel:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 24 17:25:07 OpenWrt user.debug kernel: PCI: Setting latency timer of device 0000:00:00.0 to 64
May 24 17:25:07 OpenWrt user.debug kernel: ath: EEPROM regdomain: 0x0
May 24 17:25:07 OpenWrt user.debug kernel: ath: EEPROM indicates default country code should be used
May 24 17:25:07 OpenWrt user.debug kernel: ath: doing EEPROM country->regdmn map search
May 24 17:25:07 OpenWrt user.debug kernel: ath: country maps to regdmn code: 0x3a
May 24 17:25:07 OpenWrt user.debug kernel: ath: Country alpha2 being used: US
May 24 17:25:07 OpenWrt user.debug kernel: ath: Regpair used: 0x3a
May 24 17:25:07 OpenWrt user.debug kernel: phy0: Selected rate control algorithm 'minstrel_ht'
May 24 17:25:07 OpenWrt user.info kernel: Registered led device: ath9k-phy0::radio
May 24 17:25:07 OpenWrt user.info kernel: Registered led device: ath9k-phy0::assoc
May 24 17:25:07 OpenWrt user.info kernel: Registered led device: ath9k-phy0::tx
May 24 17:25:07 OpenWrt user.info kernel: Registered led device: ath9k-phy0::rx
May 24 17:25:07 OpenWrt user.info kernel: phy0: Atheros AR9285 Rev:2 mem=0xb0000000, irq=48
May 24 17:25:07 OpenWrt user.info kernel: cfg80211: Calling CRDA for country: US
May 24 17:25:08 OpenWrt user.info kernel: cfg80211: Regulatory domain changed to country: US
May 24 17:25:08 OpenWrt user.info kernel:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
May 24 17:25:08 OpenWrt user.info kernel:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
May 24 17:25:08 OpenWrt user.info kernel:     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
May 24 17:25:08 OpenWrt user.info kernel:     (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 24 17:25:08 OpenWrt user.info kernel:     (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 24 17:25:08 OpenWrt user.info kernel:     (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
May 24 17:25:08 OpenWrt user.info kernel:     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
May 24 17:25:08 OpenWrt user.err kernel: loop: exports duplicate symbol loop_unregister_transfer (owned by kernel)
May 24 17:25:08 OpenWrt user.info kernel: PPP generic driver version 2.4.2
May 24 17:25:08 OpenWrt user.info kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
May 24 17:25:08 OpenWrt user.info kernel: NET: Registered protocol family 24
May 24 17:25:09 OpenWrt user.warn kernel: nf_conntrack version 0.5.0 (461 buckets, 1844 max)
May 24 17:25:09 OpenWrt user.warn kernel: CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please use
May 24 17:25:09 OpenWrt user.warn kernel: nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module option or
May 24 17:25:09 OpenWrt user.warn kernel: sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
May 24 17:25:09 OpenWrt user.info kernel: IMQ driver loaded successfully.
May 24 17:25:09 OpenWrt user.info kernel:       Hooking IMQ before NAT on PREROUTING.
May 24 17:25:09 OpenWrt user.info kernel:       Hooking IMQ after NAT on POSTROUTING.
May 24 17:25:10 OpenWrt user.info kernel: xt_time: kernel timezone is -0000
May 24 17:25:13 OpenWrt user.info sysinit: udhcpc (v1.16.1) started
May 24 17:25:14 OpenWrt user.info sysinit: Sending discover...
May 24 17:25:14 OpenWrt user.info sysinit: Loading defaults
May 24 17:25:14 OpenWrt user.info sysinit: Loading synflood protection
May 24 17:25:15 OpenWrt user.info sysinit: Adding custom chains
May 24 17:25:15 OpenWrt user.info sysinit: Loading zones
May 24 17:25:17 OpenWrt user.info sysinit: Sending discover...
May 24 17:25:17 OpenWrt user.info sysinit: Loading forwardings
May 24 17:25:17 OpenWrt user.info sysinit: Loading redirects
May 24 17:25:17 OpenWrt user.info sysinit: Loading rules
May 24 17:25:17 OpenWrt user.info sysinit: Loading includes
May 24 17:25:17 OpenWrt user.info sysinit: Loading interfaces
May 24 17:25:17 OpenWrt user.info firewall: info adding lan (br-lan) to zone lan
May 24 17:25:19 OpenWrt authpriv.info dropbear[1598]: Running in background
May 24 17:25:20 OpenWrt user.info sysinit: Sending discover...
May 24 17:25:20 OpenWrt user.info sysinit: WARNING: the specified certificate and key files do not exist and the px5g generator is not available, skipping SSL setup.
May 24 17:25:23 OpenWrt daemon.info dnsmasq[1746]: started, version 2.52 cachesize 150
May 24 17:25:23 OpenWrt daemon.info dnsmasq[1746]: compile time options: IPv6 GNU-getopt no-DBus no-I18N DHCP TFTP
May 24 17:25:23 OpenWrt daemon.info dnsmasq-dhcp[1746]: DHCP, IP range 192.168.1.100 -- 192.168.1.250, lease time 12h
May 24 17:25:23 OpenWrt daemon.info dnsmasq[1746]: using local addresses only for domain lan
May 24 17:25:23 OpenWrt daemon.warn dnsmasq[1746]: no servers found in /tmp/resolv.conf.auto, will retry
May 24 17:25:23 OpenWrt daemon.info dnsmasq[1746]: read /etc/hosts - 1 addresses
May 24 17:25:23 OpenWrt daemon.info dnsmasq-dhcp[1746]: read /etc/ethers - 0 addresses
May 24 17:25:24 OpenWrt user.debug kernel: ar71xx-wdt: enabling watchdog timer
root@OpenWrt:/#

Also, what happens if you issue "wifi down", then "wifi up"?

Here is what I got from the screen when I executed wifi up:

root@OpenWrt:/# wifi up
udhcpc (v1.16.1) started
Sending discover...
Sending discover...
Sending discover...

Then, logread shows additional lines (after the above):

May 24 17:26:34 OpenWrt user.info sysinit: Read error: Network is down, reopening socket
May 24 17:26:37 OpenWrt user.info sysinit: udhcpc: bind: No such device
Mazi

Re: D-Link DIR-600 A1 or Frys FR-54RTR

It looks like you don't have kmod-ath9k installed.

opkg update
opkg kmod-ath9k

I also assume you have changed these 3 lines to match your main wireless router.

        option ssid     AccessPointSSID
        option encryption psk
        option key      'example password'

You may want to erase /etc/config/wireless and run wifi detect after you install kmod-ath9k,
to make sure that the system can see your wireless interface.

You also may need to reboot after you install kmod-ath9k, before all the networking
scripts will work perfectly.

19 (edited by mazilo 2010-05-28 15:40:14)

Re: D-Link DIR-600 A1 or Frys FR-54RTR

monte wrote:

It looks like you don't have kmod-ath9k installed.

opkg update
opkg kmod-ath9k

I noticed that. Then, I reflashed my FR-54RTR with my own built OpenWRT SVN firmware  and with the ath9k module built into the kernel as seen below. Yet, no WiFi signals.

root@OpenWrt:/etc/config# lsmod
Module                  Size  Used by    Not tainted
nf_nat_tftp              432  0 
nf_conntrack_tftp       2400  1 nf_nat_tftp
nf_nat_irc               816  0 
nf_conntrack_irc        2512  1 nf_nat_irc
nf_nat_ftp              1328  0 
nf_conntrack_ftp        4624  1 nf_nat_ftp
xt_HL                   1280  0 
xt_hl                    896  0 
xt_MARK                  496 15 
ipt_ECN                 1312  0 
xt_CLASSIFY              496  0 
xt_time                 1552  0 
xt_tcpmss                992  0 
xt_statistic             816  0 
xt_mark                  512 15 
xt_length                672  5 
ipt_ecn                  976  0 
xt_DSCP                 1392  0 
xt_dscp                 1008  0 
xt_IMQ                   704  1 
imq                     2544  0 
xt_string                880  0 
xt_layer7              10368  2 
ipt_MASQUERADE           992  1 
iptable_nat             2768  1 
nf_nat                 10064  5 nf_nat_tftp,nf_nat_irc,nf_nat_ftp,ipt_MASQUERADE,iptable_nat
xt_CONNMARK              768  2 
xt_recent               5520  0 
xt_helper                816  0 
xt_conntrack            2016  0 
xt_connmark              656  0 
xt_connbytes            1232  0 
xt_NOTRACK               544  0 
iptable_raw              656  1 
xt_state                 768  3 
nf_conntrack_ipv4       7376 10 iptable_nat,nf_nat
nf_defrag_ipv4           624  1 nf_conntrack_ipv4
nf_conntrack           37488 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                   7984  0 
pppox                   1216  1 pppoe
ipt_REJECT              1680  2 
xt_TCPMSS               1856  1 
ipt_LOG                 4176  0 
xt_comment               464  0 
xt_multiport            1792  5 
xt_mac                   576  0 
xt_limit                1008  1 
iptable_mangle           992  1 
iptable_filter           768  1 
ip_tables               8544  4 iptable_nat,iptable_raw,iptable_mangle,iptable_filter
xt_tcpudp               1760 13 
x_tables                9312 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
ppp_async               6400  0 
ppp_generic            18608  3 pppoe,pppox,ppp_async
slhc                    4160  1 ppp_generic
ath9k                  79280  0 
ath9k_common            4640  1 ath9k
ath9k_hw              269712  2 ath9k,ath9k_common
ath                     6880  2 ath9k,ath9k_hw
mac80211              190128  2 ath9k,ath9k_common
ts_fsm                  2608  0 
ts_bm                   1456  0 
ts_kmp                  1344  0 
nls_base                4800  0 
crc_ccitt                976  1 ppp_async
cfg80211              110912  4 ath9k,ath9k_common,ath,mac80211
compat_firmware_class     4672  0 
compat                   432  0 
arc4                     816  2 
aes_generic            30256  0 
ecb                     1328  2 
button_hotplug          2624  0 
gpio_buttons            1968  0 
input_polldev           1360  1 gpio_buttons
input_core             16816  4 button_hotplug,gpio_buttons,input_polldev

I also assume you have changed these 3 lines to match your main wireless router since the WiFi from the apartment complex requires no encryption, but a login through a web browser.

        option ssid     AccessPointSSID
        option encryption psk
        option key      'example password'

I used the default values as follows:

        option ssid     OpenWRT
        option encryption none

You may want to erase /etc/config/wireless and run wifi detect after you install kmod-ath9k,
to make sure that the system can see your wireless interface.

I executed wifi detect and it prints out the following on the shell that looks like the content of a /etc/config/wireless default file which I deleted earlier before executing the wifi detect :

config wifi-device  radio0
        option type     mac80211
        option channel  5
        option macaddr  00:26:5a:f4:6c:14
        option hwmode   11ng
        option htmode   HT20
        list ht_capab   SHORT-GI-40
        list ht_capab   TX-STBC
        list ht_capab   RX-STBC1
        list ht_capab   DSSS_CCK-40
        # REMOVE THIS LINE TO ENABLE WIFI:
        option disabled 1

config wifi-iface
        option device   radio0
        option network  lan
        option mode     ap
        option ssid     OpenWrt
        option encryption none

You also may need to reboot after you install kmod-ath9k, before all the networking
scripts will work perfectly.

Done that and still the same problem: no WiFi signals. sad

Mazi

Re: D-Link DIR-600 A1 or Frys FR-54RTR

How are you measuring WiFi signals?

What are the wireless settings of the router you are trying to connect to?

The ssid, encryption parameters, and channel need to match the wireless router you wish to connect to.
I'm assuming the other router is doing 802.11g; is it?

Note that after you did wifi detect, it switched the mode back to "ap" (Access Point)
and disabled wireless by default.

If you want to be an access point, you need to install hostapd or hostapd-mini.
If you want to be a station (client to a wireless AP), you'll need wpa-supplicant.

I'm going to refer you to the documentation because it's not clear to me what's wrong.

http://kamikaze.openwrt.org/docs/openwrt.html#x1-120001.2.2
http://wiki.openwrt.org/doc/uci/wireless

Re: D-Link DIR-600 A1 or Frys FR-54RTR

monte wrote:

How are you measuring WiFi signals?

First, I booted the device using a default (AP mode) configuration from OpenWRT SVN firmware. Then, I configured my Linksys WRT54GS (flashed with a DD-WRT firmware) as a client. The WRT54GS could not find the signals from my FR-54RTR even they both were put next to each other. Secondly, I reversed the configurations, i.e. FR-54RTR as client and WRT54GS as AP, and the FR-54RTR could not find the signals from WRT54GS. Also, a WiFi scan on my FR-54RTR through its GUI shows no WiFi spots. Finally, I flashed my FR-54RTR back to the DLink firmware and it works, i.e. my WRT54GS device sees the WiFi signals from my FR-54RTR device, even they are put in different rooms that are 50' apart. So, this proves the WiFi modules on both devices are not malfunction.

What are the wireless settings of the router you are trying to connect to?

The device is a Linksys WRT54GS flashed with a DD-WRT firmware and is configured as an AP mode with no encryption.

The ssid, encryption parameters, and channel need to match the wireless router you wish to connect to.

Yes and they all matched. For my FR-54RTR unit, I configured it with auto for channel. Here is the /etc/config/wireless file for my FR-54RTR:

root@OpenWrt:/etc/config# cat wireless
config wifi-device  radio0
        option  type            mac80211
        option  channel         auto
        option  macaddr         00:26:5a:f4:6c:14
        option  hwmode          11ng
        #option htmode          HT20
        #list   ht_capab        SHORT-GI-40
        list    ht_capab        TX-STBC
        list    ht_capab        RX-STBC1
        #list   ht_capab        DSSS_CCK-40
        option  disabled        0

config wifi-iface
        option  device          radio0
        option  network         wan
        option  mode            sta
        option  ssid            OpenWrt
        option  encryption      none

And, here is the /etc/config/network file:

root@OpenWrt:/etc/config# cat network

config 'interface' 'loopback'
        option  'ifname'        'lo'
        option  'proto'         'static'
        option  'ipaddr'        '127.0.0.1'
        option  'netmask'       '255.0.0.0'

config 'interface' 'eth'
        option  'ifname'        'eth0'
        option  'proto'         'none'

config 'interface' 'lan'
        option  'ifname'        'lan1 lan2 lan3 lan4'
        option  'type'          'bridge'
        option  'proto'         'static'
        option  'netmask'       '255.255.255.0'
        option  'ipaddr'        '192.168.1.1'

config 'interface' 'wan'
        option  'ifname'        'wlan0'
        option  'macaddr'       '00265af46c14'
        option  'proto'         'dhcp'
        #option 'mtu'           '1500'
        #option 'ipaddr'        '192.168.1.1'
        #option 'netmask'       '255.255.255.0'
        #option 'gateway'       '192.168.1.1'
        #option 'dns'           '8.8.4.4'

root@OpenWrt:/etc/config#

I'm assuming the other router is doing 802.11g; is it?

Yes. I even tried 802.11b mode to no avail.

Note that after you did wifi detect, it switched the mode back to "ap" (Access Point)
and disabled wireless by default.

yes.

If you want to be an access point, you need to install hostapd or hostapd-mini.
If you want to be a station (client to a wireless AP), you'll need wpa-supplicant.

I believe hostapd and wpa-supplicant packages are compiled into my self-built OpenWRT SVN firmware as shown below:

root@OpenWrt:/etc/config# opkg list
base-files - 44-r21517
busybox - 1.16.1-7
crda - 1.1.0-2
ddns-scripts - 1.0.0-8
dnsmasq - 2.52-5
dropbear - 0.52-5
firewall - 2-4
hostapd - 20100418-1
hotplug2 - 1.0-beta-2
iptables - 1.4.7-1
iptables-mod-conntrack - 1.4.7-1
iptables-mod-conntrack-extra - 1.4.7-1
iptables-mod-filter - 1.4.7-1
iptables-mod-imq - 1.4.7-1
iptables-mod-ipopt - 1.4.7-1
iptables-mod-nat - 1.4.7-1
iw - 0.9.19-1
kernel - 2.6.32.14-1
kmod-ath - 2.6.32.14+2010-05-24-1
kmod-ath9k - 2.6.32.14+2010-05-24-1
kmod-button-hotplug - 2.6.32.14-2
kmod-cfg80211 - 2.6.32.14+2010-05-24-1
kmod-crc-ccitt - 2.6.32.14-1
kmod-crypto-aes - 2.6.32.14-1
kmod-crypto-arc4 - 2.6.32.14-1
kmod-crypto-core - 2.6.32.14-1
kmod-input-core - 2.6.32.14-1
kmod-input-gpio-buttons - 2.6.32.14-1
kmod-input-polldev - 2.6.32.14-1
kmod-ipt-conntrack - 2.6.32.14-1
kmod-ipt-conntrack-extra - 2.6.32.14-1
kmod-ipt-core - 2.6.32.14-1
kmod-ipt-filter - 2.6.32.14-1
kmod-ipt-imq - 2.6.32.14-1
kmod-ipt-ipopt - 2.6.32.14-1
kmod-ipt-nat - 2.6.32.14-1
kmod-ipt-nathelper - 2.6.32.14-1
kmod-loop-aes - 2.6.32.14+3.2h-1
kmod-mac80211 - 2.6.32.14+2010-05-24-1
kmod-nls-base - 2.6.32.14-1
kmod-ppp - 2.6.32.14-1
kmod-pppoe - 2.6.32.14-1
kmod-sched - 2.6.32.14-1
kmod-textsearch - 2.6.32.14-1
libc - 0.9.30.1-44
libgcc - 4.3.3+cs-44
libiptc - 1.4.7-1
liblua - 5.1.4-6
libnl-tiny - 0.1-1
librt - 0.9.30.1-44
libuci - 12012009.5-2
libuci-lua - 12012009.5-2
libxtables - 1.4.7-1
lua - 5.1.4-6
luci-admin-core - 0.9+svn6183-1
luci-admin-full - 0.9+svn6183-1
luci-cbi - 0.9+svn6183-1
luci-core - 0.9+svn6183-1
luci-fastindex - 0.9+svn6183-1
luci-http - 0.9+svn6183-1
luci-i18n-english - 0.9+svn6183-1
luci-ipkg - 0.9+svn6183-1
luci-lmo - 0.9+svn6183-1
luci-nixio - 0.9+svn6183-1
luci-sgi-cgi - 0.9+svn6183-1
luci-sys - 0.9+svn6183-1
luci-theme-base - 0.9+svn6183-1
luci-theme-openwrt - 0.9+svn6183-1
luci-uci - 0.9+svn6183-1
luci-uvl - 0.9+svn6183-1
luci-web - 0.9+svn6183-1
miniupnpd - 1.4-1
mtd - 12
ntpclient - 2007_365-4
opkg - 528-1
ppp - 2.4.4-7
ppp-mod-pppoe - 2.4.4-7
qos-scripts - 1.2.1-2
swconfig - 6
tc - 2.6.31-2
uci - 12012009.5-2
ucitrigger - 12012009.5-2
udev - 142-1
udevtrigger - 106-1
uhttpd - 10
vsc7385-ucode-ap83 - 1
vsc7385-ucode-pb44 - 1
vsc7395-ucode-ap83 - 1
vsc7395-ucode-pb44 - 1
wireless-tools - 29-4
wpa-supplicant - 20100418-1
wpad-mini - 20100418-1

Below is the output from lsmod that shows the ath9k module if that matters.

root@OpenWrt:/etc/config# lsmod
Module                  Size  Used by    Not tainted
nf_nat_tftp              432  0 
nf_conntrack_tftp       2400  1 nf_nat_tftp
nf_nat_irc               816  0 
nf_conntrack_irc        2512  1 nf_nat_irc
nf_nat_ftp              1328  0 
nf_conntrack_ftp        4624  1 nf_nat_ftp
xt_HL                   1280  0 
xt_hl                    896  0 
xt_MARK                  496 15 
ipt_ECN                 1312  0 
xt_CLASSIFY              496  0 
xt_time                 1552  0 
xt_tcpmss                992  0 
xt_statistic             816  0 
xt_mark                  512 15 
xt_length                672  5 
ipt_ecn                  976  0 
xt_DSCP                 1392  0 
xt_dscp                 1008  0 
xt_IMQ                   704  1 
imq                     2544  0 
xt_string                880  0 
xt_layer7              10368  2 
ipt_MASQUERADE           992  1 
iptable_nat             2768  1 
nf_nat                 10064  5 nf_nat_tftp,nf_nat_irc,nf_nat_ftp,ipt_MASQUERADE,iptable_nat
xt_CONNMARK              768  2 
xt_recent               5520  0 
xt_helper                816  0 
xt_conntrack            2016  0 
xt_connmark              656  0 
xt_connbytes            1232  0 
xt_NOTRACK               544  0 
iptable_raw              656  1 
xt_state                 768  3 
nf_conntrack_ipv4       7376 10 iptable_nat,nf_nat
nf_defrag_ipv4           624  1 nf_conntrack_ipv4
nf_conntrack           37488 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                   7984  0 
pppox                   1216  1 pppoe
ipt_REJECT              1680  2 
xt_TCPMSS               1856  1 
ipt_LOG                 4176  0 
xt_comment               464  0 
xt_multiport            1792  5 
xt_mac                   576  0 
xt_limit                1008  1 
iptable_mangle           992  1 
iptable_filter           768  1 
ip_tables               8544  4 iptable_nat,iptable_raw,iptable_mangle,iptable_filter
xt_tcpudp               1760 13 
x_tables                9312 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
ppp_async               6400  0 
ppp_generic            18608  3 pppoe,pppox,ppp_async
slhc                    4160  1 ppp_generic
ath9k                  77344  0 
ath9k_common            3312  1 ath9k
ath9k_hw              270512  2 ath9k,ath9k_common
ath                     6880  2 ath9k,ath9k_hw
mac80211              174432  1 ath9k
ts_fsm                  2608  0 
ts_bm                   1456  0 
ts_kmp                  1344  0 
nls_base                4800  0 
crc_ccitt                976  1 ppp_async
cfg80211              110736  3 ath9k,ath,mac80211
compat_firmware_class     4672  0 
compat                   736  0 
arc4                     816  2 
aes_generic            30256  0 
ecb                     1328  2 
button_hotplug          2624  0 
gpio_buttons            1968  0 
input_polldev           1360  1 gpio_buttons
input_core             16816  4 button_hotplug,gpio_buttons,input_polldev

At this point, I have run out of ideas to make my FR-54RTR unit as a WiFi client and am hoping anyone can help.

I'm going to refer you to the documentation because it's not clear to me what's wrong.

http://kamikaze.openwrt.org/docs/openwrt.html#x1-120001.2.2
http://wiki.openwrt.org/doc/uci/wireless

Many thanks and I will check them out later on.

Mazi

Re: D-Link DIR-600 A1 or Frys FR-54RTR

Here is some updates:

I flashed back the BackFire to my FR-54RTR and did an opkg update that automatically added a lot of kernel modules as well as the necessary packages. Now, it is able to detect WiFi spots in my neighborhood even after a reboot. I pressed the Scan button (on the WiFi -> Overview GUI page) and sometimes it returned some WiFi signals while other times no WiFi signals found. Ironically, some WiFi sources are open with no encryption and are using Default SSID. So, I manually configured /etc/config/wireless file with a Default SSID, but my FR-54RTR seemed to be unable to connect to the WiFi sources with the Default SSID and returned with several attempted messages until finally with a time out message.

Now that I know my FR-54RTR unit is able to pick up WiFi signals, I did an opkg list-installed to show what packages were installed on my FR-54RTR device. Using this information, I reconfigured/recompiled my local OpenWRT SVN trunk using make menuconfig to select the needed packages as well as using make kernel_menuconfig to select kernel drivers as built-in modules and flash the firmware to my FR-54RTR device. After the device finished booting up, I was able to see the same problem (several attemps failed to the WiFi sources with the Default SSID and a time out message). OTOH, when I pressed the Scan button (on the WiFi -> Radio0 -> Overview GUI page), it returned with no WiFi signals. sad

Mazi

Re: D-Link DIR-600 A1 or Frys FR-54RTR

Anybody ever get one of these up and stable?

If so, what build(s)? GUI working?

I tried a while back and it would either brick or the one time i got it working it would crash quite regularly.

I am back on the D-Link Firmware for now.

Would actually like to go back to the Fry's firmware to see what it looks like, but can't find the Bin for it, just the source.

Re: D-Link DIR-600 A1 or Frys FR-54RTR

AWD_Guy wrote:

Anybody ever get one of these up and stable?

I haven't been playing with OpenWrt for a while, but
if you set mtu to 1400 on the wan it's fairly stable.

AWD_Guy wrote:

I am back on the D-Link Firmware for now.

Would actually like to go back to the Fry's firmware to see what it looks like, but can't find the Bin for it, just the source.

The D-Link firmware is more full featured than the Fry's one.
The D-Link firmware includes IPv6 support.  I don't remember what else it had.

Re: D-Link DIR-600 A1 or Frys FR-54RTR

Thanks.

Actually tried the backfire RC-3 code over the weekend. Appeared much more stable. Will try MTU if needed.

I did appear to have a problem passing broadcast traffic too/from wireless <> LAN port daisy chained to my primary router.

Basically, the 54RTR was just acting as an AP. No DHCP, etc. Hosts have no problem talking routed to Internet off BEFSR81, but can't pass broadcast traffic and thus can't find each other over netbios "browser" name resolution. Need to do more testing, but the same configuration works fine on the D-link firmware. Do I have to define an uplink or trunk port in OpenWRT or something to pass broadcasts or support multiple MAC addresses coming in on a LAN port?

Host <wire> BEFSR81 <wire> FR-54RTR <wireless> Host

The other potential use I have for these is as range extenders like the WRE54G type to routers not supporting WDS. Anybody got OpenWRT working as a extender/repeater to a non WDS router like the 2Wire ones?

All the guides/posts I found are for OpenWRT-OpenWRT WDS configs.