It was compiled under a different Kernel, so it is likely to hose this new build.
Sorry, I am not a native English speaker. What do you mean by hose in this context?
That is a metaphor going back to when crowds of protesters were controlled by water hoses. Over the decades it has been adopted by IT describing episodes where something is ruined.
Hope that helps.
Running your latest build right now, currently no issues at all right now that i can see.
I am not using Rosy LuCi however i have been using luci-theme-material theme now for a while since 9133, but this is my taste and each persons taste is different.
Question regarding #2.. sorry this is just me confirming but is the change to the Wifi mean that this change:
Is present in the latest build? If so that's excellent. In addition does this mean that the next time OpenWrt does builds (18.06.3, or whatever the next iteration may be now) will contain the change as well?
Sorry - this is something that is probably obvious to you or most but as someone still learning I don't like to make assumptions on what may or may not be present
I always compile the very latest driver/firmware from the master. I download it to my machine, change some code for the AMSDU lag issue for the 1200 series, change the "make" file for mwlwifi to point to the modified driver, and ensure it is compiled for that build.
As for 18.06.3, they usually pull in the latest wifi changes for mwlwifi. So, .2 for example should have the latest wifi driver/firmware for the time it was compiled.
A while back I followed Starcms's guide (which has since been removed from the openwrt wiki) to get rid of luci certificate warnings when trying to login via the web interface. Now after this update I'm getting an ssl version interference error when I try to login to the web interface, due to what I assume has to do with whatever has changed with openssl. Can someone give me a little bit of guidance on how to either fix, remove, or bypass openssl and the self signed cert that it created so that I can get back into Luci?
Import the certificate into the certificate store and you won't have to see the self signed certificate again. At least until the next build when it creates a new self signed certificate. Just google how to accept self signed certificates for the browser of your choice.
I've added uHTTPd into the build which gives users some flexibility on how to handle certificates or just turn HTTPS off and use HTTP. So, be sure to take a look at those options as well.
Also, I know what you are talking about with Starcms's guide, but since it has been a long time since I've seen those instructions, I've forgotten how he did it. However... You can use Wayback machine to see the OpenWrt webpage and how it looked 1 year ago, so you should be able to pull out the instructions that way too.
Think this might be the guide from starcms that you're looking for:
What build are you running?
Looks like it could be another Rosy formatting issue.
Well it seems like the page is actually still up, so thanks @inph for linking it. This is what I had bookmarked so I'm not sure what I did or why the address was changed: https://openwrt.org/docs/user-guide/getting-rid-of-luci-https-certificate-warnings
The thing with the cert is that even though I followed Starcms's instructions exactly and your advice now, I was never actually able to get the firefox/chrome store to accept the cert that openssl generated. So what I did was just let my OS handle it by dropping it in my /etc/ca-certificates folder on my pc and that has worked fine for multiple updates, until now of course. So I'm a bit stuck of what I need to do with the certificate I have to get it to work again or what to do to revert what I did with Starcms's guide.
I will definitely look into the options you're suggesting when I get this sorted so thanks for mentioning uHTTPd.
It looks like rosysong was waiting for a followup from @pintopwnie - I replied with information I was able to dissect from the screenshot posted, but maybe following up to an answer on your browser and OS used may be helpful.
Could you tell me your version of Openwrt ? master or 18.06 ?
And your browser, mobile phone or PC ? Showing A snapshot would be great. Thanks! @pintopwnie
I'm sorry for the basic question, but why the new builds no longer come with dnscrypt-proxy V2 already compiled and configured to be used
We pushed a new commit to the master (merged), please update your source code, if it doesn't work,
please tell me the detailed steps to reproduce this problem, thanks!
You might be confused because Version 2 has never been a part of the base build. It has always been an option for those who want to install it. The script downloads a pre-compiled binary. -- https://dc502wrt.org/dnscrypt/
I would love to have version 2 instead of version 1, but I was told there was limitations with the way Openwrt builds its packages --- something to do with cross compiling. Let me know if you hear the issue has been resolved.
It's hears very strange for me. I use 3200acm for months, and David's firmware quite good - have no wifi problems so far. Maybe it's good idea to drop settings?
Yes, DFS is a menace - thanks to FCC.
+1. It's NOT pointless.
I check preliminary ax on Asus - it's quite impressive - about 2x speed into same conditions and diapasone! So i'm waiting for it at routers and adapters.
Just installed r9506 on my WRT32X and am seeing these "marvell-cesa f1090000.crypto" kernel errors in my logs now, too.