**** BEGIN LOGGING AT Sat Nov 24 02:59:57 2007 Nov 24 12:00:02 I would like to welcome everyone to the November issue of WIP-Day ;-) Nov 24 12:00:59 I've a couple of days ago posted a set of topics (on the -devel mailing-list): Nov 24 12:01:27 - How is it cominmg along with the OpenWrt MediaCenter Edition? Nov 24 12:02:36 - I'll personally take a longer lasting look at 'WDS' (does it work or not with 7.09 and WPA)? Nov 24 12:03:48 - and perhaps it would be a good opportunity to make a list of wishes and suggestions for the next release (which probably will be 7.12)? Nov 24 12:04:46 Anybody who has things to add - feel free to join them to the list Nov 24 12:06:04 * glp_home is going of to have lunch Nov 24 12:29:13 slapin: have you extracted that rome loader yet? Nov 24 13:07:37 Wish-list: what features or functions are missing in OpenWrt (what should the future bring)? Nov 24 14:50:56 * glp_home did just finish something with wood and an electric drill (and it was fun) Nov 24 15:26:43 glp_home: Hi. Nov 24 15:27:26 I'll be around on-and-off for the rest of today (GMT) Nov 24 15:34:50 Might have a go at getting the hostapd patches for nl80211 merged, if they haven't already been... Nov 24 15:35:47 'lo Nov 24 15:36:23 glp_home: I want to look into the current mediacenter soundproblem today Nov 24 15:52:43 OK - so they have been merged already... Nov 24 16:02:46 noz: i had access point mode working with an asus wl-500gd Nov 24 16:02:48 well, somewhat working Nov 24 16:02:57 i think it used the wrong antenna for transmitting frames Nov 24 16:03:06 so i got a very weak signal Nov 24 16:12:17 loswillios what's the problem with the sound? Nov 24 16:12:29 build fails Nov 24 16:12:55 https://dev.openwrt.org/ticket/2715 Nov 24 16:14:28 most likely a missing dependency Nov 24 16:14:39 either a real package dependency or a missing KCONFIG assignment Nov 24 16:15:02 you should review the dependencies between sound modules Nov 24 16:18:56 ok Nov 24 16:56:42 * glp_home thinks a Club-Mate moment has arrived :o) Nov 24 17:41:54 I'm looking for the wl binary with afterburner (gmode 6) enabled. Nov 24 17:46:16 minor wish list item: a lighter-weight tcpdump package. tcpdump would seem to be very useful but it is quite fat. Best guess is that a bunch of code that analyzes less important protocols could be configured out. Nov 24 17:46:25 * dhr ducks and runs for lunch Nov 24 17:46:34 dhr: feel free to make a patch Nov 24 17:47:47 dhr: can be really difficult to decide what protocols are less important? Nov 24 17:48:08 nbd, dhr: think it would be the best if it's configureable via menuconfig Nov 24 17:48:20 not all protocols individually Nov 24 17:48:25 i don't want to bloat up menuconfig Nov 24 17:48:49 we could add a distinction between tcpdump-mini and tcpdump-full Nov 24 17:49:09 nbd: also think it's better to keep it on the package "level" Nov 24 17:49:28 although we should probably only remove things that really few people actually need Nov 24 17:49:50 e.g. obsolete protocols like appletalk or ipx Nov 24 17:50:54 nbd: appletalk is not obsolete - maybe un-used and decadent - but for historical reasons extremely important :o) Nov 24 17:51:15 for historical reasons == obsolete Nov 24 17:51:16 :) Nov 24 17:51:30 especially if it's unused Nov 24 17:54:51 :) Nov 24 18:03:06 I'm right now taking a look at WDS - mainly looking through the relevant threads in the forum Nov 24 18:30:08 wds - first couple of attempts did not work :/ Nov 24 18:45:11 anybody know if the wds-router should have 'lan' or 'wifi' in 'option network' (it is quite unclear in the threads I'm reading)? Nov 24 18:46:27 glp_home: are you trying bridged or routed wds ? Nov 24 18:47:13 wds is this? http://en.wikipedia.org/wiki/Wireless_Distribution_System Nov 24 18:48:37 dhr: Theoretically but as it is not properly standardised all that is really useful is http://madwifi.org/wiki/AboutWDS Nov 24 18:50:11 I've simply (for a starter) been following http://forum.openwrt.org/viewtopic.php?id=13467 Nov 24 18:50:35 as a way to figure out if those threads are correct Nov 24 18:51:31 there is furthermore this entry: http://forum.openwrt.org/viewtopic.php?id=11472 Nov 24 18:52:38 but what I'm trying is to think the basic situation: I have an AP (connected to an adsl) and I need to extend my coverage Nov 24 18:53:29 I have a second router, someone told me to use WDS - and can I now make it work if i read the forum postings? Nov 24 18:54:08 work in such a way that i get a connection between the 2 devices (at first without encryption) Nov 24 18:55:52 so - i'm basicly trying to figure out what the wireless config files should look like Nov 24 18:57:32 h3sp4wn: sounds like you have an interesting question with the bridged or routed? Nov 24 19:01:54 I must be trying to create routed WDS (repeating), so that I can connect to the network via a laptop Nov 24 19:02:57 glp_home: afaik my question only applies with madwifi (broadcom is different and I never yet used it) Nov 24 19:04:06 h3sp4wn: should probably have mentioned that i decided first to try it with brcm, and then later add a fonera to the setup (atheros = madwifi) Nov 24 19:09:51 glp_home: I think broadcom (when it is bridged) just works (no messing with the firewall etc) the fonera you will have to use the multi ssid stuff (one in either bridged or routed client mode) using option wds 1 and another in ap mode Nov 24 19:12:46 h3sp4wn: i can say: no instant success with brcm Nov 24 19:14:02 reading through the forum posts, i get this general structure: 1. setup one device as standard router (ap mode) Nov 24 19:16:11 2. setup second device in wds mode, change 'option mode' from 'lan' to 'wds' and enter an extra line: 'option bssid "mac-adress of device 1" Nov 24 19:17:44 3. probably a good idea to give second device an ip-adress which ends on something different from '.1' (but the ip- range should be the same as the ap device) Nov 24 19:18:36 point 3, is done in the 'network' file Nov 24 19:20:15 4. in 'wireless' file edit the 'option ssid' to the same as the ap with an added -wds Nov 24 19:20:39 5. reboot both devices - and then it should work Nov 24 19:20:53 6. nothing works :/ Nov 24 19:29:13 glp_home: 2. doesn't make sense (as it is change option mode ap to option mode wds) Nov 24 19:29:37 for bridged it shouldn't need an ip Nov 24 19:30:59 I only know about madwifi -> madwifi though so its possible anything I am telling you is useless Nov 24 19:34:01 nbd, ping Nov 24 19:34:05 pong Nov 24 19:37:45 h3sp4wn: i have confidence in you, and nothing is useless (i'll just go to the other room and talk ahrd words to a device, which is misbehaving) Nov 24 19:39:31 nbd, any reason why pppd doesnt read /etc/ppp/chap-secrets? Nov 24 19:39:50 is chap enabled? ;) Nov 24 19:39:58 i think sometimes ppp defaults tp pap Nov 24 19:40:08 hmm Nov 24 19:41:58 compile or commandline option? Nov 24 19:42:16 command line Nov 24 19:52:19 nbd, hmm no support for MS-CHAPv2? Nov 24 19:52:32 dunno Nov 24 20:05:23 this wds setup attempt has yet again failed :( Nov 24 20:39:29 * glp_home needs to get more intoxicated before further attempts at 'wds' will take place Nov 24 21:27:22 {Nico}: ping Nov 24 21:36:49 dhr: ping Nov 24 21:46:52 glp: pong Nov 24 21:47:04 dhr: hola Nov 24 21:47:50 I've been doing non-OpenWWRT things today mostly. Nov 24 21:48:05 this wds concept is either a fairytale, to complicated or perhaps to easy Nov 24 21:48:23 nothing wrong with having doing other things Nov 24 21:48:47 wds is typically easy Nov 24 21:48:58 for most drivers it's just a point to point link between aps Nov 24 21:49:11 but one that supports full 802.3 addressing Nov 24 21:49:14 so you can bridge it Nov 24 21:49:40 nbd: but where is the trick to make it happen? Nov 24 21:50:38 why does it depend on the wireless chipset? Is some of it done in "hardware"? Nov 24 21:51:06 dhr: wds is not standardized. different drivers implement wds differently Nov 24 21:51:11 glp: ? Nov 24 21:51:35 * dhr breaks shrinkwrap on his new wl-500gP Nov 24 21:52:08 nbd: I'm just looking for the correct entries in the config files Nov 24 21:52:26 a wds link is configured with a separate wifi-iface Nov 24 21:52:31 and option mode wds Nov 24 21:52:51 and option bssid Nov 24 21:53:24 nbd: on both devices (the various threads in the forum are very unclear in this respect)? Nov 24 21:53:40 yes Nov 24 21:54:29 nbd: i did try the setup as just mentioned (on brcm-2.4) - and it did not work Nov 24 21:54:40 did you have a separate wifi-iface for ap mode as well? Nov 24 21:54:44 the broadcom driver might require this Nov 24 21:54:54 also using wpa on it might be broken, i'm not sure Nov 24 21:55:44 no, i did not have a separate wifi-iface for ap - but also no encryption Nov 24 21:55:51 ok, try to add it Nov 24 21:56:09 nbd: ok Nov 24 21:56:17 :) Nov 24 21:56:44 dhr: those 500gp are nice Nov 24 21:56:57 orange lights and all Nov 24 21:58:49 have not turned it on yet. Reading the "quick start guide". 200 pages! Luckily only 18 in English. Nov 24 22:01:07 dhr: you need to read about how to get it into diag-mode - and then tftp the .trx file + wait more than 6 minuts before you reboot it Nov 24 22:01:59 no GUI button to upgrade firmware? How crude. Nov 24 22:03:07 dhr: there is, but it normally doesn't work with non-asus images. take a look at: http://wiki.openwrt.org/OpenWrtDocs/Hardware/Asus/WL500GP Nov 24 22:16:59 on the wl-500f Premium page there seems to be reference to Atheros. How come? I thought it used Broadcom BCM4318. Guess: some folks replace the BCM4318 with Atheros to get closer to an open driver. Nov 24 22:17:11 correct Nov 24 22:17:13 s/500f/500g Nov 24 22:24:57 not much luck Nov 24 22:25:02 :( Nov 24 22:25:59 nbd: should the page not say that? I've just edited it to do so. (new section just after hardware: info. Could you check and improve it? Nov 24 22:26:53 look sok Nov 24 22:26:57 looks ok Nov 24 22:28:19 nbd: section on ASUS web GUI says "TRX utility needs a rewrite" and references you on IRC. Is there a trac entry? If so, this page should point to it. If not, there should be one, I'd say. Nov 24 22:37:25 Is there an IRC log where I could look up what nbd said on 2007 September 1? Nov 24 22:37:48 http://openwrt.org/logs/ Nov 24 22:44:12 nbd: thanks. The relevant part seems to be at 18:15. I don't understand from this what needs to be changed in trx utility. Can you explain? Nov 24 22:44:44 asus has a few extra bytes in the trx format to identify the model for the web interface Nov 24 22:44:51 there is an implementation of this already Nov 24 22:44:56 look for asustrx.c Nov 24 22:45:05 don't have a link right now Nov 24 22:45:08 kind of like the motorola-bin utility that I hacked on? Nov 24 22:45:43 i think the asus trx format has an extra trailer instead of an extra header Nov 24 22:45:46 not sure, though Nov 24 23:04:58 crazy_imp * r9595 /packages/libs/apr-util/Makefile: add missing libuuid dependency Nov 24 23:11:42 my google hits for asustrx.c seem to be in freewrt. For example: http://osdir.com/ml/embedded.freewrt.cvs/2006-09/msg00226.html Nov 24 23:15:37 nbd: should openwrt just copy that bit of freewrt? What are the political ramifications? The freewrt code seems to be GPLed. Nov 24 23:15:52 can copy it, no problem Nov 24 23:16:12 there are no political issues there Nov 24 23:17:19 am I missing something obvious? Is this already somewhere in OpenWRT? Nov 24 23:17:53 i don't think we use it yet Nov 24 23:18:25 Then I think I'll try it out by hand. Nov 24 23:24:45 Hmmm. Freewrt got rid of asustrx.c and folded the functionality into trx.c. 2006 Sept 29. https://www.freewrt.org/trac/search?q=asustrx&wiki=on&changeset=on&ticket=on Nov 24 23:25:20 nbd: is that the way OpenWRT should do it? (Maybe it has; looking.) Nov 24 23:26:32 i don't think it should be in trx.c Nov 24 23:26:47 since it's just a trailer with no crc or anything, it could theoretically even be generated by a shell script Nov 24 23:29:30 interesting -- the asustrx.c program does compute CRC. I guess it is just used for the normal TRX header. Nov 24 23:29:35 * dhr off to dinner Nov 24 23:32:10 yep Nov 25 00:55:21 nbd: ping Nov 25 00:55:28 pong Nov 25 00:56:11 Should I expect the Wireless LED to work with b43 on a WRTSL54GS? It did work with the old brcm43xx driver (at least came on when the i/f came up) Nov 25 00:56:53 dunno Nov 25 00:57:30 OK. np - just trying to work out whether I need to fix the i/f coming up, or the driver getting the LED to work! **** ENDING LOGGING AT Sun Nov 25 02:59:56 2007