**** BEGIN LOGGING AT Tue Sep 22 02:59:57 2009 Sep 22 06:44:51 Buongiorno! Sep 22 07:29:36 xMff: I precompiled it Sep 22 07:29:47 Using the luac that was compiled with -O1 Sep 22 07:35:25 Presumably even with -O1 luac is miscompiled, and in turn miscompiles the lua code Sep 22 07:35:44 Or something else went wrong, I'm not entirely sure Sep 22 07:41:45 But if luac was faulty, that would probably also explain why SSH didn't come up (since that is handled by some lua script as well, right?) Sep 22 07:43:41 Or actually, from the development wiki page I learn that selecting developer mode in menuconfig doesn't work? That I have to uncomment some option in some config file (config/registered) as well? Why is that? Sep 22 07:43:54 Also, I don't have that config file :-) Sep 22 07:58:45 But that would explain why SSH didn't work Sep 22 07:59:04 Still doesn't explain why my failsafe image won't work, unless the stock fonera's don't have a valid failsafe image? Sep 22 08:00:09 Is there any particular reason content is split between the fon wiki and the fon trac wiki? I'm seeing some duplicate content and content that would be better placed elsewhere, but this fragmentation doesn't seem to serve any purpose... Sep 22 08:15:16 blathijs: yes, you need to uncomment a line in the buildroot to enable the developer mode Sep 22 08:15:41 iurgi: Why? Sep 22 08:24:41 blathijs: hmmm Sep 22 08:24:45 it works like that Sep 22 08:24:46 hehe Sep 22 08:24:57 well, it's basically because it's a configuration option Sep 22 08:25:06 that file exists on both normal and developer mode Sep 22 08:25:23 and it doesn't make much sense to add a rule to the Makefile specifically for that Sep 22 08:25:38 it's a small change that anyone able to compile the buildroot should be able to do Sep 22 08:33:23 iurgi: Yeah, but I'm not so sure if it's documented in the right place Sep 22 08:33:51 iurgi: Also, if the enduser / developer option in menuconfig doesn't work, why is it there? I'd remove it to prevent confusion Sep 22 08:40:15 yes, I didn't know it was there Sep 22 08:40:26 but indeed, if it doesn't work it should be removed Sep 22 08:40:41 (I'm talking about flipper, btw, haven't looked at trunk) Sep 22 08:41:26 iurgi: Any suggestions on regaining access to my fonera? I'd try the network TFTP/telnet redboot crap, but the development page suggests that that does not work on a 2202 Sep 22 08:41:38 Or is it just the "flash tool" that doesn't work on a (non-beta) 2202? Sep 22 08:47:12 blathijs: redboot is not working on certain FON2202 units Sep 22 08:47:21 because of a misunderstanding with the manufacturer :( Sep 22 08:47:27 I am not sure if yours is one of those Sep 22 08:47:37 if it doesn't work, the best is to enable it Sep 22 08:47:48 It's included, but disabled by accident? Sep 22 08:47:55 How to enable it? Serial port? Sep 22 08:48:07 there is an explanation (in italian, but not difficult to understand) on how to do it Sep 22 08:48:11 no need for serial Sep 22 08:48:16 Where is it? Sep 22 08:48:19 I haven't tried it myself Sep 22 08:48:24 you could brick your fonera Sep 22 08:48:29 Yoy :-) Sep 22 08:48:31 so it's at your own risk Sep 22 08:48:38 if you want to be safe... get a serial Sep 22 08:48:42 let me find it for you Sep 22 08:49:16 The development wiki page says that redboot doesn't work with units sold after jan 2009, which would include my fonera Sep 22 08:49:25 or is redboot enabled again on newer units? Sep 22 08:51:38 iurgi: Is there any reason the failsafe image won't work for me? Are 2202's also shipped with a missing or broken failsafe image? Sep 22 08:53:43 hmmm Sep 22 08:53:44 no Sep 22 08:53:49 failsafe should work fine Sep 22 08:54:19 Failsafe is just a normal image with some extra software removed, I'd expect? Sep 22 08:54:25 E.g., it should have a normal dashboard? Sep 22 08:54:31 no Sep 22 08:54:38 failsafe has not even luci Sep 22 08:54:52 But it has ssh? Sep 22 08:54:54 it's just a kernel + busybox + http + upgrade_system Sep 22 08:54:55 no Sep 22 08:54:56 no ssh Sep 22 08:55:04 only http Sep 22 08:55:05 imo Sep 22 08:55:14 maybe telnet, I can't remember, but I don't think so Sep 22 08:55:18 I (think I) booted the failsafe image yesterday Sep 22 08:55:21 on failsafe you need to connect to 192.168.1.1 Sep 22 08:55:26 how did you do it? Sep 22 08:55:43 press the reset button, plug in power, hold it for 20s Sep 22 08:56:26 THis resulted in the LAN port going in bridge mode with the WAN port, and it got me an unconfigured (e.g., serial number as PSK again) MyPlace WLAN network (and no FON_ network) Sep 22 08:56:57 On MyPlace I got a normal 192.168.10.x address, but I don't think it had any actual internet connectivitiy Sep 22 08:57:23 But from your comments, it seems that I might not have booted the failsafe image, then Sep 22 08:57:32 that's incorrect Sep 22 08:57:42 failsafe has no myplace signal Sep 22 08:57:48 Right Sep 22 08:57:59 Does pressing the reset button normall just erase configuration? Sep 22 08:58:03 it has an open but without connectivity signal that says: FON_ATTENTION_PLEASE_CONNECT Sep 22 08:58:06 or something like that Sep 22 08:58:07 yes Sep 22 08:58:15 That would explain why I got MyPlace instead of my own SSID Sep 22 08:58:18 it only resets the configuration Sep 22 08:58:34 to go to failsafe you need to turn on the unit while pressing the reset button Sep 22 08:58:39 It doesn't explain why the LAN port got into bridge mode, since that wasn't the case before IIRC Sep 22 08:58:53 iurgi: That's exactly what I did Sep 22 08:58:57 But I'll try that again, then Sep 22 08:59:05 well Sep 22 08:59:11 maybe 20secs was too long Sep 22 08:59:12 ;) Sep 22 08:59:15 try with 5secs Sep 22 08:59:24 The wiki said 15, so I rounded up :-) Sep 22 08:59:28 maybe failsafe booted and you rebooted Sep 22 08:59:29 hehe Sep 22 08:59:35 15 is too much but might be safe Sep 22 09:02:02 Ah, that seems to have worked Sep 22 09:11:29 good Sep 22 09:11:30 :) Sep 22 09:12:30 What's the login for the failsafe image? Sep 22 09:12:47 admin/admin doesn't seem to work on the ATTENTION_* network Sep 22 09:13:15 I'd try the network port, but my crosslink cable seems to have gone missing since yesterday evening... Sep 22 09:14:49 I suspect my cats of hiding it, but they won't tell me where :-) Sep 22 09:14:56 the login is root Sep 22 09:15:00 password is the serial Sep 22 09:15:13 the ATTENTION network shuold have no IP Sep 22 09:15:19 you need to use cable, imo Sep 22 09:16:15 The ATTENTION network got me a DHCP lease Sep 22 09:17:07 Is the network port autosensing? Or should I really get a crosslink cable? Sep 22 09:17:31 Hm, I could probably plug it into my normal network, since that's the same range (and .1 is not taken) Sep 22 09:17:44 it's autosensing imo Sep 22 09:18:44 Ah, plugging it into my normal network worked as well, with the advantage of having internet and a fon connection at the same time :-) Sep 22 09:19:03 fon connection? Sep 22 09:19:07 failsafe has no fon connection Sep 22 09:19:08 XD Sep 22 09:19:11 connection to the fonera, I mean Sep 22 09:19:42 So I can tell you that I get a nice simple HTML page with a firmware upload interface now :-) Sep 22 09:20:17 And I can download the official firmware now without having to switch network plugs Sep 22 09:20:29 ok Sep 22 09:20:35 :) Sep 22 09:20:56 want to test a new firmware Sep 22 09:21:00 ? Sep 22 09:21:54 I'm looking to build pulseaudio packages Sep 22 09:22:15 what for? Sep 22 09:22:24 To stream audio to my fonera Sep 22 09:22:26 we already have an audio daemon Sep 22 09:22:33 audiocli? Sep 22 09:22:38 have yuo tried our audio application Sep 22 09:22:54 yes, although I'm not sure it's named like that anymore Sep 22 09:23:28 I'd like to play stuff on my laptop, and get the output on my fonera. It is way more flexible that way Sep 22 09:24:15 Hm, the failsafe page says the login is admin, not root Sep 22 09:24:30 I guess both work? Sep 22 09:24:39 hmmm Sep 22 09:24:41 maybe admin Sep 22 09:24:43 not sure Sep 22 09:24:45 root worked for me Sep 22 09:24:49 I think the username is ignored Sep 22 09:24:50 lol Sep 22 09:25:06 Heh, that might just be the case Sep 22 09:25:19 I'll check that the next time I screw up :-) Sep 22 09:26:00 The failsafe page recommends reflashing over the wireless interface Sep 22 09:26:12 hehe Sep 22 09:26:19 ?!! Sep 22 09:26:23 does it????????? Sep 22 09:26:28 wtf! Sep 22 09:26:30 it shouldn't Sep 22 09:26:35 I mean, there's no difference Sep 22 09:26:53 but that doesn't mean it should *recommend* doing it over wifi... Sep 22 09:27:04 Connect to the WiFi signal FON_ATTENTION_PLEASE_CONNECT (make sure that you are not connect by cable at the same time). Sep 22 09:27:08 I'll change it around Sep 22 09:27:21 Hmm, I can't edit the page, it seems Sep 22 09:27:31 Is there access control on the fon wiki? Sep 22 09:27:52 no, I don't think so Sep 22 09:28:00 maybe you need to create an account, yes Sep 22 09:28:06 but it's open to do it Sep 22 09:28:47 I just registered and I'm logged in Sep 22 09:29:28 But only a "view source" button, no edit page Sep 22 09:30:13 Ah, I need to confirm my email Sep 22 09:30:25 When clicking "view source", I see The action you have requested is limited to users in the group emailconfirmed. Sep 22 09:30:38 Thoug I can still view the source, that sentence refers to editing I guess Sep 22 09:31:38 Yup, that worked Sep 22 09:31:58 ok Sep 22 09:32:07 if you need help with the wiki, inouk is the guy Sep 22 09:32:08 :) Sep 22 09:35:06 inouk: Would it make sense to add a note to the wiki registration page, saying that you need to confirm your email address before you can edit pages? Or is the note there and did I totally miss it? Sep 22 09:37:46 hi there :) Sep 22 09:38:12 blathijs, hmm i think there should be one Sep 22 09:39:27 Hi :-) Sep 22 09:39:33 blathijs, well actually you are right there is none :( Sep 22 09:39:42 hehe Sep 22 09:39:47 a flaw of mediawiki Sep 22 09:40:11 hopefully updating it will correct it Sep 22 09:40:55 i'm considering an update sometime soon Sep 22 09:44:44 We'll see then :-) Sep 22 09:53:03 inouk: You said that redboot didn't work on some of the 2202's. I guess that goes for Redboot in general, not just the Redboot Flash Tool? Sep 22 09:53:15 inouk: Since the wiki sort of suggests the latter Sep 22 09:54:56 blathijs, redboot in general Sep 22 09:55:13 Right, then I'll move that note up a line Sep 22 09:55:13 consequently the flash tool as well Sep 22 09:55:21 it is using redboot Sep 22 09:55:56 Hmm, the message "Hold on, please..." from the failsafe image, probably means it's rebooted already Sep 22 09:56:08 But the page is still "loading.." Sep 22 09:56:22 (The previous message was Verified OK) Sep 22 09:56:36 Looking at the leds, it's no longer in failsafe mode Sep 22 09:57:03 how long did you wait? Sep 22 09:57:13 i think that you have a popup when flash is completed Sep 22 09:57:18 inouk: no Sep 22 09:57:27 on failsafe no Sep 22 09:57:50 It's been flashing for over 35 minutes now ;-) Sep 22 09:58:43 Yup, it no longer ping replies, so it has rebooted Sep 22 09:59:11 ah ok maybe not in failsafe Sep 22 09:59:20 blathijs, check the LEDs Sep 22 09:59:30 what do you have ON? Sep 22 09:59:48 inouk: It's rebooted, I'm already sure Sep 22 10:00:38 hihi perfect then Sep 22 10:02:47 Hmm, is there still a help page on syntax of the wiki? Sep 22 10:03:11 When I click "Editing help", I get redirected to Help:Contents, which only talks about how to contribute Sep 22 10:04:54 Hmm, the Join_FON_Wiki_Team links to the mediawiki help pages Sep 22 10:06:30 Let's add that link to Help:Contents as well Sep 22 10:11:23 inouk: Did you find that reboot-enabling page? Sep 22 10:12:21 uh, that was aimed at iurgi Sep 22 10:12:27 All those i's :-) Sep 22 10:13:44 w00t, I have a dashboard again :-) Sep 22 10:14:39 blathijs, you have redboot disable? Sep 22 10:14:55 when did you bought your fonera? Sep 22 10:14:59 http://www.pcexpert-blog.com/2009/08/abilitare-laccesso-telnet-al-redboot-della-fonera-2-0-per-installare-firmware-diversi-dalloriginale.html Sep 22 10:15:10 inouk: Dunno, haven't tried redboot yet Sep 22 10:15:10 i did not test it yet Sep 22 10:15:17 inouk: I bought it juli 2009 Sep 22 10:15:26 So according to the wiki, that would mean it's disabled Sep 22 10:15:59 But I thought of linking the Fon wiki on Redboot to that article, or would you rather not have it so exposed? Sep 22 10:16:58 hmm received in july the IP address of redboot is indeed 0.0.0.0 Sep 22 10:17:15 but i don't know for august ones Sep 22 10:17:44 But its fixed in more recent units then? Sep 22 10:19:11 Hmm, looking at that article, why is this custom firmware required? Does it contain extra tools needed to change the redboot config? Or is changing the redboot config normally not allowed to prevent accidental bricking? Sep 22 10:21:12 no problem to add the link but not the instructions themselves as it isn't tested Sep 22 10:21:38 Yeah, I'd add a fat disclaimer :-) Sep 22 10:22:19 blathijs, i guess the custom image this guy made ship a kernel module that allow to write on redboot sectors Sep 22 10:23:25 so redboot config can be modified from shell Sep 22 10:24:06 blathijs, about redboot on august fonera i don't know, iurgi might know? Sep 22 10:26:11 it's easy to test Sep 22 10:26:34 if you have linux, configure your lan interface connected to the fonera with the 192.168.1.2 for instance Sep 22 10:26:41 ping 192.168.1.1 Sep 22 10:26:45 turn off and on the fonera Sep 22 10:27:07 if you get any replies (usually 2-3 replies a few seconds after power) then you have Redboot Sep 22 10:27:10 :) Sep 22 10:28:00 Yeah, I was going to do that next (I have a local 192.168.1.x network, so that's easy) Sep 22 10:28:23 Though right now I'm wondering why the wireless connection won't get setup Sep 22 10:28:37 according to wpa_cli, the MyPlace network advertises itself as WEP, not WPA... Sep 22 10:29:04 I've seen that before, and a reboot usually fixes it, but I'm wondering what's wrong Sep 22 10:29:17 If it's the fonera, or my slightly doggy network card :-) Sep 22 10:29:43 Let's see if I can get a connection on the computer wired port Sep 22 10:30:44 ok Sep 22 10:30:47 Ah, that worked, now I have ssh (I didn't enable ssh on the WAN port yet) Sep 22 10:30:55 Any suggestions how to find out what's wrong? Sep 22 10:33:24 what is the problem? Sep 22 10:33:50 iurgi: The MyPlace network is set to WEP instead of WPA Sep 22 10:34:14 And when I get the WEP key from iwconfig output on the fonera, I can actually connect (thoug DHCP doesn't seem to work) Sep 22 10:35:49 cat /etc/config/fon Sep 22 10:36:31 That does say wpa Sep 22 10:36:38 and hostapd seems to be running Sep 22 10:38:02 Though /var/run/hostapd doesn't exist, which should contain config files I think? Sep 22 10:38:41 wtf Sep 22 10:38:51 it says WPA and your iwconfig on the fonera shows WEP? Sep 22 10:38:56 yup Sep 22 10:38:57 that makes no sense at all Sep 22 10:38:59 nope :-) Sep 22 10:39:24 from hostapd --help, I understand that /var/run/hostapd should contain its config file(s) Sep 22 10:39:28 right after a reflash? Sep 22 10:39:51 It worked at the first boot, this is the second boot Sep 22 10:40:20 And I expect it will work again when I reboot now (I've observed this behaviour before, though never checked through SSH) Sep 22 10:43:20 that is really really really weird Sep 22 10:43:25 never seen it before Sep 22 10:46:06 iurgi: I assume hostapd is responsible for setting up the WPA mode on the wireless device Sep 22 10:47:11 iurgi: Any clue what piece of code is responsible for writing hostapd's config? Sep 22 10:47:53 Ah, probably fonstated Sep 22 10:49:47 Hmm, but that lua code is compiled. How to find ConfigWifi in my source dir... Sep 22 10:50:22 Ah, found it Sep 22 10:50:56 ok Sep 22 10:55:09 Hmm, /etc/config/wireless also contains some wireless settings Sep 22 10:55:25 that is not used imo Sep 22 10:55:32 which doesn't reference wpa, but does have a setting for psk/tkip Sep 22 10:55:36 or overridden by /etc/config/fon Sep 22 10:55:48 /sbin/wifi uses it AFAICS Sep 22 10:56:13 Though I don't completely understand how Sep 22 10:56:40 Hmm, that's not really true. /sbin/wifi talks about wifi-device and wifi-iface, and /etc/config/wireless contains that stuff Sep 22 10:56:56 But I can't really see how config_get TYPE "$CONFIG_SECTION" TYPE Sep 22 10:57:03 refers to /etc/config/wireless Sep 22 10:57:14 Oh wait, I see Sep 22 10:57:21 config_load "${cfgfile:-wireless}" Sep 22 10:57:24 There Sep 22 11:03:16 Ah, hostapd is run with a config file after all Sep 22 11:03:36 It's just that "ps" cropped its output, so I thought it was referring to a non-existent dir Sep 22 11:04:17 And the hostapd config file does list wpa=1 Sep 22 11:05:45 hmmm Sep 22 11:05:50 definitely abnormal Sep 22 11:06:00 are you sure you have WEP? Sep 22 11:06:01 lol Sep 22 11:08:04 Dunno, connecting with WEP doesn't give me an IP address (but since it is OPEN authentication, that might just mean the key is wrong I think) Sep 22 11:08:39 ahhhhh Sep 22 11:08:41 no Sep 22 11:08:49 I think it's not really wep then Sep 22 11:08:58 can you paste the iwconfig? Sep 22 11:09:07 of the private signal only Sep 22 11:10:39 ath1 IEEE 802.11g ESSID:"MyPlace" Nickname:"" Mode:Master Frequency:2.412 GHz Access Point: 00:18:84:D0:42:EE Sep 22 11:10:47 Encryption key:E7BE-B50A-4A26-D83A-774D-A332-0E3E-8C50 [2] Security mode:open Sep 22 11:11:02 I removed some irrelevant lines (and the first newline got eaten somewhere) Sep 22 11:11:28 well, it does sound like wep Sep 22 11:11:29 hehe Sep 22 11:11:31 but... Sep 22 11:11:39 the length of the key is incorrect, right? Sep 22 11:11:42 32? Sep 22 11:11:46 shuold be 26 Sep 22 11:11:50 there's something fucked up Sep 22 11:11:58 is that a fon official firmware? Sep 22 11:12:17 Yup, this is Flipper Sep 22 11:12:58 Hmm, the key does seem to long yes Sep 22 11:13:37 Can I tell /bin/sh to echo commands executed? Sep 22 11:13:58 or rather, tell busybox to do that? Sep 22 11:16:10 iurgi: Do you have a working Fonera at hand? If so, could you pastebind your /etc/config/wireless somewhere? Sep 22 11:16:28 (It does seem that all the scripts use that, I haven't seen a single reference to /etc/fonfig/fon yet) Sep 22 11:16:35 s/bind/bin/ Sep 22 11:20:39 I don't think fon.ng uses that Sep 22 11:20:44 but let me check my config Sep 22 11:21:05 config 'wifi-iface' 'private' option 'device' 'wifi0' option 'ifname' 'ath1' option 'network' 'lan' option 'mode' 'ap' Sep 22 11:21:08 What's fon.ng? Sep 22 11:21:10 option ssid' 'MyPlace' Sep 22 11:21:12 crappy pasting Sep 22 11:21:15 option 'hidden' '0' option 'encryption' 'psk/tkip' option 'key' '8201000027' Sep 22 11:21:19 uops Sep 22 11:21:22 fon-ng is hte firmware Sep 22 11:21:34 http://pastebin.com/m15314894 Sep 22 11:21:40 From reading the code, I'm pretty sure it does Sep 22 11:21:44 ok Sep 22 11:21:47 maybe Sep 22 11:21:53 Unless fon-ng is something newer than flipper Sep 22 11:22:25 Or the start of my trace (/etc/fonstated/ConfigWifi) is never used Sep 22 11:23:06 Your config is identical to mine, so that's not it... Sep 22 11:23:20 Running hostapd with -dd doesn't really give me anything useful either Sep 22 11:25:23 iurgi: How about your /var/run/hostapd-something file? Sep 22 11:25:48 hostapd does say: madwifi_configure_wpa: enable WPA=0x1 Sep 22 11:26:03 Woah, wait Sep 22 11:26:07 what? Sep 22 11:26:11 Now it works Sep 22 11:26:18 Apparently just restarting hostapd was enough :-S Sep 22 11:26:38 I didn't notice because I had changed the client settings to WEP instead of WPA Sep 22 11:29:46 Yup, it completely works again now... Sep 22 11:29:57 Hmm, but iwconfig output hasn't changed Sep 22 11:30:15 so apparently WPA looks like WEP in iwconfig Sep 22 11:34:30 weird Sep 22 11:34:34 my iwconfig is different Sep 22 11:34:42 ah no Sep 22 11:34:45 haha Sep 22 11:34:47 it's the same Sep 22 11:34:48 lol Sep 22 11:34:57 that's why the 'key' was longer than 26hex Sep 22 11:35:02 because it was not a wep key Sep 22 11:35:08 you never had wep Sep 22 11:35:43 Well, my wpa_cli did made me think so (on the client) Sep 22 11:35:56 It said: 00:18:84:d0:42:ee 2417 226 [WEP] MyPlace Sep 22 11:36:12 (And refused to connect) Sep 22 11:36:14 Whereas it now says: 00:18:84:d0:42:ee 2412 211 [WPA-PSK-TKIP] MyPlace Sep 22 11:36:34 So there was something fishy about the beacons being sent, I think Sep 22 11:37:34 Hmm, I had another question a while back, which is probably one for inouk Sep 22 11:38:21 09:59:30 < blathijs> Is there any particular reason content is split between the fon wiki and the fon trac wiki? I'm seeing some duplicate content and content that would be better placed elsewhere, but this fragmentation doesn't seem to serve any purpose... Sep 22 11:39:29 well, no particular reason Sep 22 11:39:36 fon wiki intends to be help for normal users Sep 22 11:39:49 fonosfera wiki intends to be to more skilled/developer users Sep 22 11:40:25 It is sometimes unclear when to split things on user/developer, and when to collect things about the same subject together Sep 22 11:41:02 I would say it makes sense to have a single wiki, which makes moving content, linking and preventing duplication easier Sep 22 11:43:48 In particular, I saw a note about enabling developer mode by uncommenting something on the Fon wiki, which I would have liked on the trac wiki, since then I would have been able to use my SSH connection to debug my broken dashboard, instead of having to use the failsafe image :-) Sep 22 11:44:01 Anyway, time for lunch Sep 22 11:44:10 Thanks for all the pointers so far :-) Sep 22 11:54:34 yeah, you are probably right Sep 22 11:57:32 Hmm, I still can't logon through HTTP on the WAN port Sep 22 11:58:02 https Sep 22 11:58:18 is there not a sign in the firewall saying thaT? Sep 22 11:59:13 iurgi: I enabled it in the firewall, so I can connect to the HTTP port just fine (no HTTPS, though) Sep 22 11:59:22 But it won't eat my login Sep 22 11:59:44 (I don't get the normal dashboard either, but a HTTP auth prompt with username password) Sep 22 12:01:01 brb, lunch for real Sep 22 12:02:03 it's https Sep 22 12:02:04 not http Sep 22 12:02:12 what firmware version did you install? Sep 22 12:02:13 ah Sep 22 12:02:18 you have an older version Sep 22 12:02:18 ok Sep 22 12:02:20 tlak later Sep 22 12:09:04 Yeah, it's flipper Sep 22 12:09:38 blathijs, one is for dev (written by fon staff) Sep 22 12:10:00 the other for enduser (written by fon staff and community) Sep 22 12:11:33 Hmm, so I can't even write on the trac wiki then Sep 22 12:12:02 though on FON wiki users can add things indented for dev Sep 22 12:12:27 but we are not able to check everything intended for dev added to FON wiki Sep 22 12:15:15 How would I go about changing the trac wiki? Bug you guys about it? Sep 22 12:16:47 blathijs, yes we are totally opened to suggestion :) Sep 22 12:19:29 In that case, I'd like to see the note about having to modify a config file to enable developer mode moved to the dev wiki Sep 22 12:21:45 ? Sep 22 12:22:02 if you can change this file you are already in dev mode Sep 22 12:22:21 It is now at http://wiki.fon.com/wiki/Fonera_Development and I'd like to see it at http://trac.fonosfera.org/fon-ng/wiki/build Sep 22 12:22:50 inouk: When building the image, I can select "development" in menuconfig, but it doesn't work. Instead, you need to edit some config file Sep 22 12:22:57 ha you mean when building from source Sep 22 12:23:34 Also, I don't have that config file (registered) in my build, so the note should probably be changed to say you should create it if not present Sep 22 12:24:11 well i wasn't aware that selecting profile dev did not work any more Sep 22 12:24:26 is it true with the last check out? Sep 22 12:24:36 Dunno, I've only checked flipper so far Sep 22 12:25:07 And I'm not 100% sure that it didn't work, but I didn't get ssh Sep 22 12:25:21 ah ok let me try with the last check out then Sep 22 12:25:22 (on my own build) Sep 22 12:25:31 But I also thrashed my dashboard, so I couldn't tell why SSH wasn't working :-) Sep 22 12:26:00 with flipper you have to reboot twice so ssh key get generated Sep 22 12:26:49 Yeah, didn't help Sep 22 12:27:31 I've rebooted a few more times, with considerable delays in between Sep 22 12:27:40 hi there, could someone please pastebin /etc/config/network and /etc/config/wireless from a running fonera? Sep 22 12:28:44 or4n9e: fonera 1 ? Sep 22 12:29:02 what do you want to know? Sep 22 12:29:56 xMff: FYI, I managed to reflash my Fonera2 using failsafe mode :-) Sep 22 12:30:18 xMff: I need a working config with public and private AP VAPs Sep 22 12:30:33 need to adjust something like this for piranha 3.0 Sep 22 12:30:55 ah, hm no such config around here but I can help you to make one Sep 22 12:30:55 and I have troubles with ath0 vs ath1, client vs ap and so on Sep 22 12:31:29 if you have troubles with ath0 vs. ath1 you did it wrong most likely. I assume the "troubles" are with option ifname in /e/c/network ? Sep 22 12:32:07 xMff: I read at madwifi.org that one need to create an AP VAP first and then the client Sep 22 12:32:22 that would mean .... client interface needs to be ath1 Sep 22 12:32:25 BUT Sep 22 12:32:46 the openwrt scripts take care of doing it in the right order iirc Sep 22 12:32:51 if I configure openwrt as a bridge + routed client, the client interface is ath0 Sep 22 12:33:25 use "option network logical_ifname" in /e/c/wireless and do *not* reference athX in /e/c/network directly Sep 22 12:33:36 other possibility then a bridge eth0-ath0/1 would be to have eth0 for wired, ath0/1 for client mode and ath0/1 for isolated AP Sep 22 12:34:22 you can find out which athX is which interface by examining the uci state: uci -P/var/state get network.logical_iface.ifname Sep 22 12:34:46 xMff: ok, will check this, thanks Sep 22 12:35:01 inouk: Any reason to keep this page around? http://wiki.fon.com/wiki/Fonera_2.0 Sep 22 12:35:17 xMff: sorry for not coming back because of iwinfo btw. I had no time as I was attending openSUSE conference Sep 22 12:35:27 but it's on my todo list Sep 22 12:35:29 inouk: It's only linked from the category page, and seems to be replaced by http://wiki.fon.com/wiki/La_Fonera_2.0 Sep 22 12:35:59 or4n9e: np but I think it'll help a lot in your case Sep 22 12:37:06 xMff: I also think so, assumed I'd like to support all supported platforms Sep 22 12:37:44 need to have a deeper look ... haven't responded yet as I like to get a deeper idea first ... otherwise it makes not too much sense Sep 22 12:37:55 Hmm, menuconfig won't let me select "Full source" in the luci options... Sep 22 12:38:14 xMff: btw, could you, at some point in time answer my "wifi" question at openwrt forums please? Sep 22 12:38:26 or4n9e: I already did quite some time ago Sep 22 12:38:37 or4n9e: or a new one? then post me a link please Sep 22 12:38:44 xMff: I asked a followup in the meantime Sep 22 12:38:50 xMff: one sec Sep 22 12:39:34 xMff: https://forum.openwrt.org/viewtopic.php?pid=94246#p94246 Sep 22 12:40:30 or4n9e: how does the /e/c/network looks like there? Sep 22 12:40:51 problem is the right combination of ifup/wifi/ifdown as a plain wifi does not care about dhcp Sep 22 12:41:27 xMff: if you wait a sec I switch the network connection and paste piranha's /e/c/network and wireless Sep 22 12:41:44 brb Sep 22 12:44:14 xMff: here it is http://pastebin.com/m7273db07 Sep 22 12:44:23 pretty straightforward Sep 22 12:45:14 or4n9e: /sbin/wifi calls setup_interface which usually takes care of emmitting hotplug events and bringing udhcpc up. However, this will only reliably if option network is used Sep 22 12:45:24 try removing "option 'ifname' 'ath0'" Sep 22 12:45:27 it's not required Sep 22 12:46:35 so, removing "option 'ifname' 'ath0'" would solve the wifi/dhcp issue? how that? Sep 22 12:46:44 inouk: If you move the notice about enabling development mode, you should point it at fon/fonbase/files/etc/config/registered, that's where the file is (not in targets/f20 as the page currently says). This holds for flipper as well as for trunk Sep 22 12:48:14 problem is, as described in the forums post, that a plain "wifi" instead of "/etc/init.d/network restart" doesn't renew the dhcp wan side Sep 22 12:48:33 or4n9e: not sure whether it solves that but it introduces race-conditions and might confuse the scripts Sep 22 12:48:46 and thus the system has the right AP values but does not renew its dhcp on the wan side and thus fails to connect actually Sep 22 12:48:51 also it does not work with all possible wifi configs Sep 22 12:49:07 or4n9e: sorry, didn't read all the above Sep 22 12:49:17 what do you want a wifi-client mode? Sep 22 12:49:22 IC, and what do you think about my ifdown/wifi/ifup proposal I posted? Sep 22 12:49:45 iurgi: this is Piranha setup Sep 22 12:49:48 ah Sep 22 12:49:49 ok Sep 22 12:49:56 what is it for? wardriving? Sep 22 12:50:04 Im talking about some configuration in a script AAP I wrote for openwrt Sep 22 12:50:37 or4n9e: would work as well, the only difference with ifdown is that udhcpc is killed explicitly which does not happen with wifi up Sep 22 12:50:37 AAP is AutoAP for openwrt ... you can use it for wardriving yes Sep 22 12:51:47 xMff: this all is very confusing to me to be honest (lack of documentation) ... possible options are ifdown/wifi/ifup OR wifi/ifup OR wifi up Sep 22 12:52:11 what actually is the difference between "wifi up" and "wifi" Sep 22 12:52:12 ? Sep 22 12:52:25 there is none Sep 22 12:52:32 wifi w/o args implies "up" Sep 22 12:52:38 is "wifi up" the same as "wifi" followed by "ifup" Sep 22 12:52:44 IC Sep 22 12:53:15 blathijs, i'm currently flashing my fonera with an image that i build with a checkout from this morning Sep 22 12:53:38 or4n9e: wifi( up) is wireless setup + ifup, ifup is just ifconfig foo without configuring the wireless Sep 22 12:54:06 so, the "ifdown" is obsolete and I'd need "wifi" followed by "ifup" right? because a plain "wifi" without a subsequent "ifup" results in a not working dhcp on the wan side Sep 22 12:54:06 blathijs, this image has DEV as subtarget, i'll check if i have ssh access afterwards Sep 22 12:54:33 or4n9e: yes, the additional ifup kicks udhcpc back into operation Sep 22 12:54:56 or4n9e: also ifup does ifdown by itself if the interface is marked "up" already Sep 22 12:55:37 xMff: IC, but you said "wifi( up) is wireless setup + ifup" ... this would mean that "wifi" and "wifi/ifup" should end up in the same result Sep 22 12:55:44 but it doesn't Sep 22 12:56:07 the difference is, that wifi does not call ifup but only triggers the hotplug handlers Sep 22 12:56:10 for me, an explicit "ifup" AFTER "wifi" is required ... does this make sense for you? Sep 22 12:56:30 the hotplug handlers are supposed to arrange the dhcp stuff Sep 22 12:56:45 however they're designed to try reusing a running udhcpc instance Sep 22 12:56:52 which does not seem to work Sep 22 12:57:05 maybe udhcpc kills itself cause it lost it's underlying interface for a short time Sep 22 12:57:10 ah, we get closer Sep 22 12:57:40 wait a sec, I try to write a dummy to pastebin and you approve Sep 22 12:57:49 just to be on the same page Sep 22 12:58:38 when calling wifi, all vaps are destroyed and brought up again. During this time udhcpc looses its ath0 and will temrinate itself. The hotplug handler (/lib/network/config.sh, function setup_interface_dhcp) does not seem to handle this gracefully Sep 22 12:59:01 this should be fixed in a generic way because "wifi" is supposed to be able to bring everything up by itself iirc Sep 22 12:59:15 inouk: I'm currently testing the "uncomment the dev line" approach with flipper :-) Sep 22 12:59:50 xMff: http://pastebin.com/m487c35d Sep 22 13:00:22 xMff: cool, now I understand this clearer Sep 22 13:01:17 your explanation would also mean that I won't have to deal with several udhcpc instances at once right? cause it terminates when loosing ath0 Sep 22 13:01:40 right Sep 22 13:01:48 and the pastebin makes sense Sep 22 13:01:49 ? Sep 22 13:02:01 yes Sep 22 13:02:20 great Sep 22 13:02:33 what a mess if you lack proper docs Sep 22 13:02:35 lol Sep 22 13:02:35 the additional ifup does not do any harm actually but it works around a problem that should not exist in the first place :) Sep 22 13:02:59 xMff: would it make sense to file a bug for trunk? Sep 22 13:03:23 yes, since you have a test environment right now you can also add some debugging to /lib/network/config.sh Sep 22 13:03:30 esp. in the lines that deal with udhcpc Sep 22 13:03:35 e.g. the running check etc. Sep 22 13:03:41 IC Sep 22 13:03:58 I'm anyway in my way to release the next Piranha snapshot Sep 22 13:04:10 btw, have you tried AAP already by yourself? Sep 22 13:06:37 one last thing regarding ifup: what's the actual difference between "ifup wan" and "ifup"? Sep 22 13:06:56 wouldn't "ifup wan" be better for plain client mode? Sep 22 13:10:36 thinking about it, I'll go for a ifdown/uci bla/wifi/ifup combination as it brings udhcpc down in any case and is in any case better than /etc/init.d/network restart Sep 22 13:11:04 yep Sep 22 13:11:25 or is it the same in the end and isn't worth it? Sep 22 13:11:31 just wondering :D Sep 22 13:11:36 connectivity is lost anyway when switching aps so an additional down/up cycle won't hurt Sep 22 13:12:12 but I believe the underlying issue affects "static" client mode setups as well therefore I'm interested in a proper fix Sep 22 13:12:28 same here Sep 22 13:13:00 question is.... does our, now worked out, solution has any advantage over /etc/init.d/network restart Sep 22 13:13:13 yes it has Sep 22 13:13:14 or is it just the same configured manually? Sep 22 13:13:24 esp. since it does not bring down the ethernet Sep 22 13:14:13 you never know what kind of setup is deployed by a user so minimizing impact of automatically occuring events is always a good idea imo Sep 22 13:14:16 IC, one last thing regarding ifup: what's the actual difference between "ifup wan" and "ifup"? Sep 22 13:14:37 I guess you missed that question when going down and come back as xMff1 Sep 22 13:15:02 completely on the same page here Sep 22 13:15:05 "ifup" w/o args is not a valid command Sep 22 13:15:10 either ifup -a (=all) or ifup ifname Sep 22 13:15:36 ifup -a would affect ethernet as well right? Sep 22 13:15:43 i.e. wired Sep 22 13:15:44 yes Sep 22 13:15:51 it's what /etc/init.d/network restart does Sep 22 13:15:55 damn Sep 22 13:16:18 so I need to go for "ifdown wan/uci bla/wifi/ifup wan" right? Sep 22 13:16:23 yes Sep 22 13:17:01 and you sign this as the best solution available? I mean, in the end YOU'll get full credit for the change Sep 22 13:17:04 rofl Sep 22 13:17:15 yeah I sign that Sep 22 13:17:49 spend quite some time digging in the network and hotplug scripts Sep 22 13:18:23 that's the reason I'm very much comfortable with you being the ultimate decision maker Sep 22 13:18:45 you btw already got full credit for the uci commit wireless change Sep 22 13:18:53 I noted that in the README Sep 22 13:19:37 ;) Sep 22 13:19:38 blameshifting ftw Sep 22 13:19:56 now I just need to find a reasonable solution for my desire of an additional AP interface Sep 22 13:20:11 and there's nearly nothing left for Piranha 3.0 final :D Sep 22 13:20:36 at some point in time I'd like to come up with a LuCI module for AAP btw Sep 22 13:21:04 my idea is to get the conf variables and toggles out of a new conf file /e/c/aap Sep 22 13:21:31 with uci get/set commands - that would enable us to write a simple LuCI frontend Sep 22 13:22:09 logging to syslog is already implemented as of AAP 090916 Sep 22 13:22:41 so you switched to uci now? Sep 22 13:22:51 ah you plan to Sep 22 13:23:55 or4n9e: regarding the second vap: just adding an additional wifi-iface does not work? Sep 22 13:25:03 that's a bit tricky ... what I need is the following ... ethernet 10.0.0.1, ath0 in client mode, ath1 in AP mode with 172.16.0.1 Sep 22 13:25:15 OR a bridged eth0-ath1 Sep 22 13:25:35 not decided, while I tend to a non-bridged conf Sep 22 13:25:57 http://pastebin.com/m7ec21d29 Sep 22 13:26:32 you don't actually need to know the exact athX names Sep 22 13:26:45 that'd be bridged right? Sep 22 13:26:50 bridged to lan Sep 22 13:27:03 I need as the client interface urgently needs to be ath0 Sep 22 13:27:10 why? Sep 22 13:27:22 cause of the MAC address assigned by madwifi Sep 22 13:27:37 if it's ath1 I'd have a 06:18:84 Sep 22 13:27:48 and I need a 00:18:84 Sep 22 13:27:58 not sure if that's even possible Sep 22 13:28:12 inouk: Uncommenting the option dev 1 line in fon/fonbase/files/etc/config/registered works when compiling flipper, I've got SSH now Sep 22 13:28:26 inouk: Still no dashboard though, so luac with -O0 still breaks I suspect Sep 22 13:28:39 Does lucittpd keep a logfile anywhere? Sep 22 13:28:45 with a bridged conf it works, i.e. have ath0 as 00:18:84 in client mode and ath1/eth0 bridged AP with gateway 10.0.0.1 Sep 22 13:28:45 or4n9e: why is this a problem? Sep 22 13:29:14 blathijs: nope but it logs to syslog iirc Sep 22 13:29:53 blathijs: can you load lua files? try something like lua -lluci.util -e 'print(luci.util)' Sep 22 13:29:54 xMff: several reasons, 1. AAP hardcoding of ath0, 2. port forwarding stuff for my rooftop setup, 3. things I cannot really mention in a fon channel :D Sep 22 13:30:04 lol Sep 22 13:30:26 xMff: Yup, that works Sep 22 13:31:06 or4n9e: hardcoded ath0: replace it with $(uci -P/var/state get network.wan.ifname), portforwardings: add a hotplug handler, it'll receive the interface name through the environment Sep 22 13:32:21 xMff: "logs to syslog" <-- where would that be? There's nothing like syslog in /var/log/syslog, or would I need to set it up to log to an external syslog server? Sep 22 13:32:30 or4n9e: http://pastebin.com/m29f5d8cd Sep 22 13:32:35 hm, the port forwarding stuff doesn't lie in control of openwrt but the host routers Sep 22 13:32:36 blathijs: "logread" Sep 22 13:33:46 Heh, nice :-) Sep 22 13:33:54 xMff: IC, could you provide a config for non-bridged wifi? Sep 22 13:34:01 No longs from lucittdp, though Sep 22 13:34:41 blathijs: check how it's invoked by the init script, then kill it and execute it manually on the cli Sep 22 13:34:44 with eth0 gateway 10.0.0.1, ath1 (AP) gateway 172.16.0.1 and ath0 (client) with MAC 00:18:84 or this simply IMpossible? Sep 22 13:34:47 it should report some output Sep 22 13:34:55 esp. when something faisl during requests Sep 22 13:35:29 or4n9e: you can override the mac addresses with "option mac ..." in /e/c/network Sep 22 13:35:36 xMff: Ah, right Sep 22 13:36:12 also make sure to not daemonize it Sep 22 13:36:23 xMff: will try all these. just need to switch the connection to the openwrt test network ... thanks for all ya help so far Sep 22 13:36:50 xMff: will let you know at some point in time and response to the iwinfo stuff asap Sep 22 13:36:51 k Sep 22 13:37:10 Might this be a problem: module 'nixio.fs' not found: Sep 22 13:37:24 yes Sep 22 13:37:33 That's on startup, requests don't generate anything Sep 22 13:37:38 it's a core module Sep 22 13:37:48 hmm, bugger :-) Sep 22 13:37:52 opkg list_installed | grep nixio Sep 22 13:38:35 xMff: It's installed Sep 22 13:39:21 And it contains a nixio.so and util.lua Sep 22 13:39:24 No other lib files Sep 22 13:39:34 it should contain /usr/lib/lua/nixio/fs.lua Sep 22 13:39:45 and /usr/lib/lua/nixio/util.lua Sep 22 13:39:56 and the .so, yes Sep 22 13:40:40 Hmm, interesting. Let's recompile it :-) Sep 22 13:40:43 http://pastebin.com/m7e22182b Sep 22 13:40:55 put that into /usr/lib/lua/nixio/fs.lua Sep 22 13:41:07 or just grab fs.lua from your buildroot and scp it over Sep 22 13:41:27 Uh, I get an empty page on your pastebind, so I'll grab my copy Sep 22 13:43:18 Funny, I don't have that file Sep 22 13:43:36 Just util.lua in luci/libs/nixio Sep 22 13:44:44 hmm let me check Sep 22 13:45:19 trunk has it Sep 22 13:45:34 yeah was about to say that Sep 22 13:45:44 But Flipper doesn Sep 22 13:45:46 ;t Sep 22 13:46:40 Which makes me wonder if the official flipper image has it :-) Sep 22 13:47:09 Or if there is something in my flipper build that somehow got updated to a newer version that expects a trunk version of luci with that file? Sep 22 13:47:58 it could be that the luci sources are pulled from trunk because someone forgot to change the references to tags/... when tagging the flipper release Sep 22 13:48:14 trunk progressed in the meanwhile and became uncompatible Sep 22 13:48:20 *incompatible Sep 22 13:49:19 Yeah, something like that Sep 22 13:49:51 But it's not the entire "luci" directory, though Sep 22 13:52:52 Seems ff-luci has references outside of the flipper tag Sep 22 13:53:39 I'm seeing svn checkouts of http://dev.leipzig.freifunk.net/svn/ff-luci/trunk and http://x-wrt.googlecode.com/svn/trunk Sep 22 13:53:53 All other .svn dirs refer to the flipper tag Sep 22 13:54:25 whoa, this repo location is ancient Sep 22 13:54:42 was last updated a year ago or so, are you sure it's actually used? Sep 22 13:55:13 There is an svn co of it somewhere in my fon-ng checkout, which I only made a few days ago Sep 22 13:55:30 I'm now trying to find the actual checkout, my find+grep hack didn't tell me that :-) Sep 22 13:55:50 did you use the setup.sh ? Sep 22 13:55:56 It should arrange feeds as required Sep 22 13:56:17 I used install.sh? Sep 22 13:57:04 yeah mean that Sep 22 13:57:16 Yup, I did things by the book (read: trac) Sep 22 13:57:58 Seems it's stuff in openwrt/feeds/luci, so they might very well be unused Sep 22 13:58:00 anyway, it uses a private copy of luci included in the fonosfera svn Sep 22 13:58:10 and in that copy some files are just missing Sep 22 13:58:31 http://trac.fonosfera.org/fon-ng/browser/tags/Flipper-2.2.5.0/luci/libs/nixio/lua/nixio Sep 22 13:58:37 Actually, the entire openwrt/feeds/luci dir is from that url Sep 22 13:58:52 xMff: But, fs.lua should be there even for flipper? Sep 22 13:59:10 It's not only introduced until after flipper? Sep 22 14:00:24 well I do not know whether flipper was actually build from these exact sources Sep 22 14:00:39 maybe it only worked on the developers machine :) Sep 22 14:01:33 Yoy :-) Sep 22 14:01:55 you can replace the nixio folder with that from trunk Sep 22 14:02:01 api should be comptabile Sep 22 14:02:39 why do you build Flipper btw? Sep 22 14:02:46 and not one of the newer releases Sep 22 14:03:07 Flipper is the newest stable, right? Sep 22 14:03:48 I thought it would be nice to see if I could build the exact same version I was already running, before trying things like adding software and getting newer versions Sep 22 14:04:00 http://trac.fonosfera.org/fon-ng/changeset/1416 Sep 22 14:04:02 :) Sep 22 14:04:04 not anymore Sep 22 14:04:41 Hmm, my internet (or probably DNS) broke Sep 22 14:04:56 Hm, no Sep 22 14:05:03 heh, mine too Sep 22 14:05:11 Hm, DNS is still running Sep 22 14:05:25 I keep confusing my laptop by enabling both wireless and wired connections :-) Sep 22 14:06:00 seems my Fonera is refusing new cnnections now... Sep 22 14:07:44 Hmm, I already thought I saw a 2.3 tag in the browser a while back, but it was a real tag then and not some random "prepare for release" commit :-) Sep 22 14:07:49 Are there binaries yet? :-) Sep 22 14:08:50 (Btw, it seems I have two versions of luci around in my build_dir, one "local" version and one from http://svn.luci.subsignal.org/luci I think) Sep 22 14:09:09 Anyway, Let's have a go at 2.3 then Sep 22 14:09:24 If it's released, I might as well compile it Sep 22 14:09:39 Might introduce a whole new world of errors, but well :-) Sep 22 14:10:10 :) Sep 22 14:10:10 I'm wondering if the build system is cool enough to handle an svn switch without doing a full recompile... Sep 22 14:10:39 would not recommend this Sep 22 14:11:19 That's probably where the world of errors would come from :-) Sep 22 14:11:49 Would be nice not to recompile the cross tools, or does 2.3 (what's its name?) use different gcc versions anyway? Sep 22 14:13:11 xMff: That ancient url you referred to is from openwrt/feeds.conf Sep 22 14:13:44 xMff: Quite possibly I shouldn't have run scripts/feeds {update,install} -a, perhaps that introduced some conflicts Sep 22 14:15:02 this would be possible, yes Sep 22 14:22:48 brb, need to reflash my internet router Sep 22 14:23:04 Removing all the feeds (and readding the fon ones) breaks my working copy on wap_supplicant with linker errors it seems Sep 22 14:23:09 Let's just try 2.3 then :-) Sep 22 14:24:13 xMff: Hmm, but 2.2.6 has become 2.3.0, then? Sep 22 14:26:02 well, that was painless Sep 22 14:26:27 :-) Sep 22 14:27:00 xMff: I just wondered if 2.2.6 had become 2.3.0, but it seems that 2.2.6 has been released a while back already? Sep 22 14:27:07 yep Sep 22 14:27:21 Or rather, tagged, because I don't think there ar tgz's for it? Sep 22 14:42:06 inouk: Did you check if developer mode worked out of the box on trunk? Sep 22 14:47:28 Or not so painless? Sep 22 14:47:55 xMff: Any particular reason the 2.2.6 firmware is not in http://download.fonosfera.org/LATEST/ ? Sep 22 14:48:13 That's the reason I've been fiddling with Flipper in the first place, since I thougth that was the latest firmware Sep 22 14:48:16 not compiled yet? Sep 22 14:48:24 2.2.6, not 2.3.0 Sep 22 14:48:28 ah Sep 22 14:48:31 no idea Sep 22 14:48:39 (It's available a level higher in it's named folder) Sep 22 14:48:56 It's not that 2.2.6 is a dev version and 2.2.5 is the stable or something Sep 22 14:49:34 Perhaps it would be nice to make LATEST a symlink to whatever is latest... Sep 22 14:49:56 Which might even be the case already, since LATEST looks exactly like Flipper Sep 22 14:50:04 It just didn't get updated Sep 22 14:50:31 Seems there are even compiled binaries for 2.3 (Thats called "Elan", apparently?) available in the /Elan folder Sep 22 14:50:52 Hmm, compiling Elan myself fails after five lines of output Sep 22 14:50:56 Checking 'intltool-update'... failed. Sep 22 14:50:59 avahi: avahi requires intltool >= 0.35.0 Sep 22 17:41:13 hey, cool, 2.3 compiled already :-) Sep 22 18:09:46 blathijs: nice :) Sep 22 18:10:37 Now let's see what happens when I flash it in :-) Sep 22 18:12:31 did you compile it with pulseaudio? Sep 22 18:18:18 No, just a clean compile Sep 22 18:18:23 One step at a time Sep 22 18:19:07 Also, the pulseaudio package in openwrt is marked broken and is only 0.9.13 (latest is 0.9.18) Sep 22 18:21:17 Hmm, it seems the dashboard is still/again broken Sep 22 18:21:31 Or, it just took a long time to load Sep 22 18:21:43 And it's orange, so no Developer mode I guess Sep 22 18:25:33 Now, how did I switch to developer mode? Sep 22 18:25:42 Wasn't that a meta application to install? Sep 22 18:26:23 fonera 2.0g is orange, 2.0n is green Sep 22 18:26:25 or should be Sep 22 18:26:55 there was, but not released for 2.3.0.0 since it hasn't been release yet Sep 22 18:27:32 if you want to compile a developer mode, you need to make the same trick you did before, changing the /etc/config/registered file on buildroot prior to compilation Sep 22 18:27:33 So, I can't get it into dev mode from the dashboard now? :-) Sep 22 18:27:39 Yeah, I'll do that Sep 22 18:27:57 Funny that the "switch to dev mode" application is an actual "application" after all :-p Sep 22 18:28:17 nope, you can't now, sorry Sep 22 18:28:30 I'll just build a new one, no problem Sep 22 18:28:36 Hi Sep 22 18:28:45 Tomorrow is the big day!!! Sep 22 18:28:55 What big day? Sep 22 18:29:36 Fonera 2.0n release I guess Sep 22 18:33:13 yes Sep 22 18:33:15 tomorrow Sep 22 18:33:16 :o Sep 22 18:33:25 anyone's buying it? Sep 22 18:33:26 haha Sep 22 18:33:30 it's a great device Sep 22 18:33:49 Decodecoding: did you try the latest firmware? Sep 22 18:35:01 epienbro: The 2.3 release compiled without any luac segfaults for me (without changing -O options) Sep 22 18:35:29 Yes, latest firm is very good Sep 22 18:35:34 good Sep 22 18:35:35 :) Sep 22 18:35:41 Couldn't report any bug yet Sep 22 18:35:42 you tried 2.3.0.0 right? Sep 22 18:35:54 Final? I had RC4! Sep 22 18:35:57 lol Sep 22 18:36:01 sent you a mail I think Sep 22 18:36:06 RC4 had many bugs Sep 22 18:36:07 haha Sep 22 18:36:10 well, not many Sep 22 18:36:13 Didn't get it Sep 22 18:36:17 maybe 6 or 7 Sep 22 18:36:32 well, it's on http://download.fonosfera.org/Elan/ Sep 22 18:36:42 I remember now, I didn't send it to you Sep 22 18:36:43 haha Sep 22 18:36:52 well, I sent the 2.0g version Sep 22 18:36:58 I guess you didn't have time to test that one? Sep 22 18:37:05 NO Sep 22 18:37:08 iurgi: Any change that /LATEST could be pointed to /Elan? Sep 22 18:37:10 ok Sep 22 18:37:21 iurgi: It still points to Flipper, which kinda confused me Sep 22 18:37:26 blathijs: sorry, didn't unerstant the question Sep 22 18:37:27 a Sep 22 18:37:29 ah Sep 22 18:37:34 s/change/chance/ ? Sep 22 18:37:41 yes ;-) Sep 22 18:37:44 blathijs: not yet Sep 22 18:37:53 there's no Elan release for fonera 2.0g Sep 22 18:38:02 in the g we are on 2.3.0.0RC1 Sep 22 18:38:11 Lately I focused on testing 2.0n Sep 22 18:38:15 we haven't tested it throughly enough, sorry Sep 22 18:38:20 Decodecoding: yeah, I guess Sep 22 18:38:30 Ah, 2303 is the 2.0n :-) Sep 22 18:38:44 I have my 2.0g at my parent's , he he Sep 22 18:38:47 blathijs: yes Sep 22 18:38:54 Decodecoding: haha Sep 22 18:38:54 ok Sep 22 18:39:05 iurgi: In that case perhaps point it to /Cheeky for now? Sep 22 18:39:13 ah yes Sep 22 18:39:17 wha tlink specifically? Sep 22 18:39:33 http://download.fonosfera.org/LATEST/ Sep 22 18:39:40 ah Sep 22 18:39:41 ok Sep 22 18:39:42 sure Sep 22 18:40:14 Hmm, but you're doing seperate releases for n and g? Sep 22 18:40:25 Won't that be confusing with svn tags? Sep 22 18:40:43 Or will it be 2.3.0.1 when it supports g fully Sep 22 18:40:44 ? Sep 22 18:41:38 done Sep 22 18:42:05 they will be separate tags, I guess Sep 22 18:42:15 the idea is that they are excalty the same revision Sep 22 18:42:30 but until we have made a few simultaneous releases we won't konw Sep 22 18:42:31 I mean Sep 22 18:42:59 if we could have tested both enough, ideally, we would tag when both would be ready Sep 22 18:43:17 since we had to release for the fonera2.0n launch.. we didn't have the time Sep 22 18:43:30 Ah, like that :-) Sep 22 18:43:33 so this time we rleease the fonera2.0n tag and then test on the fonera2.0g Sep 22 18:43:54 if the work was good enough and we are lucky, the same tag will be valid Sep 22 18:44:03 otherwise, we will make a different tag Sep 22 18:44:05 Well, in that case, I'll be doing some testing (you people did kinda trick me believing it was stable! :-p) Sep 22 18:44:15 but in the future, the idea is that both are tested at the same time Sep 22 18:44:28 blathijs: why? Sep 22 18:44:29 lol Sep 22 18:44:36 2.3.0.0 is quite stable Sep 22 18:44:54 there are bugs, of course and hundreds of feature requests and nice to haves Sep 22 18:45:09 but I would say that everything inside the firmware works as expected Sep 22 18:45:20 faster or slower, but works Sep 22 18:45:23 But, would it make sense to release 2.3.0.1 (for both n and g) if there are further g fixes required (or n fixes, for that matter) ? Sep 22 18:46:06 hmmm Sep 22 18:46:07 Or is the final revision number meant for other things? Sep 22 18:46:23 we should be at an abstraction level that the hw should not matter Sep 22 18:47:03 that's why I said "the idea is that they are exactly the same, but until we've made a few simultaneous releases we won't know" Sep 22 18:47:14 hehe Sep 22 18:47:24 so ideally, there should be no bugs on the g that are not present on the n and vice-versa Sep 22 18:47:50 the most likely functionalities to fancy such bugs are ehthernet and wifi, for obvious reasons Sep 22 18:48:00 apart from the already konwn USB limitation of the fonera 2.0g Sep 22 18:51:40 iurgi: Why does the firmware have to have two names inside a firmware tgz? Sep 22 18:51:54 e.g, a datestamped version Sep 22 18:52:03 and fonera20.img Sep 22 18:52:15 hmm Sep 22 18:52:19 it's for the upgrade plugin Sep 22 18:52:26 an unfortunate calculation error Sep 22 18:52:30 will be fixed in the future Sep 22 18:52:36 they have the same md5sum Sep 22 18:52:39 I mean, there's Sep 22 18:52:42 Ah, the automatic upgrade plugin? Sep 22 18:52:46 1) image for redboot or ssh flashing Sep 22 18:52:53 2) tarball for web upgrade Sep 22 18:53:09 3) image for the automatic upgrade (same as 1 but different name) Sep 22 18:53:29 the automatic upgrade should not depend on the relese date... that's why Sep 22 18:53:57 But, automatic upgrade could just as well use the upgrade script, right? Sep 22 18:54:34 And the image for redboot or ssh flashing does not need to be in the tarball, right? (And could have any name?) Sep 22 18:56:00 Is there any script to create this tarball? Probably on one of your machines, but not in the repository? :-) Sep 22 18:58:12 Iurgi, is the people from Transmission working on new features for the plugin? Sep 22 18:58:25 for the fon plugin? Sep 22 18:58:26 hmm Sep 22 18:58:30 yes Sep 22 18:58:31 no I don't think so, why? Sep 22 18:58:42 blathijs: the tarball is signed Sep 22 18:58:46 I miss queueing downloads Sep 22 18:58:51 with a fon signature to ensure autenticity Sep 22 18:58:56 with a fon signature to ensure authenticity Sep 22 18:59:07 Decodecoding: transmission won't let you do that Sep 22 18:59:18 they actually have a disclaimer page explaining why Sep 22 18:59:23 they say it's not efficient Sep 22 18:59:25 and scheduling for bandwidth Sep 22 18:59:30 aha Sep 22 18:59:40 we tried to convince them that it was efficient for an embedded device Sep 22 18:59:45 I will rise the concern again Sep 22 18:59:59 I think they were not totally negative to it Sep 22 19:00:11 Well. I must say I'm downloading 10 files at a time and didn't ever freeze Sep 22 19:00:22 as for schedulling for bandwidth, I think it already supports it Sep 22 19:00:32 but it's not controlled via RPCs but only configuration file Sep 22 19:00:39 I see Sep 22 19:00:41 I also want to add this myself Sep 22 19:00:55 Decodecoding: wow, not bad: fonera20n I guess Sep 22 19:01:05 yes Sep 22 19:01:20 ok Sep 22 19:01:26 I have problems though Sep 22 19:01:34 but I think it's my f**ng ya.com line Sep 22 19:01:39 I'm pushing it to its limits Sep 22 19:01:51 every time I start downloading torrents, my SMC router dies Sep 22 19:02:01 it says something about SMURF attacks etc Sep 22 19:02:10 For me, the only limit is my crappy upload rate... Sep 22 19:02:13 but I don't think it's that... I think that's just crappy info Sep 22 19:03:01 I think it's either 1) ya.com trying to stop me from using P2P (unlikely?) or 2) the router being a crap (I will try by replacing it...) Sep 22 19:03:04 I think Foneras fit better cable modem, don't you think? Sep 22 19:04:00 less routing... Sep 22 19:04:10 http://trac.transmissionbt.com/wiki/EditConfigFiles#Scheduling Sep 22 19:04:40 Decodecoding: yeah... but ono is more expenssive... Sep 22 19:04:52 if I lived on my own, I'd pay it... but I have flat mates Sep 22 19:04:53 :) Sep 22 19:04:59 iurgi: So, if I create a tarball to manually upload, I can suffice with a single filename, as long as the upgrade script knows where to find it? Sep 22 19:05:09 no Sep 22 19:05:13 tarballs are signed Sep 22 19:05:18 it depends. Where I live, it's the cheapest I could get... Sep 22 19:05:31 iurgi: Even when I upload it manually through the dashboard? Sep 22 19:05:32 they only work on the developer mode if you don't sign them Sep 22 19:05:51 blathijs: on developer mode it works, on enduser they can only install fon signed packets Sep 22 19:06:05 In early 2010 I might switch to Vodafone Sep 22 19:06:12 blathijs: you can do your own tarballs for developer mode... just need to have the "upgrade" script Sep 22 19:06:28 iurgi: Ah, bugger. Then I'll have to boot to failsafe mode to get my fonera in developer mode I guess Sep 22 19:06:35 blathijs: and for plugins... you can copy the structure of any, the code is under the luci/ tree Sep 22 19:06:46 blathijs: hmmm Sep 22 19:06:58 yuo have developer tarballs Sep 22 19:06:59 not for elan Sep 22 19:07:03 iurgi: But, I can't create a signed tarball anyway, so no need to bother with two names :-) Sep 22 19:07:05 but I think there are for cheeky? Sep 22 19:07:22 Hmm, I could flash to cheeky developer and then to elan dev :-) Sep 22 19:07:23 Decodecoding: to vodafone? wow Sep 22 19:07:31 blathijs: yes Sep 22 19:07:34 That's probably easier than using failsafe mode, thanks :-) Sep 22 19:07:36 that's what I meant Sep 22 19:07:38 yes Sep 22 19:07:45 but... Sep 22 19:07:48 maight not work Sep 22 19:08:04 I can't remember if cheecky upgrade scripts had a version check Sep 22 19:08:06 because its a downgrade that tries to preserve settings? Sep 22 19:08:18 we use to force forward upgrades, banning downgrades Sep 22 19:08:23 Ah, I think I've seen version checks somewhere Sep 22 19:08:26 I'll se Sep 22 19:08:45 we removed that now, for sure, but I can't remember if we already did for cheeky Sep 22 19:08:49 iurgi: Hmm, /LATEST is now broken? Sep 22 19:08:51 which, now that I think of Sep 22 19:08:52 I'll try Sep 22 19:08:59 wasn't release for fonera 2.0g??? Sep 22 19:08:59 Ah, you split them Sep 22 19:09:04 LATEST is deleted Sep 22 19:09:04 yes Sep 22 19:09:08 let me check Sep 22 19:09:13 I think I fucked it up anyway Sep 22 19:09:14 lol Sep 22 19:09:21 exactly Sep 22 19:09:26 there's no cheecky for the g Sep 22 19:09:27 lol Sep 22 19:09:35 we never released 2.2.6.0 Sep 22 19:09:41 that's why latest was pointing there Sep 22 19:09:42 hehe Sep 22 19:09:44 reverting... Sep 22 19:10:00 done Sep 22 19:10:04 "released" in this case means "made an autoupgrade app" ? Sep 22 19:10:24 guck Sep 22 19:11:35 well Sep 22 19:11:37 Does guck mean yes? :-) Sep 22 19:11:43 no, that's a consequence Sep 22 19:11:49 released means officially made a release Sep 22 19:11:50 hehe Sep 22 19:12:01 we only made 2.2.6.0_RC5 or so Sep 22 19:12:09 I'd say tagging and creating tarballs goes a long way to releasing? Sep 22 19:12:14 then we stopped releases on the 2.0g till next week Sep 22 19:12:18 yes Sep 22 19:12:21 correct Sep 22 19:12:46 You people have an interesting release engineering process :-p Sep 22 19:13:05 lol Sep 22 19:13:06 why? Sep 22 19:13:08 is it weird? Sep 22 19:14:01 It hasn't been very regular so far :-) Sep 22 19:14:37 yeah... Sep 22 19:14:49 well, we had many things to decide, define, debug, discard etc Sep 22 19:14:58 It's not a complaint :-) Sep 22 19:14:58 I think after 2.3.0.0 it will be a bit more regular Sep 22 19:15:18 additionally, we haven't gathered a big developer community (yet) so we have small development power Sep 22 19:15:42 Another question. If I understand correctly, the "upgrade" app is distributed separately and contains the hardcoded url of the package it upgrades to? So you install the Elan installer first, and then run it to get Elan? Sep 22 19:15:47 fortunatelly, little by little at least we get some people that help each other on the channel Sep 22 19:16:03 hehe, that takes a lot of time of your hands, indeed Sep 22 19:16:04 blathijs: right now it is like this Sep 22 19:16:10 for a small bug/mistake we made Sep 22 19:16:18 it won't be like this for the next upgrade Sep 22 19:16:29 it will only be an upgrade button onthe applications menu Sep 22 19:16:54 You mean that Elan -> Elan + 1 upgrade will work differently? Sep 22 19:17:06 Is the code for that already present in Elan? Sep 22 19:19:56 I've only found the luci-upgrade plugin so far, which has a hardcoded url to Elan present (but that's probably code to build the upgrade for older versions?) Sep 22 19:21:16 Also, you say the tarballs are signed, but where is the signature? I can't find any signature file inside the tarball? Sep 22 19:21:40 I'm very curious tonight, it seems :-p Sep 22 19:23:31 But I'm trying to improve the documentation about tarballs, but that won't work if I don't understand how and why it works :-) Sep 22 19:26:13 Cool, there is a progress bar for firmware upgrades Sep 22 19:26:35 Slightly annoying that my wifi connection just broke halfway the upgrade... Sep 22 19:27:02 Hmm, but the progress bar is just a countdown for 30 minutes Sep 22 19:27:39 Which makes me wonder if the connection wasn't lost because it's rebooted already... Sep 22 19:28:28 Though the MyPlace signal seems missing Sep 22 19:28:57 Well, let's reboot, see what happens Sep 22 19:32:23 Hmm, that's interesting Sep 22 19:32:41 I've uploaded a dev image, but it's still in non-dev mode Sep 22 19:32:51 Is that a side effect of the config preserving code? :-) Sep 22 19:33:15 (Flash was succesful btw, so the 30 minute timer is a bit pessimistic, it was finished within 3 minutes) Sep 22 19:33:34 Failsafe mode, here I come :-) Sep 22 19:41:35 3 minutes? on a fonera 2.0 ? Sep 22 19:41:44 must be one with faster flash then Sep 22 19:41:52 usually around 25 minutes here Sep 22 19:50:34 xMff: Seems so, with a Cheeky dev tarball Sep 22 19:50:53 xMff: though it might be a bit longer, not sure if the progress bar started right away Sep 22 19:51:13 But it's less than 25 minutes anyway, since I've done another flipper flash again now Sep 22 19:51:47 yay, it's green again :-) Sep 22 19:53:47 Hmm, now I need to give my password on every click in the dashboard... Sep 22 19:54:52 wth.. Sep 22 19:55:48 Let's reboot, see if SSH gets enabled Sep 22 19:56:43 Since uploading a firmware tgz doesn't quite work when you need to login after clicking upload :-) Sep 22 19:56:54 Funny, since this is a clean flipper dev image Sep 22 19:58:21 Still not fixed.. Sep 22 20:01:00 this happens if your browser rejects cookies Sep 22 20:01:18 or if the session token in the url is not cleared Sep 22 20:02:37 I do accept cookies (worked before) and there is no session token in the url Sep 22 20:02:51 Did throw away a cookie just now to check if that fixed things (it didn't) Sep 22 20:03:51 Hmm, I do get two different cookies, both sysauth, one for / one for /luci Sep 22 20:04:56 Hmm, I deleted the cookies again, and now it does work Sep 22 20:05:16 oh well Sep 22 20:13:03 Right, now WPA is not working again Sep 22 20:13:13 Oh well, need to reboot anyway for ssh Sep 22 20:15:01 Hmm, still no WPA Sep 22 20:15:03 reboot again! Sep 22 20:17:19 Hmm, it seems the serial didn't get set properly as the WPA PSK now... Sep 22 20:38:27 Or, something else is fishy with the wifi Sep 22 20:38:41 The PSK is set properly in the config files (up to hostapd's config file) Sep 22 20:39:47 iurgi: You'll have to retag the 2.3 release for certain, the f20g target still has the cheeky version number and banner in fonbase/targets/f20 Sep 22 20:40:57 iurgi: Which kind of confused me, I thought I somehow flashed the wrong version :-) Sep 22 20:42:34 Hmm, and after (another) network restart the wifi also seems to work now Sep 22 20:43:05 Perhaps it's my laptop's wifi card after all, I did downgrade my kernel recently :-) Sep 22 20:44:10 Cool, the firewall settings panel now has submenus :-) Sep 22 20:46:24 But I still can't login to the WebGUI on the WAN port, just like with Flipper Sep 22 20:46:57 Is there some kind of limit on password length? Mine has 14 letters (and there is an underscore in there, perhaps that's a problem?) Sep 22 20:47:46 Changing it back to "admin" doesn't help either Sep 22 20:48:10 Oh well, let's leave that for debugging later Sep 22 20:48:16 Time for bed Sep 22 20:48:26 Good night, you've been a great audience! :-) **** ENDING LOGGING AT Wed Sep 23 02:59:58 2009