Asus RT-N66U

Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Broadcom SoC based Hardware
Goto page Previous  1, 2, 3 ... 152, 153, 154 ... 167, 168, 169  Next
Author Message
davparker
DD-WRT Novice


Joined: 28 Sep 2014
Posts: 2

PostPosted: Tue Apr 21, 2015 8:11    Post subject: How to enable mirroring on Asus RT-N66U Reply with quote
iptables -A PREROUTING -t mangle -j ROUTE --gw 192.168.1.40 --tee

iptables -A POSTROUTING -t mangle -j ROUTE --gw 192.168.1.40 --tee

"The above commands will make a copy of all of the traffic on your network to the
gateway IP address 192.168.1.40", for example.

When done, to switch off mirroring, use:
iptables -F -t mangle

"The above command will flush the 'mangle' table and stop mirroring traffic to IP address
192.168.1.40 without rebooting the router."

Special thanks to Bill Parker for that info!
Sponsor
tpmjb
DD-WRT Novice


Joined: 16 May 2015
Posts: 6

PostPosted: Sat May 16, 2015 7:13    Post subject: Reply with quote
Hey all,

I'm having a hell of a time with this router. I followed the wiki (which seems to have a lot of old information in it) and flashed the file dd-wrt.v24-26138_NEWD-2_K3.x_mega_RT-N66U.trx that was found in the wiki. Everything seemed to work okay, except for two very crucial things:

1) I could not be issued an IP address on LAN connections (Connected via wireless just fine)
2) Probably because of this, I could not be issued a new IP address no matter how many hours I spent on the phone with FIOS customer support.

It complicates things having to call Verizon FIOS support every time I need to change routers, but I know for sure this router works. The MAC address shouldn't change, so I should be able to DHCP renew no problem. The router fails on this.

I reflashed the original firmware FW_RT_N66U_30043763657.trx and that's what I'm using right now to post in this forum.

Halp?
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Sat May 16, 2015 10:12    Post subject: Reply with quote
After flashing dd-wrt, telnet to the router wirelessly and erase nvram. Or while applying power to the router hold the wps button in for 15 seconds or so.
I usually just erase nvram.

_________________
I am far from a guru, I'm barely a novice.
tpmjb
DD-WRT Novice


Joined: 16 May 2015
Posts: 6

PostPosted: Sun May 17, 2015 0:50    Post subject: Reply with quote
Malachi wrote:
After flashing dd-wrt, telnet to the router wirelessly and erase nvram. Or while applying power to the router hold the wps button in for 15 seconds or so.
I usually just erase nvram.


I held the WPS button when booting the router to erase NVRam. Same thing. This time I installed the latest dd-wrt.v24-26866_NEWD-2_K3.x-big-RT-N66U.trx to the router over the recovery tool instead of the web UI.

I could get an IP over wireless, but over LAN I couldn't. I would just be stuck with the default 169.xxx.xx.x address and I wouldn't be able to access anything. That and the router couldn't be issued an IP address to the outside world. Reinstall the Asus firmware and everything's peachy. No idea what is wrong, though installing the original firmware fixes the speed issues I had on the latest Asus firmware (My speed dropped to 1/8 what it was originally on their latest firmware).
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Sun May 17, 2015 1:26    Post subject: Reply with quote
Telnet to the router, type erase nvram, hit enter, then type reboot and hit enter.
It's either erase nvram or nvram erase, I never remember till I do it.

_________________
I am far from a guru, I'm barely a novice.
tpmjb
DD-WRT Novice


Joined: 16 May 2015
Posts: 6

PostPosted: Sun May 17, 2015 4:12    Post subject: Reply with quote
Malachi wrote:
Telnet to the router, type erase nvram, hit enter, then type reboot and hit enter.
It's either erase nvram or nvram erase, I never remember till I do it.


I did this, and rebooted the router. All this seemed to do was knock out the wireless on the router, for some reason. I also still couldn't get an IP address on LAN. For this reason, I had to enter recovery mode and flash the old firmware again.

Edit: I did both commands "nvram erase" and "erase nvram". They both seemed to do *something*
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Sun May 17, 2015 11:38    Post subject: Reply with quote
One of the commands would return an error message.
Of course it would knock out the wireless, it reboots the router and erases your settings.

_________________
I am far from a guru, I'm barely a novice.
tpmjb
DD-WRT Novice


Joined: 16 May 2015
Posts: 6

PostPosted: Mon May 18, 2015 3:41    Post subject: Reply with quote
Malachi wrote:
One of the commands would return an error message.
Of course it would knock out the wireless, it reboots the router and erases your settings.


