I noticed that the subdomain dev.libre-mesh.org runs with a self-signed
certificate, which is annoying because casual people browsing (and
security paranoid) won't accept to add an exception in order to read
more and will leave...
A free browser-accepted certificate can be obtained from StartSSL [1]
(for that specific domain, wildcards and extended verification certs are
not for free of course, but we there is no need for them).
[1] https://www.startssl.com/
I have experienced problem changing 5GHz channel on our routers, do you think
it may be related to this ?
If so shoulb we enable by default that option at least on lime-build or lime-
full ?
---------- Forwarded Message ----------
Subject: Re: [OpenWrt-Devel] [patch] mac80211: Force Atheros drivers to
respect the user's regdomain settings by default
Date: Friday, April 03, 2015, 12:53:00 PM
From: bkil <bk.il.hU+ibLa_qUzy(a)gmail.com>
To: Jiri Pirko <jiri(a)resnulli.us>
CC: openwrt-devel <openwrt-devel(a)lists.openwrt.org>
Unfortunately, your patch will never be merged because most developers
are from the USA:
https://dev.openwrt.org/ticket/6923https://dev.openwrt.org/ticket/7777https://dev.openwrt.org/ticket/9678https://dev.openwrt.org/ticket/12991https://dev.openwrt.org/ticket/16818https://dev.openwrt.org/ticket/16862
...
There's no use in resending or even debating it.
On Fri, Apr 3, 2015 at 12:09 PM, Jiri Pirko <jiri(a)resnulli.us> wrote:
> User's regdomain should know the correct setting. So change default for
> ath drivers to respect those.
>
> Signed-off-by: Jiri Pirko <jiri(a)resnulli.us>
> ---
> package/kernel/mac80211/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/kernel/mac80211/Makefile
b/package/kernel/mac80211/Makefile
> index 11c8bcf..ab79330 100644
> --- a/package/kernel/mac80211/Makefile
> +++ b/package/kernel/mac80211/Makefile
> @@ -503,6 +503,7 @@ define KernelPackage/ath/config
> if PACKAGE_kmod-ath
> config ATH_USER_REGD
> bool "Force Atheros drivers to respect the user's regdomain
settings"
> + default y
> help
> Atheros' idea of regulatory handling is that the EEPROM of
the card defines
> the regulatory limits and the user is only allowed to
restrict the settings
> --
> 1.9.3
> _______________________________________________
> openwrt-devel mailing list
> openwrt-devel(a)lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
_______________________________________________
openwrt-devel mailing list
openwrt-devel(a)lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
-----------------------------------------
Hi!
Although the branch merge_develop doesn't follow our naming convention seems
no one has reported specific problems with that branch.
Is there any undergoing test of that branch?
Is it already tested?
If so we should proceed to rename it to something like feature/feature_name or
hotfix/hotfix_name and then merge it into develop anyone willing to do this job
?
Cheers!
Seems LiMe syrup is an affocial componet of next openwrt release :p
---------- Forwarded Message ----------
Subject: Re: [OpenWrt-Devel] OpenWrt release name
Date: Monday, April 06, 2015, 09:35:52 AM
From: John Crispin <blogic(a)openwrt.org>
To: openwrt-devel(a)lists.openwrt.org
i think we have a winner with 96 vs 50 votes.
> == Dirty Diamond ==
> 2 cl Rum
> 2 cl Vodka
> 2 cl Tequila Silver
> 2 cl Campari
> 2 cl Curaçao Blue
> 2 cl Lime syrup
> 2 1/2 cl Orange juice
> Coca Cola
_______________________________________________
openwrt-devel mailing list
openwrt-devel(a)lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
-----------------------------------------
