RogerSC wrote:

Just a quick note, 15.05-rc3 does work with my Apple mobile devices, where the final didn't work with them very well. Gives me something that I can play with and learn from.

Interesting.

Indeed.

Both CC 15.05 and RC3 use the same wifi driver.

kop48 wrote:

JW0914 wrote:

I would imagine there will be further updates to CC, especially since it appears a lot of the bugs in CC 15.05 Final are due to the radio drivers.

As far as every single bug, probably not due to everyone not having the same the exact same hardware since the routers were created in batches by Linksys.  It's been hypothesized this is the reason why some have issues others don't.

I'm seeing regular hangs with my router on 15.05 that was not occurring on previous RCs. Is there any information that I can provide to help troubleshoot, or is this a known issue that we just need to wait for new Wi-Fi drivers to fix?

There are some who are having positive results by setting cpu affinity, and cpu performance. See below instructions. Or you can do what I did, and that was to revert back to RC3.

# create a copy of installed packages
opkg list-installed | cut -f 1 -d ' ' > /etc/config/packages.list
# Set the cpu governor to performance (it will allways work on 1.2GHz)
echo performance > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo performance > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
# Set the CPU affinity of the wifi interfces to CPU1 (Core 1)
echo 2 > /proc/irq/`cat /proc/interrupts | grep 'armada_370_xp_irq  59' | cut -f1 -d':' | cut -f2 -d' '`/smp_affinity
echo 2 > /proc/irq/`cat /proc/interrupts | grep 'armada_370_xp_irq  60' | cut -f1 -d':' | cut -f2 -d' '`/smp_affinity
# Increase the amount of reserved memory
echo 16384 > /proc/sys/vm/min_free_kbytes
echo 50 > /proc/sys/vm/vfs_cache_pressure
echo 1 > /proc/sys/vm/swappiness

Yeah, unfortunately the rc3 release has started acting up as well. Took a couple of reboots, but the same familiar behavior with Apple junk.

So it goes.

gufus wrote:

hey @gufus, how'd you get that CPU graph to show in LUCI?

I've configured collectd [I think] to show CPU graphs.
I can see that the checkbox is checked under;  Statistics -> Collectd -> System Plugins -> Processor

But when I look under; Statistics -> Graphs
all I see is; Interfaces and System Load
Nothing for CPU
This seems like a bug in LUCI to me... how did you do it?

PS. I'm running my own-built image.  It is CC 15.05 R47101

wrtpat wrote:

gufus wrote:

hey @gufus, how'd you get that CPU graph to show in LUCI?

I've configured collectd [I think] to show CPU graphs.
I can see that the checkbox is checked under;  Statistics -> Collectd -> System Plugins -> Processor

But when I look under; Statistics -> Graphs
all I see is; Interfaces and System Load
Nothing for CPU
This seems like a bug in LUCI to me... how did you do it?

PS. I'm running my own-built image.  It is CC 15.05 R47101

You need to install collectd-mod-cpu I think

What a long thread.

I just got a wrt1900ac, and bravely flashed the latest snapshot (sep29). After installing luci, thinks work now, with wrt1900ac as WDS AP and and old dir-825 as WDS client. Some issues fought on the way:

