OpenWrt Forum Archive

Topic: davidc502 1900ac 3200acm builds

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

starcms wrote:
davidc502 wrote:

I've been using adguard, and they remove the ads, so I haven't had to maintain anything myself. So, it can be a pain from a wife perspective when she wants to see an ad.

Adguard?  Did you mean to say adblock (as in what's included in your builds)?

Download the .csv from dnscrypt... It lists the DNS servers that can be connected to using dnscrypt.  There's a couple of adguard dns servers you can connect to that works really well to block ads at the dns layer.

https://download.dnscrypt.org/dnscrypt- … olvers.csv

davidc502 wrote:
starcms wrote:
davidc502 wrote:

I've been using adguard, and they remove the ads, so I haven't had to maintain anything myself. So, it can be a pain from a wife perspective when she wants to see an ad.

Adguard?  Did you mean to say adblock (as in what's included in your builds)?

Download the .csv from dnscrypt... It lists the DNS servers that can be connected to using dnscrypt.  There's a couple of adguard dns servers you can connect to that works really well to block ads at the dns layer.

https://download.dnscrypt.org/dnscrypt- … olvers.csv

Hey, I'm the one that gave u that link!  wink  Now I know what u meant.  Couldn't figure out the association between ad blocking and dnscrypt-proxy.  Spent too much of my brain power writing those SSL cert instructions.

Edit: Personally I prefer to use Adblock for the ads, and dnscrypt for protection.  Keep the two separate.  Because if you choose the adguard resolvers for dnscrypt a) you can't make a whitelist and b) they don't support DNSSEC and c) their pings may not be good depending on your location.

My personally favorite resolvers are the ones that begin with d0wn.  They support DNSSEC and no logging, have dozens of servers to choose from all around the world (to find one close to you that has a decent ping), and a nifty website (https://dns.d0wn.biz) where you can check on the status of the multiple servers they have.  Just make sure you are using the updated dnscrypt-resolvers.csv file, or it only lists about 5 of them instead of closer to about 30, and the few they list have out of date keys.  You can use this link to test your DNSSEC status (which will only be positive if you are using dnscrypt with a resolver that supports DNSSEC as well)  http://dnssec.vs.uni-due.de/

(Last edited by starcms on 24 May 2017, 20:40)

davidc502 wrote:
mariano.silva wrote:
starcms wrote:

Sick of those SSL/https warnings every time you visit LuCi?  I finally figured out how to solve it.  First I had it working for all browsers except Chrome (which is the one I care about lol), until I discovered that starting with Chrome version 58, it not only looks at the CN (common name) in the certificate, but also at SAN (subject alt name or DNS name).

19) Enjoy smile

MAN! You're a genius! I'm saving this post for the posterity smile

+1 ^^^

@starcms , can you make your post a Wiki entry in the LEDE project? Lots of people keep asking for the same over there all the time...

mariano.silva wrote:
davidc502 wrote:
mariano.silva wrote:

MAN! You're a genius! I'm saving this post for the posterity smile

+1 ^^^

@starcms , can you make your post a Wiki entry in the LEDE project? Lots of people keep asking for the same over there all the time...

Never made a wiki entry before.  Feel free to do one, just give @StarCMS credit wink

Edit:  Took me long enough to type up those instructions in the first place, not to mention figuring it out in the out to begin with lol big_smile

Edit2: If you do one, just make sure you state the pre-reqs are to have openssl (libopenssl, openssl-util) and luci-app-uhttpd installed (which are included in @david's builds)

(Last edited by starcms on 25 May 2017, 05:24)

starcms wrote:
mariano.silva wrote:
davidc502 wrote:

+1 ^^^

@starcms , can you make your post a Wiki entry in the LEDE project? Lots of people keep asking for the same over there all the time...

Never made a wiki entry before.  Feel free to do one, just give @StarCMS credit wink

Edit:  Took me long enough to type up those instructions in the first place, not to mention figuring it out in the out to begin with lol big_smile

Edit2: If you do one, just make sure you state the pre-reqs are to have openssl (libopenssl, openssl-util) and luci-app-uhttpd installed (which are included in @david's builds)

Just did it! smile  Take a look at the results, make any changes you feel are needed ... and I guess the community will chime in as well now ...

https://lede-project.org/inbox/getting- … e-warnings

mariano.silva wrote:
starcms wrote:
mariano.silva wrote:

@starcms , can you make your post a Wiki entry in the LEDE project? Lots of people keep asking for the same over there all the time...

Never made a wiki entry before.  Feel free to do one, just give @StarCMS credit wink

Edit:  Took me long enough to type up those instructions in the first place, not to mention figuring it out in the out to begin with lol big_smile

Edit2: If you do one, just make sure you state the pre-reqs are to have openssl (libopenssl, openssl-util) and luci-app-uhttpd installed (which are included in @david's builds)

Just did it! smile  Take a look at the results, make any changes you feel are needed ... and I guess the community will chime in as well now ...

https://lede-project.org/inbox/getting- … e-warnings

@mariano, I just one correction and one suggestion to your thread here, https://forum.lede-project.org/t/how-to … age/3939/, where we can keep discussion to keep this thread from going off topic.

It looks great BTW!!

(Last edited by starcms on 26 May 2017, 03:22)

Looks good -- Great Job

davidc502 wrote:
starcms wrote:
davidc502 wrote:

Thanks for bringing it to my attention about the.bin and .img files, as they were swapped incorrectly, but have now been fixed.

Keep in mind for those who want to flash again... As the LuCi gui will likely complain and not let you flash, you will need to use the sysupgrade command.

If one is doing sysupgrade, choose the .img if you want to complete erase the firmware and replace it with a new image. Use the .bin file to upgrade the current image. 
...

@david, I haven't had a single issue in months upgrading from your build to @cybrnook's builds and back, and upgrading your build on-top of itself in LuCi using the sysupgrade.bin file.  As long as I was on LEDE and not OpenWRT, everything has been fine.

What do you mean the .bin and .img files were swapped incorrectly?  The sysupgrade.bin has always been the smaller of the two and they have been named correctly.

I had them swapped on the faq page where it explains in what situation to use them in.


There seems to still be a little confusion here, in the example:

2. What's the difference between images ending with .img and .bin?

a .img is used to flash from a browser.
b .bin is used to flash from a SSH terminal. 
Example command using SSH: "sysupgrade /tmp/imageName.img" OR "sysupgrade http://webLocationOfImage.img" 

but, it might be me.

.img can be flashed from SSH too.

nitroshift

Yes, in the example SSH command, it shows file ending in .img instead of .bin.

.bin can also be used to upgrade from LuCi (browser) also.

Edit:  Maybe it should say

2. What's the difference between images ending with .img and .bin?

a .img is used to originally flash LEDE from a browser if coming from stock Linksys firmware.
b .bin is used for upgrading if already running LEDE: either from a browser (LuCi) or from a SSH terminal.
Example command using SSH: "sysupgrade /tmp/imageName.bin" OR "sysupgrade http://webLocationOfImage.bin"
c. If currently running LEDE, .img can also be used from SSH for a completely fresh start.  
This is not normally needed, except possibly if you are changing distros (i.e. going from official LEDE to @david's build).

Edit2: And on the Downloads page, I'd recommend putting 1200AC Version 1 or 2 (like how it is for the 1900ACS).

(Last edited by starcms on 26 May 2017, 07:53)

There was a commit 6 months ago or so that IMHO has screwed the flashing process by LuCi up.  Sometimes flashing using .bin works, and other times it doesn't. We used to be able to flash with LuCi using .img, but now that never works (From Stock to Lede works). So, most of the times I end up needing to sysupgrade -F from command line.


BTW -- No issues putting this on the site if most think this makes the most sense?

2. What's the difference between images ending with .img and .bin?

a .img is used to originally flash LEDE from a browser if coming from stock Linksys firmware.
b .bin is used for upgrading if already running LEDE: either from a browser (LuCi) or from a SSH terminal.
Example command using SSH: "sysupgrade /tmp/imageName.bin" OR "sysupgrade http://webLocationOfImage.bin"
c. If currently running LEDE, .img can also be used from SSH for a completely fresh start.  
This is not normally needed, except possibly if you are changing distros (i.e. going from official LEDE to @david's build).

(Last edited by davidc502 on 26 May 2017, 15:46)

I know, completely off topic, but my ISP (Cox Cable), just gave me a promotion.  Their ultimate 300/30 plan for $8 less than the regular price of my 50/5 plan.  For a whole year! w00t!  I can't quite reach 300mbps because my DOCSIS 3.0 modem is only 8x4 (they recommend 16x4 for their ultimate plan), but I'm not complaining!  This is over WiFi too with SQM nicely set up.

http://www.dslreports.com/speedtest/15870318.png

My 50/5 plan is normally $78 (with my previous promotion it was $63 for the past year), 150/10 plan is $88, 300/30 plan is $100.  I got it for $70 big_smile

Edit: One question, when I set SQM up for the downstream (I put 250000), it lowered my download speed to less than 175mbps.  Can SQM simply not handle speeds that fast?  Luckily, I don't get bad bufferbloat on downstream at all, so I set it to 0 and set upstream to 32000.  Using piece_of_cake.  As you can see, I scored an A in the test above for bufferbloat.  Upstream is what is bad without using SQM (at least for me anyway).

Edit2: On my desktop which is connected via Cat5, max download is 275mbps.  Earlier WiFi results are damn good (and my DOCSIS3.0 8x4 modem too) if I may say so!  Definitely don't plan on buying a new cable modem until I figure out if Cox is going to roll out DOCSIS 3.1 or FTTH in my area.

(Last edited by starcms on 26 May 2017, 23:49)

I leave the downstream set to 0 (disabled) as my provider is rock solid down. Then I set the upload to a value that gives me good speeds without buffer bloat when tested on dslreports. With that setup I get all A's and if I play with the upload I can get A+. Being lazy I let all A's be good enough.
Got the downstream tip from somewhere, don't remember where. Am using cake and piece of cake.

@starcms

out of respect, you may want to start another thread.

Looks like we have another kernel bump on 4.9 and 4.4 as well as a new Wifi Driver 9.3.0.7 ( for the 3200acm).

Wifi Driver as stated by dlin.

Added code to assign station ID.
1. This patch should fix Multi-BSSID problem.
2. STA mode can work for open mode.

Will pull down the new sources and begin building tonight. The new images should be posted to the site tomorrow.

Appreciate everyone's input as well contributions.  Hope everyone has a safe holiday!

Best Regards,

Correction -- Firmware Version update and NOT Driver Version.

Firmware Version to 9.3.0.7

(Last edited by davidc502 on 27 May 2017, 03:57)

davidc502 wrote:

Correction -- Firmware Version update and NOT Driver Version.

Firmware Version to 9.3.0.7

Technically both.  Driver version number might not have changed, but it has that one new commit to stop issues with multiple SSIDs.

Looking forward to the new builds with the new kernel!

For everyone following David's thread here, and wanted to be notified when he posts a new build, I would like to recommend you sign up at https://visualping.io/ . This site:

VisualPing is easy to use and requires no registration. All you have to do is go to the site, type in the website you want to track and provide an email they can send notifications to. These notifications can be set to come in hourly, daily, weekly or monthly.

There’s also a trigger option to get notifications for tiny, medium or major changes. Based on your settings, VisualPing will send you two images – a before and an after – to show how the site you are tracking has changed.

I hope the pinging does not mess with David's statistics for the site...

davidc502 wrote:

Looks like we have another kernel bump on 4.9 and 4.4 as well as a new Wifi Driver 9.3.0.7 ( for the 3200acm).

Wifi Driver as stated by dlin.

Added code to assign station ID.
1. This patch should fix Multi-BSSID problem.
2. STA mode can work for open mode.

Will pull down the new sources and begin building tonight. The new images should be posted to the site tomorrow.

Appreciate everyone's input as well contributions.  Hope everyone has a safe holiday!

Best Regards,

I saw the kernel + mvlwifi commits and came to ask if you'd started building yet hah. Glad to see you're on top of it big_smile

Thanks David!

p.s. what holiday is this?

mariano.silva wrote:

For everyone following David's thread here, and wanted to be notified when he posts a new build, I would like to recommend you sign up at https://visualping.io/ . This site:

VisualPing is easy to use and requires no registration. All you have to do is go to the site, type in the website you want to track and provide an email they can send notifications to. These notifications can be set to come in hourly, daily, weekly or monthly.

There’s also a trigger option to get notifications for tiny, medium or major changes. Based on your settings, VisualPing will send you two images – a before and an after – to show how the site you are tracking has changed.

I hope the pinging does not mess with David's statistics for the site...

It probably won't mess with the stats.. Google's pretty smart about how it counts traffic.

listerwrt wrote:
davidc502 wrote:

Looks like we have another kernel bump on 4.9 and 4.4 as well as a new Wifi Driver 9.3.0.7 ( for the 3200acm).

Wifi Driver as stated by dlin.

Added code to assign station ID.
1. This patch should fix Multi-BSSID problem.
2. STA mode can work for open mode.

Will pull down the new sources and begin building tonight. The new images should be posted to the site tomorrow.

Appreciate everyone's input as well contributions.  Hope everyone has a safe holiday!

Best Regards,

I saw the kernel + mvlwifi commits and came to ask if you'd started building yet hah. Glad to see you're on top of it big_smile

Thanks David!

p.s. what holiday is this?

For U.S. residence it is Memorial Day weekend. Most people will get a 3 day weekend off of work.

My 1900ACv1 has been rebooting occasionally and I think it's temp related. I seem to recall that there was something called "gufus fan control scripts" and I thought I had it bookmarked but I can't find it.

1) Anyone know what I'm talking about? smile
2) Would the scripts also work on dd-wrt or are they openwrt/lede specific?

Thanks!

Okay, new builds based on kernel 4.9.30 and new wifi firmware (3200acm) have been uploaded to the site.

As usual these days, I'm interested in hearing from 1900ac Version 1 owners as to if the router reboot issue is still present.  I will be building a new image on kernel 4.4.x if the reboot issue still continues.

On a side note, dnscrypt was not working when my router came up on 4.9.30. I haven't had time to troubleshoot the issue, but noticed it doesn't appear to run even though I tried to manually start/restart the process, and there's nothing in the system or kernel logs.

Thanks,

FAQ has been updated to better explain was .img and .bin is for.

Thank you starcms.

2. What's the difference between images ending with .img and .bin?

a .img is used to originally flash LEDE from a browser if coming from stock Linksys firmware.
b .bin is used for upgrading if already running LEDE: either from a browser (LuCi) or from a SSH terminal.
Example command using SSH: "sysupgrade /tmp/imageName.bin" OR "sysupgrade http://webLocationOfImage.bin"
c. If currently running LEDE, .img can also be used from SSH for a completely fresh start.
This is not normally needed, except possibly if you are changing distros (i.e. going from official LEDE to @david's build).

davidc502 wrote:

Okay, new builds based on kernel 4.9.30 and new wifi firmware (3200acm) have been uploaded to the site.

As usual these days, I'm interested in hearing from 1900ac Version 1 owners as to if the router reboot issue is still present.  I will be building a new image on kernel 4.4.x if the reboot issue still continues.

On a side note, dnscrypt was not working when my router came up on 4.9.30. I haven't had time to troubleshoot the issue, but noticed it doesn't appear to run even though I tried to manually start/restart the process, and there's nothing in the system or kernel logs.

Thanks,

I'm still getting reboots on official snapshot builds (https://forum.lede-project.org/t/wrt190 … =listerwrt)

I'm happy to test your build if you like. Let me know if you think it's necessary.