**** BEGIN LOGGING AT Thu Jan 09 02:59:58 2014 Jan 09 03:51:58 build #505 of at91 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/505 Jan 09 04:18:41 build #489 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/489 Jan 09 04:22:04 build #422 of sibyte is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/422 Jan 09 06:31:22 build #432 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/432 Jan 09 07:21:02 build #479 of lantiq is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/479 Jan 09 08:06:58 build #52 of mxs is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mxs/builds/52 Jan 09 08:07:16 build #479 of ramips is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/479 Jan 09 08:12:35 build #53 of imx6 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/53 Jan 09 08:15:06 build #369 of iop32x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/369 Jan 09 15:03:07 build #52 of mvebu is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/52 Jan 09 15:39:34 wigyori: can you tell me what's missing for the cb2/a20 in openwrt? Jan 09 16:05:34 build #358 of mcs814x is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mcs814x/builds/358 Jan 09 16:17:31 build #369 of ep93xx is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/369 Jan 09 16:23:08 luka: ping Jan 09 17:18:34 build #399 of au1000 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/399 Jan 09 17:25:58 if I mail openwrt dev mailing list with a patch - how is the road to get it into github? Jan 09 17:26:27 openwrt sources are not hosted on github Jan 09 17:26:44 openwrt has its own git repository Jan 09 17:26:52 git.openwrt.org Jan 09 17:27:15 the whole process is described here - https://dev.openwrt.org/wiki/SubmittingPatches Jan 09 17:32:00 http://patchwork.openwrt.org/project/openwrt/list/ this one was the site I was looking for :) Jan 09 17:32:18 build #409 of kirkwood is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/409 Jan 09 17:39:36 Damme: the patches send to the devel list will appear automatically in patchwork Jan 09 17:44:32 build #416 of ixp4xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/416 Jan 09 20:31:30 Hi, I have a question regarding the new IPv6 config using odhcp6c: Jan 09 20:31:44 neoraider: go ahead Jan 09 20:33:42 As far as I can tell, the only way to get IPv6 config based on RA in current OpenWRT is proto dhcpv6, which sends DHCPv6 requests even when the RA have neither managed nor other config flags set Jan 09 20:33:52 Is that correct? Jan 09 20:53:02 neoraider: yes Jan 09 20:53:46 which shouldn't be problematic as it will also be successful if it doesn't find a DHCPv6 server and only has RA information Jan 09 20:53:56 it'll just wait a few seconds before applying the data in that case Jan 09 20:54:22 Well, yes, but I don't really want to spam my network with the DHCP requests Jan 09 20:56:18 zajec_ are you the same Zajec on the "Sky Wireless Booster - AirTies Air4400" thread? Jan 09 20:58:53 yup Jan 09 20:58:57 replying right now Jan 09 20:59:45 cool, hey :) Jan 09 21:12:05 neoraider: it's one small udp packet every hour ;) Jan 09 21:12:26 once the backoff is at max Jan 09 21:13:10 feel free to change /etc/sysctl.conf and reenable kernel RA parsing though if it bothers you that much Jan 09 21:13:21 then you can remove the dhcpv6 protocol section Jan 09 21:13:44 thanks zajec_ Jan 09 21:14:17 quick question, when you say "Figure out a way to find LZMA compressed kernel" and "Figure out how to find a rootfs", do you mean the existing ones in the firwmare .bin or figure out how to make new ones? Jan 09 21:14:52 Existing ones on flash Jan 09 21:15:00 Let's say we install our firmware Jan 09 21:15:03 cyrusff, actually every 20 seconds or something, if it were every hour it wouldn't bother me Jan 09 21:15:06 CFE boots our kernel Jan 09 21:15:39 neoraider: it has a backoff strategy it begins with a few seconds but will gradually go up to once per hour Jan 09 21:15:39 our kernel has to know where "kernel" is located (to allow upgrading firmware) and it has to know where rootfs is (to mount it and run userspace) Jan 09 21:15:52 That doesn't seem to work Jan 09 21:16:19 well might be that i haven't pushed the new version yet and the backoff is still at 2 minutes Jan 09 21:16:20 anyway Jan 09 21:16:41 if it bothers you as i said feel free to use sysctl.conf Jan 09 21:16:43 zajec_ ok thanks for the clarifications. I put some new addresses in the post, are they related? Jan 09 21:19:11 Atarii: i saw your post, but it doesn't really help much Jan 09 21:19:17 Atarii: you can try to find GPL sources Jan 09 21:19:23 Atarii: they have to provide them Jan 09 21:19:37 Atarii: there is a big chance that some interesting stuff will be open sourced Jan 09 21:19:38 cyrusff, I'll try the current git version; I'd really like to keep odhcp6c for proper integration into netifd and rdnss handling :) Jan 09 21:19:41 Atarii: we can look at it Jan 09 21:19:54 Atarii: or if GLP is not available, then send request for it Jan 09 21:20:04 Atarii: since you have the device, they have to provide you GPL sources Jan 09 21:20:07 yea, they have posted source for their other devices, just not this yet Jan 09 21:20:49 I'm going to hook up a serial now and get into the bootloader to investigate further Jan 09 21:21:38 I'll try and extract a kernel too from the firmware ( i think that's at 0x00060000 - 0x0042ffff) Jan 09 21:22:36 Atarii: i have a full flash dump Jan 09 21:22:43 Atarii: so that won't really help me Jan 09 21:25:36 But now we know where the kernel and rootfs are located? Jan 09 21:26:50 Atarii: but it's OpenWrt's kernel that has to know it Jan 09 21:26:57 Atarii: and it has to find it dynamically Jan 09 21:27:06 because kernel size can change as OpenWrt is being developer Jan 09 21:27:09 *developed Jan 09 21:27:28 well, kernel offset seems to be always 0x60000, OK... Jan 09 21:27:35 but it's only constant thing there Jan 09 21:28:20 ah ok. We could create an openwrt kernel, then pad it out to the same size as the current one. That was kernel address would still match Jan 09 21:46:14 cyrusff, I've tried the git master now. As long as no RAs are received, backoff works fine, but every received RA seems to trigger a DHCP solicit and reset the backoff interval Jan 10 00:06:49 build #464 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/464 Jan 10 01:29:24 build #512 of brcm63xx is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/512 Jan 10 01:40:09 build #506 of at91 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/506 Jan 10 01:42:16 build #453 of rb532 is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/453 Jan 10 01:44:22 build #453 of ppc44x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/453 **** ENDING LOGGING AT Fri Jan 10 02:59:59 2014