OpenWrt Forum Archive

Topic: Update on Linksys WRT1900AC support

The content of this topic has been archived between 16 Sep 2014 and 7 May 2018. Unfortunately there are posts – most likely complete pages – missing.

@leitec

Your solution was correct, it finished building without errors. You might want to upload the diff to trunk.

nitroshift

Trunk is not about jumping to the newest kernel. As you may have noticed, it's been on 3.14 for a while, and 3.18 for now. OpenWrt seems to align with the LTS kernels - which at the time of writing are 3.10, 3.12 and 3.14. And I guess 3.18 will be one as well.

Any advice on which firmware to use when using lot of iOS devices? My iPhone 5s running 8.1.3 doesn't really have a reliable wifi connection in combination with the latesy stock firmware.

Go easy lads - newish to openwrt & not a programmer....

First, let me say McWrt is great - worked smoothly for all the basics straight after install.
@Chadster766 outstanding work with this mate - really appreciate your time & effort.

I've spent the last week searching topics - scouring Youtube and trying to decipher forums for info on how to actually configure & use packages once they've been downloaded and running (installing them was the easy part)....I'm only posting on the forum as I'm at my wits end & cant find the right info.

Would anyone mind guiding me here a little please? Just a few links and advice on direction is all I'm chasing....Is everything command line configuration once a package is installed? No gui on installed packages? ....or do I need to connect to another address to find a gui on a package?

All im trying to do is 3 specific things concerning wi-fi.....1) turn off 5G, 2) reduce the power on 2.4....& 3) turn the external WPS button into an external wi-fi on/off switch.

(Before advising to disable 5G in the interface, I did this but its remains up & running no matter what)

Thanks in advance....

Anyone using latest trunk snapshot and have usb drive working? I attached a hd to usb3 port and I can see the info from block info.

root@OpenWrt:/dev# block info
/dev/ubiblock0_0: UUID="8c673249-a914013e-9d6583b8-d187534c" VERSION="1024.0" TYPE="squashfs"
/dev/ubi0_0: UUID="8c673249-a914013e-9d6583b8-d187534c" VERSION="1024.0" TYPE="squashfs"
/dev/ubi0_1: UUID="01c96d15-0d85-47ca-bcff-62905ad53fdd" VERSION="w4r0" TYPE="ubifs"
/dev/ubi1_0: UUID="70267c6f-07f2-49d1-a3cc-7989602d777f" VERSION="w4r0" TYPE="ubifs"
/dev/ubiblock0_0: UUID="8c673249-a914013e-9d6583b8-d187534c" VERSION="1024.0" TYPE="squashfs"
/dev/sda1: UUID="3017ac12-36b3-4349-bbae-b109dfb7befc" LABEL="ExtFS" NAME="EXT_JOURNAL" VERSION="1.0" TYPE="ext4"

However, when I try to mount, it failed.

root@OpenWrt:/dev# block mount
block: /dev/ubi0_1 is already mounted
block: mounting /dev/sda1 (ext4) as /mnt/sda1 failed (-1) - Unknown error -1

I do have kmod_fs_ext4 installed. I also tried mount command.

root@OpenWrt:/dev# mount -t ext4 /dev/sda1 /mnt/sda1 -o rw,sync
mount: mounting /dev/sda1 on /mnt/sda1 failed: No such device

It complains no such device but I do see it's there.

Anyone know what the issue is?

@LogicoZone   I am having the same issue ... driving me nuts as i've been through ever wiki and faqs page.  I know I'm aline noob but this is driving me bonkers

@LogicoZone & craig.reiners

I'm using an e-SATA HDD and I don't have any issues. That's just to narrow down to the USB modules.

nitroshift

SaberOne wrote:

Any advice on which firmware to use when using lot of iOS devices? My iPhone 5s running 8.1.3 doesn't really have a reliable wifi connection in combination with the latesy stock firmware.

@SaberOne

Linksys close-sourced the latest firmware driver, so we've actually got no idea what it contains now.

PRIOR to that it was using the same driver as found in McWRT, which historically (both in previous stock Linksys and McWRT) has been the most stable for WiFi, even with Apple devices.

The McWRT image is here (save to your computer then do a manual firmware update from stock):
https://github.com/Chadster766/McWRT/re … 2-128k.img

