Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Fri Sep 09, 2022 11:11 Post subject:
@IONK
You have no need to double flash, factory to dd-wrt is enough on any build to get you that dd-wrt build on initial flash then followed by nvram erase && reboot and manual reconfiguration, the webflash is for upgrading from an older to newer build only.
As for identification of the board it likely meaningless you would need to check the source to confirm if the initialization is shared between different machines.
Now both my DIR-868L have 5GHz, but both of them show "880L" under model (expected: 868L), same issue as reported by dlinkrouter. nvram erase && reboot doesn't help. nvram set DD_BOARD=Dlink-DIR868L && nvram commit && reboot also doesn't help.
there can be just one answer. you messed up your factory nvram. the detection is done by the nvram settings _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
You have no need to double flash, factory to dd-wrt is enough on any build to get you that dd-wrt build on initial flash then followed by nvram erase && reboot and manual reconfiguration, the webflash is for upgrading from an older to newer build only.
there can be just one answer. you messed up your factory nvram. the detection is done by the nvram settings
Both of them are brand new units in sealed retail boxes with stock firmware. After unboxing and connecting to them, the first thing I did was to load factory-to-ddwrt.bin (09-03-2022-r50057), then dir868a-webflash.bin (09-03-2022-r50057), then I realized there's no 5GHz setting. So I loaded the very old version dir868-webflash.bin (01-20-2015-r25974) that recovered the 5GHz, but is there any chance that same old version broke the model number?
In case I have somehow messed up with the factory nvram, is there any impact on the functionality? Is there any way to recover?
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Fri Sep 09, 2022 12:58 Post subject:
You maybe right, re: flash size, I wasnt thinking about stock retarded flash limits.
To confirm board identification snafu you should dump the older build nvram to text file and look it up, same with regulatory domain information. then compare the nvrams from old/new version.
to dump to tetx file do do nvram show > /tmp/somebackup-name-date-build-version.txt
No idea why you would need to flash an ice age build to get 5GHz or Regulatory domains to show up, but this being Broadcom wouldn't surprise me if its buggy.
Also since you flashed an ice age build clear your browser cached with ctrl + f5 its known to cause issues with new builds. If you're using Chrome you may need to restart browser after cache clear.
To confirm board identification snafu you should dump the older build nvram to text file and look it up, same with regulatory domain information. then compare the nvrams from old/new version.
I tried doing a side-by-side comparison between the nvram of my home (working) 868a Repeater Bridge and new (wrong model) 868a Gateway, but there are so many differences and I quickly gave up. But I can confirm all variables with "board" are the same except for dd-board: 868 vs 880. I can PM the files if any developer needs (sorry can't attach here, too much sensitive info)
I'd be interested in the differences of cfe.bin and nvram dumps on all devices. That may give further information required to delineate any detection issues as well as the 5GHz issue.
Output of cat /proc/mtd will show you which bits to dump... _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
this case may not be the same as the issue reported in the wiki, because the issue mentioned in the wiki is about network does not show up but 5GHz settings are still available in the control panel page.
dale_gribble39 wrote:
I'd be interested in the differences of cfe.bin and nvram dumps on all devices. That may give further information required to delineate any detection issues as well as the 5GHz issue.
Output of cat /proc/mtd will show you which bits to dump...
Thanks for the inputs. Because I'm a layman, I'll appreciate the step-by-step instructions with specific commands to execute (together with the rationales if possible), so as to avoid giving unrelated/useless info that wastes my time but doesn't help solving the issue and may potentially confuse everyone. (e.g. should I restore to stock then flash ddwrt again? which version of ddwrt to flash? should I do the factory reset / nvram erase && reboot after certain step? should I take screenshot of some pages after each step? etc.) _________________ ▫ RSS feed for DD-WRT releases (2024): https://rsseverything.com/feed/7d36ab68-7733-46c3-bd8a-9c54c5cef08c.xml
▫ easyddup - A simple upgrade/downgrade utilityby yoyoma2--- as featured in 📌 Reference Links, stickies retired back to forum (Moderator's Pick 🌟)
If it helps, I just received a version A DIR-868L too a couple of days ago. After loading factory-to-ddwrt.bin (09-03-2022-r50057) then dir868a-webflash.bin (09-03-2022-r50057), I too encountered that there was no 5GHz, and the router model came up as Dlink-DIR880L. I did not downgrade the firmware to the old version so the model number issue would not be related to the downgrade.
Following this thread to see if this gets resolved.
If it helps, I just received a version A DIR-868L too a couple of days ago. After loading factory-to-ddwrt.bin (09-03-2022-r50057) then dir868a-webflash.bin (09-03-2022-r50057), I too encountered that there was no 5GHz, and the router model came up as Dlink-DIR880L. I did not downgrade the firmware to the old version so the model number issue would not be related to the downgrade.
Following this thread to see if this gets resolved.
Yes, those commands make FA appear again.
For my router, at first FA setting was there, but after a few nvram reset then it disappeared, so I'm not sure if FA is supposed to be there or not. Here's a portion of log after the 2nd reboot.
Quote:
Jan 1 08:00:15 RB kern.info kernel: [ 3.877673] Scanning device for bad blocks
Jan 1 08:00:15 RB kern.warn kernel: [ 4.607229] Options: NO_SUBPAGE_WRITE,
Jan 1 08:00:15 RB kern.notice kernel: [ 4.610994] Creating 1 MTD partitions on "brcmnand":
Jan 1 08:00:15 RB kern.notice kernel: [ 4.615949] 0x000002000000-0x000008000000 : "ddwrt"
Jan 1 08:00:15 RB kern.info kernel: [ 4.630117] VFS: Mounted root (squashfs filesystem) readonly on device 31:4.
Jan 1 08:00:15 RB kern.info kernel: [ 4.637631] Freeing unused kernel memory: 340K
Jan 1 08:00:15 RB kern.info kernel: [ 8.076540] softdog: Software Watchdog Timer: 0.08 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=1)
Jan 1 08:00:15 RB kern.warn kernel: [ 10.368920] ctf_init:2843 06:21:06 Oct 26 2022 CTF version 1.0 loaded
Jan 1 08:00:15 RB kern.warn kernel: [ 10.503401] et_module_init: passivemode set to 0x0
Jan 1 08:00:15 RB kern.warn kernel: [ 10.508186] et_module_init: txworkq set to 0x0
Jan 1 08:00:15 RB kern.warn kernel: [ 10.512609] et_module_init: et_txq_thresh set to 0x400
Jan 1 08:00:15 RB kern.warn kernel: [ 10.517751] et_module_init: et_rxlazy_timeout set to 0x3e8
Jan 1 08:00:15 RB kern.warn kernel: [ 10.523220] et_module_init: et_rxlazy_framecnt set to 0x20
Jan 1 08:00:15 RB kern.warn kernel: [ 10.528681] et_module_init: et_rxlazy_dyn_thresh set to 0
Jan 1 08:00:15 RB kern.info kernel: [ 10.537584] robo attach
Jan 1 08:00:15 RB kern.info kernel: [ 10.540114] robo id 53011
Jan 1 08:00:15 RB kern.info kernel: [ 10.543316] attaching FA
Jan 1 08:00:15 RB kern.warn kernel: [ 10.546903] aux0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.164.18 (r692288)
Jan 1 08:00:15 RB kern.info kernel: [ 10.559762] robo attach
Jan 1 08:00:15 RB kern.info kernel: [ 10.559858] robo id 53011
Jan 1 08:00:15 RB kern.info kernel: [ 10.560431] attaching FA
Jan 1 08:00:15 RB kern.info kernel: [ 10.560436] FA Core Detected!
Jan 1 08:00:15 RB kern.info kernel: [ 10.560657] attach ctf for eth%d
Jan 1 08:00:15 RB kern.info kernel: [ 10.560663] _ctf_attach:attach eth%d
Jan 1 08:00:15 RB kern.info kernel: [ 10.560695] bind ctf to eth if
Jan 1 08:00:15 RB kern.warn kernel: [ 10.572759] eth0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 7.14.164.18 (r692288)
Jan 1 08:00:15 RB kern.info kernel: [ 10.629245] switch id 11
Jan 1 08:00:15 RB kern.info kernel: [ 10.631781] switch id32 53011
Jan 1 08:00:15 RB kern.info kernel: [ 10.634850] b5301x_common: found switch: BCM53011, rev 5
Jan 1 08:00:15 RB kern.info kernel: [ 10.940693] b53_robo_cpu_port_upd, pdesc[8].cpu=1
Jan 1 08:00:15 RB kern.info kernel: [ 10.945398] bcm_robo_config_vlan_fun vid=1, vlan->members=0x2f, vlan->untag=0xf
Jan 1 08:00:15 RB kern.info kernel: [ 10.952799] bcm_robo_config_vlan_fun ports=0 1 2 3 5t
Jan 1 08:00:15 RB kern.info kernel: [ 10.957959] bcm_robo_config_vlan_fun vid=2, vlan->members=0x30, vlan->untag=0x30
Jan 1 08:00:15 RB kern.info kernel: [ 10.965403] bcm_robo_config_vlan_fun ports=4 5
Jan 1 08:00:15 RB kern.warn kernel: [ 13.226156] wl: module license 'Proprietary' taints kernel.
Jan 1 08:00:15 RB kern.warn kernel: [ 13.231722] Disabling lock debugging due to kernel taint
Jan 1 08:00:15 RB kern.warn kernel: [ 13.281865] wl_module_init: passivemode set to 0x0
Jan 1 08:00:15 RB kern.warn kernel: [ 13.286681] wl_module_init: txworkq set to 0x0
Jan 1 08:00:15 RB kern.warn kernel: [ 13.291197] PCI: Enabling device 0001:01:00.0 (0140 -> 0142)
Jan 1 08:00:15 RB kern.info kernel: [ 13.535448] _ctf_attach:attach wl0
Jan 1 08:00:15 RB kern.warn kernel: [ 13.542540] eth1: Broadcom BCM4331 802.11 Wireless Controller 7.14.164.18 (r692288)
Jan 1 08:00:15 RB kern.info kernel: [ 13.603366] _ctf_attach:attach wl1
Jan 1 08:00:15 RB kern.warn kernel: [ 13.610481] eth2: Broadcom BCM4360 802.11 Wireless Controller 7.14.164.18 (r692288)
Jan 1 08:00:15 RB kern.warn kernel: [ 13.799234] aux0: mixed HW and IP checksum settings.
Jan 1 08:00:15 RB kern.warn kernel: [ 13.804297] eth0: mixed HW and IP checksum settings.
Jan 1 08:00:15 RB user.info : [resetbutton] : successfully started
Jan 1 08:00:15 RB kern.info kernel: [ 15.414818] b53_robo_cpu_port_upd, pdesc[8].cpu=1
Jan 1 08:00:15 RB kern.info kernel: [ 15.419590] bcm_robo_config_vlan_fun vid=1, vlan->members=0x3f, vlan->untag=0x1f
Jan 1 08:00:15 RB kern.info kernel: [ 15.427040] bcm_robo_config_vlan_fun ports=0 1 2 3 4 5t
Jan 1 08:00:15 RB user.info : [bridge] : bridge br0 successfully added
Jan 1 08:00:16 RB kern.info kernel: [ 16.029391] device br0 entered promiscuous mode
Jan 1 08:00:16 RB daemon.info mstpd[706]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 10
Jan 1 08:00:16 RB daemon.info mstpd[706]: error, CTL_set_cist_bridge_config: Couldn't find bridge with index 10
Jan 1 08:00:16 RB user.info : [bridge] : interface vlan1 successfully added to bridge br0
Jan 1 08:00:16 RB kern.info kernel: [ 16.152980] device vlan1 entered promiscuous mode
Jan 1 08:00:16 RB kern.info kernel: [ 16.157972] device eth0 entered promiscuous mode
Jan 1 08:00:16 RB user.info : [bridge] : interface eth1 successfully deleted from bridge br0
Jan 1 08:00:21 RB user.info : [bridge] : interface wl1.1 successfully added to bridge br0
Jan 1 08:00:21 RB kern.info kernel: [ 21.991564] device wl1.1 entered promiscuous mode
Jan 1 08:00:22 RB user.info : [bridge] : interface eth2 successfully added to bridge br0
Jan 1 08:00:22 RB kern.info kernel: [ 22.280782] device eth2 entered promiscuous mode
Jan 1 08:00:22 RB kern.info kernel: [ 22.300294] device eth0 left promiscuous mode
Jan 1 08:00:22 RB user.info : [bridge] : interface vlan1 successfully added to bridge br0
Jan 1 08:00:22 RB kern.info kernel: [ 22.316224] device eth0 entered promiscuous mode
Jan 1 08:00:22 RB kern.info kernel: [ 22.334129] br0: port 3(eth2) entered forwarding state
Jan 1 08:00:22 RB kern.info kernel: [ 22.339560] br0: port 3(eth2) entered forwarding state
Jan 1 08:00:22 RB kern.info kernel: [ 22.344987] br0: port 2(wl1.1) entered forwarding state
Jan 1 08:00:22 RB kern.info kernel: [ 22.350312] br0: port 2(wl1.1) entered forwarding state
Jan 1 08:00:22 RB kern.info kernel: [ 22.355568] br0: port 1(vlan1) entered forwarding state
Jan 1 08:00:22 RB kern.info kernel: [ 22.360813] br0: port 1(vlan1) entered forwarding state
Jan 1 08:00:22 RB kern.info kernel: [ 22.366283] device br0 left promiscuous mode
Jan 1 08:00:22 RB kern.info kernel: [ 22.375352] device br0 entered promiscuous mode
Jan 1 08:00:22 RB kern.info kernel: [ 22.392728] device br0 left promiscuous mode
Jan 1 08:00:22 RB user.info : [gratarp] : successfully started
Jan 1 08:00:22 RB kern.notice kernel: klogd: exiting
Jan 1 08:00:22 RB user.info : [wland] : successfully started
Jan 1 08:00:22 RB user.info : [klogd] : kernel log daemon successfully stopped
Jan 1 08:00:22 RB syslog.info syslogd exiting
Jan 1 08:00:23 RB syslog.info syslogd started: BusyBox v1.35.0
Jan 1 08:00:23 RB user.info : [syslogd] : successfully started
Jan 1 08:00:23 RB user.info : [klogd] : successfully started
Jan 1 08:00:23 RB kern.notice kernel: klogd started: BusyBox v1.35.0 (2022-10-26 06:22:09 +07)
Jan 1 08:00:23 RB user.info : [cron] : successfully started
Jan 1 08:00:23 RB cron.info cron[1024]: (CRON) STARTUP (fork ok)
Jan 1 08:00:23 RB kern.info kernel: [ 23.191124] tun: Universal TUN/TAP device driver, 1.6
Jan 1 08:00:23 RB kern.info kernel: [ 23.196173] tun: (C) 1999-2004 Max Krasnyansky
Jan 1 08:00:23 RB user.info root: WireGuard number of non failed tunnels in fail set: 0
Jan 1 08:00:23 RB kern.info kernel: [ 23.869375] NET: Registered protocol family 10
Jan 1 08:00:24 RB kern.info kernel: [ 24.272767] wireguard: WireGuard 1.0.20211208 loaded. See www.wireguard.com for information.
Jan 1 08:00:24 RB kern.info kernel: [ 24.281234] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld . All Rights Reserved.
Jan 1 08:00:24 RB kern.info kernel: [ 24.290804] wireguard: packed headroom 128, message minimum length 32
Jan 1 08:00:24 RB user.info root: Enable WireGuard interface oet1 on port 51822
Jan 1 08:00:24 RB kern.info kernel: [ 24.659406] device oet1 entered promiscuous mode
Jan 1 08:00:24 RB user.info root: WireGuard 10.8.0.1/24 added to oet1
Jan 1 08:00:25 RB user.info root: WireGuard acquiring /tmp/oet.lock for 1104
Jan 1 08:00:25 RB user.info root: WireGuard /tmp/oet.lock acquired for 1104
Jan 1 08:00:25 RB user.info root: WireGuard Inbound Firewall deactivated on oet1
Jan 1 08:00:25 RB daemon.info httpd[1071]: [httpd] : httpd server started at port 80
Jan 1 08:00:25 RB user.info : [httpd] : successfully started
Jan 1 08:00:25 RB user.info : [ctf] : fast path forwarding successfully started
Jan 1 08:00:26 RB kern.info kernel: [ 26.081702] ip6_tables: (C) 2000-2006 Netfilter Core Team
Jan 1 08:00:26 RB user.info : [ctf] : fast path forwarding successfully started
Jan 1 08:00:26 RB user.info : [process_monitor] : successfully started
Jan 1 08:00:29 RB kern.notice kernel: [ 29.210561] random: nonblocking pool is initialized
Jan 1 08:00:29 RB user.info : [dropbear] : successfully started
Jan 1 08:00:29 RB authpriv.info dropbear[1287]: Running in background
Jan 1 08:00:29 RB kern.info kernel: [ 29.364740] br0: port 2(wl1.1) entered disabled state
Jan 1 08:00:31 RB daemon.err ntpclient[1275]: Failed resolving address to hostname 2.pool.ntp.org: Try again
Jan 1 08:00:31 RB daemon.err ntpclient[1275]: Failed resolving server 2.pool.ntp.org: Network is down
Jan 1 08:00:31 RB daemon.notice ntpclient[1275]: Network up, resolved address to hostname 212.18.3.19
Jan 1 08:00:31 RB daemon.debug ntpclient[1275]: Connecting to 212.18.3.19 [212.18.3.19] ...
Jan 1 08:00:32 RB kern.info kernel: [ 32.229084] br0: port 2(wl1.1) entered forwarding state
Jan 1 08:00:32 RB kern.info kernel: [ 32.234370] br0: port 2(wl1.1) entered forwarding state
Jan 1 08:00:32 RB user.info : [bridge] : interface wl1.1 successfully added to bridge br0
Jan 1 08:00:33 RB user.info : [nas] : wait for network init
Jan 1 08:00:34 RB daemon.debug ntpclient[1275]: Timed out waiting for 212.18.3.19 [212.18.3.19].
Jan 1 08:00:34 RB daemon.debug ntpclient[1275]: Connecting to 88.99.174.22 [88.99.174.22] ...
Jan 1 08:00:37 RB kern.info kernel: [ 37.353832] br0: port 3(eth2) entered forwarding state
Jan 1 08:00:37 RB kern.info kernel: [ 37.359000] br0: port 1(vlan1) entered forwarding state
I've recently bought another brand-new Dlink DIR-868L RevA1.
Original firmware version on the device is 1.00SH.
After loading r51040 factory-to-ddwrt.bin, device info shows DIR880L, no 5GHz.
After nvram erase && reboot and loading r51040 dir868a-webflash.bin, device still shows DIR880L, no 5GHz.
(No 5GHz means both wl0 and wl1 under wireless settings show 2.4GHz)
Subsequent nvram erase && reboot doesn't fix the issue.
Following the previously mentioned workaround, 5GHz is back but device still shows DIR880L.
Obviously in this case I didn't do any funny thing to mess up with NVRAM.
Brand new user of dd-wrt, got dir-868l 2nd hand for a steal, flashed factory-to-ddwrt.bin and then dir868a-webflash.bin from 12th of January. Got the same problem - no 5Ghz band. Router came with original 1.07 firmware and is A1 revision. Too many people getting the same problem for this to be a coincidence or all of us doing something wrong.
Would read up if I can get this resolved with the suggestions from here ..