- 5ghz channels that required DFS did not work (error in logs: "DFS-CAC-START DFS start_dfs_cac() failed, -1"
- 2.4ghz channel had to be set to "legacy" mode for a few android devices (Galaxy S3, Nexus 7 2012). Both have some bcm4330 chips.

The latter took a lot of time as I started by editing, and then disabling ipv6 support, all the way until tried legacy mode...

Oh, and despite being just bought, it was still and V1 version.

Thanks for your tremendous work.
I am on the 1900 v1 with cc final up and running for 19 days stable now.
Configured as Wireless and WDS AP (separate Firewall Zyxel as Router/modem) , connected with Asus RT56U as WDS Bridge, several clients on Android (HTC M8, Nexus 7 2013, Samsung S3, Asus Transformer) and Windows PC`s, hue lighting, wlan remote control, netatmo weather station and some TV`s, no Apple...IPV6 disabled
Would be glad for a hint how to activate the 5th Lan connector into the switch functionality

br
mark

Here you are:
https://dl.dropboxusercontent.com/u/177 … thread.tar

Untar, copy to /lib and create a symlink named libpthread.so.0 pointing to libpthread-0.9.33.2.so (ln -s libpthread-0.9.33.2.so libpthread.so.0) in the same directory (/lib).

What a long thread.

I just got a wrt1900ac, and bravely flashed the latest snapshot (sep29). After installing luci, thinks work now, with wrt1900ac as WDS AP and and old dir-825 as WDS client. Some issues fought on the way:

- 5ghz channels that required DFS did not work (error in logs: "DFS-CAC-START DFS start_dfs_cac() failed, -1"

Oh, and despite being just bought, it was still and V1 version.

suihkulokki wrote:

What a long thread.

I just got a wrt1900ac, and bravely flashed the latest snapshot (sep29). After installing luci, thinks work now, with wrt1900ac as WDS AP and and old dir-825 as WDS client. Some issues fought on the way:

- 5ghz channels that required DFS did not work (error in logs: "DFS-CAC-START DFS start_dfs_cac() failed, -1"

Oh, and despite being just bought, it was still and V1 version.

I 've experienced the same issue with my WRT1900AC-V2 the 5Ghz channels that require DFS don't work only channels 36, 40, 44 and 48 work. Even when i set the regulatory domain to Russia, which, according to Wikipedia doesn't have DFS-restrictions at all.

When using DD-WRT i'm able to use channels that require DFS, at least when i set the regulatory domain to Poland.

Is this a bug in OpenWRT / WRT1900AC? Or is this something that is done by design?

Nijntje wrote:

suihkulokki wrote:

What a long thread.

I just got a wrt1900ac, and bravely flashed the latest snapshot (sep29). After installing luci, thinks work now, with wrt1900ac as WDS AP and and old dir-825 as WDS client. Some issues fought on the way:

- 5ghz channels that required DFS did not work (error in logs: "DFS-CAC-START DFS start_dfs_cac() failed, -1"

Oh, and despite being just bought, it was still and V1 version.

I 've experienced the same issue with my WRT1900AC-V2 the 5Ghz channels that require DFS don't work only channels 36, 40, 44 and 48 work. Even when i set the regulatory domain to Russia, which, according to Wikipedia doesn't have DFS-restrictions at all.

When using DD-WRT i'm able to use channels that require DFS, at least when i set the regulatory domain to Poland.

Is this a bug in OpenWRT / WRT1900AC? Or is this something that is done by design?

IIRC to utilize DFS it needs to be set to auto

JW0914 wrote:

Nijntje wrote:

I 've experienced the same issue with my WRT1900AC-V2 the 5Ghz channels that require DFS don't work only channels 36, 40, 44 and 48 work. Even when i set the regulatory domain to Russia, which, according to Wikipedia doesn't have DFS-restrictions at all.

When using DD-WRT i'm able to use channels that require DFS, at least when i set the regulatory domain to Poland.

Is this a bug in OpenWRT / WRT1900AC? Or is this something that is done by design?

IIRC to utilize DFS it needs to be set to auto

Okay, so if i understand correctly you're saying (or rather typing) that the WRT1900AC+OpenWRT does support DFS?

When i set channel selection to auto it always defaults to channel 36.

Again, only channels 36, 40, 44 and 48 work those are the channels that do not have DFS-restrictions. I would really like to know if this is a bug since i'm considering returning the unit if this doesn't get fixed.

suihkulokki wrote:

What a long thread.

I just got a wrt1900ac, and bravely flashed the latest snapshot (sep29). After installing luci, thinks work now, with wrt1900ac as WDS AP and and old dir-825 as WDS client. Some issues fought on the way:

- 5ghz channels that required DFS did not work (error in logs: "DFS-CAC-START DFS start_dfs_cac() failed, -1"
- 2.4ghz channel had to be set to "legacy" mode for a few android devices (Galaxy S3, Nexus 7 2012). Both have some bcm4330 chips.

The latter took a lot of time as I started by editing, and then disabling ipv6 support, all the way until tried legacy mode...

Oh, and despite being just bought, it was still and V1 version.

v1 vs v2 stock is determined by the retailers, entirely dependent on how many hundreds/thousands of units they still have left of v1.  An analogy would be what occurred with Axe Kilo deodorant, where Axe stopped production on it over 5 years ago, yet it could still be found in major retailers until about a year ago due to the enormous stock that warehouses had built up.

In regards to the S3 and Nexus 7, both have a wireless N controller, so setting the channel to N [legacy is b/g] should work.  What occurred when you set the channel to N and tried to connect to the router from the Nexus 7 and S3?

I've been monitoring Wifi temperature, and noticed 5Ghz really doesn't heat up the hardware. However, when I ran a report on Wifi Temperature for the past 24 hours I noticed a increase in temperature that lasted until 5am. My wifi and I were asleep, but my daughter couldn't sleep, and was watching various shows over her 2.4Ghz ChromeCast.

2.4Ghz out to devices

Wifi hardware temperature

I think this weekend I'm going to do some wifi download tests (hammer it hard), and see what the temperature does for both 5Ghz and 2.4Ghz.

It just seems wifi hardware heated up a lot just for a tv stream of around 5-6mbps.

Cool, how did you do that? I would like to start a Wiki-page on Openwrt.org on the topic monitoring, but I failed in figuring out how to create such a page  -_-   I think a lot of people could benefit of a central place for stuff like that.

JW0914 wrote:

In regards to the S3 and Nexus 7, both have a wireless N controller, so setting the channel to N [legacy is b/g] should work.  What occurred when you set the channel to N and tried to connect to the router from the Nexus 7 and S3?

It 2.4Ghz new is set to N, They pick up the IP over dhcp, but trying to move a bigger chunk of data (like a typical web page), traffic stops moving completely.

Yesterday I had a few wifi hangups (didn't check if the ethernet still works), so I'll need to open up to wire in the serial..

gaga wrote:

Cool, how did you do that? I would like to start a Wiki-page on Openwrt.org on the topic monitoring, but I failed in figuring out how to create such a page  -_-   I think a lot of people could benefit of a central place for stuff like that.

If you look a page or two back, there's a post that explains how I use Community Edition of HP SiteScope, and gather metrics using SNMP as well as SSH.

There's really not a lot involved to get this working. More familiarity with SiteScope, and how to use it more than anything else. Other than that, installing the snmpd process, and using tools in SiteScope to do a snmpwalk to get the OID's needed for polling.

If you want to go that direction with a wiki, I could take screen shots and basic explanations so you could publish?

davidc502 wrote:

gaga wrote:

Cool, how did you do that? I would like to start a Wiki-page on Openwrt.org on the topic monitoring, but I failed in figuring out how to create such a page  -_-   I think a lot of people could benefit of a central place for stuff like that.

If you look a page or two back, there's a post that explains how I use Community Edition of HP SiteScope, and gather metrics using SNMP as well as SSH.

There's really not a lot involved to get this working. More familiarity with SiteScope, and how to use it more than anything else. Other than that, installing the snmpd process, and using tools in SiteScope to do a snmpwalk to get the OID's needed for polling.

If you want to go that direction with a wiki, I could take screen shots and basic explanations so you could publish?

My bad sorry, I thought it's directly in LuCi as there is actually a plugin that someone got to work with LuCi.

My issue right now is, that I don't know how to create something simple like a page in the openwrt.org howto section to get something started on the whole monitoring topic.