Joined: 18 Mar 2014 Posts: 12875 Location: Netherlands
Posted: Sun Jul 17, 2022 7:04 Post subject:
The problem is that this router is two-armed e.g. it has two CPU ports which is uncommon and the code logic/nvram parameters can not deal with that at the moment.
Just as it can not deal with tagging per port.
I have looked into a total rewrite which is necessary if we want to get this working the right way and be able to maintain it but that is an herculean task
The problem is that this router is two-armed e.g. it has two CPU ports which is uncommon and the code logic/nvram parameters can not deal with that at the moment.
Just as it can not deal with tagging per port.
I have looked into a total rewrite which is necessary if we want to get this working the right way and be able to maintain it but that is an herculean task
The current nvram parameter layout is just not sufficient
I understand this very well. In my opinion, in these cases, until it is possible to make these corrections, the only thing is to delete the Config Switch tab or, when it is opened, to open a pop-up that warns that these configurations must be made via the command. If I think less misunderstandings would arise.
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Mon Jul 18, 2022 11:59 Post subject:
egc wrote:
Just leave the switch page alone it is not working on the R7800.
Use swconfig to configure VLANs
ho1Aetoo wrote:
maybe better understandable?
Sure, seems however that there is something missing, the UI should suffice under normal circumstances, if it doesn't then there is a problem and that should be solved.
I dont understand the limitation anyway between the UI and that for some things you need to CLI, but CLI is not something we can ask from all users to understand, especially novice users, sure they could by reading the documentation, if that is at all up to snuff for all machines concerned.
Sadly BS is way to busy these days to pester him about it, last time I mentioned the subject he said the switch config pages should work, clearly there is some misunderstanding here.
Yes that would be a good idea but not something we can do per router (well we can but that would again add to the maintenance nightmare we already have )
Joined: 08 May 2018 Posts: 14207 Location: Texas, USA
Posted: Mon Jul 18, 2022 12:26 Post subject:
There was progress made during implementing swconfig to Broadcom, but for certain devices in particular, the dual ports on the CPU (or multiple switches as is the case on the R9000), there is more work required to make it functional across the board. The overall webUI issue has been true since support was added for these devices, because it's always worked for Broadcom since DD-WRT initially only supported Broadcom devices and not all devices are Broadcom. It will eventually get fixed, but the patience factor in the community at large is widely lacking and we don't have near the base of the right people to collaborate and make the heavy work light. Then again, some folks are not too keen on collaborating with other people in a group scenario, no matter what they try to imply to others. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
There was progress made during implementing swconfig to Broadcom, but for certain devices in particular, the dual ports on the CPU (or multiple switches as is the case on the R9000), there is more work required to make it functional across the board. The overall webUI issue has been true since support was added for these devices, because it's always worked for Broadcom since DD-WRT initially only supported Broadcom devices and not all devices are Broadcom. It will eventually get fixed, but the patience factor in the community at large is widely lacking and we don't have near the base of the right people to collaborate and make the heavy work light. Then again, some folks are not too keen on collaborating with other people in a group scenario, no matter what they try to imply to others.
This complicated situation is widely understood, I believe by the whole community. I don't think there is a lack of patience, we all have to thank those who actively participate in the project, but only the desire to have dd-wrt better and better.
There was progress made during implementing swconfig to Broadcom, but for certain devices in particular, the dual ports on the CPU (or multiple switches as is the case on the R9000), there is more work required to make it functional across the board. The overall webUI issue has been true since support was added for these devices, because it's always worked for Broadcom since DD-WRT initially only supported Broadcom devices and not all devices are Broadcom. It will eventually get fixed, but the patience factor in the community at large is widely lacking and we don't have near the base of the right people to collaborate and make the heavy work light. Then again, some folks are not too keen on collaborating with other people in a group scenario, no matter what they try to imply to others.
Currently the R7800 and R9000 do not use all its computing power?
