H David - thanks, this worked perfectly. I'm having problems with guest network, but will post again ocne I have troubleshooted the issue accurately

(Last edited by wayne1958 on 29 Mar 2018, 20:12)

Hello,

In need of some help, bricked my WRT3200acm, both boot partitions. Don’t ask me how as I have no idea.

How can I get it back to either default or the latest of David’s build?

Many thanks in advance

If both are truly borked, tftp would be the next logical step.

Hey David,

first I wanted to thank you for providing this great optimized Image you provide for WRT 1900...

Yesterday i tried to mount an NTFS-Drive over USB 3.0 and I failed to get automount working... now i would like to know, if it is my fault or if it is an openwrt bug. I use the latest image: 9b84c3ab05d95bb059b55953909485163c88d34a3f337019ea282e6cec5516b4 2018-03-25 02:27 without any further packages or modifications.

At first i tried to manually mount the device, which worked like expected:

root@OpenWrt:/etc/config# mount /dev/sda1 /mnt/sda1/
root@OpenWrt:/etc/config# mount
#[...]
/dev/sda1 on /mnt/sda1 type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)

Then i configured a mount point via Luci and enabled it for automount - this DID NOT WORK:

root@OpenWrt:/etc/config# cat /etc/config/fstab 
config 'global'
    option    anon_swap    '0'
    option    anon_mount    '0'
    option    auto_swap    '1'
    option    auto_mount    '1'
    option    delay_root    '5'
    option    check_fs    '0'

config 'mount'
    option    target    '/mnt/sda1'
    option    uuid    '8AA629B9A629A6A3'
    option    enabled    '1'

Digging deeper i checked the /etc/fstab (which is autogenerated, but empty, even after reboot?!):

cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>

Executing "/sbin/block mount" does not mount the device either:

block mount
block: /dev/ubiblock0_0 is already mounted on /rom
block: /dev/ubi0_1 is already mounted on /overlay
block: /dev/ubi1_0 is already mounted on /mnt/ubi1_0

While "/sbin/block detect" and "/sbin/block info" show the disk like expected (except that the uuid of block info is different from the one that block detect spits out):

root@OpenWrt:/etc# block info
#[...]
/dev/sda1: UUID="0000001800000048" MOUNT="/mnt/sda1" TYPE="ntfs"

Manually adding an entry with uuid to /etc/fstab and then mounting also fails (i tried both uuids and the dashed partuuid of blkid):

root@OpenWrt:/etc# cat /etc/fstab 
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=8AA629B9A629A6A3   /mnt/sda1   ntfs   auto,force,defaults   0  0 

root@OpenWrt:/etc# mount /mnt/sda1/
ntfs-3g: Failed to access volume 'UUID=8AA629B9A629A6A3': No such file or directory

ntfs-3g 2017.3.23 integrated FUSE 27 - Third Generation NTFS Driver
        Configuration type 1, XATTRS are on, POSIX ACLS are off

Copyright (C) 2005-2007 Yura Pakhuchiy
Copyright (C) 2006-2009 Szabolcs Szakacsits
Copyright (C) 2007-2017 Jean-Pierre Andre
Copyright (C) 2009 Erik Larsson

Usage:    ntfs-3g [-o option[,...]] <device|image_file> <mount_point>

Options:  ro (read-only mount), windows_names, uid=, gid=,
          umask=, fmask=, dmask=, streams_interface=.
          Please see the details in the manual (type: man ntfs-3g).

Example: ntfs-3g /dev/sda1 /mnt/windows

News, support and information:  ...
mount: mounting UUID=8AA629B9A629A6A3 on /mnt/sda1 failed: No such file or directory

While adding an entry with /dev/... reference works like a charm:

root@OpenWrt:/etc# cat fstab 
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/sda1   /mnt/sda1   ntfs   auto,defaults   0  0 

root@OpenWrt:/etc# mount /mnt/sda1/
root@OpenWrt:/etc#

My Questions:

• Does someone know, what I am missing or doing wrong or is it an openwrt bug (e.g. in /sbin/block)?

• Is there a possibility to work around this issue by detecting a plugged in usb disk and executing a shell-Script then?

(Last edited by sandreas on 29 Mar 2018, 22:31)

Can you give some descriptions of what is going on?