Yes, but wired didn't work either, so I had no way of changing the settings to make wireless work again.
Mrknister
DD-WRT Novice


Joined: 31 May 2015
Posts: 2

PostPosted: Sun May 31, 2015 9:06    Post subject: Re: wl0.1 cant connect Reply with quote
JNavas wrote:

Did you read the Asus RT-N66U - DD-WRT Wiki?!
If you have 64K CFE, try:


Had the same problem with virtual wireless. I tried the Kong K3 build and it worked, until I started to use QOS, then the WLAN ended in a restart loop. I tried to erase nvram, but the problem was still there. Is there any other recommended version? With Brainslayer Build I had the virtual wireless problem too!

EDIT: I have the 1.0.1.3 CFE

Regards Mrknister
BioByte
DD-WRT Novice


Joined: 07 Jun 2015
Posts: 1

PostPosted: Sun Jun 07, 2015 10:02    Post subject: still be able to boot, but all eth ports not working Reply with quote
Hi everyone,

I'm not flashing the router when it happened, just found one at this state, probably, after power failure.

When I turn power on:
1) LAN 1,2 & WAN LEDs light up dimmed (~30% of normal light)
2) after 1 sec POWER LED on
3) after ~20 sec 5GHz WLAN LED on
4) then router go to reboot for 2 times (all LEDs stay in the same state except 2.4GHz, it light up for 2 sec when router go to reboot)

When router boots last time, I'm able to connect to admin page and telnet via Wi-Fi. So I managed to erase nvram, and flash firmware, but it does not help, all ethernet ports (LANs & WAN) still are disabled.

Would anyone suggest, is any chance to unbrick it with TUMPA (JTAG) or ethernet switch is burned out?

It's serial console log for first boot cycle:

Code:
Decompressing...done
tmp_ret= 0


CFE version 5.100.127 based on BBP 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: 五  9月 14 17:47:35 CST 2012 (boyau@localhost)
Copyright (C) 2000-2008 Broadcom Corporation.

Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
CPU type 0x19749: 600MHz
Tot mem: 131072 KBytes

CFE mem:    0x80700000 - 0x80839350 (1282896)
Data:       0x80733120 - 0x807363E0 (12992)
BSS:        0x807363E0 - 0x80737350 (3952)
Heap:       0x80737350 - 0x80837350 (1048576)
Stack:      0x80837350 - 0x80839350 (8192)
Text:       0x80700000 - 0x80733118 (209176)

Null Rescue Flag.
Loader:raw Filesys:tftp Dev:(null) File:: Options:(null)
Loading: TFTP Server.
Failed.
Could not load :: Error
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: ...... 3310368 bytes read
Entry at 0x80001000
Starting program at 0x80001000
start_kernel
Linux version 2.6.22.19 (root@asus) (gcc version 4.2.3) #1 Sat Jan 10 19:02:22 CST 2015
CPU revision is: 00019749
Determined physical RAM map:
 memory: 07fff000 @ 00000000 (usable)
 memory: 08000000 @ 87fff000 (usable)
Built 1 zonelists.  Total pages: 585216
Kernel command line: root=/dev/mtdblock2 noinitrd console=ttyS0,115200
Primary instruction cache 32kB, physically tagged, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, linesize 32 bytes.
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 2048 (order: 11, 8192 bytes)
CPU: BCM5300 rev 1 pkg 0 at 600 MHz
Using 300.000 MHz high precision timer.
console [ttyS0] enabled
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 238608k/131068k available (2531k kernel code, 22572k reserved, 504k data, 196k init, 131072k highmem)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
PCI: Initializing host
PCI: Reset RC
PCI: Initializing host
PCI: Reset RC
PCI: Fixing up bus 0
PCI/PCIe coreunit 0 is set to bus 1.
PCI: Fixing up bridge
PCI: Fixing up bridge
PCI: Enabling device 0000:01:00.1 (0004 -> 0006)
PCI: Fixing up bus 1
PCI/PCIe coreunit 1 is set to bus 2.
PCI: Fixing up bridge
PCI: Fixing up bridge
PCI: Enabling device 0000:02:00.1 (0004 -> 0006)
PCI: Fixing up bus 2
NET: Registered protocol family 2
Time: MIPS clocksource has been installed.
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
highmem bounce pool size: 64 pages
squashfs: version 3.2-r2 (2007/01/15) Phillip Lougher
io scheduler noop registered (default)
HDLC line discipline: version $Revision: 4.8 $, maxframe=4096
N_HDLC line discipline registered.
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0xb8000300 (irq = 8) is a 16550A
serial8250: ttyS1 at MMIO 0xb8000400 (irq = 8) is a 16550A
PPP generic driver version 2.4.2
MPPE/MPPC encryption/compression module registered
NET: Registered protocol family 24
PPPoL2TP kernel driver, V0.18.3
PPTP driver version 0.8.5
Physically mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank
 Amd/Fujitsu Extended Query Table at 0x0040
