[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

[Markmaster]

Check the first post.....I removed the Download Master code from the firmware. It will be downloaded if/when you decide to install it.

Ok. Thanks. Install. Transfer settings I need with NVRAM Save-Restore Utility and for an hour it is ok. And i am understand, that you wont touch Wi-Fi part, but I still (in Update 7) saw Wi-Fi drain on my Android devices. I switch OFF all from the page Professional, and this wont work. So I switched all this ON and continue to investigate.

Merlin Fork ASUS RT-AC68R 374.43_2-09j9527.

I can see you are running Update 9?

 

[john9527]

Ok. Thanks. Install. Transfer settings I need with NVRAM Save-Restore Utility and for an hour it is ok. And i am understand, that you wont touch Wi-Fi part, but I still (in Update 7) saw Wi-Fi drain on my Android devices. I switch OFF all from the page Professional, and this wont work. So I switched all this ON and continue to investigate.

I really don't know how to go further with respect to any power drain.....if you go back in the thread I dug out my android tablet and tried to recreate a problem but couldn't. Wifi stayed off when it should be off.

I can see you are running Update 9?

Ding...ding...we have a winner of the Observant Award! Coming soon to a theater near you.....

 

[Markmaster]

if you go back in the thread I dug out my android tablet and tried to recreate a problem but couldn't. Wifi stayed off when it should be off.

"Keep Wi-Fi on during sleep" was on what parameter? "Always", "Only when plugged in" or "Never"? If it was on "Never" - I am not excited. We all use always to prevent Cellular data increasing.

Ding...ding...we have a winner of the Observant Award! Coming soon to a theater near you.....

Please don't be rude to me. I am very sensitive.

 

[john9527]

"Keep Wi-Fi on during sleep" was on what parameter? "Always", "Only when plugged in" or "Never"? If it was on "Never" - I am not excited. We all use always to prevent Cellular data increasing.

I'm not sure how to go about trying to see changes with setting Always. I guess I would have to run another firmware stream for a couple of days to get a baseline. Do you have a recommended level?

Please don't be rude to me. I am very sensitive.

I apologize if you viewed this badly.....it was actually a complement on your powers of observation.

 

[Markmaster]

Do you have a recommended level?

Recommended level of what? I am sorry can't get the point.
I use "Always", because of notifications, updates at home, because I think it is right. THere was a time, then Texas Instruments was a SoC maker for mobile phones. I got Galaxy Nexus with TI chip. I was very impressed, that I was never saw Wi-Fi in my battery graphic but still get all notifications and power. After that all this Qualcomm and Exynos and Wi-Fi is became more visible. But not the drain expander.
Does your tablet has root?

 

[john9527]

Recommended level of what? I am sorry can't get the point.

You had stated that the fork drains faster.....faster than which level? Do you have a level of code that you have used that behaves the way you would like that I could use to baseline the battery life?

Does your tablet has root?

Yes...but fair warning.....I'm definitely not well versed on android.

 

[Markmaster]

faster than which level?

From update 5 if I am remember correct.

Do you have a level of code that you have used that behaves the way you would like that I could use to baseline the battery life?

All day lay on the desk. This is all about it's background activity.

I'm definitely not well versed on android.

For example use https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector&hl=en , run the app, ansver positive when it asks you for root rights and keep it in background. Simple press Home button. In settings just confirm "Advanced Mode" and "Statistics from unplug".
Interface is very simple. You can switch between different type of wakelocks (Screen, CPU, Wakeup Triggers and Kernel Wakelock). We are interesting in this, Kernel wakelock only. I can see a lot of wlan_rx_wake and wlan_wd_wake here. Something in router prevent phones from deep sleep. Using "Enable WMM APSD" not helping at all. Flags that router distribute to this device are PSTAU, so the powersave mode should be enabled. Why the things going in that way they go I don't know.

 

[Builder71]

19th March a new OpenSSL release.

https://mta.openssl.org/pipermail/openssl-announce/2015-March/000020.html

"They will fix a number of security defects.
The highest severity defect fixed by these releases is classified as "high" severity."

 

[Gunner84]

What is the download master code for which you left out of your recent update.

Is it an optional extra or do I need it?

thankyou

 

[john9527]

What is the download master code for which you left out of your recent update.

Is it an optional extra or do I need it?

thankyou

Optional extra....Download Master is a download manager/bittorrent client that runs on the router.

 

[john9527]

19th March a new OpenSSL release.

https://mta.openssl.org/pipermail/openssl-announce/2015-March/000020.html

"They will fix a number of security defects.
The highest severity defect fixed by these releases is classified as "high" severity."

Sigh....saw that yesterday as I was about to formally post the V09 update.

So rather than post two formal updates, probably just days a part , here's what I did. (Posting a new update really does generate a flurry of activity)

I set up a new download location 'FixRelease' where I'll be posting any fixes in between formal releases. The code there will contain tested fixes, and is release level (not a beta). Right now, Update-09 is loaded there.

FixRelease download: Update-09
http://1drv.ms/1xeeBvS

If you have had any of the problems reported on V08 for which I've acknowledged a fix

- new Repeater mode wireless settings not working
- duplicate DHCP leases
- cannot apply DDNS settings

(or if you just want the latest, knowing another update may come soon) you can get the latest code there.

I hope this works for everyone.....If you have any feedback, please feel free

 

[Deleted member 22229]

John does ver9 contain the open ssl fix i did not see it in the change log. Also any need for factory reset or reboot after the flash to Ver-9 ?

 

[john9527]

John does ver9 contain the open ssl fix i did not see it in the change log. Also any need for factory reset or reboot after the flash to Ver-9 ?

No, the OpenSSL fix isn't going to be released until Friday.....hence my quandary....

No factory reset required moving between fork levels.

 

[Builder71]

I fixed the showwebmon.sh script.
If you wanted to use the option to exclude the year, it didn't work.

--deleted--

Crap, still doesn't work, I'll try again.

 

[john9527]

I fixed the showwebmon.sh script.
If you wanted to use the option to exclude the year, it didn't work.

--deleted--

Crap, still doesn't work, I'll try again.

I know I tested the exclude year. I wonder if there is a slight difference in the ARM vs MIPS output? Can you post the output from the 'regular' run?

 

[Builder71]

I know I tested the exclude year. I wonder if there is a slight difference in the ARM vs MIPS output? Can you post the output from the 'regular' run?

Sure:

Wed Mar 18 18:23:19 MEZ 2015    10.0.0.207      afs.moatads.com
Wed Mar 18 18:23:34 MEZ 2015    10.0.0.207      adrta.com
Wed Mar 18 18:24:04 MEZ 2015    10.0.0.207      api.buienradar.nl
Wed Mar 18 18:24:04 MEZ 2015    10.0.0.207      gadget.buienradar.nl

The exclude year line is weird.
You expect something like this:

date +"%a %b %d %T %Z"

It seems like it's doing nothing.
You can comment out both webdate lines and still get the same output.

Only the line:

webdate=$(date -d @$webdate)  # convert epoch

seems to work and does the convert action.

 

[Gravityz]

Hi John,
you are probably right about the 2.4Ghz.
The signal at 80mW is pretty good so bumping it up to 200Mw might give me better range but not so much a very higher signal at closer range.

regarding the measurement
i am using a jailbreaked Iphone 3GS with WiFi analyzer on it.

great tool and it has a 1% resolution so pretty accurate.

A couple of ideas here....

First, the 2.4GHz band is pretty robust as far as coverage at lower levels. I've seen similar results when I've done some measurements (I was easier to see reducing power than increasing it when I had a good signal to begin with).

Also, you don't say what your 'percent' measures are (I'm assuming they are something on the client). It possible that the minimum resolution is in 5% increments, so you could be going from 68% to 77% (assuming normal rounding) and have it reported as 70% to 75%.

 