Note, however, that Apple devices have known issues with Wifi and this is a general problem, not just restricted to the WRT1900AC.


While the above build has historically been the best one, one user reported that a recent trunk (development) image was the best yet for Wifi (although not known whether that's specifically with Apple devices).  However, trunk right now requires you to manually set up the Luci GUI and networking from the command line, which may or may not appeal to you.  Various members on here compile snapshots periodically with the GUI and networking already "baked in" and ready to go, so you may wish to wait until someone posts something on here.

Otherwise right now you could try McWRT as detailed above.

Aerogeek wrote:

Go easy lads - newish to openwrt & not a programmer....

First, let me say McWrt is great - worked smoothly for all the basics straight after install.
@Chadster766 outstanding work with this mate - really appreciate your time & effort.

I've spent the last week searching topics - scouring Youtube and trying to decipher forums for info on how to actually configure & use packages once they've been downloaded and running (installing them was the easy part)....I'm only posting on the forum as I'm at my wits end & cant find the right info.

Would anyone mind guiding me here a little please? Just a few links and advice on direction is all I'm chasing....Is everything command line configuration once a package is installed? No gui on installed packages? ....or do I need to connect to another address to find a gui on a package?

Generally if you've installed a package then the functionality will be there.  You MIGHT need to do a re-boot to get it fully working, and there MIGHT NOT be a GUI interface for it - you might need to install a luci-app-<package> to give you graphical control over the package (and sometimes might need to re-boot to get the changes to show in the GUI).

The above all said, two of your three requests below can be done from the standard GUI without any further packages being installed.


Aerogeek wrote:

All im trying to do is 3 specific things concerning wi-fi.....1) turn off 5G, 2) reduce the power on 2.4....& 3) turn the external WPS button into an external wi-fi on/off switch.

(Before advising to disable 5G in the interface, I did this but its remains up & running no matter what)

Thanks in advance....

Preliminary:
The McWRT gui is accessed by typing 192.168.200.1 into a web browser.  This should bring up the login screen.  Hopefully you've already changed the root password - if not then please do so!

1) turn off 5G
I'm not running McWRT any more so can't tell you exactly where to find, but something like Network -> Wifi will bring you into the WiFi settings.  Turning off 5G should be as easy as clicking "disable" on the second radio.  You might then need to click "save and apply" at the bottom of the screen.

2) reduce the power on 2.4
Can't remember if there is an option for this in McWRT?  In any case you again want to go into Network -> Wifi and then click Edit for the first radio.  There's a transmit power dropdown in later (CC, as opposed to McWRT's AA) builds that you can adjust downwards.  Do so, then again try "save and apply".  (My apologies if this option isn't in McWRT AA - as I said I'm working in the dark as I'm on CC now having run McWRT for four months.)

3) turn the external WPS button into an external wi-fi on/off switch.
I have no idea if this is possible.  I'm doubtful if functionality for this is present at all by default.  It may or may not be possible for someone to add this.  Perhaps others with greater knowledge can respond.

DavidMcWRT wrote:
SaberOne wrote:

Any advice on which firmware to use when using lot of iOS devices? My iPhone 5s running 8.1.3 doesn't really have a reliable wifi connection in combination with the latesy stock firmware.

@SaberOne

Linksys close-sourced the latest firmware driver, so we've actually got no idea what it contains now.

PRIOR to that it was using the same driver as found in McWRT, which historically (both in previous stock Linksys and McWRT) has been the most stable for WiFi, even with Apple devices.

The McWRT image is here (save to your computer then do a manual firmware update from stock):
https://github.com/Chadster766/McWRT/re … 2-128k.img

Note, however, that Apple devices have known issues with Wifi and this is a general problem, not just restricted to the WRT1900AC.


