OpenVPN CLIENT works fine (nordvpn server)
5GHz wpa2 CCMP-128 (AES)working fine 20MHz Mixed
2.4GHz wpa2 CCMP-128 (AES)working fine 20MHz Mixed
NAS via USB Samba also working fine
WEBFlashed to both partitions with Firefox 70.0.1
VPN,SAMBA,NAS,DLNA working.
WiFi NOT tested.
Firmware Version
DD-WRT v3.0-r41468 std (11/06/19)
Kernel Version
Linux 4.9.199-rc1 #1382 SMP Wed Nov 6 02:06:32 CET 2019 armv7l _________________ WRT1900ACSv2
Joined: 04 Aug 2012 Posts: 612 Location: behind the screen
Posted: Thu Nov 07, 2019 22:14 Post subject:
I connected to 2g no problems NO LOST Access to the GUI
Then I tryed from the AP via cat5 wire
Then I LOST Access to the GUI
BTY
If I do the same thing with r40009, no problems, NO LOST Access to the GUI _________________ WRT3200ACM openwrt 18.06.5
WRT3200ACM dd-wrt r41791
WRT54GL dd-wrt r21676
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Fri Nov 08, 2019 2:55 Post subject:
I presume this is with a known good 100% functional ethernet cable and ports, verified as good and functional. If so, add information to the ticket so it can be fixed. _________________ "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
Updated WRT1200AC v1 from r41459 to r41468 with no reset using Firefox 70.0.1 (64 bit) running on Win 8.1. No issues, nothing disabled prior to update, wired/wireless and vpn up immediately (ExpressVPN). Uptime about 24 hrs. Seems a bit faster. than r41459. I've had no issues with the GUI. I do not use QoS or NAS
Kernel Version Linux 4.9.199-rc1 #1382 SMP Wed Nov 6 02:06:32 CET 2019 armv7l
Nov 8 05:25:27 router daemon.notice openvpn[1654]: OpenVPN 2.4.7 arm-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Nov 6 2019
Nov 8 05:25:27 router daemon.notice openvpn[1654]: library versions: OpenSSL 1.1.1d 10 Sep 2019, LZO 2.09
Posted: Fri Nov 08, 2019 16:07 Post subject: WRT3200ACM 5 GHz WDS network (3 stations)
Installation went somewhat OK but the 5 GHz radio on the WDS AP continues to be a problem (doesn't come back up after the reboot). Usually, clicking on "Apply Settings" on the Wireless->BasicSettings tab brings the radio back up but sometimes I have to cycle power to the router. Even that doesn't always bring the 5 GHz back up. Sometimes it takes multiple reboots and/or power cycles and/or "Apply settings" to get the radio to come back up. The 2.4 GHz radio always comes up though. Everything else works good (WAN, LAN, 2.4 GHz firewall,openvpn, etc). I do have one other mystery - my Ring doorbell causes the network to momentarily pause and sometimes it takes the network completely down whenever I get a motion detected alert or when the doorbell is activated. Also, my 5 GHz network died around 0700 this morning - less than 24 hours service - took about 15 minutes to get the network working again. I guess I'll setup my WDS network to use 2.4 GHz instead since 5 GHz is so unreliable.
I would have to do some digging, but are the Marvell drivers and code that shitty in factory firmware?
Don't know but it's my understanding that Marvell has dropped development for dd-wrt. I'd buy a router with different hardware but so far there are issues with other routers. For example, I was looking at the Netgear R8000 but a lot of people are having trouble just doing an initial install of dd-wrt. Unless there's a router that has 100% non-proprietary drivers we can't expect to get the "perfect" dd-wrt router, IMHO.
Joined: 08 May 2018 Posts: 14246 Location: Texas, USA
Posted: Fri Nov 08, 2019 17:51 Post subject:
johnnyNobody999 wrote:
kernel-panic69 wrote:
I would have to do some digging, but are the Marvell drivers and code that shitty in factory firmware?
Don't know but it's my understanding that Marvell has dropped development for dd-wrt.
Pardon my being blunt, but that is one of the most ignorant statements I have ever read. Vendors and manufacturers do not develop for DD-WRT, BrainSlayer does. AFAIK, the only 'proprietary' anything is Broadcom. Everything else is supplied to kernel developers, router vendors, etc. A lot of them make it publicly accessible, Broadcom, not so much. Sometimes, there's patches and enhancements and other monkey shit inserted by Mr. Gottschall. Sometimes it works, other times, not so much. Then you have the whole code base of the DD-WRT "Linux Distribution" itself that I sometimes wonder just exactly how much of it is necessary, since there are already industry standard packages that do a lot of what is there. Tomato has never been so bloated with a whole bunch of shit, but it is a Broadcom-only firmware, always has been except for folks who have forked it and have been able to port it to other platforms. Again, sorry for being so blunt, but that is my perspective on things from keen observations and doing a little tinkering around under the hood myself. I was simply wondering if factory firmware was just as shitty stability and performance-wise or not. I guess I'd have to buy a Marvell unit and see for myself. It could be that router manufacturers and vendors are no longer using Marvell hardware, and Marvell may not be contributing to hardware support source code, drivers, etc. for Linux anymore. That may be a more accurate statement. My apologies for being so blunt and such a dick, but it's one of my more charming qualities lol _________________ "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
I would have to do some digging, but are the Marvell drivers and code that shitty in factory firmware?
Don't know but it's my understanding that Marvell has dropped development for dd-wrt.
Pardon my being blunt, but that is one of the most ignorant statements I have ever read. Vendors and manufacturers do not develop for DD-WRT, BrainSlayer does. AFAIK, the only 'proprietary' anything is Broadcom. Everything else is supplied to kernel developers, router vendors, etc. A lot of them make it publicly accessible, Broadcom, not so much. Sometimes, there's patches and enhancements and other monkey shit inserted by Mr. Gottschall. Sometimes it works, other times, not so much. Then you have the whole code base of the DD-WRT "Linux Distribution" itself that I sometimes wonder just exactly how much of it is necessary, since there are already industry standard packages that do a lot of what is there. Tomato has never been so bloated with a whole bunch of shit, but it is a Broadcom-only firmware, always has been except for folks who have forked it and have been able to port it to other platforms. Again, sorry for being so blunt, but that is my perspective on things from keen observations and doing a little tinkering around under the hood myself. I was simply wondering if factory firmware was just as shitty stability and performance-wise or not. I guess I'd have to buy a Marvell unit and see for myself. It could be that router manufacturers and vendors are no longer using Marvell hardware, and Marvell may not be contributing to hardware support source code, drivers, etc. for Linux anymore. That may be a more accurate statement. My apologies for being so blunt and such a dick, but it's one of my more charming qualities lol
No problem. My skin is thick enough. My understanding was that Marvell radio drivers are proprietary based on what I read elsewhere. Still, my point is that Marvell driver development no longer exists and that's why mu-mimo doesn't work and won't work on dd-wrt even though there's a check box for it. At least this is my understanding of why the radio doesn't work properly. Everything that I read on the internet is the truth, right?
Anyway, I'd like to find a router that is more reliable than my WRT3200ACM.
