AR670W: LAN ports broken after dd-wrt install

Post new topic   Reply to topic    DD-WRT Forum Index -> Ralink SoC based Hardware
Author Message
brons2
DD-WRT Novice


Joined: 26 Nov 2009
Posts: 11

PostPosted: Sat Nov 28, 2009 5:59    Post subject: AR670W: LAN ports broken after dd-wrt install Reply with quote
Hello,

I just applied the latest version of DD-WRT to my Airlink 101 AR670W. After I installed it, my LAN ports no longer work! Strangely, the wireless works fine. I can get to internet from the wireless network. But the 4 LAN ports do not work. I need them to work.

I telnetted into the device and did an ifconfig. Here are the results:

br0 Link encap:Ethernet HWaddr 00:1D:6A:D2:D6:E5
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:15931 errors:0 dropped:0 overruns:0 frame:0
TX packets:25804 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1430453 (1.3 MiB) TX bytes:28911989 (27.5 MiB)

br0:0 Link encap:Ethernet HWaddr 00:1D:6A:D2:D6:E5
inet addr:169.254.255.1 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

eth2 Link encap:Ethernet HWaddr FB:47:9D:6B:78:5D
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:45309 errors:0 dropped:0 overruns:0 frame:0
TX packets:898 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3764388 (3.5 MiB) TX bytes:136875 (133.6 KiB)
Interrupt:3

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

ra0 Link encap:Ethernet HWaddr 00:1D:6A:D2:D6:E5
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6178 errors:0 dropped:0 overruns:0 frame:0
TX packets:5583 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:663619 (648.0 KiB) TX bytes:6412874 (6.1 MiB)
Interrupt:4

vlan1 Link encap:Ethernet HWaddr FB:47:9D:6B:78:5D
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1120 errors:0 dropped:0 overruns:0 frame:0
TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:107200 (104.6 KiB) TX bytes:46 (46.0 B)

vlan2 Link encap:Ethernet HWaddr 00:1D:6A:D2:D6:E6
inet addr:72.177.56.163 Bcast:72.177.59.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:44185 errors:0 dropped:0 overruns:0 frame:0
TX packets:898 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3022642 (2.8 MiB) TX bytes:137157 (133.9 KiB)

It seems that bridge0 aka br0, actually has the local IP 192.186.1.1 applied to it. If I then go look in the bridging table, it says interface ra0 is an interface on bridge br0 but no other physical interfaces are in br0. I assume ra0 is probably the wireless.

If anyone has any insight please post it here. Maybe just an ifconfig to compare would be nice.

regards,
Jim
Sponsor
slaveunit
DD-WRT User


Joined: 06 Sep 2008
Posts: 163

PostPosted: Sat Nov 28, 2009 18:55    Post subject: Reply with quote
What latest is the "latest" that you installed.
brons2
DD-WRT Novice


Joined: 26 Nov 2009
Posts: 11

PostPosted: Sun Nov 29, 2009 7:46    Post subject: Reply with quote
DD-WRT v24-sp2 (10/10/09) std
(SVN revision 13064)

