Joined: 08 May 2018 Posts: 14208 Location: Texas, USA
Posted: Sun Jan 06, 2019 18:38 Post subject:
@Gradius, only things I can think of are a conflict between udev and hotplug2. My USB doesn't even WORK AT ALL on DD-WRT public builds. I got curious and tried it....
@Gradius, only things I can think of are a conflict between udev and hotplug2. My USB doesn't even WORK AT ALL on DD-WRT public builds. I got curious and tried it....
Something to try....not saying it will help you but hear me out
I hadn't used usb on my WNDR3400v1 in a really long time
Shortly after upgrading to a K3x build I noticed that I lost USB Support.....I assumed it was the price of being on K3x...but wasent positive that that was when I lost it
Many build flashes later....it "bricked" (truly only semi-bricked as it wea recoverable)
With serial connected at CFE prompt I ran nvram erase then tftpd'd an old build I used back when I first brought that router over to dd-wrt that was built by Eko...once booted twice I ran telnet and ran erase nvram...reboot
USB came back!!
Flashed a more current K3x build...followed by telneting in and running erase nvram....
I still had USB!!!
Later put the Kx3 build in my signature.....ran erase nvram.....but noticed that it diddnt wipe the user/password....so researched....then ran erase nvram followed by nvram erase then reboot...
My WNDR3400v1 currently still has USB support!!
Sorry I can not explain the why and how...as I had erased the nvram many many times on different Kx3 firmwars which never fixed my non USB Support issue in the past
I hope this helps.....maybe ¯\_(ツ)_/¯ _________________ Location 1
R7800- DD-WRT v3.0-r53562 (10/03/23) Gateway
WNDR3400v1 DD-WRT v3.0-r35531_mega-nv64k (03/26/18 ) Access Point
WRT160Nv3 DD-WRT ?v3?.0-r35531 mini (03/26/18 ) Access Point
WRT54GSv5 DD-WRT v24-r33555_micro_generic (10/20/17) Repeater
Location 2
R7800- DD-WRT v3.0-r51855 (02/25/23) Gateway
R6300v2- DD-WRT v3.0-r50671 (10-26-22) Access Point
WNDR3700v2 DD-WRT v3.0-r35531 std (03/26/18 ) Access Point
E1200 v2 DD-WRT v3.0-r35531 mega-nv64k (03/26/18 ) Gateway(for trivial reasons)
RBWAPG-5HACT2HND-BE RouterOS-v6.46.4 (2/21/20) Outdoor Access Point
2x RBSXTG-5HPACD RouterOS-v6.46.4 (2/21/20) PTP Bridge 866.6Mbps-1GbpsLAN
Location 3
2x R7000- DD-WRT v3.0-r50671 (10/26/22) Access Points
2x RBWAPG-60AD RouterOS-v6.45.9 (04/30/20) PTP Bridge 2.3Gbps-1GbpsLAN
2x RBSXTsqG-5acD RouterOS-v6.49.7 (10/14/22) PTP Bridge 866.6Mbps-1GbpsLAN Thank You BrainSlayer for ALL that you do & have done, also to "most" everyone here that shares their knowledge
Major improvement since build 38060 and previous builds: it's once again possible to select a wireless channel for the 5 GHz radio when set at VHT80. My laptop is showing a 866.7 Mbps link speed now instead of only 400. Web ui seems to have been fixed for the wifi settings. Thanks to @kwapster for pointing this out.
kwapster wrote:
MolaMola wrote:
I went back to old build 35244 to regain actual VHT80 AC speeds (with 866 Mbps link speeds) and the possibility to set a fixed channel number instead of auto channel as the only option available with that channel width.
i'm using a c9 on this build and i'm able to choose a fixed channel and i get ac speeds without issue.
@Gradius, only things I can think of are a conflict between udev and hotplug2. My USB doesn't even WORK AT ALL on DD-WRT public builds. I got curious and tried it....
First of all, thanks for looking into this issue.
Unfortunately there are still too many bugs as after an USB unplug (tried even after a power off/on) it stopped working again.
I don't think I will look at this issue again as I would use LTE/4G/3G in case of emergency only... but still it would be cool and great to have this feature fixed and working properly.
Joined: 30 Sep 2018 Posts: 47 Location: United Kingdom
Posted: Mon Jan 07, 2019 0:32 Post subject:
Router/Version: WNDR4500v1
File: dd-wrt.v24-38159_NEWD-2_K3.x_mega-WNDR4500.bin
Kernel: Not checked.
Mode: Router
Status: I flashed it to set it as Ethernet Bridge Client - this feature seems to work, however it doesn't work well on 5G - I'm not sure what is the reason, but with 100% signal strength I got only 6/6 Mbit connection and even DHCP did not work trough it. When switched to 2G - everything was OK.
I don't think its related to this firmware. Maybe its just incompatibility with master router which is Linksys EA6900 - with FreshTomato on board. _________________ Bible in short: Don't be religious. Just love God and follow Jesus
Router/Version: Netgear R7000
Firmware: DD-WRT v3.0-r38159 std (01/02/19)
Kernel: Linux 4.4.169 #4419 SMP Mon Dec 31 09:50:12 CET 2018 armv7l
Previous: r38155
Mode/Status: Gateway / working
Reset: no
Issues/Errors: service SES / AOSS / EZ-SETUP / WPS Button Turning off radio don't work, Wifi don't work correctly. The Wireless Physical Interface wl0 [2.4 GHz TurboQAM] don't work if Wireless SSID Broadcast is disabled, don't assign ip address. Wifi don't connect to internet but i don't know because. To first start don't have problem. I'm very confused.
Last edited by Frakko on Fri Jan 11, 2019 7:59; edited 1 time in total
Router/Version: Asus RT-AC56U
File: DD-WRT v3.0-r38159 std
Kernel: Linux 4.4.169 #4419 armv7l
Previous: DD-WRT v3.0-r38104 std
Reset: Yes
Mode: Gateway/AP
Status: Working
Issues/Errors: LAN indicator does not work but no other issues so far, uptime 22hrs
Not a heavy lifter: Some static leases, port forwards, port range forwards, WOL (from WAN); faster average ac thruput than previous build; in my case ac channels only configurable if US regulatory domain is selected (I'm in Ireland)
Posted: Fri Apr 12, 2019 13:48 Post subject: Linksys WRT-150N v1.1 succesfull on r38159
Router/Version: Linksys WRT-150N v1.1
File: DD-WRT.v24_mini_generic.bin (ftp://ftp.dd-wrt.com/betas/2019/01-02-2019-r38159/broadcom/dd-wrt.v24_mini_generic.bin)
Kernel:
Linux 2.4.37 #51571 Wed Jan 2 08:03:03 CET 2019 mips
Firmware version: DD-WRT v3.0-r38159 mini (01/02/19)
Previous: DD-WRT v2.4-r14929 mini generic
Reset: Yes (30-30-30 before and after upgrade)
Mode: Gateway/AP
Status: Working
Issues/Errors: Seem to run just fine! IE Edge has trouble working with the browser interface, but that will have been the case with the previous version(s), too.
