Thank you too, msoengineer. It's good to have knowledgeable people such as yourself working on this with us on bleeding edge device support. Very much appreciated and nice to have somebody else who has this router and knows how to use TTL2USB and tftp without fault.
Hopefully we can turn this around sooner rather than later so I can replace my main gateway EA8500 with this. I am assuming and very hopeful with 4 CPU cores running at 1.8ghz, we will no longer need SFE and NSS for 1Gb throughput speeds. This was really my main reason for purchasing this router. Once we get there, my Gateway EA8500 will become a WAP/VAP if this works well enough. Right now I do not plan on using the radios on this device, but I will certainly test them out. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
Joined: 06 Jun 2006 Posts: 7604 Location: Dresden, Germany
Posted: Fri Jul 12, 2024 3:38 Post subject:
own3mall wrote:
lexridge wrote:
own3mall wrote:
Did anyone get the "Switch Config" tab to show up / be usable yet? I also have customizations here where one of the ports is on another Vlan.
It's still borked, even on today's release.
Any word on if this is going to be fixed? Do any of the newly supported routers have Switch Config working / low number of bugs / mostly everything working as expected? Stability is the most important feature for me.
there will never be a switch tab for any of these devices. why? each ethernet port on has a own eth interface on system. so there is no need to such a tab since each port is available indivudually anyway.
so configure your vlans on eth0 - eth4 using the network tab _________________ "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
there will never be a switch tab for any of these devices. why? each ethernet port on has a own eth interface on system. so there is no need to such a tab since each port is available indivudually anyway.
so configure your vlans on eth0 - eth4 using the network tab
Interesting. This is important information for sure! I will look at this much closer.
EDIT: So we will need to use the tagging section at the top of the Networking tab to tag vlans? This actually may be a good thing in the end.
What about the non-booting issue with 57200+ builds? _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
Joined: 06 Jun 2006 Posts: 7604 Location: Dresden, Germany
Posted: Fri Jul 12, 2024 6:58 Post subject:
lexridge wrote:
BrainSlayer wrote:
there will never be a switch tab for any of these devices. why? each ethernet port on has a own eth interface on system. so there is no need to such a tab since each port is available indivudually anyway.
so configure your vlans on eth0 - eth4 using the network tab
Interesting. This is important information for sure! I will look at this much closer.
EDIT: So we will need to use the tagging section at the top of the Networking tab to tag vlans? This actually may be a good thing in the end.
What about the non-booting issue with 57200+ builds?
they are booting. i mentioned earlier to the moderators before release that the 7350 might have a problem since this was the only device i wasnt able to test using the nss integration. i tested MR5500, MX5500, Dynalink successfully. and on my table the asus AX89X is now working too. for the MR7350 i will take care next days or today. my test device is currently used as internet router in my home, so i wasnt able to play with it without harming myself.
hardest work the last time was getting the ipq5018 to work since there was no working support in kernel and whats available was broken into pieces and had along of wrong code. the 7350 will be easy to resolv for me since i had this already working. just nss has never been tested on the 6018 variant. to be honest. i expected it. but i will take care of it _________________ "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
Understood. Thank you sir @brianslayer for the feedback and looking forward to future releases. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
I've been messing around with setting up vlans inside the Networking tab. This is much more like setting up a PC with four independent Ethernet interfaces (not counting eth4/WAN), which is not a bad thing. We will eventually need a write up on how to do this most likely since it will differ greatly from the guides we presently have.
I have set up 3 Vlans over trunk port 4 which are working and even survive a reboot. This was tested by assigning the 5ghz radio to each vlan, one at a time, then used my Pixel phone to connect and verify it was getting the correct subnet IP addresses.
One thing I have no idea about at this point is how to tag the CPU ports, or if that is even needed with this newer hardware?
This is a pretty simple configuration and nothing is isolated here as it's just to test and get a feel for how this works now without a Switch Config tab.
Everything is labelled to make it a bit easier to understand.
EDIT: Please note that the bridge IP addresses would normally not be required if this was just going to be a AP, but as I plan to replace my EA8500 with this eventually, I set it up this way because in the end it will have a dhcp server assigned for each br1 through br3. I cannot do that until the EA8500 stops serving IPs for these vlans. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
Something I just noticed earlier this evening, this router runs very hot even at 0% CPU usage. I may poke around with some voltages and see if I can maybe add an internal RPi fan to both heat sinks. Hopefully something small enough that the top will still fit.
Re: my previous vlan post. I added this to my Startup script in an attempt to tag the CPU port. No idea if this even works since swconfig is fscked, and apparently not even needed for this router. Oh the mysteries!:
Code:
swconfig dev switch0 vlan 10 set ports "4t 6t"
swconfig dev switch0 vlan 11 set ports "4t 6t"
swconfig dev switch0 vlan 12 set ports "4t 6t"
swconfig dev switch0 set apply
I would guess I could remove the 4t since it's already configured in Networking tab, while leaving the 6t, but it's merely a guess and I have no idea if it actually works and does anything. I have searched the internet looking for more info on this and coming up completely empty handed. Probably since it's not yet supported by OpenWRT, there is not much info available.
I would guess this is probably unneeded and unnecessary, but I have time to experiment so why not?
FYI, swconfig does not show any vlans when configured only in the Networking tab. Only after I added the startup commands does this show up.
EDIT: Adding the above commands totally kills the vlans ability to assign a dhcp address. Conclusion: swconfig is not going to work with this router in its present state, and may not even be applicable for that matter. Which begs the question...do we even need to assign a vlan tag to the CPU port at all? _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
Joined: 06 Jun 2006 Posts: 7604 Location: Dresden, Germany
Posted: Sat Jul 13, 2024 6:01 Post subject:
lexridge wrote:
Something I just noticed earlier this evening, this router runs very hot even at 0% CPU usage. I may poke around with some voltages and see if I can maybe add an internal RPi fan to both heat sinks. Hopefully something small enough that the top will still fit.
Re: my previous vlan post. I added this to my Startup script in an attempt to tag the CPU port. No idea if this even works since swconfig is fscked, and apparently not even needed for this router. Oh the mysteries!:
Code:
swconfig dev switch0 vlan 10 set ports "4t 6t"
swconfig dev switch0 vlan 11 set ports "4t 6t"
swconfig dev switch0 vlan 12 set ports "4t 6t"
swconfig dev switch0 set apply
I would guess I could remove the 4t since it's already configured in Networking tab, while leaving the 6t, but it's merely a guess and I have no idea if it actually works and does anything. I have searched the internet looking for more info on this and coming up completely empty handed. Probably since it's not yet supported by OpenWRT, there is not much info available.
I would guess this is probably unneeded and unnecessary, but I have time to experiment so why not?
FYI, swconfig does not show any vlans when configured only in the Networking tab. Only after I added the startup commands does this show up.
EDIT: Adding the above commands totally kills the vlans ability to assign a dhcp address. Conclusion: swconfig is not going to work with this router in its present state, and may not even be applicable for that matter. Which begs the question...do we even need to assign a vlan tag to the CPU port at all?
i dont know what you are trying todo. this will not work on mr7350 and its also bullshit since you have independend network interfaces for each port. just use these interfaces. tag them or not. your choice.
no swconfig required at all. all works straight based on these interfaces.
current internal builds for mr7350 will work again. i just fixed the issue yesterday _________________ "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
i dont know what you are trying todo. this will not work on mr7350 and its also bullshit since you have independend network interfaces for each port. just use these interfaces. tag them or not. your choice.
no swconfig required at all. all works straight based on these interfaces.
current internal builds for mr7350 will work again. i just fixed the issue yesterday
Again, all good information to know and to the point of this thread. So swconfig and CPU tagging are out-the-window guys! Sorry, old habits die hard.
The latest internal build flashes and boots fine (r57334). Thank you sir @brianslayer and thank you sir @kernel-panic69 for sharing this build with me to test. I plan to also flash back to stock soon so I can test the factory-to-dd-wrt file as well.
NSS is now included. Hopefully not going to need it with the CPU power this unit provides. I just got the (3) dhcp servers set up but presently disabled to not interfere with existing. I hope to put this thing online sometime this afternoon and see how it really performs in the real world on a 1Gb connection. I still need to set up Entware with mqtt as well for my HA plus a few other things. I have not even touched the USB yet so still lots to do. It will be nice to finally get the lid back on it.
Thanks @BS!
EDIT: One thing I just noticed: The CPU clock is now at 864mhz, not 1.8ghz. I will fiddle with this.
EDIT2: Adding the line in Startup for CPUFREQ in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor; do [ -f $CPUFREQ ] || continue; echo -n performance > $CPUFREQ; done brings it up to 1512mhz. Not 1800mhz. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
I did see one kernel panic on this build (r57334). It was when I was creating the last of 3 dhcp servers. When I clicked Apply it crashed and rebooted but dhcp server 3 was still there upon reboot. This was before I noticed the CPU freq was low.
EDIT: I scrolled back up in minicom and found the crash dump:
Update: Any changes made inside the Networking tab does indeed cause a kernel dump once Apply is clicked (Save will not cause this, only Apply). The changes made remain however and seem to work after the reboot.
Update2: After a factory reset, it fails to boot r57334 at all. I am back on r56941 until this gets straightened out. It appears to be something with the atheros wireless drivers and the reason it worked before the reset. I had the 2.4ghz radio disabled.
Any ideas how to assign LanPort3 to an untagged vlan12? I need to assign a PVID of 12 to it without tagging it.
EDIT: I figured it out. All I had to do was assign eth2-LanPort3 to the Media br3. Piece of cake. I was over thinking it. _________________ - Linksys EA8500: I-Gateway, WAP/VAP 5ghz only. Features: WDS-AP, VLANs, Samba, WG, Entware - r59429
- Linksys EA8500: 802.11s Secondary w/VLAN Trunk over 5ghz - r59171
- Linksys MX4300: 802.11s Primary w/VLAN Trunk over 5ghz. 2.4ghz WAP/VAP only - r59171
- Linksys MX4300 (WAP/VAP (7)) Multiple VLANs over single trunk port. Entware/Samba r59451
- Linksys MR7350: WDS Station for extended Ethernet r59451
- Linksys Velop WHW03v1 x2: OpenWRT w/GRETAP tunnel for VLANs on VAPs
- OSes: Fedora 40, 10 RPis (2,3,4,5), 23 ESP8266s: Straight from Amiga to Linux in '95, never having owned a Windows PC.
Joined: 21 Jan 2017 Posts: 1797 Location: Illinois Moderator
Posted: Sun Jul 14, 2024 4:42 Post subject:
57378 still not ready for testing- strange gui bug locks you out when switching between any tabs after initial log into the gui. Sent BS an email with the log. _________________ FORUM RULES
Joined: 21 Jan 2017 Posts: 1797 Location: Illinois Moderator
Posted: Sun Jul 14, 2024 16:11 Post subject:
57395 is still not ready either; strange bug on initial load and PW change gui screen- you can change the user name and password and hit apply, then it hangs. Re attempting 192.168.1.1 it will load the page again, but as soon as you try to change tabs or make any changes and hit apply you will get locked out of the gui. Having a telnet session active and trying to resart httpd won't work either.
I cleared the cache on the browser before making changes.
I'll keep my eye on the SVN... _________________ FORUM RULES
Probably related to the issue when the info page is enabled and when using Pale moon. In other words, incomplete merging of webUI fixes because stature over complete product was the goal. Of course, save until ready to implement configuration changes via reboot is always recommended rather than impatience. _________________ "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