**** BEGIN LOGGING AT Tue Nov 05 02:59:58 2013
Nov 05 05:46:41 <builder_> build #5 of mvebu is complete: Failure [failed compile_4]  Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/5
Nov 05 08:02:06 <Guest19371> luka r38649 trunk/include/target.mk * include: add more CPU flags for arm
Nov 05 08:02:09 <Guest19371> luka r38650 trunk/target/linux/imx6/Makefile * imx6: drop unused variable from Makefile
Nov 05 08:02:13 <Guest19371> luka r38651 trunk/target/linux/ (19 files in 10 dirs) * sunxi: add new target
Nov 05 08:27:24 <Guest19371> juhosg r38652 trunk/ (42 files in 32 dirs) * kernel: update 3.10 to 3.10.18
Nov 05 10:55:05 <builder_> build #6 of imx6 is complete: Success [build successful]  Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/6
Nov 05 11:01:47 <heilterminalcons> hi i have a problem with native ipv6. it seems the right routing table is not selected (http://pastebin.de/36999)
Nov 05 11:05:50 <cyrusff> ok
Nov 05 11:08:12 <cyrusff> strange issue
Nov 05 11:12:15 <cyrusff> might have something to do with your ipv6 gateway being a global address
Nov 05 11:12:33 <cyrusff> not that there is anything wrong with it but its unusual and thus might be broken atm
Nov 05 11:13:58 <cyrusff> you could try option ip6table main in you wan-section as a workaround for now
Nov 05 11:14:05 <cyrusff> this will disable the source routing
Nov 05 11:14:16 <cyrusff> ill put it on my todo
Nov 05 11:16:55 <cyrusff> or alternatively maybe simply setting the ip6gw to a link-local address might help if the router has a stable LL-address
Nov 05 11:20:59 <heilterminalcons> it doesnt work with ll-address either
Nov 05 11:21:29 <heilterminalcons> but clients behind are working :-)
Nov 05 11:23:47 <heilterminalcons> option ip6table main is working fine
Nov 05 11:24:24 <heilterminalcons> iam running keepalived on the same machine. I will try to test without later
Nov 05 11:24:54 <jow_laptop> somehow it looks like the "iif lo" ip rules are not effective
Nov 05 11:25:56 <jow_laptop> the not working ping6 is not the only problem, ipv6 tcp-reset firewall rules for example are not effective either in this failure mode
Nov 05 11:26:29 <jow_laptop> probably because the locally generated TCP RST packets do not "find" the default route either
Nov 05 11:28:22 <cyrusff> strange
Nov 05 11:28:28 <cyrusff> ummn this is on trunk right?
Nov 05 11:28:45 <jow_laptop> yes, but a custom in-house x86_64 target
Nov 05 11:28:55 <cyrusff> which kernel version?
Nov 05 11:30:33 <heilterminalcons> its 3.4.67
Nov 05 11:30:38 <heilterminalcons> with grsec
Nov 05 11:32:12 <cyrusff> ah one sec
Nov 05 11:33:34 <cyrusff> https://dev.openwrt.org/browser/branches/attitude_adjustment/target/linux/generic/patches-3.3
Nov 05 11:33:44 <cyrusff> please apply 660
Nov 05 11:34:06 <cyrusff> and if you want source routing to fully work also 665, 668 and 670
Nov 05 11:34:27 <heilterminalcons> wow
Nov 05 11:34:28 <cyrusff> that is if you care for rfc 6204 compliance
Nov 05 11:34:34 <heilterminalcons> thanks
Nov 05 11:34:36 <heilterminalcons> a lot
Nov 05 11:34:37 <heilterminalcons> !!!
Nov 05 11:35:04 <cyrusff> sure, np
Nov 05 11:35:12 <heilterminalcons> i really thought this piece were not be broken in the default kernel
Nov 05 11:36:15 <cyrusff> well 660 is already upstream but not sure in which version, we don't have this patch in trunk
Nov 05 11:36:23 <cyrusff> but not yet in 3.4
Nov 05 11:36:40 <cyrusff> the other 3 are not really needed
Nov 05 11:36:53 <cyrusff> but are required for ipv6 rfc compliance
Nov 05 11:37:00 <cyrusff> so its a nice to have
Nov 05 11:37:10 <heilterminalcons> indeed
Nov 05 13:31:45 <JyZyXEL> how do i calculate the correct memory address for ramdisk?
Nov 05 14:47:58 <Guest19371> zioproto r38653 packages/net/tinc/Makefile * [packages] tinc: Version bump to 1.0.23
Nov 05 14:54:33 <_trine> < > The Extended 4 (ext4) filesystem  should this not be selected in the kernel?
Nov 05 14:54:53 <_trine> otherwise you would not be able to use ext2 and ext3
Nov 05 14:55:08 <_trine> someone must have changed it
Nov 05 14:57:25 <_trine>  [ ] Seagate FreeAgent DockStar   and isnt selected in the kernel when you choose kirkwood in menuconfig
Nov 05 14:57:38 <_trine> should it be?
Nov 05 14:58:48 <_trine> Kaloz, ^^^^^^^^^
Nov 05 15:00:35 <Kaloz> you're booting from nand/nor probably
Nov 05 15:02:04 <_trine> from a pen drive
Nov 05 15:02:04 <Kaloz> _trine: ah I see
Nov 05 15:02:13 <Kaloz> _trine: I'll check what else luka fucked up
Nov 05 15:02:18 <_trine> hehe
Nov 05 15:02:19 <KanjiMonster> _trine: no it should not be, you are supposed t o use a device tree appended kernel
Nov 05 15:02:40 <_trine> KanjiMonster, yes but it does not do it
Nov 05 15:02:52 <KanjiMonster> the old board support shouldn't be enabled anymore, and will be gone in 3.12
Nov 05 15:03:07 <KanjiMonster> _trine: "it"?
Nov 05 15:03:18 <_trine> t o use a device tree appended kernel
Nov 05 15:03:50 <_trine> if i understand this right
Nov 05 15:03:52 <KanjiMonster> there currently isn't one built, but it shouldn't be hard to build one
Nov 05 15:04:17 <KanjiMonster> the dtb is already getting build, you just need to assemble the apporpriate uImage
Nov 05 15:04:42 <_trine> when you make choices in menuconfig that should be enough to ensure the correct values are in the kernel
Nov 05 15:04:51 <KanjiMonster> there is nothing to be done in the kernel
Nov 05 15:05:12 <_trine> KanjiMonster, if you dont then the kernel will not boot
Nov 05 15:05:18 <_trine> at the moment
Nov 05 15:05:30 <KanjiMonster> yes, because the correct image isn't built
Nov 05 15:05:43 <_trine> you have lost me now
Nov 05 15:06:12 <KanjiMonster> look at kirkwood/image/Makefile how a custom kernel is created for ib62x0 and pogo_e02 with an appended dtb
Nov 05 15:06:21 <KanjiMonster> the same needs to be done for kirkwood
Nov 05 15:06:23 <KanjiMonster> err
Nov 05 15:06:25 <KanjiMonster> dockstar
Nov 05 15:06:54 <_trine> are you saying that if i choose dockstar in menuconfig I will not build for the dockstar
Nov 05 15:07:45 <KanjiMonster> last time I checked there is no dockstar in menuconfig
Nov 05 15:08:30 <_trine> marvel kirkwood
Nov 05 15:08:36 <KanjiMonster> yes
Nov 05 15:08:59 <_trine> that has always built an image which boots on my dockstar
Nov 05 15:09:02 <KanjiMonster> currently there isn't an appropriate kernel generated for kirkwood
Nov 05 15:09:04 <KanjiMonster> err dockstar
Nov 05 15:09:14 <_trine> now it does not unless i make changes in the kernel
Nov 05 15:09:31 <_trine> thats what i am saying
Nov 05 15:09:46 <KanjiMonster> and the kernel change will not survive an update to 3.12, so it should be done the proper way now
Nov 05 15:10:01 <KanjiMonster> because an dtb appended kernel is already possible now
Nov 05 15:10:33 <_trine> what is this proper way ?
Nov 05 15:10:41 <_trine> no one tells me anything :)
Nov 05 15:10:44 <KanjiMonster> patches welome ;)
Nov 05 15:11:51 <KanjiMonster> append an dtb to the kernel like it is done for ib62x0 and pogo_e02 - look at target/linux/kirkwood/image/Makefile
Nov 05 15:12:17 <KanjiMonster> just use "dockstar" instead of ib62x0/pogo_e02
Nov 05 15:27:20 <slachta> hehe, almost everything up to date in telephony repository! :-)
Nov 05 16:02:08 <luka> _trine: could you test this patch please http://pastebin.lukaperkov.net/openwrt/20131105_0001-kirkwood-add-support-for-dockstar.patch
Nov 05 16:03:13 <luka> i have commented DOCKSTAR_UBIFS_OPTS and DOCKSTAR_UBI_OPTS because i dont know the correct values
Nov 05 16:03:52 <luka> _trine: if the patch works i can guide you so we can get the correct values
Nov 05 16:32:52 <Guest19371> juhosg r38654 trunk/package/ system/ubox/patches/0001-mount_root-fix-jffs2-handling-on-MTD-devices-emulate.patch system/ubox/patches system/ubox/Makefile * package/ubox: fix jffs2 handling on MTD devices emulated by gluebi
Nov 05 16:32:53 <Guest19371> juhosg r38655 trunk/target/linux/ ar71xx/image/ubinize-wndr4300.ini ar71xx/image/Makefile * ar71xx: generate recovery image for WNDR4300
Nov 05 16:33:28 <stintel> woot
Nov 05 16:58:13 <_trine> luka, yes I have just got back to my KB
Nov 05 17:10:58 <Guest19371> hauke r38656 trunk/target/linux/brcm47xx/patches-3.10/075-MIPS-BCM47XX-fix-detection-of-some-boards.patch * brcm47xx: fix detection of Asus RT-N12B1 and Netgear WNR3500L
Nov 05 17:47:58 <Guest19371> kaloz r38657 trunk/target/linux/generic/patches-3.12/203-kallsyms_uncompressed.patch * [generic/3.12]: update for 3.12 final
Nov 05 17:52:33 <JyZyXEL> wiki editing gives me: Error 403 We're sorry, but we could not fulfill your request for /doku.php on this server. You do not have permission to access this server. Before trying again, close your browser, run anti-virus and anti-spyware software and remove any viruses and spyware from your computer.
Nov 05 18:19:34 <jow_laptop> JyZyXEL: pm me your current ip, maybe you're on the blocklist
Nov 05 18:42:14 <jow_laptop> JyZyXEL: nope, not on the blocklist
Nov 05 18:42:58 <Guest19371> juhosg r38658 trunk/target/linux/ar71xx/image/Makefile * ar71xx: image: allow to use optional parameters for MkuImageLzma/initramfs
Nov 05 18:42:59 <Guest19371> juhosg r38659 trunk/target/linux/ar71xx/image/Makefile * ar71xx: image: fix WNDR4300 initramfs image generation
Nov 05 18:44:03 <JyZyXEL> seems to work on my other browser
Nov 05 18:46:47 <JyZyXEL> jow_laptop: looks like it was some sort of cookie based problem
Nov 05 18:46:55 <JyZyXEL> after clearing my cookies it started working
Nov 05 18:47:14 <jow_laptop> JyZyXEL: yes, this is possible. the 403 you've seen is cause by the bad behaviour heuristics
Nov 05 19:39:16 <tripolar> hi
Nov 05 19:39:39 <tripolar> is there a way to use the "wifi" key on my wndr3800 to execute a command when its pressed?
Nov 05 19:39:50 <tripolar> are these key allready handeld somwhere?
Nov 05 19:40:03 <tripolar> key/keys
Nov 05 19:44:31 <builder_> build #399 of ppc44x is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/399
Nov 05 20:13:45 <tripolar> Hauke: do you know how to configure then buttons on a wndr3800? or is button support for this device not implemented?
Nov 05 20:29:52 <tripolar> blogic: do you know i could make another button work? wnd3800 has two front buttons one of it is BTN_2 the other one isn't recognized as it seems - i created scripts for BTN0-9
Nov 05 20:30:18 <tripolar> BTN_[0-9]
Nov 05 20:33:19 <tripolar> okay found it, it's wps
Nov 05 20:37:13 <blogic> cool
Nov 05 21:47:25 <builder_> build #433 of orion is complete: Failure [failed compile_8]  Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/433
Nov 05 23:30:54 <tripolar> hi
Nov 05 23:31:53 <slachta_> hi
Nov 05 23:36:10 <tharvey> looks like wifi interfaces are not being brought up on boot in trunk... I think the issue has been around a while - is this a known issue?
Nov 05 23:36:55 <tharvey> (I have a simple config with an mac80211/ath9k ap configured in network interface bridged with eth0 - eth0 comes up but wlan0 does not)
Nov 05 23:37:04 <tharvey> until I run 'wifi'
Nov 05 23:38:18 <tripolar> can someone tell me why no-ripemd is added to the OPENSSL_NO_CIPHERS in the openssl Makefile? if this cipher is broken on a target could it please be added conditionally, as ripemd is needed to get erlang compiled with openssl support and i'd like to push the update
Nov 06 01:28:16 <builder_> build #372 of sibyte is complete: Failure [failed shell_12]  Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/372
Nov 06 01:37:38 <builder_> build #412 of uml is complete: Failure [failed compile_5]  Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/412
Nov 06 02:59:08 <swalker> tripolar: library size considerations?
**** ENDING LOGGING AT Wed Nov 06 02:59:58 2013