Physically mapped flash: CFI does not contain boot bank location. Assuming top.
number of CFI chips: 1
cfi_cmdset_0002: Disabling erase-suspend-program due to code brokenness.
Flash device: 0x2000000 at 0x1c000000
Creating 5 MTD partitions on "Physically mapped flash":
0x00000000-0x00040000 : "pmon"
0x00040000-0x01fe0000 : "linux"
0x0016e474-0x01980000 : "rootfs"
0x01fe0000-0x02000000 : "nvram"
0x01ee0000-0x01fe0000 : "jffs2"
Found an  serial flash with 0 0KB blocks; total size 0MB
sflash: found no supported devices
dev_nvram_init: _nvram_init
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
u32 classifier
    OLD policer on
Netfilter messages via NETLINK v0.30.
nf_conntrack version 0.5.0 (2048 buckets, 16384 max)
ipt_time loading
ip_tables: (C) 2000-2006 Netfilter Core Team
net/ipv4/netfilter/tomato_ct.c [Jan 10 2015 19:01:45]
NET: Registered protocol family 1
NET: Registered protocol family 10
ip6_tables: (C) 2000-2006 Netfilter Core Team
NET: Registered protocol family 17
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.
Freeing unused kernel memory: 196k freed
Warning: unable to open an initial console.
Algorithmics/MIPS FPU Emulator v1.5
set_action 0
firmware version: 3.0.0.4.376_3754-g5ef7c1f
[1 init:init_nvram +4] init_nvram for 27
num_of_mssid_support(0x0092): [mssid] support [3] mssid
ctf: module license 'Proprietary' taints kernel.
et_module_init: passivemode set to 0x0
et_module_init: et_txq_thresh set to 0x400
WARNING: at net/core/dev.c:3659 unregister_netdevice()
Call Trace:
[<8000f42c>] dump_stack+0x8/0x34
[<80199fb4>] unregister_netdev+0x1c/0x2c
[<c0070874>] et_free+0x5c/0x230 [et]
[<c0071128>] et_probe+0x394/0x558 [et]
[<80109290>] pci_device_probe+0x7c/0xbc
[<80128bb4>] driver_probe_device+0xec/0x2b8
[<80129144>] __driver_attach+0x204/0x24c
[<801279ac>] bus_for_each_dev+0x58/0xbc
[<80127ecc>] bus_add_driver+0xb0/0x218
[<801090cc>] __pci_register_driver+0x58/0xc0
[<8004cf2c>] sys_init_module+0x178/0x1668
[<800111d0>] stack_done+0x20/0x44

wl_module_init: passivemode set to 0x0
PCI: Enabling device 0000:01:01.0 (0000 -> 0002)
eth0: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
PCI: Enabling device 0000:02:01.0 (0000 -> 0002)
eth1: Broadcom BCM4331 802.11 Wireless Controller 6.30.163.2002 (r382208)
hotplug net INTERFACE=eth0 ACTION=add
hotplug net INTERFACE=eth1 ACTION=add
/ # check_action 0
start jffs2: 4, 1048576
[1 init:init_main +7] main loop signal/state=17
start_logger:
start_usb
NTFS (with native replay) support included
optimized: speed
Build_for__asus_n66u_2011-10-27_U86_r187446_b122

