**** BEGIN LOGGING AT Tue Dec 23 02:59:59 2014 Dec 23 04:04:55 build #830 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/830 Dec 23 04:30:30 build #816 of ramips is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ramips/builds/816 Dec 23 07:13:38 build #754 of xburst is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/xburst/builds/754 Dec 23 08:18:25 build #724 of ar71xx is complete: Success [build successful] Build details are at http://buildbot.openwrt.org:8010/builders/ar71xx/builds/724 Dec 23 08:49:02 zinx it makes no sense to use vlan in which case?! Dec 23 11:23:03 hi Dec 23 11:23:19 did anybody see blogic? Dec 23 11:23:38 not on IRC Dec 23 11:23:42 you can e-mail him Dec 23 11:24:04 do you know if he will come on in the next days? Dec 23 11:24:12 he won't Dec 23 11:24:22 ok Dec 23 11:25:25 he was german, wasnt he? Dec 23 11:25:55 he is afaik Dec 23 11:28:28 does anybody else here got some old "fritzbox" or similar routers lying around that can be used as a external dsl modem? my new fritzbox from my provider needed to restart every few days, and not its kinda dead. i can send you money with paypal for shipping + 20€ for two old ones that you dont need anymore Dec 23 11:33:46 i would pay before you send of course Dec 23 11:48:06 julius_: guess you wouldn't be happy with a plain old dsl-360 Dec 23 11:56:09 does it do dsl 6000? Dec 23 11:57:47 like 750kbyte/s in the downstream Dec 23 13:36:03 cyrus r43771 trunk/package/network/config/netifd/Makefile * netifd: minor fixes, add mldversion option Dec 23 14:49:22 Devastator: in the case where you have only one physical port anyway. why would you want to separate one port from itself? what would that even be like? Dec 23 17:08:38 zinx it comes separate from the factory Dec 23 17:09:04 I guess it is the way the switch was designed or something Dec 23 17:16:11 Devastator: the switch is eth0, eth1 is not a switch, it's just a single port. it doesn't make sense to split a single port in to separate vlans. Dec 23 17:17:07 Devastator: swconfig is for separating ports that are physically on the same switch in to different virtual networks Dec 23 17:17:10 zinx I don't want to separate, I want to use as a trunk Dec 23 17:17:23 Devastator: then swconfig's vlans are not the right tool. Dec 23 17:17:33 Devastator: use relayd or such. Dec 23 17:17:57 Devastator: or one of the other ethernet bridging options :/ Dec 23 17:19:40 heheh Dec 23 17:20:00 (i mention relayd because luci has easy support for it, via luci-proto-relay) Dec 23 17:20:37 if you don't mind, I'm gonna ask Felix or jow, if they know if what I want is possible Dec 23 17:21:02 but I appreciate your help, really Dec 23 17:21:16 ?? Dec 23 17:21:52 maybe you should explain what you want better if that doesn't help. i assumed you wanted all ports on the same LAN Dec 23 17:22:21 (or WAN as the case may be) Dec 23 17:22:23 yes, I'm having trouble to explain my case, sorry about that Dec 23 17:22:45 try explaining what you want to do, rather than how you want to do it Dec 23 17:23:05 I want to make the WAN port a trunk port, with vlans 11, 12 and 13 tagged Dec 23 17:23:56 Devastator: what's the problem? Dec 23 17:23:58 you want WAN to have traffic from all vlans, with the tagging attached? Dec 23 17:24:17 well, the WAN port Dec 23 17:24:46 no, I want to have tagged traffic from vlans 11, 12 and 13 on the WAN port Dec 23 17:24:57 not from all vlans Dec 23 17:25:08 sorry Dec 23 17:25:21 i assumed those were all of them, my bad :) Dec 23 17:25:33 heheh Dec 23 17:25:45 in any case, that distinction doesn't change the solution Dec 23 17:25:45 my english is bad, so be patient :) Dec 23 17:25:49 nah it's fine Dec 23 17:25:50 Devastator: http://pastebin.com/9wtKKvL1 Dec 23 17:26:14 zajec is that tagged? Dec 23 17:27:06 y Dec 23 17:27:27 let me try :) Dec 23 17:27:53 but first, nature is calling.. oh boy :/ Dec 23 17:48:12 Devastator: looks like you can just use the normal bridging stuff and ensure 802.1q support is loaded and active Dec 23 17:49:06 back from the bathroom, I don't know why but I feel more light :) Dec 23 17:49:13 now, time to test :P Dec 23 17:55:40 Devastator: create bridge (i.e., br42, br-foo, whatever); add vlans to it (i.e., eth0.11, eth0.12, eth0.13), add trunk to it (i.e., eth1) Dec 23 17:56:55 you may need to twiddle some /sys stuff to get tagging included on eth1, idk Dec 23 18:17:29 or you may need to make another bridge :/ Dec 23 18:28:12 got one part working Dec 23 18:28:25 zajec thanks! Dec 23 18:28:54 np Dec 23 18:32:30 now I just need to put one of the LAN ports untagged into vlan 11.. Dec 23 18:57:52 * zajec has found interesting issue Dec 23 18:58:16 creating files/etc/init.d/foo won't cause linking it in /etc/rc.d/ Dec 23 18:58:31 big bug :) Dec 23 18:58:34 it seems only init scripts from packages will be linked Dec 23 18:59:00 build #757 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/757 Dec 23 18:59:57 isn't that normal? you should /etc/init.d/foo enable first, no ? Dec 23 19:00:15 no Dec 23 19:00:41 if you have a package and it includes init script using $(INSTALL_BIN) ./files/foo $(1)/etc/init.d/foo Dec 23 19:00:47 it will be linked automatically Dec 23 19:03:37 zajec: at least for miniupnpd that is not true Dec 23 19:07:24 stintel: where is this package? Dec 23 19:07:36 it's in openwrt-routing Dec 23 19:08:06 and I believe that was done intentionally for miniupnpd Dec 23 19:08:19 but I don't know how/where Dec 23 19:09:14 https://github.com/openwrt-routing/packages/blob/master/miniupnpd/Makefile Dec 23 19:09:23 $(INSTALL_BIN) ./files/miniupnpd.init $(1)/etc/init.d/miniupnpd Dec 23 19:09:25 looks ok Dec 23 19:09:27 I don't get it then Dec 23 19:16:05 build #810 of ppc40x is complete: Failure [failed compile_4] Build details are at http://buildbot.openwrt.org:8010/builders/ppc40x/builds/810 Dec 23 19:24:38 zajec: I just verified, did sysupgrade on my erl with an image containing miniupnpd, there are no links to miniupnpd in /etc/rc.d afterwards Dec 23 19:27:01 hm, ok Dec 23 19:27:05 but I don't understand it Dec 23 19:27:36 I think jow_laptop might know Dec 23 19:27:49 i added my "foo" script to the target/linux/bcm53xx/base-files/etc/init.d/foo and it's also linked in the /etc/rc.d/ Dec 23 20:39:57 nbd: not sure if you saw the other guy who reported the problem with rtcache on the ML, I missed that he contacted the author of that patch, the author replied off-list with an untested patch, OP replied on-list that it didn't work, but I am testing it and it seems to work for me Dec 23 20:40:43 I suspect he might have edited the kernel source directly and that got lost when rebuilding his image or so Dec 23 20:40:55 I'll test on my main router first, to be sure **** ENDING LOGGING AT Wed Dec 24 02:59:59 2014