Posted: Sun Mar 26, 2023 14:46 Post subject: New Build - 03/26/2023 - r52148
Welcome to Atheros r52148 beta release thread for reporting, feedback to developers and community benefit.
Please do not flash builds until installation is understood, risks involved and device specificrecovery methods.
Avoid discussions, create threads for questions, general problems or use search; this thread is not for support.
List router model & version or revision, operating & wireless modes & exact filename/firmware image flashed.
CLI Flash: 'cd /tmp' then 'wget {file URL}' (httponly) or 'curl -O {file URL}' (http, https, ftp). 'write {file} linux' then 'reboot'.
Issues, observations, and/or workarounds reported:
• WebUI: Clear history or use a portable. Temporary cache bypass: Ctrl+F5, Cmd+Shift+R or new private window/incognito.
• Please report findings with steps needed to reproduce, configuration, clients, output, logs and important information below!
Important:
• Detail issues & relevant configs, logs: syslog klog 'dmesg' 'cat /tmp/var/log/messages' nvram set console_debug=1, serial.
• Firewall NAT: 'iptables -vnL' 'iptables -t nat -vnL' 'iptables -t mangle -vnL' & 'cat /tmp/.ipt'. Misc: stracetcpdumpwireshark.
• Gremlins: reboot. cold boot. Reset & reconfigure not restore backup. Search Trac & discuss in forum before opening tickets.
• Include operating & wireless modes (e.g. Gateway, Router, AP, SB, WDS, Mesh) and applicable configurations to reproduce.
Router/Version: R7800
File/Kernel: Linux 4.9.337 #1735 SMP Sun Mar 26 03:21:55 +07 2023 armv7l
Previous/Reset: r52142 / no
Mode/Status: Gateway / working up since 14h
Services Used: PPPoE,DHCP,DHCP-Reservation,Dnsmasq + PiHole,DDNS,SSH ed25519,WiFi 2,4Ghz + 5Ghz AP's + VAP's Vanilla,USB,Port forwarding,QoS
Issues/Errors: VHT160 still a bit broken
Nice little "switch config update
Most configurations are now possible via GUI
We have tested it in the last day, works very well
Router/Version: R7800
Nice little "switch config update
Most configurations are now possible via GUI
We have tested it in the last day, works very well
Is it safe to assume that WAN CPUPORT should only be used with a WAN connection and the LAN CPUPORT should only be used on the LAN side? (i.e. you shouldn't reconfigure these to be used vice-versa?)
I currently use swconfig to assign the WAN port to the LAN (on both my dd-wrt routers) and leave the WAN CPUPORT on its own on VLAN2 on my Linksys EA8500 (port 0) and unassigned on my DLink DIR-862L (port 6 on it).
I don't know if I understood you correctly.
But you can of course assign all EXTERNAL ports to the LAN.
But then it would certainly make sense to deactivate WAN in the Setup tab.
Thanks - yes, WAN Connection type is set to "Disabled" on the "Basic Setup" page.
What I'm trying to clarify is that the CPUPORTS should never be reversed - eg. WAN CPUPORT should never be assigned to VLAN 1 and the LAN CPUPORT never assigned to VLAN 2 (for the first picture you posted).
In my situation (where WAN isn't used) that means the WAN CPUPORT is best left unassigned/unused.
and you don't want to have 2 CPU ports on the LAN, only one port is used anyway, otherwise the ports would have to be bonded somehow.
That's what I was looking for. Thanks. Was editing your picture above to show you what I was referring to.
The second configuration would require extensive configuration which isn't worth the effort.
Again, in my case, the EA8500 has the LAN CPUPORT identified as Port 6 in swconfig where as the DIR-862L the LAN CPUPORT is port 0. The WAN CPUPORT is port 0 in swconfig on the EA8500 and port 6 on the DIR-862L - is this an issue on the switch config page?
This is possible but still nonsense.
Only one port is used, data traffic always runs over one network connection and not over several at the same time.
Ever heard of port bonding?
So that several network interfaces can be used at the same time, the ports would have to be bonded, which is not the case.
Joined: 21 Aug 2019 Posts: 120 Location: Here, There And Everywhere
Posted: Mon Mar 27, 2023 10:26 Post subject:
@ho1Aetoo
I know that the switch config tab is not working for R9000, and I did not attempt to do anything. Simply clicking on the tab caused httpd to crash - before anything is shown in the browser (I tried both Firefox and Pale Moon, although this probably has nothing to do with the crash).