**** BEGIN LOGGING AT Tue Dec 01 02:59:58 2009 Dec 01 08:52:26 {Nico} good morning Dec 01 13:47:17 [florian]: you here? Dec 01 13:48:01 <[florian]> rtz: yes Dec 01 13:48:53 my usb audio sounds choppy, and i don't know if it is the kernel 2.6 or the music player :( Dec 01 13:49:13 [florian]: mtd partition setup doesn't work, but I can't figure out what's wrong Dec 01 13:49:18 let me create a log Dec 01 13:52:23 [florian]: http://openwrt.pastebin.com/m5145c2a2 Dec 01 13:53:00 [florian]: the sitecom code in platform.c is called and the partition table looks good, but something afterwards goes wrong Dec 01 13:53:31 [florian]: any pointer where I could start looking would be really helpful Dec 01 13:53:37 because I'm out of ideas Dec 01 14:02:00 <[florian]> rtz: it did not create partitions, make sure you have CONFIG_MTD_PARTITIONS set Dec 01 14:15:03 {Nico}: you here? Dec 01 14:15:18 if {Nico} or some other developer change anything to the Makefiles of a package Dec 01 14:15:25 for example net/freeswitch Dec 01 14:15:49 do i need feeds update -a to get thos changes? Dec 01 14:15:58 or is enough to do svn up on the openwrt trunk Dec 01 14:16:02 ? Dec 01 14:16:16 i would like to understand how the svn update and the feeds update are related one to the other Dec 01 14:26:04 Lalloso: svn up will just update your openwrt checkout Dec 01 14:26:20 the package stuff is in a separate checkout so you need to use ./scripts/feeds update Dec 01 14:26:46 so if i do an svn co Dec 01 14:26:58 than an svn switch to an internal repository of mine Dec 01 14:27:08 that's like creating an unofficial local openwrt branch Dec 01 14:27:13 yes Dec 01 14:27:20 will feeds update continue to work pointing to the internet? Dec 01 14:27:49 i can't lose all the important patches {Nico} is doing to the build system until they are well finalized Dec 01 14:29:13 but in the meanwhile i need to work on a specific revision of the openwrt trunk as i can't write on official openwrt repository (i'm far from having the necessary skills to acquire such a privilege) Dec 01 15:15:44 svn co is returning 405 Method not allow? Dec 01 15:15:49 just to me ? Dec 01 15:16:34 you're using the wrong protocol (https:// instead of svn://) Dec 01 16:16:39 you are right sorry jow_laptop Dec 01 16:50:06 [florian]: ping Dec 01 16:52:23 <[florian]> rtz: pong Dec 01 16:52:57 [florian]: it still doesn't work Dec 01 16:53:06 and config_mtd_partitions is set Dec 01 16:53:21 <[florian]> rtz: ok, I actually did not write that code so I guess sn9 did something wrong Dec 01 16:53:33 <[florian]> rtz: could you send me the bootlog of your original firmware? Dec 01 16:53:57 [florian]: yes, one moment Dec 01 16:54:17 [florian]: but it did work with the patch he send me Dec 01 16:54:41 [florian]: I'm not sure, if there are differences to the stuff in svn, but they can't be big Dec 01 16:54:42 <[florian]> rtz: could you send me the patch he sent you? Dec 01 16:54:56 [florian]: don't have it anymore :/ Dec 01 16:55:01 <[florian]> rtz: ah Dec 01 17:08:12 [florian]: http://openwrt.pastebin.com/m531dcef6 Dec 01 17:12:47 <[florian]> rtz: thanks, actually this it not very useful since they do not seem to do something standard with the mtd subsystem Dec 01 17:13:53 [florian]: I know Dec 01 17:14:03 [florian]: they use a special mtd driver Dec 01 17:14:28 [florian]: but I carefully checked the layout in platform.c Dec 01 17:14:48 [florian]: it's basically correct Dec 01 17:16:43 let me try something Dec 01 17:29:13 [florian]: there is a line ROOT_DEV = 0; in platform.c Dec 01 17:29:25 [florian]: should it be set to something? Dec 01 17:34:10 <[florian]> rtz: preferably let it unset Dec 01 18:06:38 nbd: Have you ever tested madwifi with adhoc + ap ? Dec 01 18:08:17 no Dec 01 18:08:22 not recently Dec 01 18:08:33 which is why i asked the question on the list Dec 01 18:12:50 [florian]: how does the kernel decide what to use as rootfs, if ROOT_DEV is 0 and not root= option is given on the commandline? Dec 01 21:35:45 ping xMff Dec 01 21:36:48 pong cshore Dec 01 22:17:43 jow * r18616 /packages/net/iptraf/ (Makefile patches/005-atheros.patch): [packages] iptraf: add patch to make iptraf recognize athX interfaces - thanks Jose Monteiro! (#6248) Dec 01 22:31:12 jow * r18617 /trunk/package/firewall/ (Makefile files/uci_firewall.sh): Dec 01 22:31:12 [package] firewall: initialize dest_port with src_dport if omitted in redirect sections to narrow Dec 01 22:31:12 down corresponding forward rules to the actual target ports - thanks Niels Boehm! (#6249) Dec 01 22:36:19 ping swalker Dec 01 22:42:22 ping xMff Dec 01 22:42:36 pong cshore1 Dec 01 22:42:55 Hi....Marc was saying you wanted me to UCI the PPTP stuff I did? Dec 01 22:43:18 cshore1: yes because I've seen you had hardcoded stuff in there Dec 01 22:43:33 yeah, it was a quick hack Dec 01 22:43:39 :) Dec 01 22:43:55 but now that I know it works I can UCI it Dec 01 22:44:10 part of it's in dnsmasq Dec 01 22:44:24 you mean the nameserver stuff? Dec 01 22:44:29 yeah Dec 01 22:44:45 use /tmp/resolv.conf.auto + killall -HUP dnsmasq Dec 01 22:45:21 this should work imo Dec 01 22:46:24 and in the init script you don't need both boot() + start() if they're identical, common boot() is implemented as boot() { start; } Dec 01 22:46:26 well what I did is split DNS....queries go to standard DNS unless they're the vpn domain, and I exclude the vpn server and a couple of other public servers from going through the VPN dns (using internet instead) Dec 01 22:46:37 ah, ok Dec 01 22:47:10 it requires the -S paramater of dnsmasq Dec 01 22:47:18 which currently isn't UCI'd Dec 01 22:47:23 it is Dec 01 22:47:29 is it? Dec 01 22:47:32 I didn't see it Dec 01 22:47:45 yep, list server in config dnsmasq Dec 01 22:48:26 list server '/example.org/1.2.3.4' Dec 01 22:48:27 list server '/foobar.com/5.6.7.8' Dec 01 22:48:56 hmmm....okay so I don't need that then Dec 01 22:48:58 but I have no good idea how to inject that at runtime Dec 01 22:50:01 hmmmm.....well I just have it hardcoded atm anyway Dec 01 22:50:24 is it in LuCI ? Dec 01 22:50:35 I think so Dec 01 22:51:38 ah the server stuff is not provided by the pptp vpn but site specific Dec 01 22:51:45 that's right Dec 01 22:52:09 then its okay to put it into uci or dnsmasq.conf and wrap the whole process into a wizzard or something Dec 01 22:52:17 it's the local router that determins the dnsmasq Dec 01 22:52:18 right Dec 01 22:52:28 based on the ISP Dec 01 22:52:44 and the domain names you just have to know Dec 01 22:52:52 yep Dec 01 22:53:21 (i.e. the VPN server name so that it's available even before PPTP is active else you can't connect, and get disconnected if you are connected) Dec 01 22:53:48 or if the internal IP is different than the one you need for the connection (that's what happened to me) Dec 01 22:53:59 so you basically decoupled your pptp "implementation" from the actual network config and made it a standalone service... did you check how well it works together with e.g. pppoe? Dec 01 22:54:47 yeah the pptp is more a second stage protocol (after acquiring normal ip connectivity) and the uci network config for it is a bit weird Dec 01 22:55:13 there's an "option ipproto" in the original stuff to specify the underlying protocol Dec 01 22:55:20 actually it uses the /etc/config/network and just automatically calls it after dnsmasq is up Dec 01 22:55:34 e.g. static + pptp or dhcp + pptp Dec 01 22:55:46 because when the network is first brought up it can connect due to lack of dns Dec 01 22:55:54 can't I mean Dec 01 22:56:10 yep Dec 01 22:56:36 I think it should be more treated like openvpn and not as an interface protocol Dec 01 22:56:45 it uses ifup right now Dec 01 22:56:53 hmmm...makes sense Dec 01 22:57:01 I don't know how OpenVPN is done Dec 01 22:57:17 was just an example, it is done differently Dec 01 22:57:23 erm separately I mean Dec 01 22:57:33 regardless of the underlying network config Dec 01 22:57:38 right Dec 01 22:58:38 so basically you'd suggest moving it out of /etc/config/network? Dec 01 22:58:54 and the Interfaces LuCI pages? Dec 01 22:59:04 yes imo it would make the whole thing easier Dec 01 22:59:38 too Dec 01 23:00:29 on the other hand pptp depends on pppd so it would be wise to reuse the stuff from ppp/pppoe/pppoa Dec 01 23:01:21 process control. pid file handling and stuff like that Dec 01 23:01:27 right Dec 01 23:02:02 yet the proto pptp + ipproto dhcp notation is weird Dec 01 23:02:25 maybe it should be similar to how it is done for wpa, e.g. proto pptp+dhcp Dec 01 23:03:14 so first setup_interface() is called for the underlying proto and then the pptp client is spawned Dec 01 23:03:54 you said connecting fails due to not-yet-available dns, doesn't the pptp client tries to reconnect? Dec 01 23:05:46 it wasn't....it complained couldn't resolve Dec 01 23:05:57 and that was the only message Dec 01 23:06:27 I see, maybe we should consider patching it then, or look whether there is an option for continuous retrues Dec 01 23:06:29 *retries Dec 01 23:06:44 once it succeeds it does retry Dec 01 23:06:50 hmm Dec 01 23:06:52 or if dns fails to find an address Dec 01 23:07:04 but when there is no dnsmasq it doesn't like it Dec 01 23:07:12 ah so the problem was that the server was not available at all Dec 01 23:07:16 right Dec 01 23:07:18 no resolver Dec 01 23:07:23 right Dec 01 23:08:22 hm Dec 01 23:08:34 is there a way to have a resolver, even one that just says not found, before the interfaces are brought up/ Dec 01 23:09:12 unlikely since not even lo is configured until shortly before pptp is brought up Dec 01 23:09:16 right Dec 01 23:10:04 I think pptp should be patched to handle the missing dns gracefully Dec 01 23:10:23 or pppd, not sure which one is responsible here exactly Dec 01 23:10:58 do you have the exact message from logread? Dec 01 23:11:06 not handy, no Dec 01 23:11:11 k Dec 01 23:12:07 I it's pptp that does that connection.... Dec 01 23:12:08 ok, so to summarize: the init script you did is for bringing up pptp a second time Dec 01 23:12:13 right Dec 01 23:13:27 and there are bunch of pppd options that are needed that aren't currently in LuCI/UCI Dec 01 23:13:40 can you compile a list of them? Dec 01 23:13:44 sure Dec 01 23:14:18 I tried to document the current openwrt stuff here: https://wiki.openwrt.org/doc/uci/network#protocol.pptp.point-to-point.tunneling.protocol Dec 01 23:15:04 persist Dec 01 23:15:04 +mppe required,stateless Dec 01 23:15:04 refuse-eap Dec 01 23:15:04 refuse-pap Dec 01 23:15:04 refuse-chap Dec 01 23:15:04 refuse-mschap Dec 01 23:15:06 lcp-echo-failure 0 Dec 01 23:17:17 persist is passed to pppd if "demand" is empty Dec 01 23:17:24 ah, ok Dec 01 23:17:48 some sites will need eap (i.e. no refuse-eap) Dec 01 23:18:12 lcp-echo-failure can be specified by the "keepalive" option Dec 01 23:18:18 lcp-echo-failure isn't required by PPTP per say but the site I use Dec 01 23:18:19 ok Dec 01 23:19:24 option demand "3 5" -> lcp-echo-interval=3, lcp-echo-failure=5 Dec 01 23:19:51 erm wrong Dec 01 23:19:59 option keepalive "3 5" Dec 01 23:20:13 config 'interface' 'vertical' Dec 01 23:20:13 option 'proto' 'pptp' Dec 01 23:20:13 option 'server' 'scvpn.vertical.com' Dec 01 23:20:13 option 'username' 'username' Dec 01 23:20:13 option 'password' 'password' Dec 01 23:20:14 option 'defaultroute' '0' Dec 01 23:20:16 option 'peerdns' '0' Dec 01 23:20:18 option 'mtu' '1352' Dec 01 23:20:20 option 'ifname' 'ppp1' Dec 01 23:20:22 option 'pppd_options' 'persist +mppe required,stateless refuse-eap refu Dec 01 23:20:24 se-pap refuse-chap refuse-mschap lcp-echo-failure 0' Dec 01 23:21:38 that's what I ended up with Dec 01 23:22:17 using the LuCI Interfaces interface Dec 01 23:23:08 I see Dec 01 23:24:13 then you ifup vertical Dec 01 23:26:00 Marc was suggesting doing it kind of like WLAN...in /etc/config/network, but a separate LuCI interface Dec 01 23:27:33 yes Dec 01 23:28:32 I think we'll make it a task, as the other stuff atm Dec 01 23:28:53 is that an NIU thing? Dec 01 23:29:01 yes Dec 01 23:29:01 I haven't looked at it yet Dec 01 23:29:50 so for the init.d script, do you instead want to patch pptp to deal gracefully with no resolver? Dec 01 23:30:00 that's the only thing that's really needed Dec 01 23:30:00 yes, this is the plan Dec 01 23:30:22 the dnsmasq stuff is because I didn't find the -S stuff in LuCI Dec 01 23:30:35 ok, I see Dec 01 23:30:46 the dnsmasq stuff needs rework anyway Dec 01 23:32:32 so is there anything you want to me to at this point? Dec 01 23:34:10 oh, yeah I also added a route in ip-up.d Dec 01 23:35:05 routes can be specified with uci as well Dec 01 23:35:17 https://wiki.openwrt.org/doc/uci/network#ipv4.routes Dec 01 23:35:41 but I did mine dynamically based on the IP of the PPP connection Dec 01 23:36:01 or interface Dec 01 23:36:07 since it changes Dec 01 23:36:19 ah Dec 01 23:36:22 hm, was it a netroute? Dec 01 23:36:28 yes Dec 01 23:36:50 the interface stuff should be no issue since the "uci routes" are brought up by hotplug and referenced by logical ifname Dec 01 23:37:03 if [ "$VR_NET" = "192.168.1" ]; then Dec 01 23:37:04 route add -net 192.168.1.0 netmask 255.255.255.0 gw $PPP_REMOTE Dec 01 23:37:04 fi Dec 01 23:37:30 ah ok Dec 01 23:38:38 hmm, hard to do that in a generic way Dec 01 23:39:05 no wait Dec 01 23:39:27 if you ommit the gateway option in uci route sections, the gateway is taken from the referenced interface Dec 01 23:40:01 would you dev pppX? Dec 01 23:40:41 http://openwrt.pastebin.com/m6e1fdd78 Dec 01 23:40:59 this should do the trick with both gw X and dev Y Dec 01 23:41:49 ok Dec 01 23:42:09 just a sec; I'm going to try converting to a proper UCI'd PPTP Dec 01 23:43:56 ok, I just checked. The -S stuff is definitely not in the version of LuCI I have on my router (but it's r17550) Dec 01 23:44:07 btw, was the error you seen in pptp something like "gethostbyname 'foo': name server error" Dec 01 23:44:35 I'm sorry I don't remember; give me a sec and I'll tell you Dec 01 23:51:44 Ok, it looks like the second pptp isn't needed I disabled it and left everthing else and rebooted and it worked fine Dec 01 23:52:54 oh wait Dec 01 23:53:00 disable didn't work Dec 01 23:53:20 it crated an Spptp entry so I didn't notice it Dec 01 23:58:07 Nope Dec 01 23:58:17 It doesn't have any messages at all Dec 01 23:58:22 it probably isn't dns Dec 02 00:36:32 ping xMff **** ENDING LOGGING AT Wed Dec 02 02:59:57 2009