_ifconfig: name=eth0 flags=1043 IFUP addr=(null) netmask=(null)
hotplug net INTERFACE=vlan1 ACTION=add
hotplug net INTERFACE=vlan2 ACTION=add
update_lan_state(lan_, 0, 0)
generate_wl_para(0x0e73): unit 0 subunit -1
num_of_mssid_support(0x0092): [mssid] support [3] mssid
generate_wl_para(0x1133): bw: 0
generate_wl_para(0x1135): chanspec: 0
generate_wl_para(0x1136): bw_cap: 3
generate_wl_para(0x113c): obss_coex: 1
wlconf_pre(0x02ed): set vhtmode 1
generate_wl_para(0x0e73): unit 1 subunit -1
num_of_mssid_support(0x0092): [mssid] support [3] mssid
chanspec_fix(0x07c5): unit: 1, bw_cap: 3, chanspec: 0
generate_wl_para(0x1133): bw: 0
generate_wl_para(0x1135): chanspec: 0
generate_wl_para(0x1136): bw_cap: 3
generate_wl_para(0x113c): obss_coex: 1
wlconf_pre(0x02ed): set vhtmode 1
set_wltxpower(0x08f1): unit: 1, txpower: 100
start_lan: setting up the bridge br0
hotplug net INTERFACE=br0 ACTION=add
vlan1: cmd=14: Operation not supported
_ifconfig: name=vlan1 flags=1043 IFUP addr=(null) netmask=(null)
start_lan: setting MAC of br0 bridge to 60:A4:4C:D2:62:C8
_ifconfig: name=eth1 flags=1043 IFUP addr=(null) netmask=(null)
generate_wl_para(0x0e73): unit 1 subunit -1
num_of_mssid_support(0x0092): [mssid] support [3] mssid
chanspec_fix(0x07c5): unit: 1, bw_cap: 3, chanspec: 0
generate_wl_para(0x1133): bw: 0
generate_wl_para(0x1135): chanspec: 0
generate_wl_para(0x1136): bw_cap: 3
generate_wl_para(0x113c): obss_coex: 1
generate_wl_para(0x0e73): unit 1 subunit 1
generate_wl_para(0x0e73): unit 1 subunit 2
generate_wl_para(0x0e73): unit 1 subunit 3

eth2: cmd=14: No such device
_ifconfig: name=eth2 flags=1043 IFUP addr=(null) netmask=(null)
eth2: No such device
_ifconfig: name=br0 flags=1043 IFUP addr=192.168.1.1 netmask=255.255.255.0
_ifconfig: name=lo flags=1043 IFUP addr=127.0.0.1 netmask=255.0.0.0
route_manip: cmd=ADD name=lo addr=127.0.0.0 netmask=255.0.0.0 gateway=0.0.0.0 metric=0
update_lan_state(lan_, 2, 0)
stop_nat_rules: apply the redirect_rules!
# wanduck: Got LAN(-1) information:

# Enable direct rule
start_lan 1773
start_services 3251
acsd: scan in progress ...
acsd: scan in progress ...
block hotplug INTERFACE=8/0/0 ACTION=add USBPORT=1-1.4 HOST=(null) DEVICE=sda
check_action 0
acsd: scan in progress ...
acsd: selected channel spec: 0xd92e (48u)
[1 init:start_dnsmasq +12] begin
[1 init:stop_dnsmasq +12] begin
[1 init:stop_dnsmasq +12] end
[1 init:start_dnsmasq +12] end
start_lan_port(0) 1
decomp: fname=/var/lib/misc/rstats-speed.gz
TZ watchdog
decomp: gzip -dc /var/lib/misc/rstats-speed.gz > /var/tmp/rstats-uncomp != 0
load: speed_count = 0
load: read source= save_path=
load_history: fname=/var/lib/misc/rstats-history.gz
decomp: fname=/var/lib/misc/rstats-history.gz
start_pptpd: getpid= 1
vlan1: cmd=14: Operation not supported
decomp: gzip -dc /var/lib/misc/rstats-history.gz > /var/tmp/rstats-uncomp != 0
decomp: fname=/var/lib/misc/rstats-history.gz
decomp: gzip -dc /var/lib/misc/rstats-history.gz > /var/tmp/rstats-uncomp != 0
load_history: load failed
disk_monitor: starting...
disk_monitor: day=1, week=6, time=0:0.
disk_monitor: decide if scan the target...
disk_monitor: 0: wait_second=86400...
disk_monitor: 1: wait_second=86400...
disk_monitor: 2: wait_second=311040000...
disk_monitor: wait_second=86400...
disk_monitor: Pause...

eth2: cmd=14: No such device
start_wan: start_wan_if(0)!
[1 init:start_wan_if +13] unit=0.
update_wan_state(wan0_, 0, 0)
convert_wan_nvram(wan0_)
update_wan_state(wan0_, 1, 0)
_ifconfig: name=eth0 flags=1043 IFUP addr=(null) netmask=(null)
start_auth:: done
start_wan_if(): End.
No switch interface!!!
udhcpc_wan:: deconfig
_ifconfig: name=eth0 flags=1043 IFUP addr=0.0.0.0 netmask=(null)
wan_down(eth0)
wan_down(eth0): .
stop_auth:: done
route_manip: cmd=DEL name=eth0 addr=0.0.0.0 netmask=0.0.0.0 gateway=(null) metric=0
U2EC starting ...
update_wan_state(wan0_, 3, 0)
update_wan_state(wan0_, 4, 3)
udhcpc:: deconfig done
check_action 0
set_action 7
set_action 0
init_main(0x1447): device failed 1 times, reboot...
Restarting system.
Please stand by while rebooting the system...
johanmazel
DD-WRT Novice


