Posted: Sun Oct 06, 2019 1:25 Post subject: WNDR4500v2
Router/Version: WNDR4500v2
File: DD-WRT v3.0-r41218 giga (10/01/19)
Kernel: Linux 3.10.108-d8 #34 Tue Oct 1 11:35:18 +04 2019 mips
Mode: AP/Switch/DHCP Forwarder
Status: Working no reset
Uptime: 17:48
Previous: 41212
Temps: WL0 43.7 °C / WL1 43.5 °C
Flashing from 41212 to 41218 did not brick the router this time around. Only thing I did different was reboot the router prior to flashing to watch the boot process through console output and watch the subsequent boot after the upgrade was initiated.
Router/Version: RT-AC87U A1
File: asus_rt-ac87u-firmware.trx
Firmware: DD-WRT v3.0-r41218 std (10/01/19)
Kernel: Linux 4.4.194 #19 SMP Tue Oct 1 07:41:40 +04 2019 armv7l
Mode/Status: Gateway/AP/OK
Reset: No
Setup Using: 2.4 GHz, 2.4 GHz guest (VAP), 5.0 GHz, IPv4, DNSMasq, Port Forwarding, USB, NAS, NTP TimeSync, and Wake-on-WAN(internet)
Issues/Errors: Yes, but connections state no Internet Connection yet they do connect after a few moments longer. Everything is working...
Can you share your config please dude as i have the same router but wifi isn't working. Do you use ipv6 or anything else?
Router/Version: Asus RT-AC87U
File: DD-WRT v3.0-r41218 std (10/01/19)
Kernel: Linux 4.4.194 #19 SMP Tue Oct 1 07:41:40 +04 2019 armv7l
Mode: Gateway (PPOE/DHCPv6/QOS/Access Restrictions/Port Forwarding/JFS/USB/Entware)
Status: WiFi Broken
Wifi hasn't worked for me since DD-WRT v3.0-r40890 std (09/03/19), both 2.4 and 5Ghz allow devices to connect but they all state "Connected, No Internet", have tried both a flash with and without reset, makes no difference
Syslog is attached, the dnsmasq-dhcp[1549] entries are relating to the wifi devices trying to connect
After having a bit of time to do some fault finding i've discovered QoS is broken, fq codel causes the wifi issue, changing to cake or pie breaks the router, both wifi and ethernet were unable to connect so had to manually set ip to get back in and change back to fq codel before disabling QoS completely.
Joined: 09 Nov 2014 Posts: 314 Location: Bakersfield, CA
Posted: Wed Oct 09, 2019 11:00 Post subject: Re: E3000?
fatalhalt wrote:
Do the newest firmwares flash onto E3000 without bricking it? Can someone confirm?
I just updated both of my E3000 client bridge routers and they're up and working, so I guess so? _________________ Deployed Routers:
Netgear R7800 - 1x build 46979
- Gateway (USB /w Entware, CAKE QoS)
Netgear R7000 - 3x build 46979
Posted: Thu Oct 10, 2019 0:32 Post subject: Re: WNDR4500v2
Veritech wrote:
Router/Version: WNDR4500v2
File: DD-WRT v3.0-r41218 giga (10/01/19)
Kernel: Linux 3.10.108-d8 #34 Tue Oct 1 11:35:18 +04 2019 mips
Mode: AP/Switch/DHCP Forwarder
Status: Working no reset
Uptime: 17:48
Previous: 41212
Temps: WL0 43.7 °C / WL1 43.5 °C
Flashing from 41212 to 41218 did not brick the router this time around. Only thing I did different was reboot the router prior to flashing to watch the boot process through console output and watch the subsequent boot after the upgrade was initiated.
.:EDIT:.
I decided to flash this router without rebooting prior to. I flashed 41218 over top 41218. This bricked the router. I have attached serial console output.
Posted: Mon Oct 21, 2019 15:57 Post subject: issue with this release
the speed checker is not working properly
or at least for me
when use the internet speed checker feature from the router page
i get reading between ( 27-50 mb/s )
if i browse to fast dot com or used the speedtest website
Joined: 08 May 2018 Posts: 14242 Location: Texas, USA
Posted: Mon Oct 21, 2019 17:11 Post subject: Re: issue with this release
khanjar wrote:
the speed checker is not working properly
or at least for me
when use the internet speed checker feature from the router page
i get reading between ( 27-50 mb/s )
if i browse to fast dot com or used the speedtest website
i get correct reading (250mb/s)
Re-read the first post in the thread. You have not stated anything about what device this pertains to or your configs, or anything of value other than the speedchecker feature of your particular device's build is not reporting correct information.