**** BEGIN LOGGING AT Mon Dec 21 02:59:56 2020 Dec 21 05:59:43 https://openwrt.org/docs/guide-user/network/wifi/guestwifi/configuration_webinterface Dec 21 05:59:58 guide needs to be updated to reflect GUI interface changes in LuCI beginning with 19.07 Dec 21 06:01:08 firewall traffic rules no longer contain the option "any" for Source address and Destination address when creating new rules Dec 21 06:02:08 it's not clear how that guide should be completed when creating DNS and DHCP rules Dec 21 06:12:31 >KGB-1< https://tests.reproducible-builds.org/openwrt/openwrt_tegra.html has been updated. (0% images and 93.7% packages reproducible in our current test framework.) Dec 21 09:27:21 * enyc meows Dec 21 09:27:48 Are there guides on assisting with testing development builds, do we get beta's etc. for 20.10 ? Dec 21 09:39:45 your use cases are test cases Dec 21 10:13:26 enyc: there will be some branch soon. if you like to test now, you can start with the snapshot builds. Dec 21 10:24:12 nbd: Quick question, is the MT7603 four interface limit a hard limit, or just nobody felt the need of supporting more than those? Dec 21 10:27:46 ynezz: ok, makes sense Dec 21 10:28:00 lynxis: ok, what about then beta? just RCs ? Dec 21 10:38:55 enyc: not yet. you're too early :) there will be beta releases soon. but we didn't even branched yet. Dec 21 11:06:51 aah i see Dec 21 11:07:55 I guess 20.12 is just the year-month of branch occuring Dec 21 11:53:01 * enyc hrrm, master build, no luci included ... Dec 21 11:53:37 installed luci packages and mostly works, status page says:- Dec 21 11:53:38 HTTP error 400 while loading class file "/luci-static/resources/view/status/index.js?v=git-20.339.75073-e54708a" Dec 21 14:15:49 enyc I have had that before on my c7 but haven't worked out why yet. Dec 21 14:16:10 I run the c7 as a dumb AP so don't realy mind. Dec 21 16:19:47 hi! i'm trying to build a very small binary for my router -- i've found and downloaded the sdk, but i am missing something. how do i set this up for CC? there's no gcc in here -- maybe i'm waay off base Dec 21 16:20:55 (i've tried building my file with a regular cross-compiler but of course is not abi compatible and just dies) Dec 21 16:22:22 deivid: https://openwrt.org/docs/guide-developer/using_the_sdk Dec 21 16:23:45 that's what i was reading -- but i don't necessarily want to make a package, i assumed this sdk would just be a set of cross-compilers for me to use Dec 21 16:24:41 it is Dec 21 16:25:11 you can find it in staging_dir Dec 21 16:25:40 but you're going to do the heavy lifting by yourself Dec 21 16:26:05 proper flags, paths etc. Dec 21 16:26:20 i have a 50 line .c file ( Dec 21 16:26:29 do you think it's easier for me to do it proper and write a package? Dec 21 16:27:07 just build some package in verbose mode with `make V=sc` and you can copy&paste the flags Dec 21 16:27:46 it's doable for one target, if you're going to support/use more then it's going to be PITA Dec 21 16:28:01 s/more then/more then one target/ Dec 21 16:29:25 look at package/utils/otrx for easy enough example Dec 21 16:31:25 here is the manual procedure https://openwrt.org/docs/guide-developer/crosscompile Dec 21 16:34:26 excellent! Dec 21 16:38:51 `mips-openwrt-linux-gcc -I../include *.c` was what i ended up running ) Dec 21 16:39:06 all of this to publish to mqtt when devices join wifi Dec 21 16:39:16 totally worth it though! thanks a lot Dec 21 16:40:37 sounds lika lua may have been easier than C.... Dec 21 16:41:07 wait can i run lua in the router? Dec 21 16:41:37 i had an initial version of grep/awk/whatever piping to `nc` and a remote python server doing tcp->mqtt Dec 21 17:01:17 deivid: of course you can run lua, and lua-mosquitto is packaged for you too, so it's nice and easy... Dec 21 17:02:33 you could have just used your grep/sed/awk and piped to mosquitto_pub even really, but sure, nc to python to mqtt sounds like it would have been a fun little stack of pieces :) Dec 21 17:03:58 i definitely did not know i could use mosquitto_pub / lua mosquitto Dec 21 17:04:23 i didn't like the nc|python, which is why i went for "trying to remember what i learnt in uni about c" Dec 21 17:07:11 there's also this, which is ~isimilar: https://github.com/openwrt/packages/pull/5701 Dec 21 18:21:47 all… what would cause Bind to not be listening on all interfaces as they come up? Dec 21 18:35:51 youre saying that if you manually (re)start bind when all is up that it does bind to all? Dec 21 18:36:22 ive had similar issue with knot, in my case it was (i think) because at start up the ip6 wasnt properly available yet Dec 21 18:36:52 ie not ip not available (with 0.0.0.0) Dec 21 18:37:51 try specifying ip (4) addresses in stead of 0.0.0.0 (if that is at all applicable) Dec 21 19:07:31 grift: seems to work after a restart, yeah. I’m not using IPv6 and tried “option disable_ipv6 1” in “config defaults” in /etc/config/network but it’s not clear what, if anything, that does. Dec 21 19:08:45 i guess also could be that ip4 isnt fully available yet at the time (in my case if was limited to ip6 only but i suppose same could happen there) Dec 21 19:10:37 i would try specifiying ip addresses in bind conf and then see if it binds to all specified ip addresses and if not then i would expect something in logread to go by **** ENDING LOGGING AT Tue Dec 22 03:00:27 2020