Joined: 30 May 2015
Posts: 7

PostPosted: Mon Jun 15, 2015 8:36    Post subject: Reply with quote
tpmjb wrote:
Malachi wrote:
One of the commands would return an error message.
Of course it would knock out the wireless, it reboots the router and erases your settings.


Yes, but wired didn't work either, so I had no way of changing the settings to make wireless work again.

I have the same problem with the 27240 build.
I willing to help for the testing if it can help solve this problem.
samandiriel
DD-WRT Novice


Joined: 13 Jun 2012
Posts: 18
Location: Edmonton, Alberta, Canada

PostPosted: Fri Jun 19, 2015 6:10    Post subject: Any advice on PPPoE not working? Reply with quote
I am looking to replace my old RT-N16, and the N66U looked like a winner. I successfully flashed build 26138, and everything seemed swell.. except I couldn't actually connect using PPPoE to my provider (CenturyLink / Qwest) using the same set up I had on my old router (ie, via a transparently bridged ActionTec C1000A modem+router). It just never connects and gets an IP (and while i have a static IP, I don't see any way to set it explicitly for PPPoE in DD-WRT although I can do so in other firmware/routers - a mystery I've not been able to solve).

I've found a few posts here and there from other users having similar issues but unfortunately no answers that have worked / seemed relevant.

Before I begin flailing about trying other builds more or less randomnly, can anyone offer any insights on getting PPPoE working with 26138, or point me to a build known to have working PPPoE? Right now my default plan is to try 26446, recommended a few posts up in this thread.

Many thanks!

_________________
Tyler Style
My Solutions IT
Getting technology working for you instead of abusing you.
KrypteX
DD-WRT Guru


Joined: 18 Jan 2014
Posts: 2411

PostPosted: Fri Jun 19, 2015 6:58    Post subject: Re: Any advice on PPPoE not working? Reply with quote
samandiriel wrote:
Before I begin flailing about trying other builds more or less randomnly, can anyone offer any insights on getting PPPoE working with 26138, or point me to a build known to have working PPPoE?

26138 is quite an old build, if you check the changelog in my signature, you'll see that there were a lot of changes for Broadcom since then, including PPPoE fixes. I suggest to flash latest 27360.

_________________
THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
samandiriel
DD-WRT Novice


Joined: 13 Jun 2012
Posts: 18
Location: Edmonton, Alberta, Canada

PostPosted: Fri Jun 19, 2015 12:39    Post subject: Re: Any advice on PPPoE not working? Reply with quote
KrypteX wrote:
26138 is quite an old build, if you check the changelog in my signature, you'll see that there were a lot of changes for Broadcom since then, including PPPoE fixes. I suggest to flash latest 27360.


Thanks for the recommendation, I shall give it a whirl.

UPDATE: Woo! It's working out of the box! Now to see if my customizations will take. Many thanks again Smile

_________________
Tyler Style
My Solutions IT
Getting technology working for you instead of abusing you.
samandiriel
DD-WRT Novice


Joined: 13 Jun 2012
Posts: 18
Location: Edmonton, Alberta, Canada

PostPosted: Sat Jun 20, 2015 1:49    Post subject: Re: Any advice on PPPoE not working? Reply with quote
KrypteX wrote:
26138 is quite an old build, if you check the changelog in my signature, you'll see that there were a lot of changes for Broadcom since then, including PPPoE fixes. I suggest to flash latest 27360.

Seems to be good so far for me, but I did find a bug. How should such be reported?

(adding static IPs for MAC addresses in Services and then saving will bork it if any of the entries are left blank - tho the IPs appear to be assigned, the list in the GUI will only be blank entries; however, entering a new reservation for the same IP generates an error. The "blank" entry has to be deleted... tho it might be difficult to tell which is the 'correct' blank entry since it doesn't display any of the data for them!)

_________________
Tyler Style
My Solutions IT
Getting technology working for you instead of abusing you.


Last edited by samandiriel on Sat Jun 20, 2015 13:18; edited 1 time in total
Goto page Previous  1, 2, 3 ... 152, 153, 154 ... 167, 168, 169  Next Display posts from previous:    Page 153 of 169
Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Broadcom 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 can attach files in this forum
You can download files in this forum