Posted: Tue Sep 12, 2017 15:54 Post subject: Re: Tried to fash doesnt work
teslacoil wrote:
Dioid wrote:
Thx had that idea too ill try that. But its the first Time in many flashing procedures, that someting like this happens, i will do a 30/30/30 first.
It's the times like this that bite you, where it provides credence as to why the things that are written in the wiki are there.
Did 2 Times Hard reset 30/30/30, after that its the first time the unit shows CPU Temperature, which was never available before, then i tried to Flash to 33345, same Problem, not possible after 2 Seconds procedure stopped, router restarts without flash and only one USB LED on, ok next 30/30/30, nvram only 24 kb, was erased i think. But now CPU Temperature isnt availible again, like before the first hardreset. Now its time to laugh at. Does NOT WORK and whats about the Cpu Temp and the USB issue? MY God.
Posted: Tue Sep 12, 2017 16:33 Post subject: Re: Tried to fash doesnt work
Dioid wrote:
Did 2 Times Hard reset 30/30/30, after that its the first time the unit shows CPU Temperature, which was never available before, then i tried to Flash to 33345, same Problem, not possible after 2 Seconds procedure stopped, router restarts without flash and only one USB LED on, ok next 30/30/30, nvram only 24 kb, was erased i think. But now CPU Temperature isnt availible again, like before the first hardreset. Now its time to laugh at. Does NOT WORK and whats about the Cpu Temp and the USB issue? MY God.
You still didn't erase the NVRAM before and after the flash as I suggested. A 30/30/30 reset on some router models doesn't even do a thing, besides wasting your time while fumbling with a power cord and reset button. These days it's usually never necessary to even bother with it.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Sep 12, 2017 18:30 Post subject: Re: Tried to fash doesnt work
teslacoil wrote:
You still didn't erase the NVRAM before and after the flash as I suggested.
cause its damn pointless, stop these myths already, ESPECIALLY the "before" part if anything..
teslacoil wrote:
A 30/30/30 reset on some router models doesn't even do a thing, besides wasting your time while fumbling with a power cord and reset button. These days it's usually never necessary to even bother with it.
just like the "have to erase before and after flash"... _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Posted: Tue Sep 12, 2017 19:43 Post subject: Re: Tried to fash doesnt work
tatsuya46 wrote:
cause its damn pointless, stop these myths already, ESPECIALLY the "before" part if anything..
tatsuya46 wrote:
just like the "have to erase before and after flash"...
Years ago, the original recommendation from the wiki, which is still in the wiki to this day, was to do a 30/30/30 reset before and after the flash. Since the erase NVRAM command does what a 30/30/30 achieves on many of today's model routers, it is essentially doing what the wiki specifies. If there is a technical reason not to do it before the flash, then great. The wiki needs updating.
redhawk0 wrote:
Here's a 5th way that I use for the E1000v2 unit that I have.
Web Gui doesn't work on this unit very well....neither does 30/30/30 method....loging to the CLI...the "erase nvram" doesn't seem to reset the router all the way. I still have the password that I set...who knows what else.
But....
If I do an "mtd erase nvram" then it unlocks/erase the nvram correctly.
Just one more thing reason you can't rely on a single method of clearing nvram on these units.
redhawk
redhawk0 wrote:
Seems to be router specific too...for example...never do an "erase nvram" from the CLI on an RT-N16...(if you've upgraded to K3.x)...the unit really only has 64K nvram...but it reports 128k in the CLI...and 256k in the web GUI...well...if the erase nvram command is done...it tries to erase more than the actual 64k.
I've learned to use the Web GUI reset only on this unit.
Now...on some units if you use the reset on the Web GUI...it doesn't clear out all the variables for the VAP....but from the CLI it does. I've seen my Ralink unit clear all nvram except the dd-wrt style color variable.
I've seen where the reset button doesn't clear anything...but most older units it still does.
Its hit or miss...you have to try each method...and once you find what works for your unit...stick with it.
sorry...can't give you a more "official" answer than that.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Sep 12, 2017 20:09 Post subject: Re: Tried to fash doesnt work
teslacoil wrote:
tatsuya46 wrote:
cause its damn pointless, stop these myths already, ESPECIALLY the "before" part if anything..
tatsuya46 wrote:
just like the "have to erase before and after flash"...
Years ago, the original recommendation from the wiki, which is still in the wiki to this day, was to do a 30/30/30 reset before and after the flash. Since the erase NVRAM command does what a 30/30/30 achieves on many of today's model routers, it is essentially doing what the wiki specifies. If there is a technical reason not to do it before the flash, then great. The wiki needs updating.
redhawk0 wrote:
Here's a 5th way that I use for the E1000v2 unit that I have.
Web Gui doesn't work on this unit very well....neither does 30/30/30 method....loging to the CLI...the "erase nvram" doesn't seem to reset the router all the way. I still have the password that I set...who knows what else.
But....
If I do an "mtd erase nvram" then it unlocks/erase the nvram correctly.
Just one more thing reason you can't rely on a single method of clearing nvram on these units.
redhawk
redhawk0 wrote:
Seems to be router specific too...for example...never do an "erase nvram" from the CLI on an RT-N16...(if you've upgraded to K3.x)...the unit really only has 64K nvram...but it reports 128k in the CLI...and 256k in the web GUI...well...if the erase nvram command is done...it tries to erase more than the actual 64k.
I've learned to use the Web GUI reset only on this unit.
Now...on some units if you use the reset on the Web GUI...it doesn't clear out all the variables for the VAP....but from the CLI it does. I've seen my Ralink unit clear all nvram except the dd-wrt style color variable.
I've seen where the reset button doesn't clear anything...but most older units it still does.
Its hit or miss...you have to try each method...and once you find what works for your unit...stick with it.
sorry...can't give you a more "official" answer than that.
redhawk
the wiki needs updating in so many places its not even funny, people still follow guides on there made from builds 5+ years ago then wonder why it doesnt work. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Posted: Tue Sep 12, 2017 20:47 Post subject: Re: Tried to fash doesnt work
Dioid wrote:
After 2-3 seconds of flashing reboot and then after 2 mins later it shows 33342 and works what the..... Doesnt flash. Never had this before.
Router: Archer c7 v2
Firmware: DD-WRT v3.0-r33342 std (09/09/17)
tried to update to DD-WRT v3.0-r33345
Reset: no
Quite strange. tried with newest Firefox with webinterface and Ubuntu 16.04.
Joined: 16 Nov 2015 Posts: 6437 Location: UK, London, just across the river..
Posted: Tue Sep 12, 2017 21:06 Post subject: Re: Tried to fash doesnt work
tatsuya46 wrote:
teslacoil wrote:
You still didn't erase the NVRAM before and after the flash as I suggested.
cause its damn pointless, stop these myths already, ESPECIALLY the "before" part if anything..
teslacoil wrote:
A 30/30/30 reset on some router models doesn't even do a thing, besides wasting your time while fumbling with a power cord and reset button. These days it's usually never necessary to even bother with it.
just like the "have to erase before and after flash"...
im sure tatsuya46 does erase nvram from time to time too
otherwise no wonder why you report so many issues have you tried erase nvram tatsuya46?
I also support re writhing block by block with new firmware does not need erase nvram because its pointless no info suppose to survive but as the Developers say we have to do it in case of any bugs like a first measure so, is there any reason not to do it...what are those artifact that suppose to survive after firmware updates, how do they look like, code leftovers, different memory locations....??
Anyway it went off topic again sorry for that ... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55819 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Sep 12, 2017 21:09 Post subject: Re: Tried to fash doesnt work
Alozaros wrote:
tatsuya46 wrote:
teslacoil wrote:
You still didn't erase the NVRAM before and after the flash as I suggested.
cause its damn pointless, stop these myths already, ESPECIALLY the "before" part if anything..
teslacoil wrote:
A 30/30/30 reset on some router models doesn't even do a thing, besides wasting your time while fumbling with a power cord and reset button. These days it's usually never necessary to even bother with it.
just like the "have to erase before and after flash"...
im sure tatsuya46 does erase nvram from time to time too
otherwise no wonder why you report so many issues have you tried erase nvram tatsuya46?
I also support re writhing block by block with new firmware does not need erase nvram because its pointless no info suppose to survive but as the Developers say we have to do it in case ob any bugs like a from line first measure so than is there any reason not to do it...what are those artifact that suppose to survive after firmware updates how do they look like, code leftovers, different memory locations....??
Anyway it went off topic again sorry for that ...
ya rare, when i want space back or when im looking at those weird symbols in nvram no one knows where they come from. certainly not upon every update.
really hope ur not thinking the growing wall of tickets is cause of no constant nvram wiping cause its not.. read through them & try it urself, ull see the issue(s) & that nvram is nothing to do with it. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
[
I would like to see the dmesg output of your WRT160NL sometime if you get a chance.
thanks -
Here it is the one from 33006:
root@DD-WRT:~# dmesg
<7>[ 0.000000] Normal zone: 0 pages reserved
<7>[ 0.000000] Normal zone: 8192 pages, LIFO batch:0
<4>[ 0.000000] Primary instruction cache 64kB, 4-way, VIPT, I-cache aliases, linesize 32 bytes.
<4>[ 0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
<7>[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
<7>[ 0.000000] pcpu-alloc: [0] 0
<4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
<5>[ 0.000000] Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd init=/sbin/init
<6>[ 0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
<6>[ 0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
<6>[ 0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
<6>[ 0.000000] Writing ErrCtl register=00000000
<6>[ 0.000000] Readback ErrCtl register=00000000
<6>[ 0.000000] Memory: 28968k/32768k available (2350k kernel code, 3800k reserved, 398k data, 192k init, 0k highmem)
<6>[ 0.000000] NR_IRQS:83
<0>[ 0.000000] irq init done
<4>[ 0.000000] plat_time_init: plat time init done
<6>[ 0.080000] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
<6>[ 0.080000] pid_max: default: 32768 minimum: 301
<6>[ 0.080000] Mount-cache hash table entries: 512
<6>[ 0.090000] NET: Registered protocol family 16
<4>[ 0.100000] Can't analyze schedule() prologue at 80066e44
<6>[ 0.120000] bio: create slab <bio-0> at 0
<5>[ 0.130000] SCSI subsystem initialized
<6>[ 0.130000] usbcore: registered new interface driver usbfs
<6>[ 0.140000] usbcore: registered new interface driver hub
<6>[ 0.140000] usbcore: registered new device driver usb
<6>[ 0.150000] Switching to clocksource MIPS
<6>[ 0.150000] NET: Registered protocol family 2
<6>[ 0.160000] TCP established hash table entries: 512 (order: 0, 4096 bytes)
<6>[ 0.160000] TCP bind hash table entries: 512 (order: -1, 2048 bytes)
<6>[ 0.170000] TCP: Hash tables configured (established 512 bind 512)
<6>[ 0.170000] TCP: reno registered
<6>[ 0.180000] UDP hash table entries: 256 (order: 0, 4096 bytes)
<6>[ 0.180000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
<6>[ 0.190000] NET: Registered protocol family 1
<5>[ 0.190000] gpio_proc: module loaded and /proc/gpio/ created
<6>[ 0.200000] Register LED Device
<5>[ 0.200000] wl0gpio_proc: module loaded and /proc/wl0gpio/ created
<4>[ 0.210000] AR7100 GPIOC major 0
<6>[ 0.210000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
<6>[ 0.220000] msgmni has been set to 56
<6>[ 0.230000] io scheduler noop registered
<6>[ 0.230000] io scheduler deadline registered (default)
<6>[ 0.230000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
<6>[ 0.260000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 19) is a 16550A
<6>[ 0.270000] console [ttyS0] enabled, bootconsole disabled
<0>[ 0.280000] guessed flashsize = 8M
<0>[ 0.290000] scanning for root partition
<0>[ 0.290000] WRT160NL/E2100L uboot detected
<0>[ 0.290000] bootloader size = 40000
<0>[ 0.300000]
<0>[ 0.300000] found squashfs at 194000
<5>[ 0.310000] Creating 8 MTD partitions on "ar7100-nor0":
<5>[ 0.310000] 0x000000000000-0x000000040000 : "RedBoot"
<5>[ 0.320000] 0x000000040000-0x0000007e0000 : "linux"
<5>[ 0.330000] 0x000000194000-0x0000007d0000 : "rootfs"
<4>[ 0.330000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
<5>[ 0.350000] mtd: partition "rootfs" set to be root filesystem
<5>[ 0.350000] 0x0000007d0000-0x0000007e0000 : "ddwrt"
<5>[ 0.360000] 0x0000007e0000-0x0000007f0000 : "nvram"
<5>[ 0.360000] 0x0000007f0000-0x000000800000 : "FIS directory"
<5>[ 0.370000] 0x0000007f0000-0x000000800000 : "board_config"
<5>[ 0.380000] 0x000000000000-0x000000800000 : "fullflash"
<4>[ 0.390000] ->Oops: flash id 0xef4017 .
<6>[ 0.390000] tun: Universal TUN/TAP device driver, 1.6
<6>[ 0.400000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
<6>[ 0.800000] PPP generic driver version 2.4.2
<6>[ 0.810000] PPP BSD Compression module registered
<6>[ 0.810000] PPP Deflate Compression module registered
<6>[ 0.820000] PPP MPPE Compression module registered
<6>[ 0.820000] NET: Registered protocol family 24
<6>[ 0.830000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
<6>[ 0.860000] ar71xx-ehci ar71xx-ehci.0: Atheros AR91xx built-in EHCI controller
<6>[ 0.870000] ar71xx-ehci ar71xx-ehci.0: new USB bus registered, assigned bus number 1
<6>[ 0.910000] ar71xx-ehci ar71xx-ehci.0: irq 3, io mem 0x1b000000
<6>[ 0.930000] ar71xx-ehci ar71xx-ehci.0: USB 2.0 started, EHCI 1.00
<6>[ 0.930000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
<6>[ 0.940000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[ 0.950000] usb usb1: Product: Atheros AR91xx built-in EHCI controller
<6>[ 0.950000] usb usb1: Manufacturer: Linux 3.10.107 ehci_hcd
<6>[ 0.960000] usb usb1: SerialNumber: platform
<6>[ 0.960000] hub 1-0:1.0: USB hub found
<6>[ 0.970000] hub 1-0:1.0: 1 port detected
<6>[ 0.980000] u32 classifier
<6>[ 0.980000] Performance counters on
<6>[ 0.990000] input device check on
<6>[ 0.990000] Actions configured
<6>[ 0.990000] Netfilter messages via NETLINK v0.30.
<6>[ 1.000000] nf_conntrack version 0.5.0 (452 buckets, 1808 max)
<4>[ 1.010000] nf_conntrack_rtsp v0.7 loading
<4>[ 1.010000] nf_nat_rtsp v0.7 loading
<6>[ 1.010000] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>[ 1.020000] TCP: westwood registered
<6>[ 1.020000] TCP: hybla registered
<6>[ 1.030000] TCP: vegas registered
<6>[ 1.030000] NET: Registered protocol family 17
<5>[ 1.030000] Bridge firewalling registered
<6>[ 1.040000] 8021q: 802.1Q VLAN Support v1.8
<6>[ 1.040000] searching for nvram
<6>[ 1.050000] nvram size = 0
<6>[ 1.080000] Atheros AR71xx hardware watchdog driver version 0.1.0
<6>[ 1.090000] ar71xx-wdt: timeout=15 secs (max=21) ref freq=200000000
<6>[ 1.100000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
<6>[ 1.110000] Freeing unused kernel memory: 192K (80310000 - 80340000)
<7>[ 3.950000] ar71xx-wdt: enabling watchdog timer
<6>[ 4.020000] libphy: ag71xx_mdio: probed
<6>[ 4.350000] Registering RTL8306SDM switch with Chip ID: 0x5988, version: 0x0000
<6>[ 4.350000] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.0:00 [uid=00008306, driver=Realtek RTL8306S]
<6>[ 4.360000] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:RMII
<6>[ 4.690000] ag71xx ag71xx.1: connected to PHY at ag71xx-mdio.0:04 [uid=00008306, driver=Realtek RTL8306S]
<6>[ 4.700000] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:RMII
<6>[ 4.870000] Loading modules backported from Linux version wt-2017-01-31-0-ge882dff19e7f
<6>[ 4.870000] Backport generated by backports.git backports-20160324-13-g24da7d3c
<7>[ 5.740000] ath: EEPROM regdomain: 0x0
<7>[ 5.740000] ath: EEPROM indicates default country code should be used
<7>[ 5.740000] ath: doing EEPROM country->regdmn map search
<7>[ 5.740000] ath: country maps to regdmn code: 0x3a
<7>[ 5.740000] ath: Country alpha2 being used: US
<7>[ 5.740000] ath: Regpair used: 0x3a
<7>[ 5.770000] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
<6>[ 5.780000] ieee80211 phy0: Atheros AR9100 MAC/BB Rev:7 AR2122 RF Rev:a2 mem=0xb80c0000, irq=2
<7>[ 6.350000] ar71xx: pll_reg 0xb8050014: 0x13000a44
<6>[ 6.350000] eth0: link up (100Mbps/Full duplex)
<6>[ 8.280000] device br0 entered promiscuous mode
<6>[ 8.310000] eth0: link down
<6>[ 8.350000] device eth0 entered promiscuous mode
<6>[ 8.410000] device eth1 entered promiscuous mode
<6>[ 8.410000] br0: port 1(eth0) entered forwarding state
<6>[ 8.420000] br0: port 1(eth0) entered forwarding state
<6>[ 8.420000] device br0 left promiscuous mode
<6>[ 8.430000] device br0 entered promiscuous mode
<6>[ 8.450000] device br0 left promiscuous mode
<7>[ 8.510000] ath: EEPROM regdomain: 0x822a
<7>[ 8.510000] ath: EEPROM indicates we should expect a country code
<7>[ 8.510000] ath: doing EEPROM country->regdmn map search
<7>[ 8.510000] ath: country maps to regdmn code: 0x22
<7>[ 8.510000] ath: Country alpha2 being used: NZ
<7>[ 8.510000] ath: Regpair used: 0x22
<7>[ 8.510000] ath: regdomain 0x822a dynamically updated by user
<6>[ 9.280000] br0: port 1(eth0) entered disabled state
<7>[ 10.350000] ar71xx: pll_reg 0xb8050014: 0x13000a44
<6>[ 10.350000] eth0: link up (100Mbps/Full duplex)
<6>[ 10.350000] br0: port 1(eth0) entered forwarding state
<6>[ 10.360000] br0: port 1(eth0) entered forwarding state
<6>[ 12.360000] br0: port 1(eth0) entered forwarding state
<6>[ 13.410000] device ath0.1 entered promiscuous mode
<6>[ 14.100000] br0: port 3(ath0.1) entered forwarding state
<6>[ 14.100000] br0: port 3(ath0.1) entered forwarding state
<6>[ 14.780000] br0: port 3(ath0.1) entered disabled state
<6>[ 16.170000] ath0: authenticate with c4:6e:1f:2b:71:da
<6>[ 16.200000] ath0: send auth to c4:6e:1f:2b:71:da (try 1/3)
<6>[ 16.220000] ath0: authenticated
<6>[ 16.260000] ath0: associate with c4:6e:1f:2b:71:da (try 1/3)
<6>[ 16.260000] ath0: RX AssocResp from c4:6e:1f:2b:71:da (capab=0x411 status=0 aid=3)
<6>[ 16.270000] ath0: associated
<6>[ 18.380000] br0: port 3(ath0.1) entered forwarding state
<6>[ 18.390000] br0: port 3(ath0.1) entered forwarding state
<6>[ 20.390000] br0: port 3(ath0.1) entered forwarding state
<6>[ 25.070000] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
<6>[ 267.700000] device eth0 left promiscuous mode
<6>[ 267.700000] br0: port 1(eth0) entered disabled state
<6>[ 267.710000] device eth1 left promiscuous mode
<6>[ 267.720000] br0: port 2(eth1) entered disabled state
<4>[ 267.850000] ipcomp6: Unknown symbol ipcomp_input (err 0)
<4>[ 267.860000] ipcomp6: Unknown symbol xfrm6_rcv (err 0)
<4>[ 267.860000] ipcomp6: Unknown symbol ipcomp_destroy (err 0)
<4>[ 267.870000] ipcomp6: Unknown symbol xfrm6_tunnel_alloc_spi (err 0)
<4>[ 267.870000] ipcomp6: Unknown symbol ip6_update_pmtu (err 0)
<4>[ 267.880000] ipcomp6: Unknown symbol ipcomp_output (err 0)
<4>[ 267.880000] ipcomp6: Unknown symbol xfrm6_find_1stfragopt (err 0)
<4>[ 267.890000] ipcomp6: Unknown symbol xfrm6_tunnel_spi_lookup (err 0)
<4>[ 267.900000] ipcomp6: Unknown symbol ip6_redirect (err 0)
<4>[ 267.900000] ipcomp6: Unknown symbol ipcomp_init_state (err 0)
<4>[ 267.950000] xfrm6_tunnel: Unknown symbol xfrm6_tunnel_register (err 0)
<4>[ 267.960000] xfrm6_tunnel: Unknown symbol xfrm6_rcv_spi (err 0)
<4>[ 267.960000] xfrm6_tunnel: Unknown symbol xfrm6_tunnel_deregister (err 0)
<4>[ 267.980000] xfrm6_mode_tunnel: Unknown symbol ip6_dst_hoplimit (err 0)
<4>[ 267.990000] xfrm6_mode_tunnel: Unknown symbol xfrm6_prepare_output (err 0)
<4>[ 268.030000] xfrm6_mode_beet: Unknown symbol xfrm6_prepare_output (err 0)
<4>[ 268.090000] ip6_tunnel: Unknown symbol xfrm6_tunnel_register (err 0)
<4>[ 268.100000] ip6_tunnel: Unknown symbol ip6_local_out (err 0)
<4>[ 268.110000] ip6_tunnel: Unknown symbol ipv6_push_nfrag_opts (err 0)
<4>[ 268.110000] ip6_tunnel: Unknown symbol ip6_route_output (err 0)
<4>[ 268.120000] ip6_tunnel: Unknown symbol ipv6_chk_addr (err 0)
<4>[ 268.130000] ip6_tunnel: Unknown symbol xfrm6_tunnel_deregister (err 0)
<4>[ 268.250000] mip6: Unknown symbol rawv6_mh_filter_unregister (err 0)
<4>[ 268.260000] mip6: Unknown symbol rawv6_mh_filter_register (err 0)
<4>[ 268.300000] ah6: Unknown symbol xfrm6_rcv (err 0)
<4>[ 268.310000] ah6: Unknown symbol ip6_update_pmtu (err 0)
<4>[ 268.310000] ah6: Unknown symbol xfrm6_find_1stfragopt (err 0)
<4>[ 268.320000] ah6: Unknown symbol xfrm_aalg_get_byname (err 0)
<4>[ 268.330000] ah6: Unknown symbol ip6_redirect (err 0)
<4>[ 268.380000] esp6: Unknown symbol xfrm6_rcv (err 0)
<4>[ 268.380000] esp6: Unknown symbol ip6_update_pmtu (err 0)
<4>[ 268.390000] esp6: Unknown symbol xfrm6_find_1stfragopt (err 0)
<4>[ 268.390000] esp6: Unknown symbol xfrm_aalg_get_byname (err 0)
<4>[ 268.400000] esp6: Unknown symbol ip6_redirect (err 0)
<4>[ 268.400000] esp6: Unknown symbol pskb_put (err 0)
<6>[ 268.620000] NET: Registered protocol family 10
<6>[ 268.630000] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
<6>[ 268.960000] device ath0.1 left promiscuous mode
<6>[ 268.960000] br0: port 3(ath0.1) entered disabled state
<6>[ 269.100000] ath0: deauthenticating from c4:6e:1f:2b:71:da by local choice (Reason: 3=DEAUTH_LEAVING)
<6>[ 269.620000] device br0 entered promiscuous mode
<6>[ 269.630000] eth0: link down
<6>[ 269.650000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
<6>[ 269.680000] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
<6>[ 269.690000] device eth0 entered promiscuous mode
<6>[ 269.700000] br0: port 1(eth0) entered forwarding state
<6>[ 269.700000] br0: port 1(eth0) entered forwarding state
<6>[ 269.730000] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
<6>[ 269.760000] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
<6>[ 269.770000] device eth1 entered promiscuous mode
<6>[ 269.770000] device br0 left promiscuous mode
<6>[ 269.780000] device br0 entered promiscuous mode
<6>[ 269.800000] device br0 left promiscuous mode
<7>[ 269.870000] ath: EEPROM regdomain: 0x822a
<7>[ 269.870000] ath: EEPROM indicates we should expect a country code
<7>[ 269.870000] ath: doing EEPROM country->regdmn map search
<7>[ 269.870000] ath: country maps to regdmn code: 0x22
<7>[ 269.870000] ath: Country alpha2 being used: NZ
<7>[ 269.870000] ath: Regpair used: 0x22
<7>[ 269.870000] ath: regdomain 0x822a dynamically updated by user
<6>[ 269.970000] br0: port 1(eth0) entered disabled state
<7>[ 270.570000] ar71xx: pll_reg 0xb8050014: 0x13000a44
<6>[ 270.570000] eth0: link up (100Mbps/Full duplex)
<6>[ 270.570000] br0: port 1(eth0) entered forwarding state
<6>[ 270.580000] br0: port 1(eth0) entered forwarding state
<6>[ 270.580000] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
<6>[ 272.580000] br0: port 1(eth0) entered forwarding state
<6>[ 274.470000] IPv6: ADDRCONF(NETDEV_UP): ath0.1: link is not ready
<6>[ 274.480000] device ath0.1 entered promiscuous mode
<6>[ 275.170000] br0: port 3(ath0.1) entered forwarding state
<6>[ 275.170000] br0: port 3(ath0.1) entered forwarding state
<6>[ 275.180000] IPv6: ADDRCONF(NETDEV_CHANGE): ath0.1: link becomes ready
<6>[ 275.860000] br0: port 3(ath0.1) entered disabled state
<6>[ 275.870000] IPv6: ADDRCONF(NETDEV_UP): ath0: link is not ready
<6>[ 277.740000] ath0: authenticate with c4:6e:1f:2b:71:da
<6>[ 277.770000] ath0: send auth to c4:6e:1f:2b:71:da (try 1/3)
<6>[ 277.790000] ath0: authenticated
<6>[ 277.820000] ath0: associate with c4:6e:1f:2b:71:da (try 1/3)
<6>[ 277.820000] ath0: RX AssocResp from c4:6e:1f:2b:71:da (capab=0x411 status=0 aid=3)
<6>[ 277.830000] ath0: associated
<6>[ 277.840000] IPv6: ADDRCONF(NETDEV_CHANGE): ath0: link becomes ready
<6>[ 279.580000] br0: port 3(ath0.1) entered forwarding state
<6>[ 279.580000] br0: port 3(ath0.1) entered forwarding state
<6>[ 281.580000] br0: port 3(ath0.1) entered forwarding state
It has a flash ID unlike any I have ever seen on a wrt160nl or e2100l.
You should link this post in the ticket you have open.... maybe BS can get you a fix.
Thanks -
how about BACKUP nvram and then try again and see if it makes a difference. If it does not show any improvements then just restore the backup.
I have sometimes seen that it made small difference with some things on broadcom. not sure about atheros though. _________________ For people who are new to the dd-wrt forums >> http://www.catb.org/~esr/faqs/smart-questions.html#rtfm
barryware wrote:
It takes a "community" to raise a router..
Internet Connection 1
Some Techicolor modem > Linksys WRT3200ACM
Internet connection 2
Ubiquiti Powerbeam Gen 2 > Netgear R9000
Official (but not really) dd-wrt General Discussion element/matrix chat
