[00:45] <Sapote> valid channels: 1 2 3 4 5 6 7 8 9 10 11 12 13 14
[00:45] <Sapote> :)
[00:45] <[mbm]> nbd: sounds like an idea
[00:45] <Sapote> wlc eth1 channel 14
[00:47] Last message repeated 1 time(s).
[00:47] <Sapote> eth1: Invalid argument
[00:47] <Sapote> wlconf eth1 down
[00:48] <Sapote> wlconf eth1 up
[00:48] <Sapote> wlc eth1 channel 14
[00:48] <Sapote> wlc eth1 channel
[00:48] <[mbm]> Sapote: this is an irc channel, not a terminal :)
[00:48] <Zer0her0> what's w/ sapote?
[00:48] <Sapote> 14
[00:48] <Sapote> lol
[00:48] <Sapote> iptraf
[00:48] <Zer0her0> he msged me useless crap
[00:49] <Sapote> iptraf compiled for wrt
[00:49] <frop> what should return "iwlist eth1 bitrate"?
[00:49] <Sapote> iptraf_2.7.0_mipsel.ipk ncurses_5.2_mipsel.ipk
[00:49] <frop> is this normal?
[00:49] <frop> eth1 3 available bit-rates :
[00:49] <frop> -737870 kb/s
[00:49] <frop> -603652 kb/s
[00:49] <frop> 4.2445 Mb/s
[00:51] <[mbm]> frop: normal or not it's wrong ...
[00:52] <dgsgeo> sorry fot the dumb question ... been looking for an hour ....
[00:52] <frop> [mbm]: why??
[00:52] <frop> :P
[00:52] <dgsgeo> how do I tell which version WRT54G hardware I have?
[00:57] <[mbm]> or you just look at what's printed on the bottom :P
[00:58] <Wowzers> the version is like 2 inches from the SN on the bootom of the wrt
[00:59] <Wowzers> i just moved over to the Whiterussian release, is there a 'wl' utility for the WhiteRussian
[01:02] <[mbm]> Wowzers: it's part of the 'non-free' set
[01:04] <pyromaniac> Wowzers, just download the package
[01:04] <pyromaniac> ipkg install URL
[01:04] <pyromaniac> for instance
[01:04] <pyromaniac> find the wl packagfe
[01:04] <pyromaniac> *package
[01:04] <nbd> /wi2
[01:04] <pyromaniac> on tracker.openwrt.org
[01:04] <nbd> oops
[01:05] <pyromaniac> :D
[01:05] <[mbm]> it's in the whiterussian/packages/non-free dir
[01:15] <Wowzers> i work at a college in So Cali and my boss was wanting to hire a full -time wireless guy
[01:15] <Wowzers> we got 3 campuses with like 130 Cisco 1200 AP's
[01:16] <[mbm]> spiffy; does that come with benefits?
[01:17] <Wowzers> ya, i work part-time there, and the full timers say the benefits are good because its in the education sector
[01:25] <Wowzers> how come its called non-free
[01:25] <[mbm]> binary only, no license
[01:25] <Wowzers> oic
[02:22] <MrLebowski> openslug
[02:23] <MrLebowski> doh
[02:24] <truth> [mbm] you were right it wasnt the clk setting , setting it to 216 seemed to wipe out some nvram settings including ip addresses.... thx again for the help
[02:25] <[mbm]> truth: hmm haven't seen that happen before
[02:27] <truth> got to re-image this machine...
[03:05] <fishhead> http://www.groklaw.net/article.php?story=20050714144923365 <--- is it just me or is SCO *CANUCKED*??
[03:34] <knoppix> need help
[03:35] <trench> knoppix: topic?
[03:35] <knoppix> openwrt seems to have lost the ability to give me a ip
[03:35] <trench> read the docs
[03:35] <knoppix> 5 days uptime and it just died
[03:35] <knoppix> i have already reinstalled
[03:37] <[mbm]> the dhcp server for the lan or getting an ip off the wan?
[03:37] <knoppix> lan ip
[03:37] <knoppix> first my static ips died anf then i couldnt get an ip at all
[03:37] <knoppix> im in fail safe now
[03:39] <[mbm]> dnsmasq running?
[03:39] <knoppix> yes
[03:39] <[mbm]> and you're using the whiterussian release?
[03:40] <knoppix> yes
[03:40] <knoppix> and i have cleared my nvram
[03:41] <knoppix> im using squash
[03:41] <[mbm]> in whiterussian it looks for an existing dhcp server before enabling dnsmasq's dhcp server
[03:41] <knoppix> no
[03:41] <knoppix> wrt is the only one
[03:41] <[mbm]> check ps and see if it passed arguments to dnsmasq
[03:44] <knoppix> -l /tmp/dhcp.leases -K -F 192.168.1.100,192.168.1.250,255.255.255.(edge of window)
[03:44] <[mbm]> yeah, dhcp server is running ..
[03:44] <knoppix> since this is failsafe i cant be sure its running in normal
[03:45] <[mbm]> you can't get in normally?
[03:45] <knoppix> even setting my ip to 192.168.1.2 i cant ping it
[03:45] <[mbm]> you might want to run "firstboot" while you're in failsafe
[03:45] <[mbm]> that'll reinitialize the jffs2 partition used for normal boots
[03:46] <knoppix> running
[03:47] <knoppix> if the jffs2 is corrupted that would explin it but why would it die for no reason?
[03:47] <[mbm]> oh, this isn't a result of messing with a config or reflashing?
[03:50] <stonezone> anyone have experience on how many tunnels openwrt/openvpn can handle?
[03:52] <knoppix> no [mbm] like i said 5 days uptime then my port fwd didnt work and i saw my lan ip changed and then i lost connectivity
[03:52] <[mbm]> knoppix: hmm did you check nvram while in failsafe?
[03:54] <knoppix> i erased it
[03:54] <knoppix> ok firstboot done
[03:54] <knoppix> brb
[03:54] <[mbm]> no need to reboot
[03:55] <[mbm]> if you want to restart the interfaces under the normal ip: unset FAILSAFE; /etc/init.d/S40networking
[04:02] <chandi> hey guys, where is the doc about creating a new package with the files I need on my wrt ?
[04:02] <[mbm]> did you read the docs in the openwrt source?
[04:05] <chandi> mbm by source you mean the cvs to compile a firmware ?
[04:07] <[mbm]> chandi: that's one of many ways to obtain the source
[04:07] <chandi> mbm okkk:)
[04:10] <Ephraim> I just upgraded to white russian and now my wrt won't associate :-(
[04:11] <Ephraim> I've checked wl0_crypto and it isn't set on either wrt
[04:11] <Ephraim> any ideas to check? I cant' find anything in the forums that seems to be related.
[04:14] <Ephraim> [mbm] - congratulation on graduating
[04:17] <fishhead> MUST BITE CANUCKS
[04:18] Action: fishhead SINKS HIS TEETH INTO WEEDY'S LEG
[04:18] <Weedy> ..
[04:18] <fishhead> :p
[04:18] Action: Weedy kills fishhead with fyre
[04:20] <Weedy> crap
[04:20] <Weedy> my ip changed
[04:34] <Paler2489> Someone chats with me. I feel a pain very much
[04:34] <[mbm]> no
[04:35] <Weedy> my god
[04:35] <Weedy> http://www.artlebedev.com/portfolio/optimus/
[04:35] <Weedy> it is a thing of beaty
[04:35] <[mbm]> it's also a photoshop fake
[04:36] <Weedy> really?
[04:36] <[mbm]> yep
[04:36] <Weedy> awww
[04:36] <Weedy> i was hoping i could buy one
[04:37] <[mbm]> I imagine a mini display on each key would be very expensive
[04:37] <Weedy> no
[04:37] <Paler2489> my god
[04:37] <Weedy> OLEDS are supposed to be quite cheap
[04:37] <stonezone> if they its fake on /. it must be true
[04:38] <stonezone> http://slashdot.org/comments.pl?sid=155812&cid=13065107
[04:39] <fishhead> yeah they are
[04:39] <fishhead> the only bad thing about oleds is lifespan
[04:39] <fishhead> HOLY MOTHER OF CANUCK
[04:39] <stonezone> http://www.artlebedev.com/portfolio/mus/
[04:39] <fishhead> IS THAT COOL
[04:40] <fishhead> wow
[04:40] <stonezone> thats funny
[04:40] <fishhead> I wonder what happens if you punch it
[04:40] <fishhead> "FUCK YOU ASSHOLE!"
[04:41] <philv> So much racism in here ;_;
[04:42] <Ephraim> hmm - "wifi" on the client wrt gives the usual error, but seems to do what it supposed to do, but "wifi" on the AP gives a new error
[04:42] <Ephraim> Error for wireless request "Set Tx Power" (8B26) :
[04:44] <Weedy> [22:20] <Weedy> which ip is cooler
[04:44] <Weedy> [22:20] <Weedy> 69.197.36.142 or 69.198.126.61
[04:44] <philv> Weedy: I definitely say 134.117.69.21
[04:44] <philv> the .69 class C is just way too cool
[04:45] <matled> 222.173.190.239!
[04:53] <[BeaR]> heya all
[04:53] <[BeaR]> i've just installed whiterussian
[04:53] <[BeaR]> but... netstumbler says that WEP is enabled
[04:54] <[BeaR]> i havent set up wep
[04:54] <[BeaR]> wl0_wep=disabled
[04:54] <[BeaR]> anyone seen this before
[04:54] <[BeaR]> ?
[04:59] <Weedy> is ther light on?
[04:59] <[BeaR]> yeah
[04:59] <[BeaR]> ican see the SSID
[04:59] <[BeaR]> but it wants a wep key
[05:01] <[mbm]> nvram unset wl0_crypto; nvram commit; wifi up
[05:02] <Ephraim> [mbm] - any idea n what the error message is telling me "Error for wireless request "Set Tx Power" (8B26) :"
[05:03] Action: [mbm] mumbles something about the wifi config being horribly screwed up in rc1
[05:04] <Ephraim> hmmm - good thing it's rc1 :-)
[05:05] <[mbm]> all of that stuff's been fixed already; just making sure *everything* works before we do an rc2
[05:05] <Ephraim> ahh, can I get the "fixed" stuff in cvs?
[05:05] <[mbm]> yep
[05:06] <Ephraim> I thought I was going crazy there for a while... I think you've restored my sanity :-)
[05:09] <Ephraim> [mbm] - if I've downloaded whiterussion by CVS, do I need to remove the directory and start again or can I just download the latests CVS over top of it?
[05:10] <[mbm]> did you check it out from cvs before?
[05:10] <Ephraim> yeah - per the instructions on the documentation
[05:11] <[mbm]> Ephraim: then you can just do an update: cvs -z3 -q up -Pd -r whiterussian
[05:12] <Ephraim> while I'm in the openwrt directory?
[05:13] <Ephraim> "cvs -d:pserver:anonymous@openwrt.org:/openwrt co -rwhiterussian openwrt" is what I used before
[05:17] <Ephraim> [mbm] - uh ok, I think I got it. I assume the relevant changesa re in the wlcompat package?
[05:20] <[mbm]> Ephraim: did you look at the number of files that were updated by that command?
[05:22] <Ephraim> [mbm] - yeah, not too many and the only one that seems really relavant is the wlcompat. losts of updates to the scripts in the target directory and some ppp stuff.
[05:28] <gravix> possibly stupid question: which firmware will allow client mode on a WPA2 network? I've been trying DD-WRT, but no dice...
[05:28] <[mbm]> any of them will with the rigth setup
[05:29] <gravix> okay, i'll keep dicking around with DD-WRT... thanks much
[05:33] <Ephraim> I have to admit - mucking around with openwrt brings back fond memories of trying to get linux to work way back in the early days :-)
[05:34] <Ephraim> ls
[05:34] <Ephraim> oops
[05:34] <Ephraim> wrong window :-)
[05:34] Action: gravix is so far at the end of his rope he just might try openwrt
[05:37] <score> hrm, any solutions for wrt54g that lock up because of bittorrent?
[05:39] <gravix> hm "lock up"?
[05:40] <dtm> Ephraim: heheheh yeah but wrt54g is more powerful than my first linux host ;)
[05:40] Action: splinterfl started Redhat linux on a AST 25mhz
[05:40] <dtm> 20 MHz 386sx with 5MB RAM, 100MB hd
[05:41] <dtm> 5 hrs 40 mins to compile linux 1.2.13
[05:41] <Ephraim> :-)
[05:41] <dtm> bewm
[05:41] <splinterfl> still in use?
[05:42] <splinterfl> heard of a few 386 files servers still hanging around... overload by it depts
[05:42] <splinterfl> overlooked
[05:42] <Ephraim> My 33mHz 486 is still in use, but it an unglorious doorstop
[05:42] Action: splinterfl has 9 75mhz P1's still in use as DNS servers
[05:42] <Ephraim> It weighs almost as much as the door it holds open :-)
[05:45] <splinterfl> wonders what could 20 barely used WRTs on a LAN do...
[05:46] Action: splinterfl thinks of all these wasted CPU cycles
[05:46] <Ephraim> a seti client?
[05:46] <splinterfl> hum...
[05:46] <gravix> it looks to me like the linksys beta firmware is the only thing that works with wpa2
[05:47] <Ephraim> gravix - openwrt does
[05:47] <Ephraim> you just have to configure it
[05:47] <Ephraim> gotta go - soo you folks later
[05:47] <Ephraim> s/soo/see/
[05:47] <gravix> thank you ephraim, goodbyeeeee!
[05:57] <score> well, lock up meaning that all connections seem to get dropped
[06:10] <[mbm]> http://www.ebaumsworld.com/interactivebuddy.html .. amusing waste of time
[06:10] <AgentHH> Hay nbd
[06:12] <matled> [mbm]: is this only 6 balloons sticked together or is something wrong with my flash player?
[06:12] <[mbm]> matled: it's a cheap stick figure that you can abuse
[06:13] <matled> mhk, really waste of time :)
[06:13] <matled> especially cpu time
[06:14] <matled> 99% cpu usage and loadavg 1.74, flash doesn't seem to be that good on linux
[07:36] <gravix> sigh... so frustrating trying to get this router to work
[07:36] <gravix> i've been loading and unloading for hours and hours
[07:37] <sbingner> [mbm]: you around? heh
[07:50] <JonasNZ> hey, any1 here own a dlink dsl-500
[09:01] <CanDoo> is there any wrt formware that support repeater mode?
[09:02] <JonasNZ> any1 here own a DLINK DSL-500
[09:03] <[mbm]> CanDoo: let's see .. they all use the same wireless driver which does wds mode .. just need to configure it (which might not be possible in some firmwares)
[09:07] <CanDoo> well wds is all well and good
[09:07] <CanDoo> i'v been playing with WDS
[09:08] <CanDoo> but wDS doens't allow the use of the AP as for cleints and point to point connections
[09:08] <CanDoo> atleast not that i'v seen
[09:09] <[mbm]> CanDoo: um, yes it does ...
[09:19] <Kaloz> .
[09:20] Action: [mbm] wonders how many other firmwares send people to us .. "you bricked your router? go tell the openwrt guys that openwrt broke it .."
[09:21] <coder> if the 'author' of 'another' firmware says that, he is a wanker
[10:13] <Weedy> just wondering how much of a beating can openWRT take?
[10:14] <[mbm]> go see; report your results
[10:17] <CanDoo> bah
[10:17] <CanDoo> this pisses me off
[10:17] <CanDoo> where can i find the source for linksys-tftp cleint
[10:18] <CanDoo> so i am able too set a password for this firmware
[10:18] <CanDoo> POS
[10:19] <[mbm]> linksys tftp client is crap; don't use it
[10:20] <olli_04> CanDoo: on win use tftpd32.exe on *nix use tftp or atftp
[10:20] <CanDoo> well the standard generic tftp cleint doens't work under debian
[10:20] <CanDoo> is kinda the catch
[10:20] <CanDoo> bitching aobut passwords and such
[10:20] <CanDoo> that the tftp client knows nothing about
[10:21] <olli_04> CanDoo: have you tried atftp ?
[10:21] Action: [mbm] points to the spiffy install guide, recently updated
[10:21] <CanDoo> the tftp password the firmware uses should be the same as the admin password
[10:21] <CanDoo> and preceed the linename to be uploaded correct?
[10:21] <CanDoo> er filename
[10:24] <olli_04> CanDoo: if you upload a image to your router and it aks for a password, please read: http://wiki.openwrt.org/OpenWrtDocs/Installing#head-344b77cce4d63bd941eb782ea25d37f9e8fd9d19
[10:25] <CanDoo> hhe
[10:25] <CanDoo> one step ahead of you on that one
[10:26] <CanDoo> problem solved
[10:26] <CanDoo> that is kinda strange
[10:26] <CanDoo> i don't understnd why have a tftp cleint ontop of the bootloaders tftpd
[10:26] <CanDoo> although form a secruity stnadpoint i do understand
[10:29] <[mbm]> you don't understand why a tftp server requires a tftp client?
[10:29] <olli_04> ooh
[10:30] <pp_> mbm: probably means the linksys tftpd with password hack
[10:43] Action: Weedy wonders if openwrt can take 12k bt peers
[10:50] <Kaloz> openwrt can, just the hardware can't
[10:50] <Kaloz> you don't have enough memory for that imho
[10:51] <[mbm]> even on the gs you only get 32M
[11:11] <CanDoo> well finaly
[11:13] <CanDoo> whoohooo i did it
[11:13] <CanDoo> yeah!
[11:13] <thefRont> openwrt running?
[11:15] <CanDoo> yes
[11:15] <CanDoo> it's WDS time
[11:15] <CanDoo> gettign the tftp workign right is a little tricky
[11:15] <CanDoo> i had did it a few years ago
[11:15] <CanDoo> when i first got the wrt
[11:15] <CanDoo> but had forgotten what i had done too redo it
[11:20] <Weedy> shit
[11:20] <Weedy> why did i leave scsi in the kernel
[11:20] <CanDoo> 000F66A9BB54
[11:39] <olli_04> pau: is your wds still working fine?
[11:39] <pau> olli_04 no man
[11:39] <pau> like
[11:40] <nitram> mhm... i am using pppoecd on an old openwrt box. on boot the ppp0 device is not up yet, it needs a while to come up. in the meantime machines in the lan try to connect to $WORLD. this leads to conntrack beeing used. once the ppp0 device is up, these previous unsuccessful "connections" remain in conntrack and lead to successive pakets not being masqueraded anymore. ip_dynaddr does not help in this case. will setting up a dummy ppp0 until ppp0 is really up maybe
[11:40] <nitram> help?
[11:40] <pau> client wifi ping AP1 but can't ping AP2, but, client by cable ping AP1 and can ping AP2
[11:40] <CanDoo> hmm
[11:41] <CanDoo> i'v set my linksys v2.2 and v2.6 to p2p reter mode. and WDS is activated on my wrt
[11:41] <CanDoo> but traffic doen'st seem to pass
[11:41] <nbd> nitram: you could try to upgrade to latest whiterussian rc
[11:42] <nitram> nbd: i want to really solve this problem and avoid any unneccessary upgrading just on a hunch that it might work
[11:42] <nbd> nitram: it could be a bug in the old netfilter stuff - if it is, there's no other way to fix it other than upgrading
[11:43] <nitram> this problem is reproducible and i heard of a couple of people who have this problem
[11:43] <CanDoo> how does adHOC differ from AP mode?
[11:43] <nitram> nbd: it is mostly a udp problem
[11:44] <nitram> nbd: do you have any idea how the ip_dynaddr stuff works?
[11:44] <nbd> nitram: no
[11:44] <nitram> damn
[11:44] <nitram> i'd like to know how the ip-change is recognized
[11:45] <nitram> that's why i would like to have a ppp0 dummy and then replace the dummy-ip with the real ip
[11:45] <nitram> and already have a default route on that
[11:45] <nbd> nitram: pppd does that when on-demand dialling is enabled
[11:46] <nitram> mhm
[11:46] <nitram> still using the pppoecd
[11:46] <nbd> new openwrt versions use pppd
[11:47] <nitram> as i said this is a highly customized openwrt
[11:47] <nbd> what did you customize?
[11:47] <nitram> so i am not really in the mood to redo everything just yet ;)
[11:47] <nbd> i can understand that
[11:47] <nitram> routing after conntrack, olympic diffserv etc
[11:48] <nbd> ah, ok
[11:48] <nitram> everything works, just these pita udp packets
[11:49] <nitram> every once in a while after the reboot when a udp packet arrives while the ppp0 dev is still not up
[11:49] <nbd> do you reboot your device that often?
[11:49] <nitram> every night, because ip changes are not detected properly
[11:49] <nitram> maybe i should try pppd
[11:50] <nitram> after reconnect the same problem
[11:50] <nitram> the old ip is still used for masquerading
[11:52] <Dabian> OK .. I think I managed to lock myself completely out from my wl-500gd. I set up a bridge on vlan0 that included vlan1 .. and both telnet and ssh is refused on both interfaces, and it doesn't seem to help to enter failsafe. Is there a way to reset the nvram, or should I keep trying boot failsafe?
[11:53] <nbd> Dabian: how do you try to boot failsafe?
[12:00] <CanDoo> 000C41188A6A
[12:02] <Dabian> nbd: I turn it on, then I wait till all the lamps are not on .. then I press and hold reset.
[12:02] <Dabian> nbd: COunt to seven, and release the button.
[12:02] <Dabian> nbd: I guess it should work?
[12:06] <Weedy> is this correct? because it does not seem to be working. iptables -t nat -A postrouting_rule -o $LAN -p tcp -s 192.168.1.0/24 -d 192.168.1.100 -m multiport --dports 59,6967,6968,8394 -j SNAT --to-source 192.168.1.1
[12:10] <nbd> Dabian: try waiting a bit longer (about 3 seconds)
[12:13] <CanDoo> 000c41188a6a
[12:14] <Kaloz> CanDoo: learn using your mouse :p
[12:14] <CanDoo> hehe
[12:14] <CanDoo> my apologies for any disturbance
[12:14] <CanDoo> i was usieng xchat as a scratch pad
[12:21] <Dabian> nbd: OK :-)
[12:26] <CanDoo> do any of you own a wap11 2.6 or 2.2 device?
[12:26] <Dabian> nbd: If I succeed, it will ignore all nvram settings and I should be able to ssh or telnet, right?
[12:26] <nbd> Dabian: telnet, yes
[12:27] <Dabian> Hmm .. I can ping 192.168.1.1 but not telnet or ssh .. connection refused.
[12:28] <Dabian> Somehow I have the feeling I'm failing to enter failsafe :/
[12:29] <Dabian> Though .. the air-led is lit up!
[12:30] <nbd> Dabian: then it's probably not failsafe
[12:30] <Dabian> No air in failsafe?
[12:31] <nbd> normally it should just do ifup lan and run the telnet server
[12:31] <Dabian> Ignoring the nvram, right?
[12:31] <nbd> normally, yes
[12:31] <Dabian> I turned off the lan in the nvram though.
[12:31] <nbd> well... not completely
[12:31] <nbd> just overriding it
[12:31] <nbd> how did you turn it off?
[12:31] <Dabian> proto=none
[12:32] <Dabian> lan_proto=none
[12:32] <Dabian> bridging it with wan.
[12:32] <Dabian> bridgeing
[12:32] <nbd> ah, that explains
[12:32] <nbd> seems like failsafe doesn't handle that correctly
[12:32] <Dabian> So, now the thing is broken?
[12:33] <Dabian> I need to make a custom image to flash on?
[12:33] <nbd> did you use squashfs or jffs2?
[12:33] <Dabian> yes
[12:33] <Dabian> I used squashfs.
[12:33] <nbd> which one?
[12:33] <nbd> ah
[12:33] <nbd> ok
[12:33] <nbd> then i'll give you a new image that should boot in failsafe correctly
[12:33] <Dabian> OK .. cool
[12:34] <Dabian> Did I discover a bug?
[12:34] <nbd> Dabian: yeah
[12:34] <Dabian> Cool :)
[12:34] <nbd> Dabian: i'll tell you when the build is ready
[12:34] <Dabian> Thanks!
[12:34] <nbd> Dabian: all your settings should remain intact after reflashing
[12:35] <Dabian> Even the j2ffs stuff?
[12:35] <nbd> yeah
[12:35] <Dabian> wow
[12:35] <nbd> you're only overwriting the readonly part of it
[12:35] <Dabian> Thats nice about squashfs :)
[12:36] <Dabian> I am puzzled that I can ping the device ... but I guess thats part of the bug.
[12:37] <nbd> i have no explanation for this
[12:39] <CanDoo> this stinks
[12:41] <nbd> what stinks?
[12:41] <CanDoo> well
[12:41] <CanDoo> i'm trying to get my wap11 v2.2 and v2.6 to talk to my wrt54G
[12:42] <CanDoo> WDS doen'st seem to work
[12:42] <CanDoo> the wap11's have no WDS settings
[12:42] <CanDoo> they have reapter and point to point settings
[12:42] <CanDoo> but dont' seem to talk wot the WDS on the wrt
[12:42] <nbd> then maybe they're not able to do wds
[12:42] <CanDoo> they wont' do client mode either
[12:43] <nbd> Dabian: http://openwrt.inf.fh-brs.de/~nbd/test/
[12:44] <Dabian> nbd: : Thanks!
[12:44] <nbd> let's see if this works
[12:44] <Dabian> Yeah :)
[12:45] <Dabian> nbd: Which image do I want?
[12:45] <Dabian> http://openwrt.inf.fh-brs.de/~nbd/test/openwrt-brcm-2.4-squashfs.trx ?
[12:46] <nbd> Dabian: yeah
[12:46] <wickus> nbd: hi
[12:46] <nbd> wickus: hi
[12:47] <wickus> nbd: i checked again the vlynq stuff and acx111
[12:47] <wickus> no support for vlynq in the acx sources
[12:47] <nbd> of course not
[12:47] <nbd> maybe we'll have to add that
[12:48] <wickus> ok
[12:54] <Weedy> you know what i just thought of
[12:54] <Weedy> with the SD card mod
[12:55] <Weedy> can you run 2 SD cards?
[12:57] <frop> i'd like to run at least one
[12:57] <frop> :)
[12:58] <Weedy> cause i was like
[12:59] <Weedy> if you could have 2
[12:59] <nbd> Dabian: works?
[12:59] <Weedy> raid them
[12:59] <frop> eheh
[13:00] <Dabian> nbd: Had a little trouble uploading .. but if I started up with reset depressed, it ate the image :)
[13:00] <Dabian> nbd: : How long do I wait before I powercycle?
[13:00] <nbd> Dabian: no idea. 2 minutes should be fine
[13:00] <nbd> Dabian: it will not reboot automatically
[13:00] <nbd> Dabian: you'll have to pull the plug
[13:01] <Dabian> Nope .. thats special for wl-500gd, I guess :)
[13:01] <nbd> yeah
[13:01] <frop> but a question...as the deluxe hasn't jtag...how to debrick it?
[13:02] <Dabian> frop: Some routers have screws. The wl-500gd is one of them.
[13:02] <nbd> frop: cfe dead -> not possible, nvram screwed -> pin shorting
[13:02] <Weedy> woah
[13:02] <frop> ohh
[13:02] <Weedy> so dont kill the cfe
[13:03] <Weedy> >.>
[13:03] <frop> isn't so good
[13:03] <frop> :)
[13:03] <frop> i'll be afraid with friend's one
[13:03] <nbd> well.. if you don't mess with cfe, it's no problem
[13:03] <frop> he'll kill me if i briks his one
[13:04] <frop> nbd: never play with mine too...still
[13:04] <frop> btw, Motorola part on Installing web page doesn't fit to me...as i need 4MB generic firmware
[13:05] <nbd> frop: ?
[13:06] <frop> heh on website documentation
[13:06] <nbd> what do you mean?
[13:06] <frop> http://wiki.openwrt.org/test.cgi/OpenWrtDocs/Installing#head-16e8d1f9495b84660425ea230a05e0305b71bdd1
[13:06] <Dabian> Lets go over the procedure to reach fail-safe on the wl500gd again ...
[13:06] <Dabian> 1. Plug in the power.
[13:06] <Dabian> 2. Wait 3 seconds.
[13:06] <Dabian> 3. Push in reset button, and hold it.
[13:06] <Dabian> 4. Wait 7 seconds.
[13:06] <Dabian> 5. Release reset button.
[13:06] <Dabian> 6. Wait about 10 seconds and you should be in fail-safe?
[13:06] <Dabian> s/10/30/
[13:06] <frop> nbd: Download the motorola firmware image (either the squashfs or the jffs2-8mb version) from the website. (Note: The motorola has 4mb flash, but requires the 8mb version. This is an ignominously confusing naming problem that hopefully will be fixed. At the moment the motorola-jffs2-4mb is entirely useless.)
[13:06] <nbd> Dabian: seems right
[13:07] <frop> for me, with my moto, only "generic-4MB" is working
[13:07] <nbd> frop: could you update that web page, please?
[13:07] <Dabian> ok .. I try again.
[13:07] <frop> nbd: ok...i'll add my "feature" at bottom
[13:08] <CanDoo> how does Adhoc differ form AP mode?
[13:08] <frop> ...like: "if this image doesn't work..."
[13:08] <nbd> frop: what version do you have?
[13:09] <frop> v3
[13:09] <nbd> frop: maybe it's version specific
[13:09] <frop> mmh...don't...we'd need feedback
[13:09] <frop> i use always generic 4mb and it always works...so...don't know
[13:10] <frop> where're major differences between "generic" and "motorola" firmware?
[13:10] <Dabian> still no luck
[13:10] <frop> headers only?
[13:11] <frop> Dabian: take reset pressed for more
[13:11] <Dabian> frop: OK, I try again :)
[13:11] <frop> Dabian: like 15/20 secs...
[13:11] <nbd> Dabian: maybe try to start pressing reset one second earlier
[13:11] <Dabian> nbd: OK.
[13:12] <nbd> hmm.. i was wrong
[13:12] <nbd> lan_proto is in the overrides file
[13:12] <nbd> just in a different place
[13:12] <nbd> so no bug there
[13:12] <nbd> has to be something else
[13:13] <Dabian> ok
[13:13] <Dabian> nvram set wan_ifname=br0
[13:13] <Dabian> nvram set wan_ifnames="vlan0 vlan1"
[13:13] <Dabian> nvram set wan_proto=static
[13:13] <Dabian> nvram set wan_ipaddr=192.168.1.1
[13:13] <Dabian> nvram set wan_netmask=255.255.255.0
[13:13] <Dabian> nvram set lan_proto=none
[13:15] <frop> ??
[13:15] <frop> little strange to my eyes
[13:15] <Dabian> My setup is different .. the IP will change, once I got a working config.
[13:16] <frop> so why not use lan_ipaddr too?
[13:16] <frop> and lan_proto static?
[13:16] <Dabian> frop: I am not sure if I can.
[13:16] <Dabian> frop: I would like to though.
[13:16] <frop> why not?
[13:17] <Dabian> You're supposed to set a bridge up like this.
[13:17] <frop> i've no bridge
[13:17] <frop> sepated lan and wlan
[13:18] <Dabian> I basicly took the stuff from the config-documentation, and replaced lan with wan, and wifi with lan.
[13:18] <frop> lan set only an ip addr
[13:18] <frop> but WHY??
[13:18] <frop> maybe i'm only late
[13:18] <Dabian> I have several ip-addresses behind the router, and I don't want them to be nattet.
[13:19] <Dabian> I don't have a router locally, I only have an external gateway.
[13:19] <nbd> you could have just used lan_*
[13:19] <Dabian> nbd: That would have been better, and have achieved the same goal?
[13:20] <nbd> Dabian: you wouldn't need to change all the other stuff
[13:20] <nbd> Dabian: the interfaces function in the same way
[13:20] <frop> well wan and lan, in my thought, are only "alias" to physical router's port
[13:21] <frop> is it wrong?
[13:21] <nbd> right
[13:21] <frop> cause they share the same NIC
[13:40] <minipanda> yeah! finally, i find here!
[13:40] <minipanda> hi, guys, i just buy a wrt54g-cn box today
[13:45] <crashev> minipanda: go and return it while you can!
[13:45] <crashev> ;]
[13:46] <minipanda> crashev: ooops, but why?
[13:46] <chaimj> how do you get tcpdump to read from multiple dump files ?? (tcpdump -r )
[13:46] <crashev> minipanda: just joking...
[13:47] <chaimj> oops, wrong channel
[13:48] <minipanda> crashev: oh, some of my friend told me i should not buy wrt54g but wrt54gs for 8Mb flash
[13:48] <minipanda> crashev: so will asterisk working on wrt54g or wrt54gs very well?
[13:48] <crashev> probably yes, havnt tryed
[13:49] <minipanda> crashev: but why you choose to use wrt54g then?
[13:50] <crashev> because it has opensource firmware, because its made by linksys with is division of cisco, because its not very expensive, because it runs linux, because its very customizable...
[13:51] <minipanda> crashev: AFAIK, dlink and netgear have a lot of AP running linux too
[13:52] <minipanda> which are cheaper than linksys
[13:52] <minipanda> and even Asus device
[13:52] <crashev> havnt heard about them - which dlinks run linux and has opensource firmware?
[13:52] <minipanda> crashev: i choose wrt54g is only because i google out that some geeks already run asterisk on wrt54g
[13:52] <crashev> yes there are packages in whiterussian
[13:52] <minipanda> crashev: dunno status about firmware, but why we take care too much about fireware?
[13:53] <minipanda> crashev: so what's your main function of wrt54g?
[13:53] <minipanda> crashev: i get wrt54g because i want to test my wireless handover patch
[13:54] <crashev> http://pawq.bioinfo.pl/wrt54g/wificonf.c <- wifi with COUNTRY SET so u can use channels > 11...
[13:55] <crashev> minipanda: I also create my own apps for WRT54g, thats why I care about it
[13:55] <d00f> does openwrt use last linksys firmware gpl ? (4.00 or 4.50)
[13:55] <Dabian> nbd: : I will try if I can enter fail safe again.
[13:55] <pp_> d00f: openwrt is already using a much later kernel :)
[13:55] <pp_> 2.4.30-based, not 2.4.20
[14:04] <CanDoo> hehe
[14:04] <CanDoo> stupid bot
[14:13] <fromoze> Hi, I wanted to ask a short question. I was waiting for a wrt54g but a wrt54gs arrives instead. Should I keep wrt54gs or ask for wrt54g? Is for a home-lan, but I would like to intrude wireless group in my town.
[14:15] <nbd> fromoze: wrt54gs is better than the g
[14:15] <fromoze> sorry if it's a wrong place for my question :/
[14:15] <olli_04> fromoze: geep the gs
[14:15] <fromoze> Ok, thanks!
[14:15] <fromoze> I'll keep it.
[14:28] <CanDoo> i have completed my wds and web instalation
[14:28] <CanDoo> and it seems to be working perfectly
[14:37] Action: moonwatcher looks for nbd...
[14:39] <nbd> hey
[14:39] <nbd> pptp is not done yet. had to fix a nasty ppp bug...
[14:40] <pp_> which reminds me to check whether my pppoe over br0 would mystically work now
[14:41] Action: moonwatcher will wait patiently...
[14:41] <moonwatcher> i hope the howto helped...
[14:55] <d00f> ++
[14:56] <dothebart> hy.
[15:00] <dothebart> i'm wondering if ipkg_depends: Warning: kernel mentioned in dependency but no package found in /usr/lib/ipkg/lists and installing new nic modules will render the router unusable...
[15:00] <nbd> dothebart: maybe you should update
[15:01] <dothebart> i'm doing an upgrade, but it seems as if it just is able to find the new kernel modules, but not the kernel itself?
[15:02] <dothebart> it allso updated the dropbear, and cut of my installation shell, so i can't see anymore what it's doing.
[15:02] <nbd> dothebart: i mean reflashing with a newer snapshot
[15:02] <dothebart> ah. ok.
[15:04] <quax> Hi, I've a problem with my wrt (wrt54GS 1.1): from the client side (windows) the connection seems to be ok, but I can't ping the wrt, and from the wrt I can't ping the windows client.
[15:04] <dothebart> so doing cvs update on the host system and rebuilding is what i want to do?
[15:04] <quax> arp requests from the wrt receive noresponse..
[15:04] <quax> that all using openwrt..
[15:05] <quax> what can I look for in my configuration?
[15:07] <dothebart> is the nic staticaly linked to the kernel?
[15:07] <quax> wifi_proto=static ?
[15:07] <quax> or what?
[15:08] <quax> I've the standard kernel from whiterussian
[15:13] <quax> no hint ? :)
[15:17] <dothebart> uh. make: *** uclibc++: No such file or directory. Stop.
[15:20] <quax> these is what I changed from the default
[15:20] <quax> http://rafb.net/paste/results/kVn0pl20.html
[15:20] <quax> and I deleted the firewall script
[15:20] <dothebart> arg. cvs update -d ;)
[15:53] <quax> don't think this is normal..
[15:53] <quax> root@OpenWrt:~# iwlist eth1 bitrate
[15:53] <quax> eth1 unknown bit-rate information.
[15:53] <quax> or is it?
[16:55] <tmbinc> is the WGT634U the only one with USB2.0?
[16:57] <tmbinc> i have some trouble on WGT634U with usb-storage, but as it's all experimental i'm not sure where the problem lies
[17:02] <BULLE> tmbinc: silly question, with an WGT634U how do you flash openwrt to it ?
[17:03] <BULLE> tmbinc: do you need to open the thing, and use a serial or jtag interface, or is there some simiple way of loading the firmware ?
[17:05] <tmbinc> BULLE: i opened it, and attached a serial port
[17:05] <BULLE> i see
[17:05] <tmbinc> BULLE: i'm currently using nfs'd debian until at least the kernel works ok
[17:06] <tmbinc> though if you're brave, you would be able to hack into the stock firmware and replace the kernel in flash
[17:06] <tmbinc> if this fails, you need serial ;)
[17:07] <tmbinc> i hacked an old, cheap cellphone "usb" datacable, which had a PL2303 with TTL (or even 3.3V) levels, so that wasn't really a problem
[17:31] <hedpe> is a USB port possible on the wrt54g?
[17:31] <olli_04> hedpe: no, you need a asus wl-500g deluxe it has two usb 2.0 ports
[17:32] <hedpe> olli: how do you look for these kinds of things on the board? like what gave away the serial port on the board for example? are they labeled?
[17:34] <BULLE> tmbinc: well, i have 0 hardware experience realy, so i try to avoid mucking around with the internals of my hardware
[17:34] <BULLE> tmbinc: mind, it all seems very intresting thoug, to much around with the internals of ones hardware
[17:35] <tmbinc> olli_04: do they usually work stable on 2.6.12?
[17:36] <olli_04> hedpe: do you mean something like this: http://wiki.openwrt.org/TableOfHardware
[17:37] <olli_04> tmbinc: no, because the propritary wireless broadcom driver doesn't work with kernel 2.6 (the wireless driver is aviable in binary only from broadcom)
[17:37] <tmbinc> ah ok, so it's not a NEC ehci?
[17:37] <tmbinc> (like on my WGT634U)
[17:38] <olli_04> tmbinc: i don't know, i've never seen openwrt running on a wgt634u
[17:38] <hedpe> thanks olli
[17:38] <tmbinc> well if it would be EHCI, you wouldn't need any special driver. :)
[17:40] <olli_04> tmbinc: as i said, i don't know if openwrt is running on the wgt634u, so i could not help you out on this
[18:15] <matled> you've got speakers at you wrt?
[18:15] <PolarWolf> That's pretty cool. But only one question bugs me..."why?"
[18:15] <robr> hmm.. usb headset
[18:15] <robr> why -> mp3 player on places w/o pc
[18:15] <robr> wireless music
[18:16] <robr> btw its a wl500g, but wrt should work as well
[18:16] <robr> why -> 'because it's possible' ;-)
[18:17] <robr> could i put the binaries / sources somewhere to let other users use them?
[19:13] <ob1kenewb> I don't find the wlconf prog after having flashing my box any hints ?
[19:13] <ob1kenewb> and the wl program neither
[19:16] <Dabian> nbd: I think its impossible for me to get in failsafe, if the air-led is supposed to stay off.
[19:24] <Dabian> Has nbd left?
[19:24] <Dabian> Thats terrible.
[19:34] <ob1kenewb> Error for wireless request "Set Encode" (8B2A) :
[19:34] <ob1kenewb> SET failed on device eth1 ; Invalid argument.
[19:35] <ob1kenewb> I got this with iwconfig
[19:35] <erik_--> Dabian have you brick a wrt54g ?
[20:46] <pp_> u-hum
[20:47] <pp_> err
[21:39] <ob1kenewb> hi, it's impossible to disable WEP on my wrt
[21:43] <stonezone> anyone run fakeap on their wrt?
[22:12] <stonezone> http://www.steelcitysfinest.com/HondaAccordAd.htm
[22:13] <FireEgl> I just received a WRT54GS v2.1 ..Has anybody else tried openwrt on that version?
[22:13] <Vince||> stonezone: it is a perl script and there is no perl for openwrt, it is too big
[22:14] <stonezone> that makes complete sense
[22:14] <Vince||> stonezone: it wouldn't be to difficult to implement the same thing in C or in shell
[22:15] <Vince||> you just need to generate random names and to change the ssid
[22:15] <Vince||> I suppose wificonf will do the trick to change the ssid
[22:15] <Vince||> and md5sum will generate random names
[22:25] <robr> does the openwrt emergency mode (or what is it called) work on an asus wl500-g as well?
[22:26] <robr> i messes
[22:26] <robr> :S
[22:26] <robr> i messed up the nvram network settings
[22:26] <robr> i can reflash using boot_wait, but i would like to keep my jffs. is this possible?
[22:49] <ab0oo> nbd: ping.
[22:50] <port7> why is ipkg adding 'Packages' to the end of the package repositry url?
[22:58] <stonezone> damn, that sucked, road runner down for almost an hour
[23:01] <Semhirage> ouch
[23:01] <Semhirage> i'd call and demand a credit
[23:02] <stonezone> they would laugh
[23:02] <stonezone> bastaads
[23:02] <Semhirage> =/
[23:03] <Semhirage> i get mad credits from isp if it goes down for more than 5 minutes and i don't have 24 hour warning
[23:03] <stonezone> you must not live in hawaii
[23:03] <stonezone> shitty service here
[23:03] <Semhirage> newp
[23:03] <Semhirage> Wisconsin here
[23:03] <Semhirage> speakeasy onelink for isp
[23:03] <stonezone> ah, a real state
[23:04] <stonezone> http://bsdvault.net/bsdfap.txt
[23:04] <stonezone> wrong window
[23:04] <Semhirage> normally i would rag about what a pos this state is, but after today and the courts decided in my favor and im not going to jail and i get to keep my son, yea WI ain't half bad
[23:05] <stonezone> lol, i guess congrats are in order
[23:05] Action: stonezone pats Semhirage on the back, nice job.
[23:05] <ab0oo> The wisconsin child support courts can KMA.
[23:05] <stonezone> seems like most states are that way
[23:05] <Semhirage> small ones, the major congrats will come 9 MO down the road when his mother has no rights and never gets to see him again
[23:06] <stonezone> was just talking to my dad about that, he got a 20+ grand bill back in the day saying he was seriously delinquent
[23:06] <stonezone> even though he had custody
[23:06] <ab0oo> My wife's ex-husband has custody 6 weeks per year, and pays less than$300/month in child support, and has for only 5 of the 12 years my daughter (step, but she's been mine for 9 years) has been alive.
[23:07] Action: stonezone remembers to never ever have kids
[23:07] <ab0oo> Has anyone compiled the ISC DHCP server for openWrt? It won't compile in buildroot.
[23:07] <Semhirage> i had no problem paying my CS when it was taking care of my son, i had a big problem when she was buying oz's and dimebags with it
[23:08] <[mbm]> ab0oo: it won't run on openwrt either
[23:08] <ab0oo> [mbm]: why not? I'm kinda desperate for it.
[23:08] <[mbm]> ab0oo: kernel configs; it was mentioned in the forum a few times
[23:09] <ab0oo> didn't search there. has anyone ever used (or understood) dhcp-relay and dhcp-forward?
[23:10] Action: [mbm] doesn't have a network large enough to need a forward/relay
[23:10] <PolarWolf> 's what you need to get DHCP requests to the other end of routers
[23:10] <ab0oo> I'm a little confused on the difference between forward and relay.
[23:10] <ab0oo> I have a DHCP server at my CO-LO server (10 hops away from my router) that I want to serve DHCP from.
[23:10] <ab0oo> is that a "relay" or an "agent" job?
[23:11] <PolarWolf> I bet agent, I'm not entirely sure though
[23:12] <PolarWolf> google should know
[23:13] <ab0oo> I really couldn't find a difinitive "this is the difference" doc.
[23:20] <fusQuanto> is the wrt54g capable of being used to sniff AIM conversatinos of employees on my network?
[23:21] <[mbm]> privacy?
[23:21] <stonezone> dsniff
[23:21] <fusQuanto> hardware wise i mean, no limitations?
[23:22] <pyromaniac> fusQuanto, it's illegal in most countries :-)
[23:22] <pyromaniac> fusQuanto, isn't AIM encrypted? (i realy dunno) msn is.
[23:22] <[mbm]> can be
[23:23] <zinx> i doubt either are encrypted to any significant degree
[23:23] <fusQuanto> aim isnt
[23:23] <port7> anyone know about problems with ipkg update
[23:24] <port7> its adding the string 'Packages' to the end of the repositry url
[23:24] <[mbm]> port7: that's not a bug, the list of available packages is called "Packages"
[23:24] <port7> hmm
[23:25] <port7> ok
[23:25] <port7> maybe its a diff error then
[23:26] <pyromaniac> who knows? it might be all in your imagination?
[23:26] <port7> ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-ryoIJq http://downloads.openwrt.org/whiterussian/packages/Packages'
[23:26] <port7> aye
[23:26] <[mbm]> port7: look above for a dns or routing error
[23:27] <port7> will do
[23:27] <port7> tho i can resolve names ok
[23:27] <port7> and ping the outside world
[23:27] <[mbm]> from the router or from your computer?
[23:27] <pyromaniac> well i can asure you that the file exists
[23:28] <port7> from the router
[23:28] <port7> tho i can't ping downloads.openwrt.org
[23:28] <pyromaniac> i can
[23:29] <port7> wonder if my isp is having probs
[23:29] <port7> can ping some places but not others
[23:29] <port7> e.g.
[23:29] <port7> can ping www.linux.org
[23:30] <port7> but not downloads.openwrt.org
[23:30] <port7> ok maybe i will try tomorrow
[23:30] <pyromaniac> change dns :)
[23:30] <port7> ok it worked now
[23:30] <pyromaniac> k?
[23:30] <port7> thats weird
[23:30] <pyromaniac> soloution?
[23:31] <port7> i think venus just passed overhead
[23:31] <port7> that must have fixed it
[23:33] <port7> thanks for the input people :-)
[23:34] <fusQuanto> does the 54g have a port monitoring or SPAN function?
[23:35] <[mbm]> not really
[23:36] <fusQuanto> how do i aim sniff :(
[23:36] <pp_> you can bridge two ports and tcpdump the bridge
[23:36] <pp_> it'll kill your perf tho
[23:37] <fusQuanto> hmm
[23:37] <port7> ntop would be a cool package to have
[23:38] <[mbm]> fusQuanto: a script from el33ts5riptk1ddies.com might help :P
[00:00] --- Sat Jul 16 2005
[00:45] <Sapote> :)
[00:45] <[mbm]> nbd: sounds like an idea
[00:45] <Sapote> wlc eth1 channel 14
[00:47] Last message repeated 1 time(s).
[00:47] <Sapote> eth1: Invalid argument
[00:47] <Sapote> wlconf eth1 down
[00:48] <Sapote> wlconf eth1 up
[00:48] <Sapote> wlc eth1 channel 14
[00:48] <Sapote> wlc eth1 channel
[00:48] <[mbm]> Sapote: this is an irc channel, not a terminal :)
[00:48] <Zer0her0> what's w/ sapote?
[00:48] <Sapote> 14
[00:48] <Sapote> lol
[00:48] <Sapote> iptraf
[00:48] <Zer0her0> he msged me useless crap
[00:49] <Sapote> iptraf compiled for wrt
[00:49] <frop> what should return "iwlist eth1 bitrate"?
[00:49] <Sapote> iptraf_2.7.0_mipsel.ipk ncurses_5.2_mipsel.ipk
[00:49] <frop> is this normal?
[00:49] <frop> eth1 3 available bit-rates :
[00:49] <frop> -737870 kb/s
[00:49] <frop> -603652 kb/s
[00:49] <frop> 4.2445 Mb/s
[00:51] <[mbm]> frop: normal or not it's wrong ...
[00:52] <dgsgeo> sorry fot the dumb question ... been looking for an hour ....
[00:52] <frop> [mbm]: why??
[00:52] <frop> :P
[00:52] <dgsgeo> how do I tell which version WRT54G hardware I have?
[00:57] <[mbm]> or you just look at what's printed on the bottom :P
[00:58] <Wowzers> the version is like 2 inches from the SN on the bootom of the wrt
[00:59] <Wowzers> i just moved over to the Whiterussian release, is there a 'wl' utility for the WhiteRussian
[01:02] <[mbm]> Wowzers: it's part of the 'non-free' set
[01:04] <pyromaniac> Wowzers, just download the package
[01:04] <pyromaniac> ipkg install URL
[01:04] <pyromaniac> for instance
[01:04] <pyromaniac> find the wl packagfe
[01:04] <pyromaniac> *package
[01:04] <nbd> /wi2
[01:04] <pyromaniac> on tracker.openwrt.org
[01:04] <nbd> oops
[01:05] <pyromaniac> :D
[01:05] <[mbm]> it's in the whiterussian/packages/non-free dir
[01:15] <Wowzers> i work at a college in So Cali and my boss was wanting to hire a full -time wireless guy
[01:15] <Wowzers> we got 3 campuses with like 130 Cisco 1200 AP's
[01:16] <[mbm]> spiffy; does that come with benefits?
[01:17] <Wowzers> ya, i work part-time there, and the full timers say the benefits are good because its in the education sector
[01:25] <Wowzers> how come its called non-free
[01:25] <[mbm]> binary only, no license
[01:25] <Wowzers> oic
[02:22] <MrLebowski> openslug
[02:23] <MrLebowski> doh
[02:24] <truth> [mbm] you were right it wasnt the clk setting , setting it to 216 seemed to wipe out some nvram settings including ip addresses.... thx again for the help
[02:25] <[mbm]> truth: hmm haven't seen that happen before
[02:27] <truth> got to re-image this machine...
[03:05] <fishhead> http://www.groklaw.net/article.php?story=20050714144923365 <--- is it just me or is SCO *CANUCKED*??
[03:34] <knoppix> need help
[03:35] <trench> knoppix: topic?
[03:35] <knoppix> openwrt seems to have lost the ability to give me a ip
[03:35] <trench> read the docs
[03:35] <knoppix> 5 days uptime and it just died
[03:35] <knoppix> i have already reinstalled
[03:37] <[mbm]> the dhcp server for the lan or getting an ip off the wan?
[03:37] <knoppix> lan ip
[03:37] <knoppix> first my static ips died anf then i couldnt get an ip at all
[03:37] <knoppix> im in fail safe now
[03:39] <[mbm]> dnsmasq running?
[03:39] <knoppix> yes
[03:39] <[mbm]> and you're using the whiterussian release?
[03:40] <knoppix> yes
[03:40] <knoppix> and i have cleared my nvram
[03:41] <knoppix> im using squash
[03:41] <[mbm]> in whiterussian it looks for an existing dhcp server before enabling dnsmasq's dhcp server
[03:41] <knoppix> no
[03:41] <knoppix> wrt is the only one
[03:41] <[mbm]> check ps and see if it passed arguments to dnsmasq
[03:44] <knoppix> -l /tmp/dhcp.leases -K -F 192.168.1.100,192.168.1.250,255.255.255.(edge of window)
[03:44] <[mbm]> yeah, dhcp server is running ..
[03:44] <knoppix> since this is failsafe i cant be sure its running in normal
[03:45] <[mbm]> you can't get in normally?
[03:45] <knoppix> even setting my ip to 192.168.1.2 i cant ping it
[03:45] <[mbm]> you might want to run "firstboot" while you're in failsafe
[03:45] <[mbm]> that'll reinitialize the jffs2 partition used for normal boots
[03:46] <knoppix> running
[03:47] <knoppix> if the jffs2 is corrupted that would explin it but why would it die for no reason?
[03:47] <[mbm]> oh, this isn't a result of messing with a config or reflashing?
[03:50] <stonezone> anyone have experience on how many tunnels openwrt/openvpn can handle?
[03:52] <knoppix> no [mbm] like i said 5 days uptime then my port fwd didnt work and i saw my lan ip changed and then i lost connectivity
[03:52] <[mbm]> knoppix: hmm did you check nvram while in failsafe?
[03:54] <knoppix> i erased it
[03:54] <knoppix> ok firstboot done
[03:54] <knoppix> brb
[03:54] <[mbm]> no need to reboot
[03:55] <[mbm]> if you want to restart the interfaces under the normal ip: unset FAILSAFE; /etc/init.d/S40networking
[04:02] <chandi> hey guys, where is the doc about creating a new package with the files I need on my wrt ?
[04:02] <[mbm]> did you read the docs in the openwrt source?
[04:05] <chandi> mbm by source you mean the cvs to compile a firmware ?
[04:07] <[mbm]> chandi: that's one of many ways to obtain the source
[04:07] <chandi> mbm okkk:)
[04:10] <Ephraim> I just upgraded to white russian and now my wrt won't associate :-(
[04:11] <Ephraim> I've checked wl0_crypto and it isn't set on either wrt
[04:11] <Ephraim> any ideas to check? I cant' find anything in the forums that seems to be related.
[04:14] <Ephraim> [mbm] - congratulation on graduating
[04:17] <fishhead> MUST BITE CANUCKS
[04:18] Action: fishhead SINKS HIS TEETH INTO WEEDY'S LEG
[04:18] <Weedy> ..
[04:18] <fishhead> :p
[04:18] Action: Weedy kills fishhead with fyre
[04:20] <Weedy> crap
[04:20] <Weedy> my ip changed
[04:34] <Paler2489> Someone chats with me. I feel a pain very much
[04:34] <[mbm]> no
[04:35] <Weedy> my god
[04:35] <Weedy> http://www.artlebedev.com/portfolio/optimus/
[04:35] <Weedy> it is a thing of beaty
[04:35] <[mbm]> it's also a photoshop fake
[04:36] <Weedy> really?
[04:36] <[mbm]> yep
[04:36] <Weedy> awww
[04:36] <Weedy> i was hoping i could buy one
[04:37] <[mbm]> I imagine a mini display on each key would be very expensive
[04:37] <Weedy> no
[04:37] <Paler2489> my god
[04:37] <Weedy> OLEDS are supposed to be quite cheap
[04:37] <stonezone> if they its fake on /. it must be true
[04:38] <stonezone> http://slashdot.org/comments.pl?sid=155812&cid=13065107
[04:39] <fishhead> yeah they are
[04:39] <fishhead> the only bad thing about oleds is lifespan
[04:39] <fishhead> HOLY MOTHER OF CANUCK
[04:39] <stonezone> http://www.artlebedev.com/portfolio/mus/
[04:39] <fishhead> IS THAT COOL
[04:40] <fishhead> wow
[04:40] <stonezone> thats funny
[04:40] <fishhead> I wonder what happens if you punch it
[04:40] <fishhead> "FUCK YOU ASSHOLE!"
[04:41] <philv> So much racism in here ;_;
[04:42] <Ephraim> hmm - "wifi" on the client wrt gives the usual error, but seems to do what it supposed to do, but "wifi" on the AP gives a new error
[04:42] <Ephraim> Error for wireless request "Set Tx Power" (8B26) :
[04:44] <Weedy> [22:20] <Weedy> which ip is cooler
[04:44] <Weedy> [22:20] <Weedy> 69.197.36.142 or 69.198.126.61
[04:44] <philv> Weedy: I definitely say 134.117.69.21
[04:44] <philv> the .69 class C is just way too cool
[04:45] <matled> 222.173.190.239!
[04:53] <[BeaR]> heya all
[04:53] <[BeaR]> i've just installed whiterussian
[04:53] <[BeaR]> but... netstumbler says that WEP is enabled
[04:54] <[BeaR]> i havent set up wep
[04:54] <[BeaR]> wl0_wep=disabled
[04:54] <[BeaR]> anyone seen this before
[04:54] <[BeaR]> ?
[04:59] <Weedy> is ther light on?
[04:59] <[BeaR]> yeah
[04:59] <[BeaR]> ican see the SSID
[04:59] <[BeaR]> but it wants a wep key
[05:01] <[mbm]> nvram unset wl0_crypto; nvram commit; wifi up
[05:02] <Ephraim> [mbm] - any idea n what the error message is telling me "Error for wireless request "Set Tx Power" (8B26) :"
[05:03] Action: [mbm] mumbles something about the wifi config being horribly screwed up in rc1
[05:04] <Ephraim> hmmm - good thing it's rc1 :-)
[05:05] <[mbm]> all of that stuff's been fixed already; just making sure *everything* works before we do an rc2
[05:05] <Ephraim> ahh, can I get the "fixed" stuff in cvs?
[05:05] <[mbm]> yep
[05:06] <Ephraim> I thought I was going crazy there for a while... I think you've restored my sanity :-)
[05:09] <Ephraim> [mbm] - if I've downloaded whiterussion by CVS, do I need to remove the directory and start again or can I just download the latests CVS over top of it?
[05:10] <[mbm]> did you check it out from cvs before?
[05:10] <Ephraim> yeah - per the instructions on the documentation
[05:11] <[mbm]> Ephraim: then you can just do an update: cvs -z3 -q up -Pd -r whiterussian
[05:12] <Ephraim> while I'm in the openwrt directory?
[05:13] <Ephraim> "cvs -d:pserver:anonymous@openwrt.org:/openwrt co -rwhiterussian openwrt" is what I used before
[05:17] <Ephraim> [mbm] - uh ok, I think I got it. I assume the relevant changesa re in the wlcompat package?
[05:20] <[mbm]> Ephraim: did you look at the number of files that were updated by that command?
[05:22] <Ephraim> [mbm] - yeah, not too many and the only one that seems really relavant is the wlcompat. losts of updates to the scripts in the target directory and some ppp stuff.
[05:28] <gravix> possibly stupid question: which firmware will allow client mode on a WPA2 network? I've been trying DD-WRT, but no dice...
[05:28] <[mbm]> any of them will with the rigth setup
[05:29] <gravix> okay, i'll keep dicking around with DD-WRT... thanks much
[05:33] <Ephraim> I have to admit - mucking around with openwrt brings back fond memories of trying to get linux to work way back in the early days :-)
[05:34] <Ephraim> ls
[05:34] <Ephraim> oops
[05:34] <Ephraim> wrong window :-)
[05:34] Action: gravix is so far at the end of his rope he just might try openwrt
[05:37] <score> hrm, any solutions for wrt54g that lock up because of bittorrent?
[05:39] <gravix> hm "lock up"?
[05:40] <dtm> Ephraim: heheheh yeah but wrt54g is more powerful than my first linux host ;)
[05:40] Action: splinterfl started Redhat linux on a AST 25mhz
[05:40] <dtm> 20 MHz 386sx with 5MB RAM, 100MB hd
[05:41] <dtm> 5 hrs 40 mins to compile linux 1.2.13
[05:41] <Ephraim> :-)
[05:41] <dtm> bewm
[05:41] <splinterfl> still in use?
[05:42] <splinterfl> heard of a few 386 files servers still hanging around... overload by it depts
[05:42] <splinterfl> overlooked
[05:42] <Ephraim> My 33mHz 486 is still in use, but it an unglorious doorstop
[05:42] Action: splinterfl has 9 75mhz P1's still in use as DNS servers
[05:42] <Ephraim> It weighs almost as much as the door it holds open :-)
[05:45] <splinterfl> wonders what could 20 barely used WRTs on a LAN do...
[05:46] Action: splinterfl thinks of all these wasted CPU cycles
[05:46] <Ephraim> a seti client?
[05:46] <splinterfl> hum...
[05:46] <gravix> it looks to me like the linksys beta firmware is the only thing that works with wpa2
[05:47] <Ephraim> gravix - openwrt does
[05:47] <Ephraim> you just have to configure it
[05:47] <Ephraim> gotta go - soo you folks later
[05:47] <Ephraim> s/soo/see/
[05:47] <gravix> thank you ephraim, goodbyeeeee!
[05:57] <score> well, lock up meaning that all connections seem to get dropped
[06:10] <[mbm]> http://www.ebaumsworld.com/interactivebuddy.html .. amusing waste of time
[06:10] <AgentHH> Hay nbd
[06:12] <matled> [mbm]: is this only 6 balloons sticked together or is something wrong with my flash player?
[06:12] <[mbm]> matled: it's a cheap stick figure that you can abuse
[06:13] <matled> mhk, really waste of time :)
[06:13] <matled> especially cpu time
[06:14] <matled> 99% cpu usage and loadavg 1.74, flash doesn't seem to be that good on linux
[07:36] <gravix> sigh... so frustrating trying to get this router to work
[07:36] <gravix> i've been loading and unloading for hours and hours
[07:37] <sbingner> [mbm]: you around? heh
[07:50] <JonasNZ> hey, any1 here own a dlink dsl-500
[09:01] <CanDoo> is there any wrt formware that support repeater mode?
[09:02] <JonasNZ> any1 here own a DLINK DSL-500
[09:03] <[mbm]> CanDoo: let's see .. they all use the same wireless driver which does wds mode .. just need to configure it (which might not be possible in some firmwares)
[09:07] <CanDoo> well wds is all well and good
[09:07] <CanDoo> i'v been playing with WDS
[09:08] <CanDoo> but wDS doens't allow the use of the AP as for cleints and point to point connections
[09:08] <CanDoo> atleast not that i'v seen
[09:09] <[mbm]> CanDoo: um, yes it does ...
[09:19] <Kaloz> .
[09:20] Action: [mbm] wonders how many other firmwares send people to us .. "you bricked your router? go tell the openwrt guys that openwrt broke it .."
[09:21] <coder> if the 'author' of 'another' firmware says that, he is a wanker
[10:13] <Weedy> just wondering how much of a beating can openWRT take?
[10:14] <[mbm]> go see; report your results
[10:17] <CanDoo> bah
[10:17] <CanDoo> this pisses me off
[10:17] <CanDoo> where can i find the source for linksys-tftp cleint
[10:18] <CanDoo> so i am able too set a password for this firmware
[10:18] <CanDoo> POS
[10:19] <[mbm]> linksys tftp client is crap; don't use it
[10:20] <olli_04> CanDoo: on win use tftpd32.exe on *nix use tftp or atftp
[10:20] <CanDoo> well the standard generic tftp cleint doens't work under debian
[10:20] <CanDoo> is kinda the catch
[10:20] <CanDoo> bitching aobut passwords and such
[10:20] <CanDoo> that the tftp client knows nothing about
[10:21] <olli_04> CanDoo: have you tried atftp ?
[10:21] Action: [mbm] points to the spiffy install guide, recently updated
[10:21] <CanDoo> the tftp password the firmware uses should be the same as the admin password
[10:21] <CanDoo> and preceed the linename to be uploaded correct?
[10:21] <CanDoo> er filename
[10:24] <olli_04> CanDoo: if you upload a image to your router and it aks for a password, please read: http://wiki.openwrt.org/OpenWrtDocs/Installing#head-344b77cce4d63bd941eb782ea25d37f9e8fd9d19
[10:25] <CanDoo> hhe
[10:25] <CanDoo> one step ahead of you on that one
[10:26] <CanDoo> problem solved
[10:26] <CanDoo> that is kinda strange
[10:26] <CanDoo> i don't understnd why have a tftp cleint ontop of the bootloaders tftpd
[10:26] <CanDoo> although form a secruity stnadpoint i do understand
[10:29] <[mbm]> you don't understand why a tftp server requires a tftp client?
[10:29] <olli_04> ooh
[10:30] <pp_> mbm: probably means the linksys tftpd with password hack
[10:43] Action: Weedy wonders if openwrt can take 12k bt peers
[10:50] <Kaloz> openwrt can, just the hardware can't
[10:50] <Kaloz> you don't have enough memory for that imho
[10:51] <[mbm]> even on the gs you only get 32M
[11:11] <CanDoo> well finaly
[11:13] <CanDoo> whoohooo i did it
[11:13] <CanDoo> yeah!
[11:13] <thefRont> openwrt running?
[11:15] <CanDoo> yes
[11:15] <CanDoo> it's WDS time
[11:15] <CanDoo> gettign the tftp workign right is a little tricky
[11:15] <CanDoo> i had did it a few years ago
[11:15] <CanDoo> when i first got the wrt
[11:15] <CanDoo> but had forgotten what i had done too redo it
[11:20] <Weedy> shit
[11:20] <Weedy> why did i leave scsi in the kernel
[11:20] <CanDoo> 000F66A9BB54
[11:39] <olli_04> pau: is your wds still working fine?
[11:39] <pau> olli_04 no man
[11:39] <pau> like
[11:40] <nitram> mhm... i am using pppoecd on an old openwrt box. on boot the ppp0 device is not up yet, it needs a while to come up. in the meantime machines in the lan try to connect to $WORLD. this leads to conntrack beeing used. once the ppp0 device is up, these previous unsuccessful "connections" remain in conntrack and lead to successive pakets not being masqueraded anymore. ip_dynaddr does not help in this case. will setting up a dummy ppp0 until ppp0 is really up maybe
[11:40] <nitram> help?
[11:40] <pau> client wifi ping AP1 but can't ping AP2, but, client by cable ping AP1 and can ping AP2
[11:40] <CanDoo> hmm
[11:41] <CanDoo> i'v set my linksys v2.2 and v2.6 to p2p reter mode. and WDS is activated on my wrt
[11:41] <CanDoo> but traffic doen'st seem to pass
[11:41] <nbd> nitram: you could try to upgrade to latest whiterussian rc
[11:42] <nitram> nbd: i want to really solve this problem and avoid any unneccessary upgrading just on a hunch that it might work
[11:42] <nbd> nitram: it could be a bug in the old netfilter stuff - if it is, there's no other way to fix it other than upgrading
[11:43] <nitram> this problem is reproducible and i heard of a couple of people who have this problem
[11:43] <CanDoo> how does adHOC differ from AP mode?
[11:43] <nitram> nbd: it is mostly a udp problem
[11:44] <nitram> nbd: do you have any idea how the ip_dynaddr stuff works?
[11:44] <nbd> nitram: no
[11:44] <nitram> damn
[11:44] <nitram> i'd like to know how the ip-change is recognized
[11:45] <nitram> that's why i would like to have a ppp0 dummy and then replace the dummy-ip with the real ip
[11:45] <nitram> and already have a default route on that
[11:45] <nbd> nitram: pppd does that when on-demand dialling is enabled
[11:46] <nitram> mhm
[11:46] <nitram> still using the pppoecd
[11:46] <nbd> new openwrt versions use pppd
[11:47] <nitram> as i said this is a highly customized openwrt
[11:47] <nbd> what did you customize?
[11:47] <nitram> so i am not really in the mood to redo everything just yet ;)
[11:47] <nbd> i can understand that
[11:47] <nitram> routing after conntrack, olympic diffserv etc
[11:48] <nbd> ah, ok
[11:48] <nitram> everything works, just these pita udp packets
[11:49] <nitram> every once in a while after the reboot when a udp packet arrives while the ppp0 dev is still not up
[11:49] <nbd> do you reboot your device that often?
[11:49] <nitram> every night, because ip changes are not detected properly
[11:49] <nitram> maybe i should try pppd
[11:50] <nitram> after reconnect the same problem
[11:50] <nitram> the old ip is still used for masquerading
[11:52] <Dabian> OK .. I think I managed to lock myself completely out from my wl-500gd. I set up a bridge on vlan0 that included vlan1 .. and both telnet and ssh is refused on both interfaces, and it doesn't seem to help to enter failsafe. Is there a way to reset the nvram, or should I keep trying boot failsafe?
[11:53] <nbd> Dabian: how do you try to boot failsafe?
[12:00] <CanDoo> 000C41188A6A
[12:02] <Dabian> nbd: I turn it on, then I wait till all the lamps are not on .. then I press and hold reset.
[12:02] <Dabian> nbd: COunt to seven, and release the button.
[12:02] <Dabian> nbd: I guess it should work?
[12:06] <Weedy> is this correct? because it does not seem to be working. iptables -t nat -A postrouting_rule -o $LAN -p tcp -s 192.168.1.0/24 -d 192.168.1.100 -m multiport --dports 59,6967,6968,8394 -j SNAT --to-source 192.168.1.1
[12:10] <nbd> Dabian: try waiting a bit longer (about 3 seconds)
[12:13] <CanDoo> 000c41188a6a
[12:14] <Kaloz> CanDoo: learn using your mouse :p
[12:14] <CanDoo> hehe
[12:14] <CanDoo> my apologies for any disturbance
[12:14] <CanDoo> i was usieng xchat as a scratch pad
[12:21] <Dabian> nbd: OK :-)
[12:26] <CanDoo> do any of you own a wap11 2.6 or 2.2 device?
[12:26] <Dabian> nbd: If I succeed, it will ignore all nvram settings and I should be able to ssh or telnet, right?
[12:26] <nbd> Dabian: telnet, yes
[12:27] <Dabian> Hmm .. I can ping 192.168.1.1 but not telnet or ssh .. connection refused.
[12:28] <Dabian> Somehow I have the feeling I'm failing to enter failsafe :/
[12:29] <Dabian> Though .. the air-led is lit up!
[12:30] <nbd> Dabian: then it's probably not failsafe
[12:30] <Dabian> No air in failsafe?
[12:31] <nbd> normally it should just do ifup lan and run the telnet server
[12:31] <Dabian> Ignoring the nvram, right?
[12:31] <nbd> normally, yes
[12:31] <Dabian> I turned off the lan in the nvram though.
[12:31] <nbd> well... not completely
[12:31] <nbd> just overriding it
[12:31] <nbd> how did you turn it off?
[12:31] <Dabian> proto=none
[12:32] <Dabian> lan_proto=none
[12:32] <Dabian> bridging it with wan.
[12:32] <Dabian> bridgeing
[12:32] <nbd> ah, that explains
[12:32] <nbd> seems like failsafe doesn't handle that correctly
[12:32] <Dabian> So, now the thing is broken?
[12:33] <Dabian> I need to make a custom image to flash on?
[12:33] <nbd> did you use squashfs or jffs2?
[12:33] <Dabian> yes
[12:33] <Dabian> I used squashfs.
[12:33] <nbd> which one?
[12:33] <nbd> ah
[12:33] <nbd> ok
[12:33] <nbd> then i'll give you a new image that should boot in failsafe correctly
[12:33] <Dabian> OK .. cool
[12:34] <Dabian> Did I discover a bug?
[12:34] <nbd> Dabian: yeah
[12:34] <Dabian> Cool :)
[12:34] <nbd> Dabian: i'll tell you when the build is ready
[12:34] <Dabian> Thanks!
[12:34] <nbd> Dabian: all your settings should remain intact after reflashing
[12:35] <Dabian> Even the j2ffs stuff?
[12:35] <nbd> yeah
[12:35] <Dabian> wow
[12:35] <nbd> you're only overwriting the readonly part of it
[12:35] <Dabian> Thats nice about squashfs :)
[12:36] <Dabian> I am puzzled that I can ping the device ... but I guess thats part of the bug.
[12:37] <nbd> i have no explanation for this
[12:39] <CanDoo> this stinks
[12:41] <nbd> what stinks?
[12:41] <CanDoo> well
[12:41] <CanDoo> i'm trying to get my wap11 v2.2 and v2.6 to talk to my wrt54G
[12:42] <CanDoo> WDS doen'st seem to work
[12:42] <CanDoo> the wap11's have no WDS settings
[12:42] <CanDoo> they have reapter and point to point settings
[12:42] <CanDoo> but dont' seem to talk wot the WDS on the wrt
[12:42] <nbd> then maybe they're not able to do wds
[12:42] <CanDoo> they wont' do client mode either
[12:43] <nbd> Dabian: http://openwrt.inf.fh-brs.de/~nbd/test/
[12:44] <Dabian> nbd: : Thanks!
[12:44] <nbd> let's see if this works
[12:44] <Dabian> Yeah :)
[12:45] <Dabian> nbd: Which image do I want?
[12:45] <Dabian> http://openwrt.inf.fh-brs.de/~nbd/test/openwrt-brcm-2.4-squashfs.trx ?
[12:46] <nbd> Dabian: yeah
[12:46] <wickus> nbd: hi
[12:46] <nbd> wickus: hi
[12:47] <wickus> nbd: i checked again the vlynq stuff and acx111
[12:47] <wickus> no support for vlynq in the acx sources
[12:47] <nbd> of course not
[12:47] <nbd> maybe we'll have to add that
[12:48] <wickus> ok
[12:54] <Weedy> you know what i just thought of
[12:54] <Weedy> with the SD card mod
[12:55] <Weedy> can you run 2 SD cards?
[12:57] <frop> i'd like to run at least one
[12:57] <frop> :)
[12:58] <Weedy> cause i was like
[12:59] <Weedy> if you could have 2
[12:59] <nbd> Dabian: works?
[12:59] <Weedy> raid them
[12:59] <frop> eheh
[13:00] <Dabian> nbd: Had a little trouble uploading .. but if I started up with reset depressed, it ate the image :)
[13:00] <Dabian> nbd: : How long do I wait before I powercycle?
[13:00] <nbd> Dabian: no idea. 2 minutes should be fine
[13:00] <nbd> Dabian: it will not reboot automatically
[13:00] <nbd> Dabian: you'll have to pull the plug
[13:01] <Dabian> Nope .. thats special for wl-500gd, I guess :)
[13:01] <nbd> yeah
[13:01] <frop> but a question...as the deluxe hasn't jtag...how to debrick it?
[13:02] <Dabian> frop: Some routers have screws. The wl-500gd is one of them.
[13:02] <nbd> frop: cfe dead -> not possible, nvram screwed -> pin shorting
[13:02] <Weedy> woah
[13:02] <frop> ohh
[13:02] <Weedy> so dont kill the cfe
[13:03] <Weedy> >.>
[13:03] <frop> isn't so good
[13:03] <frop> :)
[13:03] <frop> i'll be afraid with friend's one
[13:03] <nbd> well.. if you don't mess with cfe, it's no problem
[13:03] <frop> he'll kill me if i briks his one
[13:04] <frop> nbd: never play with mine too...still
[13:04] <frop> btw, Motorola part on Installing web page doesn't fit to me...as i need 4MB generic firmware
[13:05] <nbd> frop: ?
[13:06] <frop> heh on website documentation
[13:06] <nbd> what do you mean?
[13:06] <frop> http://wiki.openwrt.org/test.cgi/OpenWrtDocs/Installing#head-16e8d1f9495b84660425ea230a05e0305b71bdd1
[13:06] <Dabian> Lets go over the procedure to reach fail-safe on the wl500gd again ...
[13:06] <Dabian> 1. Plug in the power.
[13:06] <Dabian> 2. Wait 3 seconds.
[13:06] <Dabian> 3. Push in reset button, and hold it.
[13:06] <Dabian> 4. Wait 7 seconds.
[13:06] <Dabian> 5. Release reset button.
[13:06] <Dabian> 6. Wait about 10 seconds and you should be in fail-safe?
[13:06] <Dabian> s/10/30/
[13:06] <frop> nbd: Download the motorola firmware image (either the squashfs or the jffs2-8mb version) from the website. (Note: The motorola has 4mb flash, but requires the 8mb version. This is an ignominously confusing naming problem that hopefully will be fixed. At the moment the motorola-jffs2-4mb is entirely useless.)
[13:06] <nbd> Dabian: seems right
[13:07] <frop> for me, with my moto, only "generic-4MB" is working
[13:07] <nbd> frop: could you update that web page, please?
[13:07] <Dabian> ok .. I try again.
[13:07] <frop> nbd: ok...i'll add my "feature" at bottom
[13:08] <CanDoo> how does Adhoc differ form AP mode?
[13:08] <frop> ...like: "if this image doesn't work..."
[13:08] <nbd> frop: what version do you have?
[13:09] <frop> v3
[13:09] <nbd> frop: maybe it's version specific
[13:09] <frop> mmh...don't...we'd need feedback
[13:09] <frop> i use always generic 4mb and it always works...so...don't know
[13:10] <frop> where're major differences between "generic" and "motorola" firmware?
[13:10] <Dabian> still no luck
[13:10] <frop> headers only?
[13:11] <frop> Dabian: take reset pressed for more
[13:11] <Dabian> frop: OK, I try again :)
[13:11] <frop> Dabian: like 15/20 secs...
[13:11] <nbd> Dabian: maybe try to start pressing reset one second earlier
[13:11] <Dabian> nbd: OK.
[13:12] <nbd> hmm.. i was wrong
[13:12] <nbd> lan_proto is in the overrides file
[13:12] <nbd> just in a different place
[13:12] <nbd> so no bug there
[13:12] <nbd> has to be something else
[13:13] <Dabian> ok
[13:13] <Dabian> nvram set wan_ifname=br0
[13:13] <Dabian> nvram set wan_ifnames="vlan0 vlan1"
[13:13] <Dabian> nvram set wan_proto=static
[13:13] <Dabian> nvram set wan_ipaddr=192.168.1.1
[13:13] <Dabian> nvram set wan_netmask=255.255.255.0
[13:13] <Dabian> nvram set lan_proto=none
[13:15] <frop> ??
[13:15] <frop> little strange to my eyes
[13:15] <Dabian> My setup is different .. the IP will change, once I got a working config.
[13:16] <frop> so why not use lan_ipaddr too?
[13:16] <frop> and lan_proto static?
[13:16] <Dabian> frop: I am not sure if I can.
[13:16] <Dabian> frop: I would like to though.
[13:16] <frop> why not?
[13:17] <Dabian> You're supposed to set a bridge up like this.
[13:17] <frop> i've no bridge
[13:17] <frop> sepated lan and wlan
[13:18] <Dabian> I basicly took the stuff from the config-documentation, and replaced lan with wan, and wifi with lan.
[13:18] <frop> lan set only an ip addr
[13:18] <frop> but WHY??
[13:18] <frop> maybe i'm only late
[13:18] <Dabian> I have several ip-addresses behind the router, and I don't want them to be nattet.
[13:19] <Dabian> I don't have a router locally, I only have an external gateway.
[13:19] <nbd> you could have just used lan_*
[13:19] <Dabian> nbd: That would have been better, and have achieved the same goal?
[13:20] <nbd> Dabian: you wouldn't need to change all the other stuff
[13:20] <nbd> Dabian: the interfaces function in the same way
[13:20] <frop> well wan and lan, in my thought, are only "alias" to physical router's port
[13:21] <frop> is it wrong?
[13:21] <nbd> right
[13:21] <frop> cause they share the same NIC
[13:40] <minipanda> yeah! finally, i find here!
[13:40] <minipanda> hi, guys, i just buy a wrt54g-cn box today
[13:45] <crashev> minipanda: go and return it while you can!
[13:45] <crashev> ;]
[13:46] <minipanda> crashev: ooops, but why?
[13:46] <chaimj> how do you get tcpdump to read from multiple dump files ?? (tcpdump -r )
[13:46] <crashev> minipanda: just joking...
[13:47] <chaimj> oops, wrong channel
[13:48] <minipanda> crashev: oh, some of my friend told me i should not buy wrt54g but wrt54gs for 8Mb flash
[13:48] <minipanda> crashev: so will asterisk working on wrt54g or wrt54gs very well?
[13:48] <crashev> probably yes, havnt tryed
[13:49] <minipanda> crashev: but why you choose to use wrt54g then?
[13:50] <crashev> because it has opensource firmware, because its made by linksys with is division of cisco, because its not very expensive, because it runs linux, because its very customizable...
[13:51] <minipanda> crashev: AFAIK, dlink and netgear have a lot of AP running linux too
[13:52] <minipanda> which are cheaper than linksys
[13:52] <minipanda> and even Asus device
[13:52] <crashev> havnt heard about them - which dlinks run linux and has opensource firmware?
[13:52] <minipanda> crashev: i choose wrt54g is only because i google out that some geeks already run asterisk on wrt54g
[13:52] <crashev> yes there are packages in whiterussian
[13:52] <minipanda> crashev: dunno status about firmware, but why we take care too much about fireware?
[13:53] <minipanda> crashev: so what's your main function of wrt54g?
[13:53] <minipanda> crashev: i get wrt54g because i want to test my wireless handover patch
[13:54] <crashev> http://pawq.bioinfo.pl/wrt54g/wificonf.c <- wifi with COUNTRY SET so u can use channels > 11...
[13:55] <crashev> minipanda: I also create my own apps for WRT54g, thats why I care about it
[13:55] <d00f> does openwrt use last linksys firmware gpl ? (4.00 or 4.50)
[13:55] <Dabian> nbd: : I will try if I can enter fail safe again.
[13:55] <pp_> d00f: openwrt is already using a much later kernel :)
[13:55] <pp_> 2.4.30-based, not 2.4.20
[14:04] <CanDoo> hehe
[14:04] <CanDoo> stupid bot
[14:13] <fromoze> Hi, I wanted to ask a short question. I was waiting for a wrt54g but a wrt54gs arrives instead. Should I keep wrt54gs or ask for wrt54g? Is for a home-lan, but I would like to intrude wireless group in my town.
[14:15] <nbd> fromoze: wrt54gs is better than the g
[14:15] <fromoze> sorry if it's a wrong place for my question :/
[14:15] <olli_04> fromoze: geep the gs
[14:15] <fromoze> Ok, thanks!
[14:15] <fromoze> I'll keep it.
[14:28] <CanDoo> i have completed my wds and web instalation
[14:28] <CanDoo> and it seems to be working perfectly
[14:37] Action: moonwatcher looks for nbd...
[14:39] <nbd> hey
[14:39] <nbd> pptp is not done yet. had to fix a nasty ppp bug...
[14:40] <pp_> which reminds me to check whether my pppoe over br0 would mystically work now
[14:41] Action: moonwatcher will wait patiently...
[14:41] <moonwatcher> i hope the howto helped...
[14:55] <d00f> ++
[14:56] <dothebart> hy.
[15:00] <dothebart> i'm wondering if ipkg_depends: Warning: kernel mentioned in dependency but no package found in /usr/lib/ipkg/lists and installing new nic modules will render the router unusable...
[15:00] <nbd> dothebart: maybe you should update
[15:01] <dothebart> i'm doing an upgrade, but it seems as if it just is able to find the new kernel modules, but not the kernel itself?
[15:02] <dothebart> it allso updated the dropbear, and cut of my installation shell, so i can't see anymore what it's doing.
[15:02] <nbd> dothebart: i mean reflashing with a newer snapshot
[15:02] <dothebart> ah. ok.
[15:04] <quax> Hi, I've a problem with my wrt (wrt54GS 1.1): from the client side (windows) the connection seems to be ok, but I can't ping the wrt, and from the wrt I can't ping the windows client.
[15:04] <dothebart> so doing cvs update on the host system and rebuilding is what i want to do?
[15:04] <quax> arp requests from the wrt receive noresponse..
[15:04] <quax> that all using openwrt..
[15:05] <quax> what can I look for in my configuration?
[15:07] <dothebart> is the nic staticaly linked to the kernel?
[15:07] <quax> wifi_proto=static ?
[15:07] <quax> or what?
[15:08] <quax> I've the standard kernel from whiterussian
[15:13] <quax> no hint ? :)
[15:17] <dothebart> uh. make: *** uclibc++: No such file or directory. Stop.
[15:20] <quax> these is what I changed from the default
[15:20] <quax> http://rafb.net/paste/results/kVn0pl20.html
[15:20] <quax> and I deleted the firewall script
[15:20] <dothebart> arg. cvs update -d ;)
[15:53] <quax> don't think this is normal..
[15:53] <quax> root@OpenWrt:~# iwlist eth1 bitrate
[15:53] <quax> eth1 unknown bit-rate information.
[15:53] <quax> or is it?
[16:55] <tmbinc> is the WGT634U the only one with USB2.0?
[16:57] <tmbinc> i have some trouble on WGT634U with usb-storage, but as it's all experimental i'm not sure where the problem lies
[17:02] <BULLE> tmbinc: silly question, with an WGT634U how do you flash openwrt to it ?
[17:03] <BULLE> tmbinc: do you need to open the thing, and use a serial or jtag interface, or is there some simiple way of loading the firmware ?
[17:05] <tmbinc> BULLE: i opened it, and attached a serial port
[17:05] <BULLE> i see
[17:05] <tmbinc> BULLE: i'm currently using nfs'd debian until at least the kernel works ok
[17:06] <tmbinc> though if you're brave, you would be able to hack into the stock firmware and replace the kernel in flash
[17:06] <tmbinc> if this fails, you need serial ;)
[17:07] <tmbinc> i hacked an old, cheap cellphone "usb" datacable, which had a PL2303 with TTL (or even 3.3V) levels, so that wasn't really a problem
[17:31] <hedpe> is a USB port possible on the wrt54g?
[17:31] <olli_04> hedpe: no, you need a asus wl-500g deluxe it has two usb 2.0 ports
[17:32] <hedpe> olli: how do you look for these kinds of things on the board? like what gave away the serial port on the board for example? are they labeled?
[17:34] <BULLE> tmbinc: well, i have 0 hardware experience realy, so i try to avoid mucking around with the internals of my hardware
[17:34] <BULLE> tmbinc: mind, it all seems very intresting thoug, to much around with the internals of ones hardware
[17:35] <tmbinc> olli_04: do they usually work stable on 2.6.12?
[17:36] <olli_04> hedpe: do you mean something like this: http://wiki.openwrt.org/TableOfHardware
[17:37] <olli_04> tmbinc: no, because the propritary wireless broadcom driver doesn't work with kernel 2.6 (the wireless driver is aviable in binary only from broadcom)
[17:37] <tmbinc> ah ok, so it's not a NEC ehci?
[17:37] <tmbinc> (like on my WGT634U)
[17:38] <olli_04> tmbinc: i don't know, i've never seen openwrt running on a wgt634u
[17:38] <hedpe> thanks olli
[17:38] <tmbinc> well if it would be EHCI, you wouldn't need any special driver. :)
[17:40] <olli_04> tmbinc: as i said, i don't know if openwrt is running on the wgt634u, so i could not help you out on this
[18:15] <matled> you've got speakers at you wrt?
[18:15] <PolarWolf> That's pretty cool. But only one question bugs me..."why?"
[18:15] <robr> hmm.. usb headset
[18:15] <robr> why -> mp3 player on places w/o pc
[18:15] <robr> wireless music
[18:16] <robr> btw its a wl500g, but wrt should work as well
[18:16] <robr> why -> 'because it's possible' ;-)
[18:17] <robr> could i put the binaries / sources somewhere to let other users use them?
[19:13] <ob1kenewb> I don't find the wlconf prog after having flashing my box any hints ?
[19:13] <ob1kenewb> and the wl program neither
[19:16] <Dabian> nbd: I think its impossible for me to get in failsafe, if the air-led is supposed to stay off.
[19:24] <Dabian> Has nbd left?
[19:24] <Dabian> Thats terrible.
[19:34] <ob1kenewb> Error for wireless request "Set Encode" (8B2A) :
[19:34] <ob1kenewb> SET failed on device eth1 ; Invalid argument.
[19:35] <ob1kenewb> I got this with iwconfig
[19:35] <erik_--> Dabian have you brick a wrt54g ?
[20:46] <pp_> u-hum
[20:47] <pp_> err
[21:39] <ob1kenewb> hi, it's impossible to disable WEP on my wrt
[21:43] <stonezone> anyone run fakeap on their wrt?
[22:12] <stonezone> http://www.steelcitysfinest.com/HondaAccordAd.htm
[22:13] <FireEgl> I just received a WRT54GS v2.1 ..Has anybody else tried openwrt on that version?
[22:13] <Vince||> stonezone: it is a perl script and there is no perl for openwrt, it is too big
[22:14] <stonezone> that makes complete sense
[22:14] <Vince||> stonezone: it wouldn't be to difficult to implement the same thing in C or in shell
[22:15] <Vince||> you just need to generate random names and to change the ssid
[22:15] <Vince||> I suppose wificonf will do the trick to change the ssid
[22:15] <Vince||> and md5sum will generate random names
[22:25] <robr> does the openwrt emergency mode (or what is it called) work on an asus wl500-g as well?
[22:26] <robr> i messes
[22:26] <robr> :S
[22:26] <robr> i messed up the nvram network settings
[22:26] <robr> i can reflash using boot_wait, but i would like to keep my jffs. is this possible?
[22:49] <ab0oo> nbd: ping.
[22:50] <port7> why is ipkg adding 'Packages' to the end of the package repositry url?
[22:58] <stonezone> damn, that sucked, road runner down for almost an hour
[23:01] <Semhirage> ouch
[23:01] <Semhirage> i'd call and demand a credit
[23:02] <stonezone> they would laugh
[23:02] <stonezone> bastaads
[23:02] <Semhirage> =/
[23:03] <Semhirage> i get mad credits from isp if it goes down for more than 5 minutes and i don't have 24 hour warning
[23:03] <stonezone> you must not live in hawaii
[23:03] <stonezone> shitty service here
[23:03] <Semhirage> newp
[23:03] <Semhirage> Wisconsin here
[23:03] <Semhirage> speakeasy onelink for isp
[23:03] <stonezone> ah, a real state
[23:04] <stonezone> http://bsdvault.net/bsdfap.txt
[23:04] <stonezone> wrong window
[23:04] <Semhirage> normally i would rag about what a pos this state is, but after today and the courts decided in my favor and im not going to jail and i get to keep my son, yea WI ain't half bad
[23:05] <stonezone> lol, i guess congrats are in order
[23:05] Action: stonezone pats Semhirage on the back, nice job.
[23:05] <ab0oo> The wisconsin child support courts can KMA.
[23:05] <stonezone> seems like most states are that way
[23:05] <Semhirage> small ones, the major congrats will come 9 MO down the road when his mother has no rights and never gets to see him again
[23:06] <stonezone> was just talking to my dad about that, he got a 20+ grand bill back in the day saying he was seriously delinquent
[23:06] <stonezone> even though he had custody
[23:06] <ab0oo> My wife's ex-husband has custody 6 weeks per year, and pays less than$300/month in child support, and has for only 5 of the 12 years my daughter (step, but she's been mine for 9 years) has been alive.
[23:07] Action: stonezone remembers to never ever have kids
[23:07] <ab0oo> Has anyone compiled the ISC DHCP server for openWrt? It won't compile in buildroot.
[23:07] <Semhirage> i had no problem paying my CS when it was taking care of my son, i had a big problem when she was buying oz's and dimebags with it
[23:08] <[mbm]> ab0oo: it won't run on openwrt either
[23:08] <ab0oo> [mbm]: why not? I'm kinda desperate for it.
[23:08] <[mbm]> ab0oo: kernel configs; it was mentioned in the forum a few times
[23:09] <ab0oo> didn't search there. has anyone ever used (or understood) dhcp-relay and dhcp-forward?
[23:10] Action: [mbm] doesn't have a network large enough to need a forward/relay
[23:10] <PolarWolf> 's what you need to get DHCP requests to the other end of routers
[23:10] <ab0oo> I'm a little confused on the difference between forward and relay.
[23:10] <ab0oo> I have a DHCP server at my CO-LO server (10 hops away from my router) that I want to serve DHCP from.
[23:10] <ab0oo> is that a "relay" or an "agent" job?
[23:11] <PolarWolf> I bet agent, I'm not entirely sure though
[23:12] <PolarWolf> google should know
[23:13] <ab0oo> I really couldn't find a difinitive "this is the difference" doc.
[23:20] <fusQuanto> is the wrt54g capable of being used to sniff AIM conversatinos of employees on my network?
[23:21] <[mbm]> privacy?
[23:21] <stonezone> dsniff
[23:21] <fusQuanto> hardware wise i mean, no limitations?
[23:22] <pyromaniac> fusQuanto, it's illegal in most countries :-)
[23:22] <pyromaniac> fusQuanto, isn't AIM encrypted? (i realy dunno) msn is.
[23:22] <[mbm]> can be
[23:23] <zinx> i doubt either are encrypted to any significant degree
[23:23] <fusQuanto> aim isnt
[23:23] <port7> anyone know about problems with ipkg update
[23:24] <port7> its adding the string 'Packages' to the end of the repositry url
[23:24] <[mbm]> port7: that's not a bug, the list of available packages is called "Packages"
[23:24] <port7> hmm
[23:25] <port7> ok
[23:25] <port7> maybe its a diff error then
[23:26] <pyromaniac> who knows? it might be all in your imagination?
[23:26] <port7> ipkg_download: ERROR: Command failed with return value 1: `wget --passive-ftp -q -P /tmp/ipkg-ryoIJq http://downloads.openwrt.org/whiterussian/packages/Packages'
[23:26] <port7> aye
[23:26] <[mbm]> port7: look above for a dns or routing error
[23:27] <port7> will do
[23:27] <port7> tho i can resolve names ok
[23:27] <port7> and ping the outside world
[23:27] <[mbm]> from the router or from your computer?
[23:27] <pyromaniac> well i can asure you that the file exists
[23:28] <port7> from the router
[23:28] <port7> tho i can't ping downloads.openwrt.org
[23:28] <pyromaniac> i can
[23:29] <port7> wonder if my isp is having probs
[23:29] <port7> can ping some places but not others
[23:29] <port7> e.g.
[23:29] <port7> can ping www.linux.org
[23:30] <port7> but not downloads.openwrt.org
[23:30] <port7> ok maybe i will try tomorrow
[23:30] <pyromaniac> change dns :)
[23:30] <port7> ok it worked now
[23:30] <pyromaniac> k?
[23:30] <port7> thats weird
[23:30] <pyromaniac> soloution?
[23:31] <port7> i think venus just passed overhead
[23:31] <port7> that must have fixed it
[23:33] <port7> thanks for the input people :-)
[23:34] <fusQuanto> does the 54g have a port monitoring or SPAN function?
[23:35] <[mbm]> not really
[23:36] <fusQuanto> how do i aim sniff :(
[23:36] <pp_> you can bridge two ports and tcpdump the bridge
[23:36] <pp_> it'll kill your perf tho
[23:37] <fusQuanto> hmm
[23:37] <port7> ntop would be a cool package to have
[23:38] <[mbm]> fusQuanto: a script from el33ts5riptk1ddies.com might help :P
[00:00] --- Sat Jul 16 2005