[john9527]

The exclude year line is weird.
You expect something like this:
date +"%a %b %d %T %Z"

Easy answer (it's that US mindset again....I'm sorry)....

My time is reported in GMT.....yours is MEZ (German World Time).....change GMT to MEZ in the script.

 

[Builder71]

Easy answer (it's that US mindset again....I'm sorry)....

My time is reported in GMT.....yours is MEZ (German World Time).....change GMT to MEZ in the script.

Sjeezzz, WHY didn't I see this?
That works.

 

[KGB7]

From update 5 if I am remember correct.

All day lay on the desk. This is all about it's background activity.

For example use https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector&hl=en , run the app, ansver positive when it asks you for root rights and keep it in background. Simple press Home button. In settings just confirm "Advanced Mode" and "Statistics from unplug".
Interface is very simple. You can switch between different type of wakelocks (Screen, CPU, Wakeup Triggers and Kernel Wakelock). We are interesting in this, Kernel wakelock only. I can see a lot of wlan_rx_wake and wlan_wd_wake here. Something in router prevent phones from deep sleep. Using "Enable WMM APSD" not helping at all. Flags that router distribute to this device are PSTAU, so the powersave mode should be enabled. Why the things going in that way they go I don't know.

The app doesnt work for everyone, read the reviews.

Wakelock issue is android issue, an issue that has been around since 2.4. It could also be an app flaw, an app that is NOT made by Google.

If you running custom firmware, then talk to the firmware maker about the wakelock issue, or switch to another custom firmware.