**** BEGIN LOGGING AT Fri Dec 27 02:59:58 2013 **** BEGIN LOGGING AT Fri Dec 27 06:01:12 2013 Dec 27 07:11:42 build #396 of kirkwood is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/kirkwood/builds/396 Dec 27 08:12:20 build #407 of xburst is complete: Failure [failed compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/407 Dec 27 08:13:48 build #357 of ep93xx is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/357 Dec 27 08:24:27 build #386 of au1000 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/au1000/builds/386 Dec 27 08:58:19 build #403 of ixp4xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ixp4xx/builds/403 Dec 27 13:15:28 nice talk of nbd @ 30C3 Dec 27 13:16:47 yes :-) (videostream: http://streaming.media.ccc.de/saalg/native/hq/) Dec 27 13:46:03 build #386 of ar71xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/386 Dec 27 14:48:39 rundfreifunk, plntyk, yes thx nbd :) Dec 27 14:59:15 nbd, cool talk! are you still around for a chat? Dec 27 15:29:01 <_rmk_> boo! Dec 27 15:29:31 <_rmk_> blogic: linksys ag241 - should 12.09 be reachable after flashing via 192.168.1.1 ? Dec 27 15:30:21 <_rmk_> I have the red/green flashing LED but it doesn't seem to respond on that ip... unlike 8.09.2 did Dec 27 15:51:23 build #331 of mpc52xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/331 Dec 27 15:51:55 <_rmk_> yea, 8.09.2 works, 10.03.1 and 12.09 appear not to Dec 27 15:59:44 build #466 of lantiq is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/466 Dec 27 16:02:17 build #315 of octeon is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/315 Dec 27 16:05:56 build #440 of rb532 is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/440 Dec 27 16:08:44 build #440 of ppc44x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/440 Dec 27 16:41:44 <_rmk_> gah, this is proving impossible Dec 27 16:42:13 <_rmk_> how do you configure pppoa under openwrt? and don't say look at http://wiki.openwrt.org/doc/uci/network#protocol.pppoa.ppp.over.atm.aal5 because it doesn't appear to work Dec 27 16:43:08 <_rmk_> I just seem to have lo, eth0 and br-lan interfaces, despite having /proc/avalanche and that showing that the adsl has trained Dec 27 18:47:52 falstaff_: i'm in the freifunk corner now Dec 27 19:47:50 nbd, wo ist der? :-) Dec 27 20:06:19 <_rmk_> okay, getting really frustrated with this Dec 27 20:06:28 falstaff_: halle 3, erster stock Dec 27 20:06:30 <_rmk_> does 'config' in /etc/config/network need to have a 3rd argument? Dec 27 20:06:42 <_rmk_> for example, why doesn't this work: Dec 27 20:06:45 <_rmk_> config route6 Dec 27 20:06:47 <_rmk_> option interface lan Dec 27 20:06:49 <_rmk_> option target 2001:4d48:ad52:3200::/56 Dec 27 20:06:51 <_rmk_> option gateway fe80::214:fdff:fe10:1be7 Dec 27 20:06:53 <_rmk_> config route6 Dec 27 20:06:56 <_rmk_> option interface lan Dec 27 20:06:58 <_rmk_> option target fd8f:7570:feb6::/48 Dec 27 20:07:01 <_rmk_> option gateway fec0::214:fdff:fe10:1be7 Dec 27 20:07:05 <_rmk_> the first gets installed, but the second doesn't Dec 27 20:07:15 <_rmk_> ah, hang on. Dec 27 20:07:29 <_rmk_> how did that end up fec0 Dec 27 20:08:01 * _rmk_ fixes, and reboots it Dec 27 20:08:13 :D I'm sure we are all glad we could help Dec 27 20:10:52 <_rmk_> just to make sure - it's not possible to bridge the pppoa onto the ethernet sanely if the ethernet segment also has other traffic on? Dec 27 20:11:10 <_rmk_> eg, to run pppoe on a machine behind openwrt Dec 27 20:14:57 if openwrt already has a working connection, I see no reason another ppp can't be opened from behind it Dec 27 20:15:14 or are we talking about a single ppp? Dec 27 20:16:41 pppoa can't be bridged Dec 27 20:16:47 because it's on atm, not ethernet Dec 27 20:17:13 there would have to be a pppoa to pppoe converter Dec 27 20:17:19 but i'm not aware of any such implementation Dec 27 20:18:44 <_rmk_> so, if you have to use pppoa over adsl you have to terminate the ppp connection at the modem Dec 27 20:19:19 yes Dec 27 20:20:35 <_rmk_> I'm in the perverse situation where I now have FTTC _and_ ADSL1 and ADSL1 is faster than FTTC despite the line being 0.5 miles longer Dec 27 20:20:43 <_rmk_> the ADSL1 line being 0.5 miles longer Dec 27 20:21:50 <_rmk_> we're talking about the fttc line being vdsl2 and 0.8 miles, doing only 5mbps vs the adsl1 line being 1.3 miles and doing around 7.5mbps Dec 27 20:21:53 <_rmk_> go fibure Dec 27 20:21:54 <_rmk_> figure Dec 27 20:22:42 <_rmk_> so I'm now having to pick my way through working out how to get the config I'm currently using with the fttc back onto the adsl1 line, and since it now carries ipv6 on that config which I'm not wanting to lose Dec 27 20:23:33 have you tried the supplied modem on the VDSL line? Dec 27 20:23:57 if it's not a bad copper pair, it may be your supplier is usin vectoring Dec 27 20:25:03 <_rmk_> you mean the BT supplied Huawei modem? that gets 5.7mbps. My draytek gets almost 10mbps but draycrap is full of bugs in the ip stack / dns transproxy / pppoe bridge Dec 27 20:25:36 <_rmk_> so I'm scrapping the idea of using the fttc line altogether until I can find a different vdsl2 modem for it Dec 27 20:30:27 I would check if the Huawei has the latest firmware Dec 27 20:30:53 from what I see, BT is doing vectoring pilots already Dec 27 20:30:58 <_rmk_> it's a locked down thing Dec 27 20:31:58 have you tried leaving it online overnight for a few nights? Dec 27 20:33:36 you could also plug it in and call the help desk. They could trigger an upgrade if you are not up to date Dec 27 20:34:08 or at least they should be able to :) Dec 27 20:34:52 <_rmk_> as far as BT are concerned, 5.7mbps is what my line supports and that's that. Dec 27 20:43:51 <_rmk_> haha, yes I can. Dec 27 20:43:51 <_rmk_> Access-Concentrator: bras-red3.l-wat-B2224060702021 Dec 27 20:43:54 <_rmk_> AC-Ethernet-Address: 00:16:b6:c4:c5:f3 Dec 27 20:44:36 <_rmk_> setup an atm bridge to create the nas0 device Dec 27 20:44:42 <_rmk_> bring that interface up Dec 27 20:44:58 <_rmk_> run rp-pppoe-relay: pppoe-relay -C br-lan -S nas0 Dec 27 20:46:10 <_rmk_> and it works. Dec 27 20:51:59 <_rmk_> now just need to work out how to get openwrt to set this up on boot automatically Dec 27 20:52:10 _rmk_: you can actually bridge nas0 Dec 27 20:52:33 _rmk_: so you're not using pppoa, but pppoe over atm Dec 27 20:53:49 <_rmk_> doesn't that result in all traffic seen at the bridge being forwarded up the adsl line? Dec 27 20:55:56 yes, but normally you want to bridge pppoe to a separate interface, maybe a separate vlan or something Dec 27 20:57:16 <_rmk_> my main concern at the moment is getting the fttc line off the bt supplied modem and onto the draytek so it doesn't get a ~6mbps cap placed on it Dec 27 20:57:33 <_rmk_> ... which will be very difficult to remove Dec 27 21:09:29 <_rmk_> yes, that works from boot :) Dec 27 21:17:17 blogic r39168 trunk/target/linux/ramips/patches-3.10/999-raeth_fixes.patch * ralink: fix tso regression in the ethernet driver Dec 27 21:17:34 blogic r39169 trunk/package/base-files/ files/lib/upgrade/common.sh files/etc/init.d/boot files/etc/init.d/umount files/lib/functions.sh * base-files: fix mount-utils incompatibility Dec 27 21:17:46 blogic r39170 trunk/package/network/ config/swconfig/src/uci.c config/swconfig/src/cli.c config/swconfig/src/swlib.c * swconfig: remove useless variables, return -1 on errors Dec 27 21:17:57 blogic r39171 trunk/tools/firmware-utils/src/buffalo-lib.c * firmware-utils: check_magic() in buffalo-lib.c always return 0 Dec 27 21:29:58 build #483 of brcm47xx is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/brcm47xx/builds/483 Dec 27 22:08:00 build #493 of at91 is complete: Failure [failed compile_9] Build details are at http://buildbot.openwrt.org:8010/builders/at91/builds/493 Dec 27 22:10:37 build #410 of sibyte is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/410 Dec 27 22:11:27 build #452 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/452 Dec 27 23:31:04 build #499 of brcm63xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/brcm63xx/builds/499 Dec 27 23:40:17 heil r39172 packages/net/haproxy/ Makefile patches/0011-BUILD-proto_tcp-remove-a-harmless-warning.patch * package haproxy: fix gcc 4.7 warning Dec 27 23:48:42 build #477 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/477 Dec 27 23:53:45 build #475 of atheros is complete: Failure [failed shell_19] Build details are at http://buildbot.openwrt.org:8010/builders/atheros/builds/475 Dec 28 00:37:30 build #40 of mxs is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mxs/builds/40 Dec 28 00:39:53 build #358 of iop32x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/358 Dec 28 01:02:13 build #420 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/420 Dec 28 01:16:48 build #467 of lantiq is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/467 Dec 28 02:07:33 build #41 of mvebu is complete: Failure [failed shell_7 compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/41 **** ENDING LOGGING AT Sat Dec 28 02:59:58 2013