root@DD-WRT:~# dmesg
<5>Linux version 2.6.23.17 (root@dd-wrt) (gcc version 4.1.2) #972 Sat Oct 10 11:53:38 CEST 2009
<4>
<4> The CPU frequency set to 266 MHz
<6>32M RAM Detected!
<4>CPU revision is: 0001906c
<4>Determined physical RAM map:
<4> memory: 02000000 @ 08000000 (usable)
<6>Wasting 1048576 bytes for tracking 32768 unused pages
<7>On node 0 totalpages: 40960
<7> Normal zone: 320 pages used for memmap
<7> Normal zone: 0 pages reserved
<7> Normal zone: 40640 pages, LIFO batch:7
<7> Movable zone: 0 pages used for memmap
<4>Built 1 zonelists in Zone order. Total pages: 40640
<5>Kernel command line: console=ttyS1,57600n8 root=/dev/mtdblock4 rootfstype=squashfs noinitrd
<4>Primary instruction cache 16kB, physically tagged, 4-way, linesize 16 bytes.
<4>Primary data cache 16kB, 4-way, linesize 16 bytes.
<6>Synthesized TLB refill handler (20 instructions).
<6>Synthesized TLB load handler fastpath (32 instructions).
<6>Synthesized TLB store handler fastpath (32 instructions).
<6>Synthesized TLB modify handler fastpath (31 instructions).
<4>cause = 800008, status = 1000ff00
<4>PID hash table entries: 1024 (order: 10, 4096 bytes)
<4>calculating r4koff... 0028b0aa(2666666)
<4>CPU frequency 266.67 MHz
<4>Using 133.333 MHz high precision timer.
<6>console [ttyS1] enabled
<6>Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
<6>Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
<6>Memory: 28032k/32768k available (2341k kernel code, 4664k reserved, 314k data, 124k init, 0k highmem)
<7>Calibrating delay loop... 266.24 BogoMIPS (lpj=1331200)
<4>Mount-cache hash table entries: 512
<6>NET: Registered protocol family 16
<6>Generic PHY: Registered new driver
<6>NET: Registered protocol family 2
<6>Time: MIPS clocksource has been installed.
<6>IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
<6>TCP established hash table entries: 8192 (order: 4, 65536 bytes)
<6>TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
<6>TCP: Hash tables configured (established 8192 bind 8192)
<6>TCP reno registered
<4>Load RT2880 Timer Module(Wdg/Soft)
<6>devfs: 2004-01-31 Richard Gooch (rgooch@atnf.csiro.au)
<6>devfs: boot_options: 0x1
<6>squashfs: version 3.0 (2006/03/15) Phillip Lougher
<6>io scheduler noop registered
<6>io scheduler deadline registered (default)
<4>Ralink gpio driver initialized
<6>Serial: 8250/16550 driver $Revision: 1.3 $ 2 ports, IRQ sharing disabled
<6>serial8250: ttyS0 at I/O 0xa0300500 (irq = 9) is a 16550A
<6>serial8250: ttyS1 at I/O 0xa0300c00 (irq = Cool is a 16550A
<6>PPP generic driver version 2.4.2
<6>PPP Deflate Compression module registered
<6>PPP BSD Compression module registered
<6>MPPE/MPPC encryption/compression module registered
<6>NET: Registered protocol family 24
<6>PPPoL2TP kernel driver, V1.0
<6>tun: Universal TUN/TAP device driver, 1.6
<6>tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
<5>ralink flash device: 0x400000 at 0xbf000000
<6>Ralink SoC physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank
<4> Amd/Fujitsu Extended Query Table at 0x0040
<5>number of CFI chips: 1
<5>cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
<0>
<4>found squashfs at 117000
<5>Creating 6 MTD partitions on "Ralink SoC physically mapped flash":
<5>0x00000000-0x00030000 : "uboot"
<5>0x00030000-0x00040000 : "uboot-config"
<5>0x00040000-0x00050000 : "factory-defaults"
<5>0x00040000-0x003f0000 : "linux"
<5>0x00117000-0x003f0000 : "rootfs"
<4>mtd: partition "rootfs" doesn't start on an erase block boundary -- force read-only
<5>0x003f0000-0x00400000 : "nvram"
<4>u32 classifier
<4> Actions configured
<4>Netfilter messages via NETLINK v0.30.
<4>nf_conntrack version 0.5.0 (1024 buckets, 4096 max)
<4>ctnetlink v0.93: registering with nfnetlink.
<6>IPv4 over IPv4 tunneling driver
<6>GRE over IPv4 tunneling driver
<6>ip_tables: (C) 2000-2006 Netfilter Core Team
<6>IPP2P v0.8.2 loading
<5>ClusterIP Version 0.8 loaded successfully
<6>TCP bic registered
<6>TCP cubic registered
<6>TCP westwood registered
<6>TCP highspeed registered
<6>TCP hybla registered
<6>TCP htcp registered
<6>TCP vegas registered
<6>TCP scalable registered
<6>NET: Registered protocol family 1
<6>NET: Registered protocol family 17
<4>Welcome to PF_RING 3.2.1
<4>(C) 2004-06 L.Deri <deri@ntop.org>
<6>NET: Registered protocol family 27
<4>PF_RING: bucket length 128 bytes
<4>PF_RING: ring slots 4096
<4>PF_RING: sample rate 1 [1=no sampling]
<4>PF_RING: capture TX No [RX only]
<4>PF_RING: transparent mode Yes
<4>PF_RING initialized correctly.
<4>PF_RING: registered /proc/net/pf_ring/
<6>802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
<6>All bugs added by David S. Miller <davem@redhat.com>
<4>GDMA1_MAC_ADRH -- : 0x00000000
<4>GDMA1_MAC_ADRL -- : 0x00000000
<4>Ralink APSoC Ethernet Driver Initilization. v2.00 256 rx/tx descriptors allocated, mtu = 1500!
<4>NAPI enable, weight = 0, Tx Ring = 256, Rx Ring = 256
<4>GDMA1_MAC_ADRH -- : 0x0000fb47
<4>GDMA1_MAC_ADRL -- : 0x9d6b785d
<1>PROC INIT OK!
<0>decode /dev/mtdblock4
<4>VFS: Mounted root (squashfs filesystem) readonly.
<6>Mounted devfs on /dev
<6>Freeing unused kernel memory: 124k freed
<4>rt2860v2_ap: module license 'unspecified' taints kernel.
<4>
<4>phy_tx_ring = 0x09d90000, tx_ring = 0xa9d90000, size: 16 bytes
<4>
<4>phy_rx_ring = 0x09d91000, rx_ring = 0xa9d91000, size: 16 bytes
<4>GDMA1_FWD_CFG = 10000
<3>br0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
<4>Algorithmics/MIPS FPU Emulator v1.5
<4>RtmpOSNetDevDetach(): RtmpOSNetDeviceDetach(), dev->name=ra0!
<4>0x1300 = 00064380
<4>0x1300 = 00064380
<6>device ra0 entered promiscuous mode
<6>br0: port 1(ra0) entering learning state
<6>device vlan2 entered promiscuous mode
<6>device eth2 entered promiscuous mode
<6>device vlan2 left promiscuous mode
<6>br0: topology change detected, propagating
<6>br0: port 1(ra0) entering forwarding state
<6>etherip: Ethernet over IPv4 tunneling driver
root@DD-WRT:~#
finiteLoop
DD-WRT Novice


Joined: 24 Nov 2009
Posts: 4

PostPosted: Sun Nov 29, 2009 8:30    Post subject: Reply with quote
13064 is a broken build. Use 13069.

You need to read the main AR670W thread, probably start around page 29.
brons2
DD-WRT Novice


Joined: 26 Nov 2009
Posts: 11

PostPosted: Sun Nov 29, 2009 10:33    Post subject: Reply with quote
I installed 13069 and now it works, thanks.

It looks like the change made was to add VLAN1 (in addition to ra0) to bridge br0. VLAN1 was not a member of br0 in 13064.

I suppose that change could have been made via the command shell if I a) knew which interface represented the internal ports and b) knew the command syntax :-)

