**** BEGIN LOGGING AT Sat Dec 21 02:59:59 2013 Dec 21 04:29:55 build #426 of ar7 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/ar7/builds/426 Dec 21 05:42:19 build #401 of xburst is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/401 Dec 21 10:03:02 build #351 of ep93xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ep93xx/builds/351 Dec 21 13:28:40 build #344 of adm5120 is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/adm5120/builds/344 Dec 21 13:33:49 jow r39152 trunk/package/network/ services/dnsmasq/files/dnsmasq.init services/dnsmasq/Makefile services/dnsmasq/files/dnsmasq.hotplug * dnsmasq: rework init procedure Dec 21 13:39:41 build #325 of mpc52xx is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/mpc52xx/builds/325 Dec 21 13:42:00 build #434 of rb532 is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/434 Dec 21 13:43:54 build #434 of ppc44x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/434 Dec 21 13:50:07 jow r39153 trunk/package/system/opkg/Makefile * opkg: switch to git repository (#14655) Dec 21 13:58:18 jow r39154 branches/attitude_adjustment/package/opkg/Makefile * AA: opkg: merge r39153 Dec 21 14:51:32 build #460 of lantiq is complete: Failure [failed shell_7 compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/460 Dec 21 17:23:01 nbd: little question. The rtl8306 switch need a mask to work properly. am i right? Dec 21 17:23:52 like in the linksys wrt160nl Dec 21 18:12:00 swalker: Who deals with commit access requests these days? Mailed Kaloz on 16th Dec, but got no reply... Dec 21 18:16:09 jmccrohan: I'm not sure but that sounds typical Dec 21 18:40:27 sirs Dec 21 18:40:33 why #openwrt is secret ? Dec 21 18:40:58 could you please consider removing +s channel mode, so people could find the channel on the list Dec 21 18:41:10 shhhhh! Don't tell anybody about it! Dec 21 18:41:29 thanks.. i wonder why "/msg alis list *wrt*" doesn't show that channel Dec 21 18:44:43 i wont no worries Dec 21 18:44:54 i can keep secrets :P Dec 21 18:51:18 hi Pteridium Dec 21 18:51:30 hi Dec 21 18:51:40 is there any news about solos Dec 21 18:51:47 conexant thing Dec 21 18:51:52 no Dec 21 18:52:55 and i don't have the skills to port it to backfire Dec 21 18:53:24 in addition, the bootloader is a problem Dec 21 18:53:58 me neither Dec 21 18:54:04 yea fuck it Dec 21 18:55:01 yes Dec 21 18:55:08 thats a pity Dec 21 18:56:21 there are a lot of socs that cannot be ported because the developers can't do more Dec 21 18:57:00 simply they do his best Dec 21 18:57:57 AngryAlien: have you experience porting linux and drivers? Dec 21 19:00:01 build #434 of x86 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/x86/builds/434 Dec 21 19:02:46 build #404 of sibyte is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/404 Dec 21 19:34:04 build #446 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/446 Dec 21 19:45:06 nbd r39155 trunk/package/network/services/hostapd/patches/510-wpa_supplicant_p2p_parse_ifcomb.patch * wpa_supplicant: fix interface combination parsing issues Dec 21 20:02:53 build #471 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/471 Dec 21 20:24:52 all, I need some advice on the expected behaviour of swconfig/driver regarding untagged ports and the port pvid Dec 21 20:26:06 first, how should swconfig and the driver behave if a user tries to leave a port untagged in multiple vlans? Dec 21 20:26:47 and second, if a port is not untagged in any vlans, what should its pvid be? Dec 21 20:31:00 usually it stays at 0 or takes the vid of the first assigned vlan (some switched treat pvid 0 as an invalid state and stop working) Dec 21 20:32:04 and having more than one vlan untagged is technically allowed for 802.1Q, but there is no requirement for it to be supported Dec 21 20:41:57 thanks, I guess I need to to a bit more reading on multiple untagged vlans Dec 21 20:42:29 so far I'm finding some strong opinions like this one: "Multiple untagged VLANs violates the laws of physics." :) Dec 21 20:46:55 vampo: switch internally, all traffic is tagged, the question is just a) keep the tag or strip it when sending the packets out; and b) if an incoming frame does not have a vlan tag, use which vid for generating one Dec 21 20:47:47 so there is no problem on stripping the tag on more than one vlan, but all the incoming traffic can only go to one of the vlans (usually the pvid sets the vid for the generated tag) Dec 21 20:53:29 so if I understand correctly a PC connected to a port with untagged vlan 5 and 10 can access both vlans? Dec 21 20:54:06 vampo: yes and no, and it depends on the switch Dec 21 20:54:23 vampo: it can receive from vlan 5 and 10, but it can only send to one of them Dec 21 20:56:01 well, it can do by sending the traffic tagged, but it can't know if a received untagged frame came from vlan 5 or vlan 10 Dec 21 20:56:23 I'm sure there is some obscure use case where this makes sense Dec 21 20:57:03 hehehe that's exactly what I'm trying to imagine! in what case that would be usefull Dec 21 20:58:03 KanjiMonster: excuse me, ¿is spu the hardware crypto? Dec 21 20:58:12 Pteridium: yes Dec 21 20:58:40 good! Dec 21 21:00:32 found on 6368, 6362 and 63268 (but not 63168) Dec 21 21:00:55 and has a gpl/bsd driver since 4.12.04 Dec 21 21:03:50 KanjiMonster: http://entrechips.blogspot.com.es/2013/03/ont-i-240g-b-movistar-alcatel-lucent.html Dec 21 21:04:10 the guy that hava this board is a colleague Dec 21 21:04:19 have* Dec 21 21:04:34 bcm6818based Dec 21 21:05:55 Do you want to ask him to test owrt on it? Dec 21 21:07:05 well, i ask him, of course Dec 21 21:07:53 I have got myself a bcm... oh, bcm6818. misread that as 6318. Dec 21 21:08:36 :) Dec 21 21:09:35 vampo: see http://standards.ieee.org/getieee802/download/802.1Q-2011.pdf p. 126 , Note 1: "In other words, it is possible to configure any VID as untagged on egress, but it is not necessarily possible to configure more than one VID as untagged on egress. It is an implementation option as to whether only a single untagged VID per Port on egress is supported, or whether multiple untagged VIDs per Po Dec 21 21:09:38 rt on egress are supported." Dec 21 21:11:18 Pteridium: well, bcm6318 is a quite a different beast, and will require modifications to the current code base Dec 21 21:12:25 difficult modifications? Dec 21 21:13:30 i mean: need rewrite of drivers and other stuff? Dec 21 21:15:03 yes Dec 21 21:15:26 KanjiMonster: thanks. I'll try to test this and see what the switch can handle Dec 21 21:15:27 not rewrite, but they need to be adapted, and a bit more than when usually adding a 63xx board Dec 21 21:15:33 build #34 of mxs is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/mxs/builds/34 Dec 21 21:16:31 i'll ask him; maybe i can do a little part of the job :$ Dec 21 21:17:06 and that kind of answers another question. If the PVID is made to follow the vlan membership, why is the explicit set necessary... Dec 21 21:17:50 thanks for the input Dec 21 21:23:35 build #457 of ppc40x is complete: Failure [failed shell_14] Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/457 Dec 22 00:02:02 build #459 of cobalt is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/cobalt/builds/459 Dec 22 00:02:10 build #352 of iop32x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/iop32x/builds/352 Dec 22 00:28:12 build #461 of lantiq is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/lantiq/builds/461 Dec 22 00:50:45 build #35 of mvebu is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/mvebu/builds/35 Dec 22 00:52:10 build #35 of imx6 is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/imx6/builds/35 Dec 22 01:52:13 build #414 of avr32 is complete: Failure [failed shell compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/414 **** ENDING LOGGING AT Sun Dec 22 02:59:59 2013