**** BEGIN LOGGING AT Tue Dec 31 02:59:57 2019 Dec 31 10:09:16 anyone from english grammar commando available? is that "Firmware image download problem" correct ? https://git.openwrt.org/6dbaf71411e7f16cc1c920b6a63bbe33ef2b8921 **** BEGIN LOGGING AT Tue Dec 31 10:17:38 2019 **** BEGIN LOGGING AT Tue Dec 31 10:25:24 2019 Dec 31 11:01:42 * ldir waves in the general direction of https://github.com/openwrt/openwrt/pull/1968 Dec 31 11:44:00 ynezz: the echo text is probably redundant, since wget will already spew out error messages (at least on a first glance we don't surpress the output), so just existing should be enough Dec 31 11:50:22 is jow lurking by any chance? Dec 31 12:08:31 to be a little pedantic, to me, "image" means something like a block-for-block copy. not all firmwares are images, although i say "image" all the time to mean firmware, even when the firmware is a structured thing that gets unpacked. Dec 31 12:20:26 this is the problem with bikes and sheds. ynezz ship it and if someone is sufficiently perturbed by it then another commit can follow Dec 31 12:23:46 ldir: that's why I argue to drop the message entirely, as wget will already have complained with a proper error message ;) Dec 31 12:29:55 ldir: what's up? Dec 31 12:30:37 I was thinking that the iptables bump will have to happen sooner or later. Dec 31 12:31:06 it looks to me that the only thing that uses libiptc is collectd Dec 31 12:31:10 yes, but it needs to be done after some actual testing with all (relevant) packages enabled Dec 31 12:31:52 iirc libiptc is some kind of shim or glue code that is actually redirecting to lip4tc and libip6tc Dec 31 12:32:08 but I might be misremembering, its too long ago Dec 31 12:32:51 he he - yes that's sort of what it looks like to me, a lib built of libip4tc libip6tc & xtables Dec 31 12:32:57 so I'm thinking... Dec 31 12:33:30 that anything that relies on libiptc could look at the source libs directly... well that's what I'm trying with collectd at least Dec 31 12:33:53 collectd upstream is quite active Dec 31 12:34:13 given that iptables usptream dropped libiptc for good, I'd assume collectd to follow up soonish Dec 31 12:34:30 until then we can maybe simply mark that one affected plugin @BROKEN Dec 31 12:35:07 let me see if this build works and go from there :-) Dec 31 12:47:24 KanjiMonster: ldir: I like that `wget || exit 1`, thanks Dec 31 12:57:29 hi, is there any reason why afaict by default (in 18.06) we don't apply syn flood protection to forwarded hosts (in LAN zone)? Dec 31 13:41:27 might be a better bump to iptables https://git.openwrt.org/?p=openwrt/staging/ldir.git;a=commit;h=957a04598b58094a4426cc9baa62740d9301751c Dec 31 13:42:46 and corresponding tweak to collectd https://github.com/ldir-EDB0/packages/commit/aa1970c5d7164ef6f92c18a23fe9d8eb0b1f101e Dec 31 15:22:50 build #221 of x86/geode is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/x86%2Fgeode/builds/221 Dec 31 15:24:05 build #223 of omap/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/omap%2Fgeneric/builds/223 Dec 31 15:31:33 build #236 of kirkwood/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/kirkwood%2Fgeneric/builds/236 Dec 31 16:20:36 build #236 of ramips/rt288x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/ramips%2Frt288x/builds/236 Dec 31 16:36:27 build #197 of x86/legacy is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/x86%2Flegacy/builds/197 Dec 31 17:21:52 build #193 of brcm2708/bcm2709 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/brcm2708%2Fbcm2709/builds/193 Dec 31 17:28:44 build #194 of lantiq/xrx200 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/lantiq%2Fxrx200/builds/194 Dec 31 17:32:54 build #192 of brcm2708/bcm2708 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/brcm2708%2Fbcm2708/builds/192 Dec 31 17:41:52 build #195 of bcm53xx/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/bcm53xx%2Fgeneric/builds/195 Dec 31 18:18:23 build #186 of ar7/ac49x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/ar7%2Fac49x/builds/186 Dec 31 18:21:08 build #189 of octeon/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/octeon%2Fgeneric/builds/189 Dec 31 18:33:50 build #184 of malta/be is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/malta%2Fbe/builds/184 Dec 31 18:50:13 build #182 of ath79/generic is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/ath79%2Fgeneric/builds/182 Dec 31 19:22:52 build #180 of samsung/s5pv210 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/samsung%2Fs5pv210/builds/180 Dec 31 20:51:17 ldir: thanks for having a look at the uefi pull request, that's really becoming essential, as many contemporary mainboards (especially the more embedded type) no longer ship with a legacy CSM shim at all, so hard-require UEFI to boot Dec 31 20:53:08 Don't know what to say about that really. Dec 31 20:53:57 All I've done is pull that pr, rebase it, fix up the conflicts and push the result to another tree. Dec 31 20:54:39 I know that the pull request has been a pain so far, but I'd really just wanted to say thanks :) (personally I'm more focussed on non-x86 OpenWrt uses - or OpenWrt on qemu-kvm, so I can usually avoid it) Dec 31 20:55:57 I've played with previous versions of that pull request on ivy-bridge/ UEFI, which was working fine Dec 31 20:56:14 I can't push it to the original PR, so I expect it to be another place where it can bit rot. Dec 31 20:57:08 I could push it to master, but I don't really want to be shouted at for something that I don't really understand anyway. Dec 31 20:57:45 It was the person struggling in the forum to deal with the conflicts that I wanted to make life a little easier for. Dec 31 20:57:53 maybe, hopefully not - it would be great if it could find its way towards master soon(ish) Dec 31 20:58:01 build #188 of sunxi/cortexa7 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org/master/images/builders/sunxi%2Fcortexa7/builds/188 **** BEGIN LOGGING AT Tue Dec 31 21:45:20 2019