Appreciate the help.
aguaviv
DD-WRT Novice


Joined: 05 Jan 2010
Posts: 5

PostPosted: Tue Jan 05, 2010 15:42    Post subject: Reply with quote
I have the same problem. If there's no web access how did you solve it? Can you give me the link to the AR670W main thread.

Appreciate the help.
slaveunit
DD-WRT User


Joined: 06 Sep 2008
Posts: 163

PostPosted: Tue Jan 05, 2010 16:41    Post subject: Reply with quote
http://www.dd-wrt.com/phpBB2/viewtopic.php?t=32995
sawecw
DD-WRT Novice


Joined: 06 Dec 2009
Posts: 16

PostPosted: Sat Jan 09, 2010 14:00    Post subject: 13525 Reply with quote
aguaviv wrote:
I have the same problem. If there's no web access how did you solve it? Can you give me the link to the AR670W main thread.


When I had this problem with 13064, I was still able to access the router over wireless. So I carefully reflashed 13069 wirelessly.

At this point, rather than using 13069 which requires you to wade through 10 forum pages to find a buried link to some random downloader site that makes you wait a minute before your download starts and leaves you less than certain that you have a trojan free version, I suggest using the latest ddwrt hosted test build, 13525. The link for that build is:

http://www.dd-wrt.com/dd-wrtv2/down.php?path=downloads%2Fothers%2Feko%2FBrainSlayer-V24-preSP2%2F12-28-09-r13525%2Fairlink101-ar670w/
slaveunit
DD-WRT User


