Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Wed Jul 06, 2022 20:07 Post subject:
@zzantozz
Please clear your browser cache with CTRL+F5, for any undefined values and other UI inconsistencies. No caching is recommended atm browser side nor will it ever be recommend.
Joined: 08 May 2018 Posts: 14224 Location: Texas, USA
Posted: Wed Jul 06, 2022 20:51 Post subject:
zzantozz wrote:
- After updating, upstream bandwidth was abysmal. I think it's related to the Security > Firewall > Filter multicast checkbox, which was unchecked after update. (Firewall is off for client bridge mode.) "Filter multicast" has previously caused problems with WAN traffic. It also won't stay checked when I save, apply, or reboot, which makes me think the setting isn't correctly represented in the UI.
I can't enable multicast filtering. You dug into the annals of the archives of the forum, but failed to look into something more recent. It's a glitch in the webUI, check the nvram value to see if it is correct and your assumption is wrong, anyway. It's probably related to using bunk configuration for wifi (the stickies and wikis do not have optimal settings) -- screenshots, please.
zzantozz wrote:
- "Client" and "Client bridge" mode now seem to be named "Station" and "Station bridge", respectively, but it doesn't seem like any documentation has been updated.
Please clear your browser cache with CTRL+F5, for any undefined values and other UI inconsistencies. No caching is recommended atm browser side nor will it ever be recommend.
Makes sense. Sorry I didn't think about that.
the-joker wrote:
Client Bridge and Client Bridge Routed are now correctly named since they are provided by WDS only and are both fake bridges of sorts.
Fine with me. Just pointing out that future users are going to encounter out-of-date docs, which will cause extra forum posts.
kernel-panic69 wrote:
I can't enable multicast filtering. You dug into the annals of the archives of the forum, but failed to look into something more recent. It's a glitch in the webUI, check the nvram value to see if it is correct and your assumption is wrong, anyway. It's probably related to using bunk configuration for wifi (the stickies and wikis do not have optimal settings) -- screenshots, please.
Prologue: I know some networking, but I don't claim to be an expert. I'm pretty good with Linux systems, though, and I'm happy to dig in and provide config values.
First, there doesn't appear to be a "filter_multicast" setting here:
(192.168.1.8 is this device.) If there are specific UI screens you want, I can post those, too.
Also, the issue with slow upload is pretty sporadic. I haven't been able to nail down a specific scenario that causes it. In general, things are working fine.
kernel-panic69 wrote:
I haven't gotten a round tuit yet. Sorry I didn't write new wikis sooner
Ha, no worries. I'm a dev myself. It's just a reminder that docs ward off future user questions
Well, if clicking the save button after checking it and checking it again and again ad infinitum don't werk, then do:
Code:
nvram set block_multicast=1
nvram commit
reboot
Problem solved. _________________ "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
Joined: 18 Mar 2014 Posts: 12889 Location: Netherlands
Posted: Fri Jul 08, 2022 6:01 Post subject:
kernel-panic69 wrote:
zzantozz wrote:
- After updating, upstream bandwidth was abysmal. I think it's related to the Security > Firewall > Filter multicast checkbox, which was unchecked after update. (Firewall is off for client bridge mode.) "Filter multicast" has previously caused problems with WAN traffic. It also won't stay checked when I save, apply, or reboot, which makes me think the setting isn't correctly represented in the UI.
I can't enable multicast filtering. You dug into the annals of the archives of the forum, but failed to look into something more recent. It's a glitch in the webUI, check the nvram value to see if it is correct and your assumption is wrong, anyway. It's probably related to using bunk configuration for wifi (the stickies and wikis do not have optimal settings) -- screenshots, please.
zzantozz wrote:
- "Client" and "Client bridge" mode now seem to be named "Station" and "Station bridge", respectively, but it doesn't seem like any documentation has been updated.
I haven't gotten a round tuit yet. Sorry I didn't write new wikis sooner
For Wireless bridge modes, there is no reason to turn off the firewall (just as there is no reason to change Operating mode)
Yes the firewall is not necessary and yes there is no working firewall because there is no WAN!
Please show us the internals, the proof. These modes have no functional arp or multicast routing by design, no? _________________ "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
Please show us the internals, the proof. These modes have no functional arp or multicast routing by design, no?
If this is aimed at me, I'm not sure how to reply. I'm not sure the bandwidth issue is an ongoing problem. I've only seen it a couple of times and haven't been able to reliably reproduce it. It seems like the multicast thing might have been a red herring that I picked up from older wikis and forum posts.
However, if there's something specific you want to see, I'm happy to post it.
Router/Version: Linksys WRT1200AC (original, I think, no version listed)
File/Kernel: tried the 4 July 2022 factory-to-ddwrt build, but it failed, eventually found the 19 Jan 2018 factory-to-ddwrt, which did
Previous/Reset: stock firmware/yes
Mode/Status: can't get it running!
Issues/Errors: I had this old WRT1200AC with stock firmware, and it was hard to find a working image. I tried several, and this old one (r34578) is the only one that worked. I found it mentioned in an old forum thread. After doing the factory-ddwrt-image, I also couldn't find a working image to update to after a few tries, including this latest build, so I'm sitting at a build from Jan 2018 for now.
@IONK: A little birdie told me that the issue was already fixed, but I didn't see any actual commits for it or checked to see if new images were uploaded to the server.
