Joined: 18 Mar 2014 Posts: 12917 Location: Netherlands
Posted: Mon Mar 13, 2023 16:39 Post subject:
Router Model: Linksys EA8500
Firmware Version: DD-WRT v3.0-r52004M Community Build by EGC (03/13/23)
Upgraded from: DD-WRT v3.0-r51728M Community Build by EGC (02/15/23)
Reset: No not this time
Status: Up and running for 8 hours, basic setup as Gateway, static leases, 2.4 GHz and 5 GHz switched off, OpenVPN server working, WireGuard Server working (multiple clients e.g. phone, laptop and site-to-site connection with remote location), NAS and Samba working, Avahi and Avahi-utils working.
IPv6 working.
Upgraded from: DD-WRT v3.0-r51741 std (02/18/23) (had been up for nearly 4 weeks)
Reset: No, not this time
Status: Up and running for 8 hours, basic setup as Gateway, static leases, port forwarding DDNS, WOL, 2,4GHz, VAP for IoT, 5Ghz, (Vanilla Firmware, Disabled Airtime), DDNS (Inadyn) to freedns.afraid.org.
On demand governor with minimum 800 MHz.
IPv6 working with PD /56.
Errors: The 5 GHz channel selection is action up. After upgrade it had reverted to auto (I had 80 MHz, 100 UU) the channel was OK and was working, in the end I had to choose 112 LL.
Log was clean and performance was good.
The problem with the channels occurs after each reboot, for example with 149.
I use on the test router 116+UU with the channel the problem does not occur, however, after a restart the TX power is much lower.
I was briefly in the attic and had no more wireless reception (which surprised me a bit).
Back downstairs I then looked and in a few meters distance to the router I had on the smartphone no full signal ...
Then I clicked in the WLAN tab on "apply" and the transmission power was again normal / better.
Is the case after each reboot
In addition, the maximum transmit power is no longer displayed correctly in webIF (since some builds)
Router/Version: Netgear XR500
Update method: WebUpgrade
File/Kernel: dd-wrt-webupgrade.bin / Linux 4.9.337 #1644 SMP Mon Mar 13 06:16:55 +07 2023 armv7l
Previous/Reset: r51935 / no
Mode/Status: Gateway / Up and running for 3:54 hours
Issues/Errors: Nothing significant
________________________________________________________________________________________________
Router/Version: TP-Link TL-WR841ND v11
Update method: WebUpgrade
File/Kernel: tl-wr841nd-webflash.bin / Linux 3.18.140-d6 #166433 Mon Mar 13 09:16:54 +06 2023 mips
Previous/Reset: r51937 / no
Mode/Status: AP wired and wireless / Up and running for 3:01 hours
Issues/Errors: Nothing significant
The fact is that the router connected to the Internet (to the Internet provider). And it reports an error, the orange WAN indicator flashes (the icon in the form of a planet). Internet is working, I just think it's a glitch
Thank you BS and gurus! _________________ Atheros
Netgear XR500 Nighthawk - DD-WRT 54545
Tp-Link TL-WDR4900 v1.3 - DD-WRT 53133
TP-Link WR1043ND v4 - DD-WRT 51838
TP-Link WR1043ND v2 - Gargoyle OS 1.13.0
TP-Link WR841ND v11 - DD-WRT 55819
Broadcom
Asus RT-AC87U R - DD-WRT 55819
Asus RT-N66U - DD-WRT 55819
Linksys WRT54GL v1.1 - DD-WRT 54517M
Linksys WRT54GL v1.1 - FreshTomato 2023.4_MIPS_K26
Linksys WRT54GL v1.1 - Gargoyle OS 1.6.2
EA8500 5GHz went to auto ch after upgrade also.
It was set to 161 LL but now status shows 149 UU so it's all 'bout same nevermind anyways so I leave it like it is
Upgraded from: DD-WRT v3.0-r51741 std (02/18/23) (had been up for nearly 4 weeks)
Reset: No, not this time
Status: Up and running for 8 hours, basic setup as Gateway, static leases, port forwarding DDNS, WOL, 2,4GHz, VAP for IoT, 5Ghz, (Vanilla Firmware, Disabled Airtime), DDNS (Inadyn) to freedns.afraid.org.
On demand governor with minimum 800 MHz.
IPv6 working with PD /56.
Errors: The 5 GHz channel selection is action up. After upgrade it had reverted to auto (I had 80 MHz, 100 UU) the channel was OK and was working, in the end I had to choose 112 LL.
Log was clean and performance was good.
Thanks BS!
I reverted to 51741.
5 GHz is acting up the signal seems weaker but the main problem started after I Enabled VLAN on the switch config tab (a new setting), I lost WAN access
It turned out my CPU ports became tagged which stops WAN access, I could untagged them which restored WAN access but this is just BAD!
After downgrading it was completely borked and I had to reset to defaults luckily I had a backup.
I very much appreciate recent fixes to Switch Config tab, classically known as VLANs, but still must agree with egc.
EA8500 r51976 crashing (without recovery) is fixed with r52004, but remains single a crash per radio since r50963.
I am still willing to step through test builds, or bisect r50932 through r50962 to help locate where the crash begins.
BTW not only at boot firmware switch to Vanilla it can also easily be triggered with apply button in wireless settings.
Upgraded from: DD-WRT v3.0-r51741 std (02/18/23) (had been up for nearly 4 weeks)
Reset: No, not this time
Status: Up and running for 8 hours, basic setup as Gateway, static leases, port forwarding DDNS, WOL, 2,4GHz, VAP for IoT, 5Ghz, (Vanilla Firmware, Disabled Airtime), DDNS (Inadyn) to freedns.afraid.org.
On demand governor with minimum 800 MHz.
IPv6 working with PD /56.
Errors: The 5 GHz channel selection is action up. After upgrade it had reverted to auto (I had 80 MHz, 100 UU) the channel was OK and was working, in the end I had to choose 112 LL.
Log was clean and performance was good.
Thanks BS!
I reverted to 51741.
5 GHz is acting up the signal seems weaker but the main problem started after I Enabled VLAN on the switch config tab (a new setting), I lost WAN access
It turned out my CPU ports became tagged which stops WAN access, I could untagged them which restored WAN access but this is just BAD!
After downgrading it was completely borked and I had to reset to defaults luckily I had a backup.
Not good this build
this is caused by a bugfix. the switch config tab was inoperational the last builds. now its working again. so you stumbled about a working feature and you reverted because the non working page made less troubles?
and of course you can tag ports per vlan. (or not). just do it. its just a checkbox
what you miss is that its not possible that a port is member of multiple vlans. your screenshot of openwrt shows nothing else. so its enough to set the tag property by port which becomes than a property of the vlan membership then. so the vlan assigned to the port is then tagged (or untagged). thats all.
about the so called "weaker" signal. there was also a fix for the power setting which may have not worked for some builds. so the so called weaker signal might be just caused by your now working output power setting. (which you can increase of course) _________________ "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
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Tue Mar 14, 2023 6:33 Post subject:
blkt wrote:
I very much appreciate recent fixes to Switch Config tab, classically known as VLANs, but still must agree with egc.
EA8500 r51976 crashing (without recovery) is fixed with r52004, but remains single a crash per radio since r50963.
I am still willing to step through test builds, or bisect r50932 through r50962 to help locate where the crash begins.
BTW not only at boot firmware switch to Vanilla it can also easily be triggered with apply button in wireless settings.
again the single crash is intentional. to reload the firmware vom dd-wrt to vanilla it have todo a very dirty trick which may crash the wifi card. (depends on the chipset) but it reloads the vanilla firmware then and reinitializes. _________________ "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