What lights do you see when the router is turned on for a few minutes? Can any clients connected via ethernet get to the internet? Are they receiving a IP address? If yes, can you ping the gateway?

I have a USB stick I usually log to, but have been using it for other purposes.  So, I decided after reading your post to plug it back in, but now I can't even get it to mount.  Will keep looking though.

I've used LuCi mount points in the past to get mine working. The formatting below is likely screwed up.

Enabled    Device                                Mount Point    Filesystem    Options    Root    Check     

UUID: ee230621-995e-489e-9822-a4f5f8092698 (not present)    /mnt/usb    ext4    rw    no    yes

(Last edited by davidc502 on 29 Mar 2018, 22:45)

I have a USB stick I usually log to, but have been using it for other purposes.  So, I decided after reading your post to plug it back in, but now I can't even get it to mount.  Will keep looking though.

I've used LuCi mount points in the past to get mine working. The formatting below is likely screwed up.

Wow, this was a fast response :-) Well - If I can help you with anything (e.g. logs), just ask! I regularly check this thread for updates.

The WRT1900ACv1 is a totally different machine from the v2 and the rest of the WRTs so you should be completely free of the problems with v1. I would stick with the cobra firmware while I don't know what the difference with shelby is really about.

I suspect there are config problems. I would reset the router to the defaults. That would remove the WIFI so you would need to reconfigure from scratch with a ethernet connection. I would just try setting the ssid and passphrase without changing anything else and see how that works. I always use a different ssid for the 2.4Ghz and 5Ghz bands although I don't know if that is mandatory.

I think that should give a way to check if there are problems with the router or the firmware. If there are no problems with the practically default settings then you can carefully change the settings until the problems reappear to locate the cause.

EDIT: There can be real problems with routing when the wireless and ethernet are both connected. The networking needs to know what interface to choose and can get confused when there is more than one way to listen/send.

(Last edited by beginner67890 on 30 Mar 2018, 00:58)

tested the r6520 on the 1900v1 but i just could not get openvpn to work properly--kept getting the "write to tun/tap : invalid argument (code=22)."  even restored to factory default and configured from scratch and just can't get openvpn to work properly.  had to revert back to the r5113 for openvpn to work properly.

I very rarely use VPN, but last time, which was some time ago, it worked. It isn't working anymore, so it isn't just you.  At this point I don't know what's going on with, and I don't have the time to troubleshoot it.

Hopefully, someone who needs it more than I do will track the problem down and share the solution.

no worry and thank you for your builds.

All my tests are done fresh new installs... I don't think resetting will make a difference if no configs were done when I setup the router.

I never use the same sid, but am curious why they are the same in default.

I think the older builds play much better than the newer, but i wanted the latest for the build quality without having to patch drivers and such. Will wait it out if i have to. As í am one of the few who can live with factory firmware,. Though I am doing well with UK ACS/V2 firmware without hiccups.

Just tired with Linksys being so slow to fix known issues and security.

Hello David,
Many thanks for getting back to me. Seems I was having more than one problem last night that created much frustration and confusion. I have managed to resolve all the other problems and ripped out of router from the network and today plugged it directly into my Mac, and surprised that I could login okay. The IP range changed and I had not realised that as I was not expecting it to change. I did a reset as I still don't know how to tell if your latest build is running or not?
Under System > Backup / Flash > Backup / Restore I did a Perform Reset, unticking Keep Settings.  Then via Flash new firmware image I applied your new .mig files and with WinSCP I uploaded and sysupgrade the .bin file (hoping that was the correct method?)
Please correct me if this is not the correct process?
Kind regards,

(Last edited by Morrile on 30 Mar 2018, 10:24)

Just a heads up to all people flashing to the r6520. As some of the wifi config files have changed I would recommend not keeping your settings when flashing. It works fine here for me and I flashed and did not keep configs. I don't use vpn or USB.

@davidc502

i am having trouble with gretap tunnels with your latest build (WRT1200AC). i think there is already a fix which was released shortly after your latest version:
bugs.openwrt.org/index.php?do=details&task_id=1452

if it is not too much trouble i would really appreciate it if you could include it. thx for all your work!

and what has changed? I don't think so. I always keep the configs and it works fine of course.

Is the WRT32x not compatible with the WRT3200 builds? Any plans to change this?

(Last edited by makedir on 30 Mar 2018, 14:57)

I am running out of ideas. The WRT1900ACv2 should be about the same as my WRT1200ACv1 and there have been no troubles with my wifi for either band. I just have wireless-n in my laptop and firestick for the 5Ghz radio so the AC features are not used. I set the radio0 to the AC mode anyway and get 300Mbit connections without problems. The radio1 is set to N mode for 2.4Ghz and connects to the other laptop at 54Mbit without fail so maybe that old card is limited to wireless-g speeds.

I thought a fresh install had the wifi disabled so didn't think there would be any default ssid for either band. I am sure the passphrase is blank in the beginning. My router is working fine now so I don't want to reset to defaults just to investigate.

My only idea would be maybe there is something with the way the wifi client is configured except that must work with the factory Linksys firmware so shouldn't be a problem. Have you noticed a difference running the 1900ACS firmware on the 1900ACv2? That seems to be a wild move. Maybe there were regulatory changes made to the ACS that are not good for the ACv2?

Maybe somebody else has a suggestion. I am out of ideas.

Hi, to clarify the firmware  I have ran and used during brake in started with stock build that came on my router.

Once I realised the original firmware had bugs, i quickly upgraded to the latest build. Which at the time had issues with android devices. Was getting up to 20 mbps max. After trial and error, i found i needed to customise my android device to get around 45 mbps download speeds on the 5GHz  N band  with a 150 mbps connection. With 2.4ghz N I connect at 72 mbps and have up to 35 mbps download speeds. With my laptop I can get 120 mbps download speeds with a 300mbps connection.

So after making sure no router issues were apparent, i move on to ACS V1 firmware and tested. Then moved on to Linksys ACS V2 firmware and decided on linksys UK firmware for my base to keep and run happily with.

So the only issues I found were with the factory base firmware. Once I got that resolved,  then moved on to test some of David's builds, back in February.  Did not have an issue but knew there was newer and better builds to come, so i waited for my warranty to end and move to test with the current builds.

I see no differences between AC/v2 and ACS builds from David, nor do I see any improvements from one over the other.

I think if here is an issue, it may be the newest changes to v2 hardware from refurbishment program, in closing up open doors  for overriding features.

At this time, no matter how i configure for the best connectivity that seems stable enough, there is no benefit to run the newer build for me at this time. There is another option to try but it is from a different party not supported here. If none of the newest builds ever work out for me, I may move on to try my final option to move away from the stagnant linksys outdated firmware.

New firmware 9.3.2.6 for 88W8964... Maybe MU-MIMO support?

yuhhaurlin started working on it last month, but isn't his only project. Maybe we will hear something new before long.

I think it's great MU-MIMO is coming. As we add more and more wireless devices, MU-MIMO will be a feature we want to take advantage of.

Is the WRT32x supported or not? Isnt it a WRT3200 just with (whatever) modifcations?

(Last edited by makedir on 30 Mar 2018, 22:29)

There was a couple of kernel bumps, wifi driver, and wifi firmware changes, so I went ahead and built a new image and stuck it out on the server.

r6565 is available now for those who want to upgrade.

kernel 4.14.29
wifi driver 10.3.4.0-20180330
wifi firmware 9.3.2.6

Also there were a couple of requests for packages that were missing that are back.
1. Mini-dlna was added back.
2. Samba was added back.
3. Transmission continues to fail and has not been added back to the fold yet.

Hi David,

Thanks for this:)

First time user of your FW (i think) unning it now on my WRT1900ACS. I've used openwrt before but this build looks really clean, I like it!

I've installed these packages and smbd appears to be running but it doesn't show up under network yet... Any tips?

Okay, got her working, had to add to etc/samba/smb.conf.template
local master = yes
preferred master = yes

(Last edited by Cantenna on 31 Mar 2018, 01:37)

David how do I upgrade without losing the partition with FW stok? I always down your vs. factory and install via linksys webpage, would there be a more practical way to do the luci direct update without losing the linksys partition?

There's a couple ways of doing it... There have been some who have flashed from the partition they are on, but I don't necessarily recommend it. What you can do is just use the advance reboot in LuCi, and boot back over to the factory firmware. From the factory FM use the .img to flash the lede partition. I'm not sure that it will let you do the .bin from the factory FW, but you can try as that will likely keep your settings.