**** BEGIN LOGGING AT Thu May 23 03:00:36 2019 **** BEGIN LOGGING AT Thu May 23 06:08:34 2019 May 23 08:16:38 mangix: haven't found the time to comment, and currently travelling. any idea why there is an unrelated change (-DBUILD_SHARED_LIBS=yes)? May 23 09:05:17 https://github.com/sponsors May 23 09:05:27 OpenWrt should look at this May 23 09:07:10 it might be better if you could bring it to the attention of wider audience through mailing list May 23 10:04:00 stintel: beats me. May 23 11:13:21 mangix: I commented on the issue, we'll see :) May 23 11:21:39 ynezz ping May 23 11:22:06 ynezz do you join the openwrt meeting in hamburg? May 23 11:23:01 aparcar[m]: yeah, I plan to May 23 14:33:32 jow: I've manged to create a .pot and .lmo for some of our own apps, and it all "just works" but how is the language list generated? I used a differnet language at first, and it couldn't be selected in admin/system/system. I had to make my file match one of the existing languages. May 23 14:33:49 I added mine to the list in /etc/config/luci and restarted it. May 23 14:34:04 is it just rejecting it because there's no base.blah.lmo file? May 23 14:34:36 probably doesn't really matter, it will be a langauge that already exists in base when it gets done properly, just used something different for testing. May 23 20:43:10 code to support Dual Channel Wi-Fi has been released into the OpenWrt repository May 23 20:43:16 https://www.lightreading.com/open-source/edgewater-wireless-cablelabs-hook-up-on-dual-channel-wifi/d/d-id/751694?_mc=RSS_LR_EDT&utm_source=dlvr.it&utm_medium=twitter May 23 20:43:28 Is this in the OpenWrt github? May 23 20:45:21 and is this fixt? May 23 20:45:23 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12272 May 23 20:46:01 I just spoted theat cve on twitter May 23 20:47:08 the CVEW itself is referring to https://github.com/openwrt/luci/commit/9e4b8a91384562e3baee724a52b72e30b1aa006d - in other words, it's fixed since early april May 23 20:47:35 OK thanks May 23 20:51:27 the dual-channel thing looks like proprietary marketing bull^w lingo, it's definitely not part of OpenWrt at the moment (and I'm very doubtful that it ever will, I'm not really patient enough to read the whole whitepaper, but I don't really spot a source link - furthermore it will be heavily hardware dependent, probably using only proprietary drivers, as I doN't think any of the mainline drivers can May 23 20:51:33 do it at the moment) May 23 20:52:29 pkgadd yeah that is what I was thinking. I look at new pulls and haven't seen anything like it so.... May 23 20:52:41 Tapper: CVEs on twitter huh May 23 20:53:02 Yeah I run the OpenWrt help twitter so see what people say about openwrt May 23 20:53:14 oh yeah i forgot :) May 23 20:53:21 and someone asked about that cve? May 23 20:54:13 I keep a search buffer for openwrt open 24-7 so any tweets that mention openwrt I get to see. May 23 20:54:26 ok May 23 20:56:25 and, pretty much as expected, all 'source' links for the dual-channel crap are 404, respectively asking for a login May 23 20:57:38 Borromini lol if I put a smiley face in thuis chat window it crashs my screen reader lol May 23 20:57:52 * Tapper grins May 23 20:58:18 :D May 23 20:58:24 There I go again breaking shit! May 23 20:58:28 i've seen people use actual smileys and they get printed May 23 20:58:37 Tapper: 20:56:25 < pkgadd> and, pretty much as expected, all 'source' links for the dual-channel crap are 404, respectively asking for a login May 23 20:58:38 but no idea how i'd make them in plain irssi. at least it shows them :) May 23 20:59:10 * Tapper nods at pkgadd May 23 20:59:28 Borromini: that's (probably) not an irssi question at all, but more a question of how your x terminal accepts unicode glyphs May 23 21:00:07 Borromini this one was from the windows 10 emoji panel. May 23 21:00:40 It was a smiling face with smiling eyes. May 23 21:01:04 my client is Instantbird May 23 21:01:17 It has not bin updated in a long time. May 23 21:01:44 I don't know what I could use tho. I need one that works with my screen reader. May 23 21:03:45 All Dual Channel Wi-Fi code is stored in the CableLabs GitHub team “DCW,” located at https://github.com/orgs/cablelabs/teams/dcw/repositories. May 23 21:04:00 which isn't public May 23 21:04:57 none of the provided links work May 23 21:05:14 Bah May 23 21:05:31 so mutch for open! May 23 21:05:42 While in broad general I've wondered many years that why there isn't included in stadards that one oculd use both (or even more, if available) wifi frequencies when offered in same (E)SSID or so... but meh... May 23 21:05:48 so much for "released" "to OpenWrt" May 23 21:06:00 * Tapper nods May 23 21:06:19 ..also their method would need also support from client, so.. what? May 23 21:06:53 Right up there with "My ChinaInc $8 special is running OpenWrt Barrier Breaker on a Lexra core, why won't you support it? May 23 21:07:12 and it apparently works by exploiting the hardware functionality usually used for HT/ VHT, probably making it unavailable - so 20 MHz channels only, 'yeah' May 23 21:10:12 oh, Lexra... I've got a few of these around. May 23 21:10:48 I'd like to see in broad general (an "and/or") multi-freq support in standardised way in wifi, and then multipath-tcp in more general :) May 23 21:12:12 rtl8192du (there are three variants, single-mac/ single-phy, dual-mac/ single-phy, dual-mac/ dual-phy) May 23 21:13:59 mp-tcp would work across whole internet and such, so scope is much more wide than just radiolink, but while at it... :D May 23 21:14:39 I have an Ikanos Fusiv May 23 21:15:00 * Borromini tips his hat May 23 21:15:01 my condolences ;) May 23 21:15:02 night gents May 23 21:15:09 n8 Borromini May 23 21:15:51 nn May 23 21:16:19 that ikanos router is likely to never become anyhting useful May 23 21:18:50 I am off now to laters! **** ENDING LOGGING AT Fri May 24 03:00:35 2019