While the above build has historically been the best one, one user reported that a recent trunk (development) image was the best yet for Wifi (although not known whether that's specifically with Apple devices).  However, trunk right now requires you to manually set up the Luci GUI and networking from the command line, which may or may not appeal to you.  Various members on here compile snapshots periodically with the GUI and networking already "baked in" and ready to go, so you may wish to wait until someone posts something on here.

Otherwise right now you could try McWRT as detailed above.

Just to give an update. I flashed the latest trunk yesterday morning and configure the wifi from scratch.

In my house, it's a big apple shop that we have at least a dozen apple devices. In short, latest trunk image from yesterday with kernel 3.18.5 does not bring any stability for apple devices. Constantly, the connection is dropped despite it shows still connected. WiFi has to turned off an back on from device to get back online (again, not always work).

Within about 24 hours of testing, I experienced issue on iphone, mackbook pro, macbook pro retina and macbook air.

I rolled back to latest McWRT 1.0.8 for now since it offers stability I need with apple devices.

DavidMcWRT wrote:
SaberOne wrote:

Any advice on which firmware to use when using lot of iOS devices? My iPhone 5s running 8.1.3 doesn't really have a reliable wifi connection in combination with the latesy stock firmware.

@SaberOne

Linksys close-sourced the latest firmware driver, so we've actually got no idea what it contains now.

PRIOR to that it was using the same driver as found in McWRT, which historically (both in previous stock Linksys and McWRT) has been the most stable for WiFi, even with Apple devices.

The McWRT image is here (save to your computer then do a manual firmware update from stock):
https://github.com/Chadster766/McWRT/re … 2-128k.img

Note, however, that Apple devices have known issues with Wifi and this is a general problem, not just restricted to the WRT1900AC.


While the above build has historically been the best one, one user reported that a recent trunk (development) image was the best yet for Wifi (although not known whether that's specifically with Apple devices).  However, trunk right now requires you to manually set up the Luci GUI and networking from the command line, which may or may not appeal to you.  Various members on here compile snapshots periodically with the GUI and networking already "baked in" and ready to go, so you may wish to wait until someone posts something on here.

Otherwise right now you could try McWRT as detailed above.

Is there any limitations to the sysupgrade. I was thinking of flashing Kaloz build and using the system upgrade feature from here: https://downloads.openwrt.org/snapshots … u/generic/ , in about a week or so, just to see how things are progressing.

LogicoZone wrote:

Just to give an update. I flashed the latest trunk yesterday morning and configure the wifi from scratch.

In my house, it's a big apple shop that we have at least a dozen apple devices. In short, latest trunk image from yesterday with kernel 3.18.5 does not bring any stability for apple devices. Constantly, the connection is dropped despite it shows still connected. WiFi has to turned off an back on from device to get back online (again, not always work).

Within about 24 hours of testing, I experienced issue on iphone, mackbook pro, macbook pro retina and macbook air.

I rolled back to latest McWRT 1.0.8 for now since it offers stability I need with apple devices.

Did you try the following possible fix when running trunk?:

root@wrt1900ac:~# uci set wireless.@wifi-iface[0].disassoc_low_ack=0
root@wrt1900ac:~# uci set wireless.@wifi-iface[1].disassoc_low_ack=0
root@wrt1900ac:~# uci commit
root@wrt1900ac:~# wifi


EDIT: PS, thank you for the update notes!

(Last edited by DavidMcWRT on 5 Feb 2015, 23:15)

mojolacerator wrote:
DavidMcWRT wrote:
SaberOne wrote:

Any advice on which firmware to use when using lot of iOS devices? My iPhone 5s running 8.1.3 doesn't really have a reliable wifi connection in combination with the latesy stock firmware.

@SaberOne

Linksys close-sourced the latest firmware driver, so we've actually got no idea what it contains now.

PRIOR to that it was using the same driver as found in McWRT, which historically (both in previous stock Linksys and McWRT) has been the most stable for WiFi, even with Apple devices.

The McWRT image is here (save to your computer then do a manual firmware update from stock):
https://github.com/Chadster766/McWRT/re … 2-128k.img

Note, however, that Apple devices have known issues with Wifi and this is a general problem, not just restricted to the WRT1900AC.


While the above build has historically been the best one, one user reported that a recent trunk (development) image was the best yet for Wifi (although not known whether that's specifically with Apple devices).  However, trunk right now requires you to manually set up the Luci GUI and networking from the command line, which may or may not appeal to you.  Various members on here compile snapshots periodically with the GUI and networking already "baked in" and ready to go, so you may wish to wait until someone posts something on here.

Otherwise right now you could try McWRT as detailed above.

Is there any limitations to the sysupgrade. I was thinking of flashing Kaloz build and using the system upgrade feature from here: https://downloads.openwrt.org/snapshots … u/generic/ , in about a week or so, just to see how things are progressing.

should be OK.  Note that while settings should be retained, any packages manually installed will need to be re-installed - as will the GUI/networking.

(Last edited by DavidMcWRT on 5 Feb 2015, 23:14)

DavidMcWRT wrote:

Did you try the following possible fix when running trunk?:

root@wrt1900ac:~# uci set wireless.@wifi-iface[0].disassoc_low_ack=0
root@wrt1900ac:~# uci set wireless.@wifi-iface[1].disassoc_low_ack=0
root@wrt1900ac:~# uci commit
root@wrt1900ac:~# wifi


EDIT: PS, thank you for the update notes!

Yes. this is first thing I tried. As said in my earlier post, this seems not helping my case.

DavidMcWRT wrote:
mojolacerator wrote:
DavidMcWRT wrote:

@SaberOne

Linksys close-sourced the latest firmware driver, so we've actually got no idea what it contains now.

PRIOR to that it was using the same driver as found in McWRT, which historically (both in previous stock Linksys and McWRT) has been the most stable for WiFi, even with Apple devices.

The McWRT image is here (save to your computer then do a manual firmware update from stock):
https://github.com/Chadster766/McWRT/re … 2-128k.img

Note, however, that Apple devices have known issues with Wifi and this is a general problem, not just restricted to the WRT1900AC.


While the above build has historically been the best one, one user reported that a recent trunk (development) image was the best yet for Wifi (although not known whether that's specifically with Apple devices).  However, trunk right now requires you to manually set up the Luci GUI and networking from the command line, which may or may not appeal to you.  Various members on here compile snapshots periodically with the GUI and networking already "baked in" and ready to go, so you may wish to wait until someone posts something on here.

Otherwise right now you could try McWRT as detailed above.

Is there any limitations to the sysupgrade. I was thinking of flashing Kaloz build and using the system upgrade feature from here: https://downloads.openwrt.org/snapshots … u/generic/ , in about a week or so, just to see how things are progressing.

should be OK.  Note that while settings should be retained, any packages manually installed will need to be re-installed - as will the GUI/networking.

ok, tx.

Anyone having issue that router reboot itself when copying large files from attached HD on USB3 via samba share? This is happening on McWRT 1.0.8.

I had issue before but not quite certain. Today, I tried to copy 4GB files via SAMBA share and i lost connection and router rebooted. This is via wifi.

Then, I tried again with ethernet connection for same files. It barely finished then rebooted. Seems always happening when copy large files over Samba share.

LogicoZone wrote:
DavidMcWRT wrote:

Did you try the following possible fix when running trunk?:

root@wrt1900ac:~# uci set wireless.@wifi-iface[0].disassoc_low_ack=0
root@wrt1900ac:~# uci set wireless.@wifi-iface[1].disassoc_low_ack=0
root@wrt1900ac:~# uci commit
root@wrt1900ac:~# wifi


EDIT: PS, thank you for the update notes!

Yes. this is first thing I tried. As said in my earlier post, this seems not helping my case.

Apologies I missed that in your post.  Thanks for confirming you tried it.

@DavidMcWRT

Linksys did NOT close the sources on the latest driver, if they did it couldn't have been ported to OpenWRT!

nitroshift

(Last edited by nitroshift on 6 Feb 2015, 07:10)

I'm a bit perplexed and hoping someone might be able to offer insight into what I'm missing here... I'm attempting to get extroot working on a 256GB [PNY] USB 3 stick and am running into an issue with getting pivot overlay to work.

FW: Kaloz's 20150128
OpenWrt Chaos Calmer r44181 / LuCI Master (git-14.359.33351-5e6c33e)
Kernel: 3.18.3

The problem appears to be in the fstab config file, as if I use "cat /etc/config/fstab" I see the changes I've made have been successfully saved; but when I use "block detect" I see  the config file without the changes I've made, preventing the sda1 partition from being auto mounted to /overlay (I can manually mount it via "mount /dev/sda1 /overlay" successfully).

I've tried every variation of options within http://wiki.openwrt.org/doc/howto/extroot as well as options suggested on other sites with nothing working... so my first question is am I doing something wrong or overlooking a step that maybe isn't listed?

I've included a screenshot via OneDrive of the command output of the cat and block commands.  If more information is required from me, please let me know.

Screenshot: http://1drv.ms/1AyNhZH

EDIT: I have tried three different options for the option targets: without uuid, with uuid, and with both uuid and device path; as well as trying delay_root at 0, 5, 15, & 20.

(Last edited by JW0914 on 6 Feb 2015, 08:23)

@JW0914

After altering the fstab file you *need* to restart the router or

/etc/fstab reload

nitroshift

nitroshift wrote:

@JW0914

After altering the fstab file you *need* to restart the router or

/etc/fstab reload

nitroshift

It's not possible to give fstab commands because it's been depreciated by block; attempting to issue commands such as "/etc/fstab reload", "/etc/init.d/fstab restart", "/etc/init.d/fstab start", etc. all return a "not found" error.

Restarting had no effect on the extroot /overlay partition.  Once the router boots back up, it mounts sda1 back to /mnt/sda1 under mounted filesystems even though the mount point of the sda1 mounts list lists it as "/overlay".

There's something occurring with how the fstab config file is being applied on the block backend, as it's not applying the fstab config file to the config file block is using... and it's not just mount points, if I change the delay_root from the default of 5 to any other value in the fstab config file, it does not change in the block configuration (via "block detail") before a reboot by using "block umount"/"block mount" or following a reboot.  However, there's no issue with manually mounting it regardless of which way you configure the fstab config file.

The only way around this I've found is to add the manual mount command to the startup command section.

EDIT: This issue only affects an external partition that's attempting to mount as the /overlay mount point... all other external partitions mount fine, as does an external swap partition.  One user did report that with barrier breaker you must use uuids in the fstab config file, however both times I've tried using just uuids renders the Mount Point LuCI page inoperable with a line error at line 11 (sda1's uuid), as well as makes the fstab config file read only.

(Last edited by JW0914 on 6 Feb 2015, 10:45)

nitroshift wrote:

@DavidMcWRT

Linksys did NOT close the sources on the latest driver, if they did it couldn't have been ported to OpenWRT!

nitroshift

Thanks for the clarification, that makes sense,  I was getting more confused then usual.

nitroshift wrote:

@DavidMcWRT

Linksys did NOT close the sources on the latest driver, if they did it couldn't have been ported to OpenWRT!

nitroshift

For the latest official stock firmware:

* .c files were removed from the GPL release
* the license was changed from GPL to proprietary in the .h files

That's close-sourcing to me!!

In addition:

* the stock change log indicated new driver software - but due to the above we don't know that exactly it is!

Now, given that some people have been reporting poor wifi with the latest stock, the latest stock might be the (same as the) new Marvell Open Source driver code - but why would they then make the stock version proprietary?

LogicoZone wrote:

Anyone having issue that router reboot itself when copying large files from attached HD on USB3 via samba share? This is happening on McWRT 1.0.8.

I had issue before but not quite certain. Today, I tried to copy 4GB files via SAMBA share and i lost connection and router rebooted. This is via wifi.

Then, I tried again with ethernet connection for same files. It barely finished then rebooted. Seems always happening when copy large files over Samba share.

Yes, i had similar issues with both 1.0.5 and 1.0.8. Happens when copying large amount of data to my 4TB Ext4 drive. Not rebooting, but going completely dumb. All connections going down, luci not working, cant log on via ssh, but the leds are still on. Must switch of and on manually to restart the router. I posted the issue here, but haven't received any reply.

LogicoZone wrote:
DavidMcWRT wrote:

Did you try the following possible fix when running trunk?:

root@wrt1900ac:~# uci set wireless.@wifi-iface[0].disassoc_low_ack=0
root@wrt1900ac:~# uci set wireless.@wifi-iface[1].disassoc_low_ack=0
root@wrt1900ac:~# uci commit
root@wrt1900ac:~# wifi


EDIT: PS, thank you for the update notes!

Yes. this is first thing I tried. As said in my earlier post, this seems not helping my case.

I can confirm this wasn't helpful in my situation either - My MacBook Pro Early 2011 would connect to any of 2 wifi but no Internet connection and won't see local NAS. Though IpHone and iPad and iMac have no issues at all.

Sorry, posts 2876 to 2875 are missing from our archive.