Joined: 06 Sep 2008
Posts: 163

PostPosted: Sat Jan 09, 2010 15:16    Post subject: Reply with quote
Why would you take the risk of reflashing over wireless when there is a recovery mode?
sawecw
DD-WRT Novice


Joined: 06 Dec 2009
Posts: 16

PostPosted: Sat Jan 09, 2010 19:39    Post subject: Reply with quote
slaveunit wrote:
Why would you take the risk of reflashing over wireless when there is a recovery mode?


Good point! As I paid $20 for the router, I probably was not too worried personally, but wireless updating is not something to recommend.
BuonaDomenica
DD-WRT Novice


Joined: 10 Apr 2008
Posts: 40

PostPosted: Sat May 08, 2010 5:59    Post subject: same dead LAN ports Reply with quote
I have those same dead lan ports but still can access the router via wireless. No mater what built version of DD-wrt is flashed the LAN ports stay dead. I flashed through wireless after the dead ports appeared.

I can't reach the recovery page which is mentioned under page 29 in the main thread as I have tried at least 100 times.

Is there another way of reactivating the LAN ports via command line under Telnet? As I said wireless works fine but just no LAN

what other options are out there to get at least the original firmware back on there?

thanks for any help
BD
d3hilton
DD-WRT Novice


Joined: 18 Feb 2010
Posts: 40

PostPosted: Wed May 12, 2010 14:57    Post subject: Re: same dead LAN ports Reply with quote
I commented on another thread of yours, but I found a subset of these routers didn't work above 12874. If you can get in wirelessly, set the WAN to be part of the switch. Since it is separate you should be able to use that even when the LAN ports are not working, Then I would try and reflash 12874.

ARE you holding the reset button in when you plug it in and wait 30 sec?

Remember a 30-30-30 reset means, Hold the button for 30 sec while powered, then while your still holding it in, pull the plug for 30 sec, then keep holding the button in, while you plug it in, and keep holding the reset for another 30 sec. If you want the factory firmware, you will need to get into recovery mode I believe to load it, I don't think you can load it from DD-WRT.

BuonaDomenica wrote:
I have those same dead lan ports but still can access the router via wireless. No mater what built version of DD-wrt is flashed the LAN ports stay dead. I flashed through wireless after the dead ports appeared.

I can't reach the recovery page which is mentioned under page 29 in the main thread as I have tried at least 100 times.

Is there another way of reactivating the LAN ports via command line under Telnet? As I said wireless works fine but just no LAN

what other options are out there to get at least the original firmware back on there?

thanks for any help
BD

_________________
DD-WRT 24-sp2
Current:
Linksys wrt610n v2
Netgear wndr3300
Airlink101 AR690W
Linksys WRT-350N
Linksys WRT54g v8

Past routers
Netgear WPN834bV2
Airlink101 AR670W
Linksys WRE54g

Non DD-WRT
TRENDnet TEW639gr, TEW638, TEW637ap
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Ralink SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum