New Build - 04/24/2021 - r46446

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.)
Author Message
kernel-panic69
DD-WRT Guru


Joined: 08 May 2018
Posts: 8968
Location: Texas, USA

PostPosted: Sat Apr 24, 2021 15:04    Post subject: New Build - 04/24/2021 - r46446 Reply with quote
[WARNING]: This thread is only for feedback on this beta release for developers and the community's benefit.
DO NOT flash this beta release unless you understand the risks involved and device specific recovery methods.
Avoid discussions! Create threads for questions, general problems or use search; this thread is not for support.
Please list router model & revision, operating & wireless mode(s) and exact filename/firmware image flashed.


Downloads: (DD-WRT website) HTTPS & FTP (try another if a link does not work)

CLI Flash: 'cd /tmp' then 'wget {file URL}' (or 'curl -k {file URL} -o {file}') with http (not https) or ftp. Then 'write {file} linux'.

Repository: Trac SVN changelog since last build r46442 (GitHub mirror)

Notes:
OpenVPN 2.5.2: Guides, Server, PBR, Reverse PBR, Client (see second post), Kill Switch, update tips, scripts and more.
WireGuard 1.0.20210219/Tools: Guides, Client, Server, Advanced, PBR, KS, update tips, scripts & more. Thanks BS & egc!
• CVE-2019-14899 VPN fix (applicability depends on VPN setup) and GUI toggle since r41813.
Select ath10k radios now feature on-the-fly firmware type switching between Customized DD-WRT and Vanilla QCA binaries!
SmartDNSMiniDLNA • Unbound 1.13.1 • CoovaChilli 1.6 • Tor 0.4.5.7 • OpenSSL 1.1.1k • Dnsmasq 2.85 Privoxy 3.0.32
In-kernel Samba (ksmbd 3.3.9+): default min/max versions changed. • WSD updateANTFS/NTFS3 kernel mode driver++.

Issues:
• Show us your findings with steps to reproduce, configuration, output, logs and important information below!

Important:
• For issues provide applicable info: 'dmesg', 'cat /tmp/var/log/messages', syslog, klog, serial, strace, tcpdump, wireshark etc.
• Any firewall NAT or WAN issues, show output: 'iptables -vnL', 'iptables -t nat -vnL', 'iptables -t mangle -vnL' and /tmp/.ipt file.
• Search SVN tickets & discuss in forum before opening. Before reporting: reset & manually set up, not restore from a backup.
• Please include operating & wireless modes (e.g. Gateway, Router, AP, CB, WDS, Mesh) & relevant configuration information.

Example Template:
Code:
[b]Router/Version: [/b]
[b]File/Kernel: [/b]
[b]Previous/Reset: [/b]
[b]Mode/Status: [/b]
[b]Issues/Errors: [/b]

_________________
Official Forum Rules, Guidelines & Helpful InformationFirmware FAQInstallation WikiWhere Do I Download Firmware?
DON'T use Chromium-based browsersRTFM/STFW TL;DR is NOT an excuse. • Why Should I Care What Color the Bikeshed Is?
Please DO NOT PM me with questions; Ask in the forum. ---------------------- Linux User #377467 counter.li.org / linuxcounter.net
Sponsor
Fonzi
DD-WRT Novice


Joined: 20 Mar 2021
Posts: 41

PostPosted: Sat Apr 24, 2021 23:08    Post subject: Reply with quote
Router setup:
WRT1900ACS V2

Configuration
Build 46446
OpenVPN - tap mode bridged
Wireguard - 11 clients
Wifi 5GHZ AC-Only WHT80
Wifi 2.4GHZ - NG-Mixed - Dynamic 20/40 - Ch. 13 - ext ch=lower
Security WP2+AES on both radios
Port forwarding utilized for SMTP, IMAP, HTTP and HTTPS (IMAP on non-standard port)

Kernel crash after 4h uptime. No event obvious to trigger it. Same as previous builds > 46069


Last edited by Fonzi on Mon Apr 26, 2021 15:24; edited 1 time in total
o2bad455
DD-WRT User


Joined: 08 Oct 2015
Posts: 121

PostPosted: Sun Apr 25, 2021 15:32    Post subject: Reply with quote
Router/Version: WRT1900ACSv2 / r46446
File/Kernel: webflash / Linux 4.9.267 #2574 SMP Sat Apr 24 05:57:05 +07 2021 armv7l
Previous/Reset: r46069(r46395) / No
Mode/Status: Gateway, OpenVPN Client, FreeRadius Server, multiple wlans each using a different single flavor of WPA (i.e., none are mixed)
Issues/Errors: Working well with a good mix of Apple and non-Apple clients, thanks! Log attached for comparison purposes.

Update: No significant issues or errors after 24+ hours uptime. I've been having minor wifi stabiity issues on 5G for one Windows 10 PC, but I think it's unrelated to the build - most likely interference.

_________________
My DD-WRT Routers:
Linksys/Marvell WRT1900ACSv2 (r46885 - test only)
Linksys/Marvell WRT1900ACSv1 (r46069 - daily use)
HP-Laptop/Intel/x86-64 (r46316 - test only due to unsupported wifi)
Netgear/Broadcom R7000 (3x: r45928 - remote use)
Linksys/Broadcom WRT54G/GS (4x: r44715 - occasional use)
Netgear/Atheros R9000 (bought broken and awaiting delivery)
ruprect
DD-WRT Novice


Joined: 29 Sep 2016
Posts: 34

PostPosted: Mon Apr 26, 2021 9:46    Post subject: Reply with quote
Linksys WRT1900ACS Firmware Version DD-WRT v3.0-r46446 std (04/24/21)
Kernel Version Linux 4.9.267 #2574 SMP Sat Apr 24 05:57:05 +07 2021 armv7l
Previous: r46446 / No reset

Upgraded using FF on W10Pro

SAMBA share (NTSC HDD) still falls over and has for many releases now. Lasted a couple hours. Can't connect either via Wired or Wireless connection. GUI is still up

Wifi is still up in Win10, but I will update if//when it disconnects.

No Apple devices, the GUI shows SAMBA still enabled, for what that'1s worth.
o2bad455
DD-WRT User


Joined: 08 Oct 2015
Posts: 121

PostPosted: Thu Apr 29, 2021 15:31    Post subject: Reply with quote
UPDATE: After just over three days up (since a pre-scheduled automatic Monday morning reboot), our test ACSv2 router on r46466 lost all client connectivity this morning, although the SSIDs were still being broadcast (5 G intermittently, 2.4G more reliably). Fortunately, I had set up persistent logs which I successfully downloaded after a reboot. ACSv2-r46466 Logs attached (first log file spilled over to second log file after first 1.5 days, probably due to apparent 8MB txt file limitation in jffs). Our production ACSv1 router on r46069 has been up longer with zero issues so far, FWIW.

EDIT: The device with MAC ending C8:C9, which seems to be popular in the logs despite less user-initiated usage than the other connected devices, is an iPhone X on Apple's latest firmware (14.x IIRC).

_________________
My DD-WRT Routers:
Linksys/Marvell WRT1900ACSv2 (r46885 - test only)
Linksys/Marvell WRT1900ACSv1 (r46069 - daily use)
HP-Laptop/Intel/x86-64 (r46316 - test only due to unsupported wifi)
Netgear/Broadcom R7000 (3x: r45928 - remote use)
Linksys/Broadcom WRT54G/GS (4x: r44715 - occasional use)
Netgear/Atheros R9000 (bought broken and awaiting delivery)


Last edited by o2bad455 on Thu Apr 29, 2021 15:58; edited 1 time in total
Fonzi
DD-WRT Novice


Joined: 20 Mar 2021
Posts: 41

PostPosted: Thu Apr 29, 2021 15:54    Post subject: Reply with quote
o2bad455 wrote:
Fortunately, I had set up persistent logs which I successfully downloaded after a reboot. ACSv2-r46466 Logs attached (first log file spilled over to second log file after first 1.5 days, probably due to apparent 8MB txt file limitation in jffs).


Did you also get the kernel (DMESG) log? I noted in my case that the crashes always followed the "ieee80211 phy0: Mac80211 start BA <Mac-address of connected device>, which the DMESG output is overcrowded with on these routers. And then NULL Pointer...virtual address 00000004.
I checked my Kernel logs. Interestingly, out of 26 connected devices, it was always one of these that was the last line before the crash:
ieee80211 phy0: Mac80211 start BA +
- Ipad
- Iphone
- Mac Airbook
- Samsung S7
- Samsung S9+
- Chromecast (!) (This one I cannot explain - the other devices do show signs of problems - wifi connected shown, still no network, but the Chromecast we haven't heard about before..)

I checked this across builds 46166, 46177, 46259, 46294, 46301, 46316, 46329, 46442 and 46446.
What we both seem to have experienced is that 46446 takes (a lot) longer, before it eventually crashes. In my case 4H, in your case a couple of days. I hope that is a sign that they are tweaking on something where it eventually will be fixed.
o2bad455
DD-WRT User


Joined: 08 Oct 2015
Posts: 121

PostPosted: Thu Apr 29, 2021 16:05    Post subject: Reply with quote
Fonzi wrote:
Did you also get the kernel (DMESG) log?


I can't get that directly after a reboot, but as long as both the syslogd and klogd were still running, I think the same DMESG messages (plus some metadata) should be in my combined logs.

And Yes about the usual suspects, LoL! As noted in my moments-ago edit to immediately previous post, the culprit might well be an iPhone X with MAC ending C8:C9. Win10 PC and Android phone probably each had far more actual use, but that iPhone sure seems to be over-represented in the error log entries.

_________________
My DD-WRT Routers:
Linksys/Marvell WRT1900ACSv2 (r46885 - test only)
Linksys/Marvell WRT1900ACSv1 (r46069 - daily use)
HP-Laptop/Intel/x86-64 (r46316 - test only due to unsupported wifi)
Netgear/Broadcom R7000 (3x: r45928 - remote use)
Linksys/Broadcom WRT54G/GS (4x: r44715 - occasional use)
Netgear/Atheros R9000 (bought broken and awaiting delivery)
Argenis
DD-WRT User


Joined: 18 Feb 2019
Posts: 143

PostPosted: Thu Apr 29, 2021 19:28    Post subject: Reply with quote
Upgraded 3200ACM from 23rd build without resetting, using Firefox production and wired connection of course.

I'd have to say for the 3200ACM series, this is perhaps the most solid release so far, 4 days of no issues at all, OpenVPN client working without issues and DNSSEC working great.

Will update if anything else happens as I test some more stuff with this build.

_________________
Router: Linksys WRT3200ACM WLAN0 and 1 have same SSID
88W8964 802.11ac WLAN0 Mode AP VHT80 80MHz Mixed Mode Channel and Extension Channel Auto Extension LL-6
88W8964 802.11ac WLAN1 Mode AP 20 MHz Mixed Mode Channel Auto
SD8887 802.11ac disabled but visible on GUI and CLI
TX Power 19 dBm
Antenna Gain 0 dBi
U-APSD (Automatic Power Save)Enabled 
Protection Mode None
RTS Threshold Disabled
Short Preamble Disabled 
Short GI Enabled
Single User Beamforming Enabled
Multi User Beamforming Enabled 
AP Isolation Disabled
Beacon Interval 100
DTIM Interval 2
WMM Support Enabled 
Radar Detection Disabled 
ScanList default
Sensitivity Range (ACK Timing) 500 (Default: 500 meters)
Max Associated Clients 256 (Default: 256 Clients)
Minimum Signal for authenticate -128
Minimum Signal for connection -128
Poll Time for signal lookup 10
Amount of allowed low signals 3
Wireless security is WPA2 Personal CCMP-128 only
QAM256 is off
Monza
DD-WRT User


Joined: 01 Jul 2018
Posts: 293

PostPosted: Wed May 05, 2021 14:06    Post subject: Reply with quote
Upgraded WRT1200AC v1's from r46442 to r46446 using Brave 1.10.97 (64-bit) running on Linux Mint 20.1 OS hardwired via Cat6.

Successful update and reboot. No reset, nothing disabled prior to update, uptime approx 10 days, wired/wireless connected, vpn up immediately (Expressvpn). I do not use NAS. SFE, QoS and IPv6 are always disabled. OpenVPN client/DNSMasq and radios always enabled. I do not have any Apple devices.

Kernel Version Linux 4.9.267 #2574 SMP Sat Apr 24 05:57:05 +07 2021 armv7l

No issues with a routine update session.
alix78
DD-WRT Novice


Joined: 06 May 2021
Posts: 3

PostPosted: Thu May 06, 2021 8:58    Post subject: Cannot mount SSD drive on USB Reply with quote
Hi all,
first thank you for all that great work i have been using for years Very Happy .
This firmware is solid as reported by Argenis on the WRT3200ACM for classical router use, including VPN (ExpressVPN), fast, lower cpu usage and lower temperature than preceding versions. No issue at the update step, good !

However, i currently face an issue trying to mount a ssd drive on the USB port of the WRT3200ACM.
I had the same issue with with r45632 and r44048.

Disk is a Seagate IronWolf Pro 960Go with an ext4 partition that works fine on a Ubuntu18.04 laptop with same cable. However, mounted either using usb3.0 or esatap cables, the issue is the same on the router:
=> When activating the USB core service the following issue is reported:
* at reboot, internet access is no more available until usbcore is deactivated.
* dmesg seems to show that the drive speed cannot be adapted/negociated (log reported below from the usb core activation to the first iteration of the loop "hard resetting link->exception...").
* on the usb service panel of ddwrt, no disk is reported (as well as on dmesg...)

I saw similar issue on other linux system that related this to outdated kernel modules but i am absolutely not a specialist. Thanks for your help and work once again !

************************************************
Current status :
Firmware: DD-WRT v3.0-r46446 std (04/24/21)
Time: 10:45:47 up 4 days, 20:30, load average: 0.00, 0.00, 0.00
Code:
 [419823.513032] usbcore: registered new interface driver usbfs
[419823.518690] usbcore: registered new interface driver hub
[419823.524144] usbcore: registered new device driver usb
[419823.555185] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[419823.565805] ehci-platform: EHCI generic platform driver
[419823.579959] ehci-pci: EHCI PCI platform driver
[419826.642299] xhci-hcd f10f8000.usb3: xHCI Host Controller
[419826.647770] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 1
[419826.655440] xhci-hcd f10f8000.usb3: hcc params 0x0a000990 hci version 0x100 quirks 0x00010010
[419826.664118] xhci-hcd f10f8000.usb3: irq 45, io mem 0xf10f8000
[419826.670321] hub 1-0:1.0: USB hub found
[419826.674203] hub 1-0:1.0: 1 port detected
[419826.678545] xhci-hcd f10f8000.usb3: xHCI Host Controller
[419826.684057] xhci-hcd f10f8000.usb3: new USB bus registered, assigned bus number 2
[419826.691832] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.
[419826.700663] hub 2-0:1.0: USB hub found
[419826.704657] hub 2-0:1.0: 1 port detected
[419826.880893] usbcore: registered new interface driver usb-storage
[419826.941961] ehci-orion: EHCI orion driver
[419826.946360] orion-ehci f1058000.usb: EHCI Host Controller
[419826.951971] orion-ehci f1058000.usb: new USB bus registered, assigned bus number 3
[419826.959739] orion-ehci f1058000.usb: irq 38, io mem 0xf1058000
[419826.975734] orion-ehci f1058000.usb: USB 2.0 started, EHCI 1.00
[419826.982039] hub 3-0:1.0: USB hub found
[419826.985973] hub 3-0:1.0: 1 port detected
[419827.055987] ahci-mvebu f10a8000.sata: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl platform mode
[419827.065165] ahci-mvebu f10a8000.sata: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
[419827.074562] scsi host0: ahci-mvebu
[419827.078250] scsi host1: ahci-mvebu
[419827.081850] ata1: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x100 irq 42
[419827.089907] ata2: SATA max UDMA/133 mmio [mem 0xf10a8000-0xf10a9fff] port 0x180 irq 42
[419827.426917] ata1: SATA link down (SStatus 0 SControl 300)
[419827.705735] ata2: SATA link down (SStatus 0 SControl 300)
[419827.817546] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
[419827.825070] ata2: irq_stat 0x80000040, connection status changed
[419827.831216] ata2: hard resetting link
[419828.795740] ata2: SATA link down (SStatus 0 SControl 300)
[419828.801260] ata2: EH complete
[419828.884236] ata2: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
[419828.891763] ata2: irq_stat 0x80000040, connection status changed
[419828.897918] ata2: limiting SATA link speed to 1.5 Gbps
[419828.903166] ata2: hard resetting link


Last edited by alix78 on Thu May 06, 2021 14:31; edited 2 times in total
o2bad455
DD-WRT User


Joined: 08 Oct 2015
Posts: 121

PostPosted: Thu May 06, 2021 11:51    Post subject: Reply with quote
UPDATE #2: Our above-described issues on r46446 (our WRT1900ACSv2) persist after many reboots and adjustment attempts over the past two weeks. The trigger seems to be that fully updated Apple device clients (e.g., latest iOS 14, iPadOS 14, and iWatchOS 7 - we don't have any MacOS but I'd suspect the same) are randomizing their wifi MAC addresses on reconnection and/or during reconnection attempts. This is apparently now Apple's default behavior for privacy purposes! Supposedly it can be disabled on each Apple device, and possibly per SSID, but I haven't had access to a device long enough to figure out how. Surprisingly, the same devices are not causing any noticeable issues for the router itself or other clients on r46069 (our WRT1900ACSv1).

EDIT:
The Apple feature permitting randomized MAC can be disabled per SSID Network by turning off the Private Address toggle (just under the Auto-Join toggle) in the Apple device's wifi settings for that particular network. Apple is confusingly calling the randomized MAC a "Wi-Fi Address". LoL!

EDIT #2:
When reviewing logs, it may be helpful to note that an Apple-randomized MAC address should have a second character of 2, 6, A or E. Any other second character for an Apple device should indicate a physical MAC.

_________________
My DD-WRT Routers:
Linksys/Marvell WRT1900ACSv2 (r46885 - test only)
Linksys/Marvell WRT1900ACSv1 (r46069 - daily use)
HP-Laptop/Intel/x86-64 (r46316 - test only due to unsupported wifi)
Netgear/Broadcom R7000 (3x: r45928 - remote use)
Linksys/Broadcom WRT54G/GS (4x: r44715 - occasional use)
Netgear/Atheros R9000 (bought broken and awaiting delivery)
SurprisedItWorks
DD-WRT Guru


Joined: 04 Aug 2018
Posts: 1190
Location: Appalachian mountains, USA

PostPosted: Thu May 06, 2021 15:33    Post subject: Reply with quote
iOS "randomization" of MAC addresses isn't what that term suggests. On a given wifi network, it will always use the same MAC address. I use that feature to manage some static leases.
_________________
Five WRT1900ACSv2's on 42926, 44048, 46069: VLANs, VAPs, NAS, client mode, OpenVPN client (AirVPN), DDNS, wireguard servers and clients (AzireVPN), two DNSCrypt DNS providers (incl Quad9) via OpenVPN/wireguard clients.
o2bad455
DD-WRT User


Joined: 08 Oct 2015
Posts: 121

PostPosted: Thu May 06, 2021 16:41    Post subject: Reply with quote
SurprisedItWorks wrote:
iOS "randomization" of MAC addresses isn't what that term suggests. On a given wifi network, it will always use the same MAC address. I use that feature to manage some static leases.


Agreed about Apple's expressed intent for "randomization", but the MACs simply aren't the same even on the same SSID (have to verify if same wlan and/or channel). I did some reading and it turns out that Apple previously announced plans to add "rotation" within each SSID, so I assume that's what's now happened in the latest iOS release. Whatever the cause, the combined effect with recently updated (e.g., past two weeks) Apple devices is well and truly random (except for the 2nd hex digit). It's increasingly difficult to track different Apple devices for testing.

EDIT: For example, the Apple iPhone X with randomized MAC ending ...C8:C9 from my April 26-29 log, posted above, changed to ...db:19 in my attached May 3-6 log. Same router, same build, same iPhone, just a couple of post-crash router reboots later.

EDIT #2: Oops, I made a mistake. Not sure why, but it looks like the iPhone (iOS 14.4.2) actually connected using WPA2 (wlan0.1 @ 5GHz) in the later log versus WPA3 (wlan0 @ 5GHz) in the earlier log, so Apple hasn't necessarily implemented "rotation" yet, after all.

EDIT #3: BTW, the attached log covering May 3-6 was recovered from jffs backup this morning, post-reboot, after pretty much the same symptoms (inability to connect) as I'd posted on April 29, but with a lot fewer total errors so perhaps easier to sift out any underlying cause.

_________________
My DD-WRT Routers:
Linksys/Marvell WRT1900ACSv2 (r46885 - test only)
Linksys/Marvell WRT1900ACSv1 (r46069 - daily use)
HP-Laptop/Intel/x86-64 (r46316 - test only due to unsupported wifi)
Netgear/Broadcom R7000 (3x: r45928 - remote use)
Linksys/Broadcom WRT54G/GS (4x: r44715 - occasional use)
Netgear/Atheros R9000 (bought broken and awaiting delivery)
SurprisedItWorks
DD-WRT Guru


Joined: 04 Aug 2018
Posts: 1190
Location: Appalachian mountains, USA

PostPosted: Fri May 07, 2021 14:37    Post subject: Reply with quote
Hi @o2bad455... FWIW, I just checked my iPhone XS on iOS 14.5.1 against five SSIDs for which Private Address is set, and all of them have the same MACs as they had months ago when I coded them into my dnsmasq settings.

So indeed, they aren't random yet!

_________________
Five WRT1900ACSv2's on 42926, 44048, 46069: VLANs, VAPs, NAS, client mode, OpenVPN client (AirVPN), DDNS, wireguard servers and clients (AzireVPN), two DNSCrypt DNS providers (incl Quad9) via OpenVPN/wireguard clients.
o2bad455
DD-WRT User


Joined: 08 Oct 2015
Posts: 121

PostPosted: Fri May 07, 2021 17:55    Post subject: Reply with quote
SurprisedItWorks wrote:
Hi @o2bad455... FWIW, I just checked my iPhone XS on iOS 14.5.1 against five SSIDs for which Private Address is set, and all of them have the same MACs as they had months ago when I coded them into my dnsmasq settings.

So indeed, they aren't random yet!


Confirmed, thanks! It's good to know too that Apple's MAC randomization (or Private Address) is behaving consistently across dd-wrt builds with same SSID.

So, Apple MAC randomization should perform as follows:

A) Same SSID on different radios should yield same psuedo-MAC. This I've now confirmed on a single router.

B) Different SSIDs on same radio should yield different psuedo-MACs. This I've also confirmed (despite my initial misinterpretation) on a single router.

I'll try to check any old router logs that I might still have for different routers using the same SSID (none at the moment), at least if any two were both tested with Apple clients updated to iOS 14.x, but I think it'd be safe to assume at this point that the psuedo-MAC should remain the same for the same exact SSID even on different routers. AKAIK, nothing else should affect that (other than disabling or enabling Private Address and/or a pre-iOS-14 device in which cases the real physical MAC should always be presented).

So, the only way to get an Apple device to report two different MACs to a same SSID should be either when it's first updated to iOS 14.x, or when a user toggles the Private Address on or off for that SSID in the device's wifi settings. I'm confident that neither of these occurred during my r46446 testing (although it could have occurred during my testing of previous builds when some devices were certainly updated from iOS 13 to iOS 14, etc.).

Conclusion:
It looks to me like my initial hunch was wrong. That is, Apple's MAC-randomization feature is probably NOT the cause of at least my r46446 router becoming completely nonresponsive every 2-3 days.

_________________
My DD-WRT Routers:
Linksys/Marvell WRT1900ACSv2 (r46885 - test only)
Linksys/Marvell WRT1900ACSv1 (r46069 - daily use)
HP-Laptop/Intel/x86-64 (r46316 - test only due to unsupported wifi)
Netgear/Broadcom R7000 (3x: r45928 - remote use)
Linksys/Broadcom WRT54G/GS (4x: r44715 - occasional use)
Netgear/Atheros R9000 (bought broken and awaiting delivery)
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Marvell MVEBU based Hardware (WRT1900AC etc.) All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum