**** BEGIN LOGGING AT Fri Jan 29 03:02:12 2021 Jan 29 06:47:37 is there anyine here right now that knows how to work with the ath10k board files? Jan 29 09:23:02 Borromini: ping Jan 29 09:24:01 does Borromini commit to any repository? I need a name for a Reported-by line Jan 29 09:28:46 aparcar[m]: Stijn something. it escapes me Jan 29 09:29:06 aparcar[m]: Stijn Segers Jan 29 09:29:33 dang. Well i'll correct it before a commit Jan 29 09:29:53 stintel: and thank you Jan 29 09:30:18 aparcar[m]: well his given name is easy for me to remember :P Jan 29 09:34:21 ;) Jan 29 10:12:30 aparcar[m]: and for completeness sake, I also reported that on IRC :P Jan 29 10:18:23 stintel: sorrrey Jan 29 10:19:02 aparcar[m]: no worries, just nitpicking Jan 29 10:23:42 xD Jan 29 10:23:51 thanks for the mention aparcar[m] ;) Jan 29 10:33:38 "if you have issues, tell it ti Stijn" ;) Jan 29 10:37:17 * stintel hides Jan 29 11:28:49 karlp: any news one this? https://github.com/openwrt/packages/commit/d5bace89cf93f4dfab5f03f48ee87d06444876e8 libwebsockets is on v4.1.6 in the meantime: https://github.com/warmcat/libwebsockets/releases/tag/v4.1.6 Jan 29 11:29:52 i suspect that the current version packaged in openwrt is broken anyway Jan 29 11:37:42 I suspect the 4.1.x is broken too, just differently Jan 29 11:38:00 4.1.early was broken, I'll get around to testing 4.1.today sometime, maybe next week. Jan 29 11:38:26 what do you use lws with? always good to know more test apps Jan 29 11:39:00 ttyd and the basics do work but for some reason ssl does not work and i suspect thats lws related Jan 29 11:39:01 given it's breakage rate, and the communication style of upstream, it's not always very motivating to try out new versions. Jan 29 11:40:11 you can try it out if you like, and let me know, but it needs to work for both ttyd and mosquitto. Jan 29 11:44:24 thanks, probably best for me to await your test first. if that passes then I could test it with ttyd is that helps you. I am not familiar with mosquitto Jan 29 12:08:54 Hi, I'm using https://openwrt.org/docs/guide-user/firewall/fw3_configurations/intercept_dns for dns intercept Jan 29 12:09:18 however I want to whitelist one ip address from having its dns intercepted Jan 29 12:09:21 as I Jan 29 12:09:39 * as I'm running adguard/pihole on that ip Jan 29 12:10:15 and want it to be able to resolve dns, so that I can point my router dns to it. Jan 29 12:10:52 But without being able to whitelist the ip address, the dns resolvers is stuck in a loop Jan 29 12:12:55 I've tried this in addition to the above rule but it doesn't seem to work: https://paste.rs/CPd Jan 29 12:25:16 the #openwrt channel will probably yield better results shalzz Jan 29 12:26:06 ok, I see. Will post there thanks! Jan 29 12:29:06 but that rule is redirecting all tcp/udp traffic from lan with destination port 53 to the router dns resolver Jan 29 12:53:03 shalzz: random idea. run adguardhome on the router. Jan 29 15:20:34 Are there already plans that the image-builder (ar71xx) comes to Python3 ? It still needs Python2 Jan 29 15:26:04 hsp: no, ar71xx is gone, ath79 is successor Jan 29 15:26:30 19.07 is using Python2, next release will be with Python3 Jan 29 15:37:46 ynezz, ar71xx is gone?? I am confused, i have Archer C7 V2. there is ar71xx ==> https://downloads.openwrt.org/releases/19.07.6/targets/ar71xx Jan 29 15:40:54 yes, ar71xx wont be available in the next release Jan 29 15:41:16 21.05 or whatever time it takes Jan 29 15:41:58 so you would need to switch to ath79 with your c7v2 device Jan 29 15:42:39 you can even try it in current 19.07.6 release https://firmware-selector.openwrt.org and type 'c7 v2' to get the list Jan 29 15:43:42 and select ath79 variant Jan 29 15:44:45 ynezz, can i flash ath97-sysupgrade.bin if ar71xx is already on it? Jan 29 15:51:22 ynezz, or how do i get to ath79 from ar71xx ? Jan 29 15:54:22 hsp: you can, but with -F and -n (don't keep settings) Jan 29 15:56:38 Borromini, why don't keep settings ? Jan 29 15:58:30 https://openwrt.org/docs/guide-user/installation/ar71xx.to.ath79 Jan 29 15:58:36 ^^ Jan 29 16:00:04 hsp: FYI there is #openwrt dedicated for such kind of discussions, this is #openwrt-devel dedicated to idling :) Jan 29 16:05:03 What can happen if I keep the settings? Jan 29 16:07:26 hsp trust us you don't want to keep settings when going from ar71xx to ath79xx Jan 29 16:07:54 Some of the network names are different you could brick your router. Jan 29 16:10:34 OK, I'll stick with ar71xx for now while it's available Jan 29 17:19:16 friday night, good time to do some quick pen-testing to help audit the openwrt selinux sandbox: http://openwrt.defensec.nl:7681 Jan 29 18:30:53 adrianschmutzler: are you kidding? Jan 29 18:31:11 that cyrillic thing was absolutely unnecessary Jan 29 18:31:31 it was very necessary. He wrote kernel2minor and kernel2minor is commented in cyrillic Jan 29 18:31:46 i don't see anything wrong in what I wrote and I resent your comment. Jan 29 18:32:37 That was a sarcastic comment which is not appropriate in these circumstances. Or at least not nice enough for rule #12. Jan 29 18:33:03 You may of course argue whether cyrillic for commenting is appropriate or not, but not like this. Jan 29 18:33:14 *facepalm* Jan 29 18:33:39 i'll refrain from commenting on GH moving forward then. Jan 29 18:35:13 sorry, I'm glad that you discussed this and highlighted the challenges. but you were looking down at him with that comment and that's not appropriate. Jan 29 18:36:00 Of course that's not the worst case I ever saw, but it was slightly over the edge IMO. Jan 29 18:36:18 there was a smiley and it was really meant as an inside joke Jan 29 18:36:49 but okay. I guess the edges are getting closer as time moves on. Jan 29 18:37:18 It's really not worth the noise Jan 29 18:38:08 in any case I'll stop commenting on this PR. I made my technical point and I'll leave it at that. Let's see if they come up with reviewable code. Jan 29 18:38:35 yes, but please don't be offended. Jan 29 18:39:47 I just thought this was slightly inappropriate and wanted to prevent further comments in this direction. and now may just go back to the subject, please. Jan 29 18:39:52 it'll be forgotten tomorrow. I'ev had a bad day. Jan 29 18:41:07 and as you stated correctly, the facts are on the table now, so let's wait what people will do with them Jan 29 18:41:18 *nod* Jan 29 19:47:16 i dont think it can ever be a release goal, would be unrealistic Jan 29 19:47:25 wrong chan Jan 29 19:57:14 oh i like this: https://github.com/openwrt/openwrt/commit/331892f85f1cfab21b26a1f84824f4110e06027f Jan 29 19:57:54 would also be good to adjust modes because theres quite a few files that are executable where they shouldnt be Jan 29 20:00:14 this one for example: package/base-files/files/lib/functions/uci-defaults.sh Jan 29 20:00:30 grift: this one was changed Jan 29 20:00:34 the only one in this patch Jan 29 20:00:42 its installed with +x but its just a bunch of functions and now the shebang is also gone Jan 29 20:00:52 the mode as wel? Jan 29 20:01:07 so both the sbebang as removed as well the +x? Jan 29 20:01:10 nice Jan 29 23:16:05 so... other than accidentally doing things you don't mean, what does removing exec bit actually change, security wise? **** ENDING LOGGING AT Sat Jan 30 02:59:57 2021