OpenWrt

[00:02] <inh> well that didnt work
[00:02] <inh> :/
[00:02] <Death_INC> lol
[00:02] <inh> lan_iaddr to 192.168.2.1 and now i cant get in
[00:02] <Death_INC> did you miss the part where I said it won't give dhcp unless you fix dnsmasq.conf?
[00:03] <inh> yea
[00:03] <inh> all better
[00:03] <inh> jsut gave my eth0 2.2 ip
[00:03] Action: Death_INC blinks
[00:03] <Death_INC> dont set addresses on eth0
[00:03] <inh> not for the wrt
[00:03] <inh> for my laptop
[00:03] <Death_INC> aah
[00:03] <inh> since it wont dhcp :p
[00:04] <inh> what id love to be able to do is get into my router over wifi. not the wifi on the wrt, the wifi on my 192.168.0.1 router
[00:04] <Death_INC> you can if you disabled firewall
[00:04] <Death_INC> and didnt fuck up your wan link yet
[00:05] <inh> 192.168.2.0 * 255.255.255.0 U 0 0 0 br0
[00:05] <inh> 192.168.0.0 * 255.255.255.0 U 0 0 0 vlan1
[00:05] <inh> default 192.168.0.1 0.0.0.0 UG 0 0 0 vlan1
[00:05] <inh> ?
[00:05] <inh> did i?
[00:05] <Death_INC> I dont think so heh
[00:05] <[mbm]> why are you even making a new subnet anyways?
[00:05] <Death_INC> [mbm]: I donno, I didnt want to talk him out of it
[00:05] <inh> i dont know...
[00:05] <[mbm]> like I said before, we had the discussion, it's in the logs
[00:06] <Death_INC> can make all the ports on "lan" network then you can have everything on 0.x
[00:06] <Death_INC> or just not use the wan port
[00:07] <inh> ok.. i guess i can connet the wrt to the 0.1 router, via the lan port right?
[00:07] <Death_INC> but another subnet won't actually hurt anything
[00:07] <inh> and that makes things simpler
[00:07] <Death_INC> just complicate your setup
[00:07] <Death_INC> ya
[00:07] <inh> ok so lets do that
[00:08] <inh> since at 4 or 5 am, when i jsut got the wrt i was confused as hell and just doing what [mbm] said, not really learning anything
[00:08] <[mbm]> if you ask how I'll consider a ban ;)
[00:08] <Death_INC> lol
[00:08] Action: [mbm] thinks inh needs to revisit the logs from the last time
[00:08] Action: Death_INC thinks [mbm] just passed subtle hints and moved on to the sledge hammer
[00:09] Action: inh thnks hes jsut gonna go learn this rap anyway he can and stop buging everyone
[00:17] <Death_INC> [mbm]: have you had WPA+AES work reliably for you? ... I've got it working on and off but it seems flakey
[00:19] <Death_INC> well, WPA-PSK in general
[00:20] Action: [mbm] uses a crappy 64bit wep .. easily cracked but no point when there's any number of open access points nearby
[00:21] <Death_INC> bah heh
[00:22] <Death_INC> I want to do a mesh network, but if I'm going to let other people use it I want some security :\
[00:22] <Death_INC> mine's been wide open otherwise heh, didnt even bother with wep
[00:22] <[mbm]> I haven't really played with nas
[00:23] <Death_INC> I think maybe I'll just wait till the source for the new beta firmware is released and see if that makes things work nicer for me heh
[00:23] Action: Death_INC sighs
[00:24] <inh> [mbm], kmod-vfat takes care of vfat and fat, but what can i do about the rest? CONFIG_PARTITION_ADVANCED=y
[00:24] <inh> CONFIG_MSDOS_PARTITION=y
[00:24] <inh> CONFIG_FAT_FS=y
[00:24] <inh> CONFIG_MSDOS_FS=y
[00:24] <inh> CONFIG_VFAT_FS=y
[00:24] <Death_INC> what rest
[00:24] <Death_INC> vfat=msdos
[00:24] <inh> no theres supposed to be a msdos.o moduel or something
[00:24] <Death_INC> you don't need one
[00:25] <Death_INC> msdos is legacy
[00:25] <inh> i do if im to follow the sd card mod
[00:25] <Death_INC> vfat will mount it
[00:25] <inh> ok
[00:25] <inh> now i gotta get the mmc module to load
[00:28] <Death_INC> microsoft management console module?
[00:28] <Death_INC> wait, I'm not talking this is being logged :x
[00:28] <inh> hehe
[00:28] <inh> multimedia card
[00:29] <Death_INC> might I ask why you need that much space?
[00:29] <inh> for kicks
[00:29] <inh> dont need anyhting
[00:29] <Death_INC> lol
[00:29] <inh> i dont need the wrt
[00:30] <Dabian> I am going to set mine up as a bridge today - I hope. A bridge between wan and lan.
[00:30] <Death_INC> Dabian, that's easy
[00:30] <Death_INC> sorta
[00:30] <Death_INC> lol
[00:30] <Dabian> Death_INC: Heheh ..
[00:31] <Death_INC> not quite sure what you mean, it's easy or not heh
[00:31] <Dabian> Death_INC: I have installed it .. I am still telnetting, because I havn't managed to get it on the internet yet.
[00:31] <Dabian> Death_INC: The setup is this:
[00:31] <Dabian> Death_INC: I have an external gateway, that is located at my ISP.
[00:32] <Dabian> Death_INC: So all i need is to put the WL-500gd between my uplink, and my main hub, I guess.
[00:33] <Death_INC> but you dont need to do address translation?
[00:33] <Dabian> Nope .. no nat is nessesary.
[00:33] <Death_INC> just plug everything into lan ports heh
[00:33] <Dabian> Yeah .. that might be the sollution.
[00:33] <Death_INC> which still dosnt explain the point of that excercise
[00:33] <Dabian> Optimal, I want to have a port the lan hub, and a port for the DMZ hub though.
[00:34] <Death_INC> use your wan as dmz or something then
[00:34] <Death_INC> you can however, configure all 5 ports as different vlans
[00:34] <Dabian> Death_INC: The point is that I want the wrt to do some QoS .. but first step will be to make it bridge.
[00:35] <Death_INC> qos is pretty hard to do if you're just bridging
[00:35] <Death_INC> might want to do routing for that
[00:35] <Dabian> ok
[00:35] <Dabian> How come?
[00:35] <Death_INC> I mean I think it's possible, but I dont know
[00:35] <Dabian> I can spare an IP for the box
[00:35] <Death_INC> switching between ports on the same vlan is done in hardware
[00:35] <Death_INC> for starters
[00:35] <Dabian> ok
[00:36] <Death_INC> if you had different ports bridged together, you might be able to
[00:36] <Death_INC> using linux bridging
[00:36] <Death_INC> but I really don't know how that would work
[00:36] <Dabian> So you would adwise, that I set it up as router, and change default gateways on my computers?
[00:36] <Death_INC> well you'd need a second subnet then
[00:37] <Death_INC> or you could configure it to do proxy arp I suppose
[00:37] <Death_INC> and do a 1-for-1 matching for all your IPs
[00:37] <Death_INC> then you not really doing NAT
[00:37] <Death_INC> unless your ISP will route your networks to an address on your end
[00:37] <Dabian> I can actually do two subnets, if nessesary, I guess.
[00:37] <Death_INC> well, you doing NAT but not PAT
[00:38] <Dabian> Death_INC: No, the ISP route directly to IP.
[00:38] <Death_INC> don't get me wrong, it's probably possible to do what you want to do
[00:38] <Death_INC> but don't expect it to be easy ;)
[00:38] <Dabian> Well, I don't want to complicate things for starters, I guess. I need to get the WL-500gd on net, so I can ipkg stuf.
[00:38] <Death_INC> the cisco PIX uses proxy arp to do that, would probably be your simplest solution
[00:39] <Dabian> What does proxy arp mean? arp == address resolution protocol == brodcasting in order to discover which MAC/IP other stations have, right?
[00:39] <Death_INC> but, I haven't done it so I cant really help alot ;)
[00:39] <Death_INC> proxy arp works like this...
[00:40] <storchi> hello, can someone help me to fix a transmission rate problem?
[00:40] <Dabian> storchi: Yes. Not I though.
[00:40] <Dabian> storchi: That is, not right now, because I need to learn a little about it first.
[00:41] <Dabian> storchi: Besides, I'm listening to Death_INC.
[00:41] <Death_INC> your wrt knows that it will accept traffic destined to "1.2.3.4" and "1.2.3.5" on wan which will be nat'd to say 1.2.4.4 and 1.2.4.5 on lan respectively.... when it sees a request for ARP for 1.2.3.4 or 5 on the wan, it replies with its MAC address and routes the packet thru
[00:41] <Death_INC> and your wrt's address could be say 1.2.3.2
[00:41] <Dabian> routes the packet tru" (last I got -- you were cut)
[00:41] <Death_INC> wasnt cut, that was the end of the line heh
[00:41] <storchi> at frist how can i send direct to you?- first time irc...
[00:42] <Death_INC> so it pretends to be all 3 addresses on your wan side, but anything it gets for 2 of them are nat'd to other addresses on the lan side as if it were routed to your wrt
[00:42] <Death_INC> understand?
[00:42] <Dabian> 1.2.3 and 1.2.4 is different subnets?
[00:42] <Death_INC> yes
[00:43] <Dabian> Nice
[00:43] <Death_INC> and as far as everything on the inside knows the wrt is the router
[00:43] <Death_INC> but, like I said I dont know how to configure it on linux
[00:43] <Death_INC> just know it's possible :b
[00:44] <Dabian> Lemme make an example .. because I am not totally set on what to do yet.
[00:44] <Death_INC> probably just have to configure the additional addresses on your loopback interface or something
[00:45] <Death_INC> Dabian: bridging could work fine, I just have less experience there
[00:45] <Dabian> Well
[00:45] <Death_INC> Dabian: google tells me http://www.burnpc.com/website.nsf/all/3a64a6369757819686256f960068ad75!OpenDocument
[00:46] <Dabian> One of the reasons I thought of bridging, is that it seems the openwrt can do bridging between lan and radio
[00:46] <Dabian> But of course, it doesn't do QoS for that ..
[00:46] <Death_INC> yes, it uses br0 interface
[00:46] <Dabian> yeah
[00:47] <Dabian> OK .. here is an example simular to my setup ... the net I own, is "1.1.1.0", my ISP has a router at 1.1.1.1.
[00:47] Action: Death_INC nods
[00:48] <Death_INC> your wrt would be say 1.1.1.2 and you would configure extra addresses to be nat'd to your other internal addresses
[00:48] <Dabian> The router is not in house .. I assume its a big cisco thing at the ISP that routes several net works.
[00:48] <Death_INC> if you have the whole class C you could configure it to just do 1-for-1 for everything besides 1.2
[00:48] <Dabian> Death_INC: I was planning on giving the wrt 2 :)
[00:48] <Dabian> Death_INC: I have the subnetmask: 255.255.255.248
[00:49] <Dabian> just a small 8 IP net .. and 1 ip for ISP router, 2 for broadcast/network, I guess.
[00:49] Action: Death_INC nods
[00:49] <Dabian> So the idea was to avoid NAT, and use firewalling instead.
[00:49] <Death_INC> would be nice, and you can probably do it
[00:50] <Dabian> Also, I can alias the interfaces, so I can get a lan on the "inside".
[00:50] <Death_INC> just make sure your rules are applied to the real interface not the bridge interface
[00:51] <Death_INC> and you could have it doing NAP/PAT for your wireless clients instead of having them part of the bridge
[00:51] <Death_INC> can do pretty much anything
[00:51] <Dabian> Death_INC: The most important thing I want to do with the wrt, for now, is to do some QoS, so I can listen to music and/or talk in my SIP ip phone without jitter and other problems because people surf on my webserver or I am downloading or whatever.
[00:51] <Death_INC> brctl controls the bridges
[00:51] <Dabian> Right now I don't use the radio at all.
[00:52] <Death_INC> actually it shouldnt be a problem at all since tc is per-interface not per-network
[00:53] <Death_INC> just unset all your wan_* and change lan_ifnames to "vlan0 vlan1 eth1"
[00:53] <Dabian> tc ...
[00:53] <Death_INC> tc is what configures the qos
[00:53] <Death_INC> wondershaper uses it
[00:53] <Dabian> wondershaper :)
[00:54] <Dabian> sounds nice :)
[00:54] <Death_INC> I'm going to get food heh
[00:54] <Death_INC> good luck
[00:54] <Dabian> thanks !
[00:57] <Dabian> I need to read
[00:57] <Dabian> something basic about this stuff.
[00:59] <wt> anyone here?
[01:00] <wt> I have a question about openwrt
[01:00] <wt> and it makes me sad
[01:01] <wt> dhcp client doesn't seem to work in the experimental...I had a router that just up and stopped working after I had set it up
[01:01] <wt> I got another and it won't get dhcp now
[01:01] <wt> what could have gone wrong?
[01:02] <wt> I guess no one is here right now
[01:08] <wt> anyone here now?
[01:09] <ldc> yep
[01:09] <wt> openwrt?
[01:09] <wt> do you use it? or have you used it?
[01:09] <wt> I am having a weird issue
[01:10] <wt> it won't get a dhcp response
[01:10] <wt> even though the real firmware did
[01:10] <ldc> working on getting openwrt to support my netgear box...
[01:10] <wt> oh
[01:11] <wt> which one?
[01:11] <ldc> wgt634u
[01:11] <wt> I would like to see some custom firmware for the fsm7326p
[01:11] <wt> that would be bad ass
[01:11] <wt> it already runs linux
[01:12] <wt> are you having any probs with dhcp?
[01:12] <ldc> heh... that's just a plain switch...
[01:12] <wt> it's a managed switch
[01:12] <wt> layer 3 switch
[01:12] <ldc> probably cheaper and easier to just get a PC and a bunch of 8-port network-cards
[01:13] <wt> 1200 about
[01:13] <wt> and it has poe
[01:14] <ldc> well well... i have not had any problems with dhcp... But lots of ISP's have those 30 minute delay's before a new MAC can request a new ip
[01:15] <wt> it's weird, the thing was working, and then it just up and didn't
[01:15] <ldc> and the dhcp daemon is running as it should? no errormessages in the logs?
[01:16] <Dabian> I am very confused about the nvram and what it is used for.
[01:16] <wt> Dabian: storage of settings
[01:16] <Dabian> yes, I know nvram is cmos for pc .. you can save stuff in ti.
[01:16] <Dabian> it
[01:16] <wt> Dabian: and it lets you temporarily test settings
[01:16] <Dabian> if I don't commit
[01:16] <wt> you put new settings in
[01:17] <wt> that's true
[01:17] <wt> so what's the question?
[01:17] <Dabian> Well
[01:17] <Dabian> I know Linux
[01:17] <wt> are you asking why some settings are stored there?
[01:17] <Dabian> if I want to change ip, I use ifconfig, if I want to change routing, I use /sbin/route
[01:18] <Dabian> wt: Well, I don't understand what is reading the settings, and how they affect the wrt
[01:18] <Dabian> I'm totally green with wrt.
[01:18] <Dabian> Just got this one yesterday
[01:18] <wt> ifup wan reads the appropriate wan_* settings
[01:19] <Dabian> ahh
[01:19] <wt> the settings are stored there just to leave as much space free on the device as possible
[01:19] <Dabian> I see, it tries to get an IP over dhcp.
[01:19] <wt> word
[01:19] <wt> ming says something stupid right now though
[01:19] <wt> and it's only 840 mi away from me
[01:19] <wt> so it's kinda hard to troubleshoot
[01:19] <Dabian> So, what I need to do, is to assign a static ip, and tell it that it has static ip, I guess.
[01:20] <Dabian> ming?
[01:20] <wt> ok
[01:20] <wt> do something like this
[01:20] <wt> nvram set wan_proto=static
[01:21] <wt> nvram set wan_ipaddr=xxx.xxx.xxx.xxx
[01:21] <wt> nvram set wan_netmask=xxx.xxx.xxx.xxx
[01:21] <wt> nvram set wan_gateway=xxx.xxx.xxx.xxx
[01:21] <PolarWolf> Hum..
[01:22] <wt> nvram set wan_dns=xxx.xxx.xxx.xxx
[01:22] <wt> nvram set wan_hostname=xxxxxxxxxxx
[01:22] <wt> nvram commit
[01:22] <wt> reboot
[01:23] <wt> or do the ifdown wan and ifup wan before the commit
[01:23] <wt> I think
[01:23] <wt> maybe I am wrong
[01:23] <Dabian> What should the wan_hostname be?
[01:25] <wt> whatever you want the hostname of the router to be
[01:25] <Dabian> right
[01:25] <wt> I think
[01:25] <PolarWolf> Enter new password:
[01:25] <PolarWolf> Re-enter new password:
[01:25] <PolarWolf> passwd: An error occurred updating the password file.
[01:25] <PolarWolf> Yay
[01:25] <Dabian> iheartcanada: Hey
[01:25] <iheartcanada> What does your name mean Dabian?
[01:26] <iheartcanada> Is it like Debian?
[01:27] <Dabian> iheartcanada: Dabian is chinese for feces I've been told .. and many thinks its related to Debian, but actually it comes from a random nick generator when I had to get a name in a game years ago.
[01:27] <iheartcanada> oh
[01:27] <iheartcanada> weird
[01:27] <iheartcanada> well Debian is a great distribution
[01:27] <Dabian> iheartcanada: I am not sure about the chinese part .. I think maybe the guy that told me was just teasing me.
[01:28] <iheartcanada> So is it settled, is there a faster better replacement for wrt54g or what?
[01:29] <Dabian> iheartcanada: I just bought the WL-500g deluxe, its 200 MHz .. its important to notice there is a _huge_ difference between wl-500g, and wl-500g deluxe.
[01:29] <iheartcanada> oh
[01:30] <Dabian> iheartcanada: The openwrt.org website has a list of supported, unsupported (and possibly later supported) devices
[01:30] <iheartcanada> why is it that openwrt work for wl-500g? is wl-500g and wrt54g not made by different companies? with different hardware?
[01:31] <Dabian> wt: When I did ifdown wan .. I lost connection to the wrt, and power cycled.
[01:31] <Dabian> wt: I just checked, the cables should be right ..
[01:31] <iheartcanada> ifdown power cycles? that's messed up
[01:31] <Dabian> iheartcanada: Nah .. I pulled the plug.
[01:31] <Dabian> ;-)
[01:31] <iheartcanada> lol
[01:32] <Dabian> I couldn't telnet to the device anymore.
[01:32] <macsat> Dabian on a Chineese server : http://image2.sina.com.cn/gm/mobile/zt2004/hjwsm/dabian.gif
[01:32] <macsat> ...I am afraid that you COULD be correct about the chineese meaning ;-)
[01:32] <wt> Dabian: that is messed up
[01:32] <Dabian> macsat: Maybe its time to consider a new nick .. :-P
[01:32] <macsat> hehe
[01:33] <Dabian> wt: Yes
[01:33] <Dabian> wt: I notice that board might have quirks
[01:33] <wt> okay, now I am just confused
[01:34] <Dabian> wt: I think its mentioned in the nvram.overrides
[01:34] <wt> I am just gonna build one and ship it down there
[01:34] <Dabian> is what I mean.
[01:35] <olifozzy> hey
[01:35] <Dabian> There is a check for if the boardtype is "bcm95365r" and the boardnum is "45" .. and I think mine fits that description.
[01:36] <olifozzy> i m wondering how to store the essid value ? so that when my router reboot the value is still there
[01:37] <Dabian> It does this: NVRAM_vlan0hwname="et0", NVRAM_vlan1hwname="et0", NVRAM_lan_ifnames="vlan0 eth1"
[01:37] <Dabian> which I don't really understand.
[01:38] <Dabian> wt: I'll give another try, this time writing to the nvram as you suggested?
[01:38] <Dabian> nah .. this time I don't have the wan up yet .. so ..
[01:39] <Dabian> iheartcanada: Which channel do I know you from? I remember your nick, but not the channel.
[01:40] <coder> olifozzy nvram set wl0_ssid=your_essid ; nvram commit; reboot
[01:40] <olifozzy> coder : thanks
[01:40] <iheartcanada> must be electronics
[01:41] <Dabian> wt: Btw, I am also using experimental, so when I get this thing up, I can test dhcp somehow, maybe?
[01:50] <Dabian> ok
[01:51] <Dabian> wt: Now it works .. I reboot the wrt, and I can ping the wan ip .. only, I cannot ping anything else on the wan subnet.
[01:52] <Dabian> I tried inserting som permissing firewall rules using "iptables -I blabla"
[01:53] <Death_INC> Dabian: it'll be lost when you reboot unless you put it into a boot script
[01:54] <Death_INC> ./etc/init.d/S4?firewall is what it uses
[01:54] <Death_INC> 45?
[01:54] <olifozzy> Death_INC : yes
[01:55] <Death_INC> PolarWolf: firstboot, or if jffs2 reboot
[01:55] Action: Death_INC gone again
[01:56] <Dabian> Death_INC: I entered the firewall rules after the reboot. :)
[01:56] <Dabian> Death_INC: Because I couldn't ping.
[01:56] <PolarWolf> Death_INC: Yeah, just found it in the IRC logs
[01:57] <PolarWolf> I thought these days firstboot is run automagically?
[01:59] <Dabian> ok
[01:59] <Dabian> right now I just need to get the darn wan interface up
[02:00] <Dabian> one step at a time.
[02:01] <Dabian> My wrt is connected with the lan3-port to the locale switch, while the wan-port is connected to my DMZ hub.'
[02:01] <Dabian> I have used nvram set wan_ipaddr, gateway, netmask, dns and hostname,
[02:02] <Dabian> I've used ifup wan, and iptables -I blabla to give permission.
[02:02] <Dabian> I can ping the wan's own ip from the wrt, but not from the outside, and I cannot ping out of the wrt.
[02:03] <Dabian> Maybe this is the time to try and switch the cables to see if that helps.
[02:05] <Dabian> it didn't.
[02:05] <olifozzy> does openwrt support upnp ?
[02:06] <Dabian> btw
[02:06] <Dabian> I think someone metioned that the wan is really another vlan
[02:07] <Dabian> oh well
[02:10] <Dabian> ahh
[02:10] <Dabian> at last
[02:10] <Dabian> I found http://openwrt.org/OpenWrtDocs/Configuration
[02:10] <Dabian> I hope that will explain stuff to me. :)
[02:18] <Dabian> http://openwrt.org/OpenWrtNVRAM is also cool
[02:22] <roam> how can I install the official linksys firmware after running openwrt?
[02:22] <nbd> roam: read our documentation
[02:22] <Dabian> roam: Get the original firmware from linksys site, then install it like you did openwrt.
[02:23] <Dabian> roam: Be sure you get the right image.
[02:23] <wbx> moin nbd
[02:23] <roam> Dabian: It doesn't work with boot wait cause the firmware is to big.
[02:23] <nbd> moin wbx
[02:23] <wbx> nbd: next 10 hours i have time for openwrt.. will update to netgear kernel..
[02:23] <Dabian> roam: Too big?
[02:24] <Dabian> wbx: Netgear has a kernel? Is it free?
[02:24] <Dabian> free as in freedom..
[02:24] <nbd> wbx: cool. i haven't had much time for openwrt in the last few days. that'll probably change after tuesday
[02:25] <wbx> Dabian: same stuff as linksys, but et/wl driver is a little bit newer
[02:26] <Dabian> wbx: I have an asus device .. their firmware seemed to be GPL.
[02:26] <Dabian> I don't know what linksys has.
[02:27] <wbx> nbd: we still need a good idea how to support both kernels..
[02:27] <Dabian> When I look at the OpenWrtNVRAM .. it doesn't seem to say "for this model, this, for that model that" .. does this mean I can assume that all the recommended settings are good for any device, including my wl-500gd ?
[02:28] <nbd> wbx: support them in what way? packaging stuff, compiling stuff, what do you mean?
[02:28] <roam> Dabian: There's a 3MB limit for tftp-images
[02:28] <roam> Dabian: on the router
[02:29] <Dabian> roam: No idea how to beat that.
[02:29] <Dabian> roam: You might be "stuck" with openwrt.
[02:29] <nbd> roam: you're not stuck with openwrt
[02:29] <wbx> nbd: coexistence in our buildroot.
[02:30] <nbd> roam: it's in our configuration
[02:30] <wbx> nbd: without cvs tagging. so you change a model like netgear and images and kernel for this device is build..
[02:31] <nbd> wbx: just make a working package directory for the netgear and i'll find a way to integrate it cleanly :)
[02:31] <wbx> nbd: ::p
[02:35] <roam> nbd: I want to continue using openwrt, but I need wireless this afternoon. So I need to install the official firmware.
[02:36] <nbd> roam: so you can't find it in the docs?
[02:36] <roam> nbd: Found something if I have a serial console.
[02:37] <nbd> roam: here: http://openwrt.org/OpenWrtFaq#head-e9d1d6a54806a68fe48c16766aef84207101a130
[02:40] <nettie> Hey wbx!, how's going?
[02:42] <PolarWolf> nbd: It seems bridgeutils is b0rk in HEAD
[02:42] <nbd> PolarWolf: what's b0rken?
[02:42] <PolarWolf> nbd: Control file for the package
[02:43] <PolarWolf> PATH="/data/openwrt/experimental/openwrt/staging_dir_mipsel/usr/bin:/data/openwrt/experimental/openwrt/staging_dir_mipsel/bin:/bin:/sbin:/usr/bin:/usr/sbin" ipkg-build -c -o root -g root /data/openwrt/experimental/openwrt/build_mipsel/bridge-utils-1.0.6/ipkg/bridge /data/openwrt/experimental/openwrt/bin/packages
[02:43] <PolarWolf> *** Error: CONTROL/control is missing field Package
[02:43] <PolarWolf> etc
[02:43] <nbd> PolarWolf: had problems like that a few days ago
[02:43] <nbd> PolarWolf: fixed them
[02:43] <nbd> PolarWolf: are the same problems back again now?
[02:43] <coder> PolarWolf: yesterday was Mr. T's birthday
[02:43] <PolarWolf> nbd: I did a cvs update an hour or so ago
[02:44] <nbd> thanks... i'll fix it
[02:44] <roam> nbd: Thanks
[02:45] <nbd> roam: worked?
[02:45] <PolarWolf> nbd: ta
[02:45] <PolarWolf> nbd: btw, considered including Tor as package?
[02:46] <nbd> PolarWolf: if someone packages it, we'll take it :)
[02:46] <PolarWolf> nbd: I did, it just needs updating to the latest version
[02:47] <nbd> PolarWolf: after updating your buildroot, did you clean the old stuff?
[02:47] <PolarWolf> nbd: Deleted build_mipsel
[02:48] <nbd> strange
[02:49] <nbd> nothing's changed in the bridge since my last successful build
[02:49] <PolarWolf> Weird
[02:50] <PolarWolf> grep: ./ipkg/bridge.control: No such file or directory
[02:50] <nbd> so you just did cvs update -PAd and the file is still not there?
[02:51] <PolarWolf> Just a regular cvs update, like I always do.
[02:51] <PolarWolf> Lemme see what happens
[02:52] <roam> nbd: I will try the squashfs image from your repository first.
[02:52] <PolarWolf> Seems to help
[02:52] <nbd> PolarWolf: i always use -PAd
[02:52] <PolarWolf> nbd: Good tip, it seems to create the file(s)
[02:53] <PolarWolf> Lemme see what happens no. `make` still bums out, I'm restarting
[02:53] Action: PolarWolf doesn't use CVS that much
[02:53] <nbd> remove build_mipsel again
[02:53] <PolarWolf> I generally stick to release quality code :P
[02:53] <nbd> that should do it
[02:53] <PolarWolf> I did
[02:54] <nbd> normally HEAD works. but a dev broke a lot of stuff in the last few days
[02:54] <PolarWolf> At least my kernel patches still apply
[02:57] <kentpaul> i'm a bit confused, i just installed openwrt, and it says to change password, when i do so it says an error occurred
[02:57] <J4k3> isn't kent paul the british bastard I slapped down at the malibu club? :)
[02:58] <kentpaul> heh yep :P
[02:58] <kentpaul> so i checked the state of my / and it's full
[02:58] <nbd> kentpaul: jffs2 image?
[02:58] <kentpaul> root@OpenWrt:/etc# df
[02:58] <kentpaul> Filesystem 1k-blocks Used Available Use% Mounted on
[02:58] <kentpaul> /dev/root 1472 1472 0 100% /
[02:58] <kentpaul> yes
[02:58] <nbd> kentpaul: reboot
[02:58] <kentpaul> ah
[02:59] <olifozzy> could someone help me with iptables and dmz befor nervous breakdown ?
[03:00] <nbd> olifozzy: maybe someone could help you if you would describe your problem
[03:00] <kentpaul> ah thats better :)
[03:01] <olifozzy> i ve put all the policies to forward , accept , DNAT, etc... ping is ok but i can't manage to acces servers on the dmz host
[03:03] <teemu_> is there good network/internet traffic monitor for openwrt
[03:03] <teemu_> that would show network traffic per lan ip
[03:05] <kentpaul> bah someone could have added the ll alias by now :)
[03:07] <PolarWolf> how about not getting used to system specific aliases instead?
[03:08] <kentpaul> what are they ?
[03:09] <PolarWolf> there aren't any, afaik.
[03:09] <kentpaul> etc/profile will need a manual update then :P
[03:14] <kentpaul> if my settings (using the linksys firmware) were setup to use mac filtering, will this still be setup on openwrt ?
[03:14] <kentpaul> i beleive the settings come from nvram varables and they dont appear to have be altered
[03:14] <nbd> should work
[03:15] <kentpaul> cool :P
[03:17] <kentpaul> is there a command that will display the build version currently installed, as opposed to uname -a or cat /proc/version. something openwrt specific
[03:17] <kentpaul> so that when i ask a question and i'm asked what version i have, i can provide an accurate answer
[03:18] <nbd> no
[03:19] <nbd> if there's a bug, please try my unofficial openwrt build
[03:19] <nbd> http://openwrt.org/downloads/nbd/gcc34/
[03:19] <kentpaul> ah
[03:19] <kentpaul> there is no problem so far :)
[03:19] <nbd> cool
[03:20] <kentpaul> i installed this one : openwrt-wrt54g-squas..> 23-Apr-2005 23:16 1.4M
[03:21] <kentpaul> from here : http://openwrt.org/downloads/experimental/bin/
[03:21] <kentpaul> the jffs2 one i sorry, i copied the wrong file
[03:21] <kentpaul> not as up to date as yours i see :P
[03:24] <nbd> yeah. the official snapshots don't get released very often
[03:24] <nbd> and i provide my builds so we don't get that many duplicate bug reports :)
[03:25] <kentpaul> heh :P
[03:28] <roam> re
[03:29] <storchi> can someone help me with a transmission rate problem?
[03:30] <roam> nbd: your squashfs-firmware shows the same behavour as the jffs2 build: no telnetd, just sshd and no login possible.
[03:30] <roam> nbd: That's on a G v1.1
[03:31] <nbd> roam: please try http://openwrt.org/downloads/nbd/gcc34.old/
[03:31] <kentpaul> think i may try to set this up as my primary domain controller with samba
[03:31] <roam> nbd: Flashing the official firmware with your method worked and fixed my wirelessproblems.
[03:32] <roam> nbd: I will maybe later today or tomorrow.
[03:32] <roam> nbd: right now I need wireless.
[03:32] <nbd> k
[03:33] <storchi> i need help for my ad hoc network
[03:33] <roam> nbd: I also noticed that the DMZ-LED never stopped with your firmware after flashing
[03:33] <roam> nbd: I guess it
[03:34] <nbd> seems like an init script is hanging
[03:34] <roam> that
[03:34] <roam> s what I thought.
[03:34] <roam> anything I can do to help debugging?
[03:36] <storchi> help
[03:37] <nbd> roam: i'll make an image that starts telnetd earlier... can you flash that, then?
[03:37] <minifozzy> can i use tcpdump to debug my iptables / dmz issue ?
[03:38] <nbd> you can try
[03:45] <malte> hm. yesterday everything worked okay, but as of today my wrt54g won't get an ip from my ISP
[03:46] <malte> when i connect directly to the adsl modem, however, i can run dhclient and get an ip
[03:46] <malte> when i connect directly with my workstation, that is
[03:47] <malte> is there no dhcp client in openwrt? how does it get its ip in the first place?
[03:49] <Ge0rG> malte: there is udhcp from busybox afaik
[03:49] <malte> okay, i'll try that. brb (need to disconnect to try it)
[03:50] <nbd> roam: ping
[03:53] <roam> nbd: pong
[03:54] <roam> nbd: yes I can try. Just send URL.
[03:57] <nbd> roam: http://openwrt.inf.fh-brs.de/~nbd/test/
[03:58] <Kaloz> nbd: any idea, why the embedded packages doesn't show up via ipkg status?
[03:58] <Kaloz> nbd: they used to
[03:59] <Kaloz> nbd: i mean everything works, the separately installed apckages appear up, and so on.
[03:59] <nbd> Kaloz: maybe the c-version of ipkg stores things differently
[03:59] <roam> nbd: Will try that later
[03:59] <Kaloz> nbd: no. it worked for me with the new version, too before
[03:59] <nbd> Kaloz: several people report that the telnet server doesn't get started in new builds
[04:00] <nbd> Kaloz: do you know why?
[04:00] <Kaloz> it works for me
[04:00] <Kaloz> BusyBox v1.00 (2005.05.20-14:12+0000) Built-in shell (ash)
[04:00] <Kaloz> so at least 2 days ago it worked
[04:02] <nbd> can you try a new build?
[04:03] <Kaloz> sure, ina few hours.. i have to get a server up and running today
[04:04] <nbd> k
[04:06] <Kaloz> yo wbx
[04:13] <wbx> Kaloz: i am cleaning up our linux dir for patches. and if this works, i update drivers to netgear gpl source
[04:14] <RItalMan> has anyone got the new 4.50.5 driver work ?
[04:14] <Kaloz> kay. but is suggest to do this in 2 steps :)
[04:16] <wbx> Kaloz: sure. first i cleanup, test the resulting images, commit, then do the update :}
[04:27] <minifozzy> is it safe to put iptables -t nat -A POSTROUTING -j MASQUERADE ?
[04:32] <wigyori> re
[04:38] <stupidkid> what interface use ipv6 people?
[04:38] <stupidkid> is it br0?
[04:39] <Piega`> what is the cheapest router for openwrt?
[04:41] <jopi> nbd: telnetd fails in official experimetnal version or in your current branch ?
[04:42] <jopi> I am coompiling official version for remote upgrading a wrt box 14k thousand km away
[04:42] <jopi> It would be a little problem if I can´t get in afeter upgrade
[04:42] <jopi> :(
[04:46] <synth> so you can run kismet on an active wlan interface?
[04:46] <synth> actively sniffing while running normal?
[04:46] <synth> (wrt54g)
[04:47] <AzzIzzA_> no
[04:47] <synth> someone said you could.. liars.
[04:47] <AzzIzzA_> kismet requires the card to be in monitor mode, so you cant transmit
[04:47] <synth> oh well i might as well just turn kismet on and leave it on
[04:48] <synth> i dont use the wireless these days..
[04:50] <nbd> jopi: in the official snapshot, it works, but the official snapshot has some other problems
[04:51] <nbd> jopi: better wait until it works with my build again
[04:55] <wbx> Piega`: wrt54g v2
[04:55] <Piega`> k
[04:55] <wbx> Piega`: but the differences are marginal
[04:55] <Piega`> tnx
[04:56] <stupidkid> ifconfig | grep -1 vlan1 | cut -s -d ' ' -f12 | grep addr | cut -d ':' -f2
[04:56] <stupidkid> can you help me get my ipaddress
[04:57] <stupidkid> i'm trying to write an ipv6 script and i need to strip that ipv4 out
[05:02] <wbx> stupidkid: paste the output of ifconfig anywhere
[05:03] <stupidkid> http://rafb.net/paste/results/CUu9My31.html
[05:05] <stupidkid> wbx, what interface it use for ipv6?
[05:05] <stupidkid> dev sit0?
[05:05] <wbx> depends on your setup.
[05:06] <stupidkid> it's default setup
[05:06] <wbx> stupidkid: you want to get your ipv4 address from vlan1?
[05:06] <stupidkid> yeah i got it
[05:06] <stupidkid> some guys in debian helped me out
[05:06] <stupidkid> now i just want to know which interface to use with ipv6
[05:06] <wbx> there is no ipv6 default included.
[05:07] <wbx> you need to install kmod-packages, and find a tunnel broker, if you do not have native ipv6
[05:08] <stupidkid> can i use native ipv6?
[05:08] <wbx> depends on your isp.
[05:08] <jopi> nbd: thx
[05:08] <stupidkid> i used to do that when i had no openwrt installed.
[05:08] <jopi> nbd: I assume, there´s a diff between official version and yours?
[05:08] <stupidkid> and it worked.
[05:08] <wbx> i have native ipv6 here at home. i only need to load the ipv6 modul..
[05:08] <wbx> jopi: a big diff.
[05:09] <jopi> i mean
[05:09] <stupidkid> wbx, can i pm you the script that i made?
[05:09] <jopi> a ".diff"
[05:09] <jopi> :P
[05:09] <wbx> stupidkid: i have no need for this script :}
[05:09] <wbx> jopi: use cvs diff :p
[05:09] <stupidkid> no?
[05:09] <stupidkid> can you help me set it up
[05:09] <jopi> ok, thanks
[05:09] <stupidkid> ?
[05:09] <jopi> I´ll wait, then
[05:10] <wbx> i have to go to election in nrw/germany first. bbl
[05:10] <stupidkid> ok, when you be back wbx?
[05:13] <nbd> wbx: i finally found an ebay powerseller that seems to sell orignal prolific datacables for siemens s55. i asked him to verify that this is really prolific
[05:14] <nbd> wbx: i'm thinking about buying some cables there, preparing them for use as serial console interfaces and then reselling them
[05:14] <stupidkid> ah, he gone :(
[05:14] <stupidkid> do you use ipv6 nbd?
[05:14] <nbd> no
[05:15] <stupidkid> oh
[05:16] <stupidkid> ipv6 on openwrt is hard
[05:16] <jopi> isn´t there a howto in openwrt page?
[05:17] Action: Ge0rG is using ipv6 without trouble
[05:18] <stupidkid> ah
[05:18] <stupidkid> Ge0rG, can ya help me using native ipv6?
[05:19] <stupidkid> this is the script that i wrote but it didn't work
[05:19] <stupidkid> #!/bin/sh
[05:19] <stupidkid> IPV4=$(ifconfig | grep -A1 vlan1 | grep inet | sed 's/.*addr://' | sed 's/ Bcast.*//')
[05:19] <stupidkid> ifconfig sit0 up
[05:19] <stupidkid> ipv6=$(ipv6 $IPV4)0000:0000/48
[05:19] <stupidkid> ifconfig br0 add $ipv6
[05:19] <stupidkid> ip -6 route add 2000::/3 via ::192.88.99.1 dev sit0
[05:19] <stupidkid> can ya help me fix it
[05:19] <stupidkid> ?
[05:20] <stupidkid> ifconfig sit0 add $ipv6 *
[05:21] <stupidkid> this is my ifconfig: http://rafb.net/paste/results/abIRhi11.html
[05:21] <Ge0rG> stupidkid: look with sh -x $script to see what exactly goes wrong
[05:21] <Ge0rG> gotta go now :/
[05:21] <stupidkid> man!!!!!
[05:22] <stupidkid> everybody gone
[05:22] <stupidkid> :(
[05:22] Action: stupidkid cries
[05:30] <Soopaman> hola
[05:31] <Soopaman> are there any tutorials for opening up/reading firmware images?
[05:32] <stupidkid> you installed openwrt?
[05:32] <wbx> nbd: nice idea. if i get a rabatt :}
[05:32] <stupidkid> hey
[05:33] <stupidkid> wbx you still there
[05:33] <stupidkid> lol
[05:33] <stupidkid> can ya help me please
[05:33] <Soopaman> stupidkid, nope, i'm trying to figure out a way into my router without jtagging
[05:33] <wbx> no. in the meantime i vote :p
[05:33] <stupidkid> c'mon wbx !!!
[05:36] <nbd> wbx: the guy sells the cables for EUR 1, shipping is EUR 4,90 for the first, plus EUR 1,50 for every other
[05:37] <wbx> 1,5 euro for every other. hmm.
[05:37] <wbx> nbd: why he does not chip 20 for 5,90 one package :}
[05:37] <nbd> so about 2,50 per cable, i think that's reasonable
[05:37] <nbd> i don't know
[05:37] <wbx> sure.
[05:38] <nbd> i hope that these cables really are prolific. when i get the reply, i'll order a few cables for testing
[05:39] <nbd> it's much cheaper than the other kits using max233
[05:39] <nbd> and usb is more common now than a real serial port
[05:41] <coob> wbx: if you need anyone to test anything on the wag54g v1, i've a spare one i can afford to brick
[05:42] <wbx> v1 is not linux. v2 is linux
[05:43] <wbx> nbd: yeah. test first.. not like the fucking nokia cables i have..
[05:43] <dionoea> anyone here have a decent howto concerning radius usage ? (with a freeradius howto)
[05:43] <dionoea> on openwrt of course :)
[05:44] <coob> wbx, that doesn't mean it can't run linux.
[05:44] <wbx> coob: but it would be very difficult, without boardspecific kernel code
[05:45] <wbx> coob: may be they even do not use ti chipset
[05:45] <coob> want me to crack it open and have a look?
[05:45] <wbx> it is your decision..
[05:46] <wbx> next week may be i hack on wag.. now i try to update wl/et drivers.. may be it will solveour asus wl500g issues.
[05:51] <dionoea> no radius howto then ? ... :(
[05:51] <dionoea> btw, what does "eth1: ignore i/f due to error(s)" mean when running nas ?
[05:54] <coob> wbx: i can't see any ti chips
[05:54] <wbx> make a picture with a digicam
[05:58] <coob> digicam's not around - i'll scan it
[06:10] <wbx> coob: uh. scanning a router?!
[06:12] <SiD3WiNDR> :))
[06:14] <nbd> wbx: well... if the datacable seller tells me it's prolific and it's not, then i can return the cables
[06:14] <nbd> wbx: that's why i ask first
[06:15] <nbd> wbx: at least the article picture has the word 'prolific' written on it
[06:25] <coob> wbx: sure why not :)
[06:34] <PolarWolf> root@lsrouter:~# cat /proc/sys/kernel/lowlatency
[06:34] <PolarWolf> 1
[06:34] <PolarWolf> hmm :P
[06:36] <coob> there's no ARM openwrt stuff is there
[06:36] <coob> cos this is arm heh
[06:37] <PolarWolf> Change all the compiler flags to produce arm :-)
[06:38] <coob> i have a little uclibc/arm experience
[06:38] <coob> mostly on the ipod
[06:50] <coob> wbx: http://booc.coob.org/wag54gv1/
[06:51] <wbx> coob: you see, totally different to wagv2
[06:54] <coob> yep
[06:54] <coob> i wonder why
[06:54] <coob> surely manufacturing is easier if you have one base board with modules
[07:07] <z3ro> hmm. I am still having trouble with the timers in the kernel for the wag54g...
[07:08] <z3ro> prom_printf works, but printk works very slowly... I guess prom_printf uses the bootloader and printk uses the kernel timers?
[07:12] <nbd> how exactly does the problem show?
[07:13] <nbd> maybe i can figure out something if you give me a more detailed description
[07:15] <z3ro> well, right now I am working with a clean kernel and checking each diff so I can make sure I applied everything required... so hopefully I'll find something.
[07:16] <z3ro> since prom_printf works perfect, and printk outputs very slowly I guess the problem is with the timing stuff in the kernel.
[07:16] <nbd> z3ro: so you think it's a problem with the serial driver?
[07:17] <z3ro> nbd: well, it could be... but I think it's the timers. when it gets to "calculating r4koff" it just hangs there - no crash, but just sits there doing nothing.
[07:18] <nbd> z3ro: and before that like it outputs stuff quickly?
[07:18] <nbd> s/like/line/
[07:19] <z3ro> nbd: no, it outputs "linux started" (that uses prom_printf) then after that, everything else is slow.
[07:19] <z3ro> but prom_printf uses the bootloader (yamon/adam2) to print stuff, afaik.
[07:21] <nbd> really think you should try 2.4.30. we don't know what fixes went into the montavista kernel... but some of that stuff probably went into newer 2.4 versions as well
[07:22] <z3ro> nbd: you mean start with 2.4.30 instead of 2.4.17?
[07:22] <nbd> maybe yes
[07:23] <nbd> it's probably best to start from a fully patched openwrt kernel
[07:23] <z3ro> hmm, I guess there would not be any huge changes from 2.4.17->2.4.30, so that should be okay.
[07:38] <teemu_> mmm
[07:38] <teemu_> is there good network/internet traffic monitor for openwrt
[07:39] <teemu_> that would show network traffic per lan ip
[07:39] <ralf> z3ro: hi
[07:39] <ralf> wrt: SHUT UP!
[07:39] <nbd> ralf: no use talking to a bot
[07:39] <ralf> z3ro: how uptime is calculated?
[07:40] <ralf> from jiffies?
[07:40] <iggy> believe so
[07:40] <z3ro> I'm not really sure... I have never looked into that.
[07:40] <ralf> and the kernel store jiffies into some variable?
[07:41] <ralf> if i set that variable to something else what will happen?
[07:41] <iggy> it'll change jiffies
[07:42] <ralf> hehe
[07:42] <nbd> from kernel/info.c: val.uptime = jiffies / HZ;
[07:42] <ralf> but will happen some disaster?
[07:42] <iggy> btw, jiffies is the name of the value
[07:42] <iggy> ralf: nothing spectacular will happen
[07:42] <Soopaman> are there any tutorials for opening up/reading firmware images? i'm trying to figure out a way into my router without jtagging
[07:42] <nbd> Soopaman: what router, what firmware?
[07:42] <iggy> people used to change it with kernel modules to test the wrapping/etc when they moved to 64bit jiffies
[07:44] <ralf> and the variable is named jiffie?
[07:45] <ralf> i can just do jiffies = X ?
[07:45] <iggy> from nbd's snippet above, yes
[07:46] <ralf> ok, thanks
[07:46] <iggy> I don't know if it's that simple, you can probably find someone's code to do it online
[07:48] <coob> took*
[07:48] <coob> z3ro: http://booc.coob.org/wag54gv1/
[07:48] <z3ro> coob: wag54gv1 does not run linux.
[07:48] <coob> i know
[07:48] <z3ro> v2 does.
[07:48] <coob> i was just wondering if there were major hardware differences, it seems so - v2 is mips right?
[07:49] <z3ro> oh, lol, when you said "images" I thought you meant firmware images. :p
[07:49] <coob> hah
[07:49] <z3ro> yes, v2 is mips.
[07:49] <z3ro> I have no idea what v1 is though.
[07:49] <coob> arm
[07:50] <coob> http://booc.coob.org/wag54gv1/wag54gv1-front.jpg <-- big arm720 :)
[07:50] <stupidkid> hey what interface we use for ipv6?
[07:50] <z3ro> hmm... well, it might be possible to get linux running on it, but you'd be starting from scratch: without a linksys reference tarball.
[07:50] <coob> yep :/
[07:51] <coob> z3ro: i know someone who's done that before (on the ipod, which uses an arm7tdmi), but he's a hardcore reverse engineer :/
[07:51] <z3ro> coob: yeah. It's *much* easier when you have at least something to start from.
[07:52] <coob> the wag54gv1 firmware is horridd, port forwards would stop working for no reason, and the dsl stuff would only connect at half the speed it should've :/
[07:53] <nbd> vxworks?
[07:53] <coob> yep
[07:54] <nbd> hmm
[07:57] <z3ro> *sigh* why didn't I find thie before: http://www.linux-mips.org/wiki/index.php/Porting :p
[07:57] <z3ro> *this
[07:58] <coob> have you got the kernel loading?
[07:58] <z3ro> coob: not yet
[07:58] <coob> which bootloader does the linksys stuff use?
[07:59] <z3ro> the wag54g uses adam2, the others either cfe or pmon.
[08:01] <coob> ah yes i think my dlink uses that :/
[08:02] <Eagle__Fire> lol, ksilebo got owned
[08:03] <chaimj> anyone got these messages ? : MASQUERADE: Route sent us somewhere else
[08:04] <coob> z3ro: is the wag54gv2 based around the TI AR7?
[08:04] <z3ro> coob: yes
[08:04] <ralf> as i touched jiffies the kernel crashed
[08:05] <coob> maybe looking at some dlink source may help you then
[08:06] <z3ro> coob: yeah, I have a few archives I'm using as reference.
[08:06] <coob> ftp://ftp.dlink.co.uk/dsl_routers_modems/dsl-300t/gpl_source_code/DSL-300T.B01T16_GPL_release.tgz
[08:07] <coob> http://www.google.com/translate?u=http%3A%2F%2Fwww.webalice.it%2Fandrea.usenet%2Fdsl-302t.htm&langpair=it%7Cen&hl=en&ie=UTF8
[08:07] <z3ro> 300t? hmm, I have not seen that one before.
[08:07] <coob> if you can work through the machine translation :)
[08:07] <coob> yeah it's not a router perse
[08:07] <z3ro> it it based on the ar7?
[08:07] <z3ro> *is
[08:07] <coob> yep
[08:07] <coob> not wireless
[08:08] <coob> just a box with power, ethernet and adsl
[08:08] <coob> more of a modem
[08:08] <ralf> good
[08:08] <ralf> it is what i'm looking for
[08:08] <ralf> coob: he name? :)
[08:08] <ralf> *the
[08:08] <coob> dlink dsl-300t (in the uk anyway)
[08:08] <ralf> linux inside?
[08:08] <z3ro> coob: I'll wget it after the linux_2_4_30 checkout is done.
[08:09] <ralf> coder: lol, i was reading the link you pasted
[08:09] <storchi> can somebody help me with my ad hoc network?
[08:09] <ralf> the 2°
[08:10] <ralf> after i have read all i noticed that
[08:10] <ralf> it was translated from italian
[08:10] Action: ralf is italian
[08:10] <coder> which link? can't remember
[08:10] <ralf> http://www.google.com/translate?u=http%3A%2F%2Fwww.webalice.it%2Fandrea.usenet%2Fdsl-302t.htm&langpair=it%7Cen&hl=en&ie=UTF8
[08:11] Action: coob not coder
[08:11] <coob> http://www.webalice.it/andrea.usenet/dsl-302t.htm
[08:11] <stupidkid> can someone help me with ipv6 problem
[08:11] <coder> I did not paste that
[08:12] <storchi> my ad hoc network falls back to 802.11b - rates and propagate it to other nodes
[08:12] <coob> hmm i lagged out there i think
[08:13] <ralf> coob: i know that modem
[08:13] <ralf> is the one that tin ships with the adsl line
[08:14] <ralf> is black?
[08:14] <coob> mine is gray
[08:14] <ralf> mm
[08:14] <coob> http://www.dlink.co.in/dlink/Products/broadband/imagesbroadband/dsl302t.jpg
[08:14] <coob> like that
[08:15] <ralf> it seems like tin has changhed the outside
[08:15] <ralf> our 300t are black
[08:15] <ralf> but there is busybox inside
[08:15] <coob> yep
[08:15] <ralf> so i guess there is even linux
[08:15] <coob> of course, i pasted the link to the src
[08:15] <ralf> btw our 300t are locked
[08:15] <coob> locked?
[08:15] <coob> Connected to 192.168.1.1.
[08:15] <coob> Escape character is '^]'.
[08:15] <coob> login: root
[08:15] <coob> Password:
[08:15] <ralf> we have only a page from the web interface
[08:16] <coob> BusyBox v0.61.pre (2004.06.18-02:49+0000) Built-in shell (ash)
[08:16] <ralf> yes
[08:16] <ralf> no root password
[08:16] <teemu_> ;
[08:16] <teemu_> ;I
[08:16] <ralf> btw hacking the firmware and editing /etc/pawwsd
[08:16] <teemu_> what kind network bandwidth statistic you use on your openwrt?
[08:16] <ralf> with the same pass as user
[08:16] <ralf> will unlock it
[08:22] <chaimj> should vlan1 be removed after installation ?
[08:25] <nettie> hey z3ro how's going?
[08:26] <nettie> any of you guys is using the wireless isolation feature of the latest wl.o please?
[08:30] <storchi> my ad hoc network runs after a while only in 802.11b rates, why?
[08:30] <frop> re
[08:31] <z3ro> nettie: hi
[08:32] <nettie> z3ro: hey z3ro I noticed you found interesting porting infos ;)
[08:32] <z3ro> yeah :)
[08:32] <z3ro> it should help a lot.
[08:32] <nettie> sounds cool
[08:34] <nettie> does wbx sorted out the cable problem os he's still stucked?
[08:34] <nettie> os=or
[08:34] <z3ro> nettie: I don't know.
[08:34] <nbd> i think he doesn't have a working cable yet
[08:34] <nettie> ouc
[08:34] <nettie> ouch
[08:34] <nettie> I think I'll build one for him
[08:34] <nettie> this week
[08:37] <nbd> i'll order some cables the next days. trying to get original prolific-based siemens s55 cables
[08:37] <nbd> i think i found someone who sells these things, i just need to verify
[08:39] <Eagle__Fire> i use the Nokia 3595 cables, they're prolific-based
[08:39] <Eagle__Fire> at least the manufacturing run i got mine from
[08:40] <Eagle__Fire> green packaging, small rectangular black case
[08:40] <wbx> i get a cable on tuesday...
[08:41] <Eagle_Fire> woot woot
[08:41] <z3ro> :)
[08:41] <wbx> more specific, a friend of mine will solder my max3233
[08:41] <Eagle_Fire> heh
[08:41] <wbx> s/3$/2/
[08:42] <Eagle_Fire> is so much easier to get a usb cable instead
[08:42] <Eagle_Fire> it does the voltage conversions inhouse, only 3 wires to solder
[08:42] <z3ro> Eagle_Fire: I thought the usb phone cables did not work?
[08:42] <wbx> tse. not for me. ordered 3 unsupported nokia cables..
[08:42] <z3ro> only serial worked?
[08:42] <Eagle_Fire> well
[08:42] <Eagle_Fire> you need a usb serial phone cable
[08:43] <Eagle_Fire> like for the Nokia 3595/6010
[08:43] <Eagle_Fire> they have a serial protocol so the usb data cables have usb-serial converters in them
[08:43] <Eagle_Fire> wbx, what ones did you try
[08:44] <z3ro> Eagle_Fire: and these nokia usb cables have a linux driver?
[08:44] <z3ro> so it works just like a normal /dev/ttyS*
[08:44] <Eagle_Fire> no idea
[08:44] <wbx> for nokia 6310
[08:44] <Eagle_Fire> i sent mbm the same one as i have, and he didn't have any issues getting it to linux correctly
[08:44] <Eagle_Fire> but i can tell you it works great with windows
[08:45] <z3ro> Eagle_Fire: well, I can't get a "real" nokia cable, but I can get this: http://www.dse.co.nz/cgi-bin/dse.storefront/4290b752052e0ce8273fc0a87f9906e7/Product/View/E3014
[08:45] <z3ro> problem is, I don't know if it's going to work.
[08:46] <wbx> may be it will work with windows.. there is a driver cd. but i have no windows
[08:46] <Eagle_Fire> z3ro: it won't work
[08:46] <Eagle_Fire> i think the discriminating factor is whether there's a PCB inline
[08:46] <Eagle_Fire> so some blackbox in the center of the cable
[08:46] <Eagle_Fire> this one looks like a straightthrough
[08:47] <z3ro> I see.
[08:47] <z3ro> any other brands that work?
[08:47] <Eagle_Fire> http://www.daydeal.com/product.php?productid=2211
[08:47] <kshatriya> hey all :)
[08:48] <Eagle_Fire> if that picture is accurate, it is *the* cable that mbm and i have
[08:48] <kshatriya> i have a question, i wonder if it is possible to get a message in syslog when a client logs on to my wireless network ... (not via dhcp, just when it gets authenticated on the accesspoint)
[08:49] <wbx> nbd will buy 2000 working cables next week ;)
[08:49] <Eagle_Fire> kshatriya, you can write a script that reads the associated list and makes messages when it changes
[08:49] <Eagle_Fire> 2000? damn
[08:49] <Eagle_Fire> why so many
[08:50] <wbx> he want to sell them and get rich ;)
[08:50] <kshatriya> Eagle_Fire: that's a good idea
[08:50] <Eagle_Fire> cool
[08:50] <Eagle_Fire> ...where is he getting them
[08:50] <kshatriya> :)
[08:50] <wbx> top secret.
[08:51] <Eagle_Fire> i hope it's for cheap
[08:51] <kshatriya> any idea where i can get the associated list ? with iwconfig ?
[08:51] <Eagle_Fire> kshatriya, with the wl utility
[08:51] <Stereo> he'll sell a dozen and end up with a crateful of them :)
[08:51] <Eagle_Fire> "wl assoclist"
[08:51] <Ksilebo> Hi.
[08:51] <kshatriya> aha, great!
[08:51] <kshatriya> i'm going to start making that script right away :)
[08:53] <Eagle_Fire> i don't suppose busybox has a diff tool
[08:53] <RItalMan> yes it got
[08:53] <Eagle_Fire> built into openwrt though?
[08:53] <RItalMan> but needs to be configured at build time
[08:54] <RItalMan> not enable by default
[08:54] <Eagle_Fire> wonder how a script would diff the assoclist then
[08:54] <Stereo> kshatriya: the arpwatch utility might be what you are looking for
[08:54] <Eagle_Fire> nevermind, a nested for loop would probably work
[08:54] <Stereo> it's a package that watches for new MACs and mails them to you
[08:55] <RItalMan> Eagle_Fire: what do you expect from assoclist ?
[08:55] <Eagle_Fire> but what if the person doesn't send any arp/
[08:55] <kshatriya> Ah, that's interesting as well
[08:55] <Eagle_Fire> a list of associated MACs
[08:55] <RItalMan> ok, and wl assoclist is not enough ?
[08:55] <Eagle_Fire> in the form "assoclist xx:xx:xx:xx:xx:xx"
[08:55] <Eagle_Fire> one line per client
[08:55] <Eagle_Fire> well that gives you a "what's on right now" list
[08:56] <RItalMan> yes
[08:56] <Eagle_Fire> what you'd want is a diff saying "Client xx:xxetc associated"
[08:56] <RItalMan> playing with sed and awk is great for that
[08:57] <Eagle_Fire> i was thinking nested for loops in a shell script
[08:57] <RItalMan> yes that would be ok
[08:57] <Eagle_Fire> but do let us see it when it's done
[08:59] <nbd> wbx: what are you telling people about me? :)
[08:59] <nbd> wbx: you aren't supposed to let anyone know about the 2000 cables :P
[09:00] <Eagle_Fire> lolz
[09:00] <wbx> nbd: shit *g*
[09:00] <Eagle_Fire> i bet they're stolen
[09:00] <wbx> i can not keep any secrets.
[09:00] <Eagle_Fire> that'll teach you to confide in people, nbd
[09:00] <nbd> i guess so
[09:01] <nbd> and then he even tells everyone that i want to use that plan to get rich *sigh*
[09:01] <Eagle_Fire> the true path to getting rich never lies in a single plan
[09:02] <Eagle_Fire> you need a series of plans, each more expensive to start than the first
[09:02] <stupidkid> hey
[09:02] <stupidkid> can someone help me with ipv6? 6to4
[09:02] <Eagle_Fire> we don't like ipv6 here
[09:02] <stupidkid> openwrt is not supported?
[09:03] <Eagle_Fire> no, ipv6 can work in openwrt
[09:03] <stupidkid> i tried everything
[09:03] <Eagle_Fire> we just find that ipv6 is pointless
[09:03] <stupidkid> :D
[09:03] <stupidkid> it's cool
[09:03] <wbx> it is useless. nobody use it.
[09:04] <stupidkid> oh
[09:04] <RItalMan> stupidkid: what is your pb with ipv6 ?
[09:04] <stupidkid> i couldnt get it to work
[09:04] <Eagle_Fire> it's in one of those chicken-and-egg causality loops
[09:04] <stupidkid> lolz
[09:04] <nettie> wireless isolation works ;)
[09:04] <Eagle_Fire> woot
[09:05] <nettie> pretty easy just change wl0_ap_isolate to 1 and restart the wifi interface :)
[09:05] <stupidkid> Starting ipv6 (2002:18b1:347c)Error: either "local" is duplicate, or "via" is a garbage.
[09:05] <stupidkid> IP6NET=2002:$(printf "%02x%02x:%02x%02x" `echo $IP | sed 's/\./ /g'`)
[09:06] <stupidkid> echo -n "$(IP6NET)"
[09:06] <stupidkid> echo -n "Starting ipv6 (${IP6NET})"
[09:06] <Eagle_Fire> nettie: was that in the wiki?
[09:06] <stupidkid> IP=$(ifconfig | grep -A1 vlan1 | grep inet | sed 's/.*addr://' | sed 's/ Bcast.*//')
[09:06] <stupidkid> do you know what's wrong?
[09:06] <stupidkid> it says Error: either "local" is duplicate, or "via" is a garbage.
[09:06] <RItalMan> stupidkid: what kind of connectivity would you like to implement ? using a tunnel broker ? native IPv6 on wan iface ?
[09:06] <stupidkid> native IPv6 on wan iface
[09:06] <nettie> not sure, I'll check and if it's not there add it ;)
[09:07] <phedny> basically, the ipv6 address is invalid ;)
[09:07] <phedny> there should be 8 sections seperated by a colon, not three
[09:07] <stupidkid> RItalMan: can you help me with native ipv6 on wan iface
[09:07] <phedny> or you should include a dubble colon ;)
[09:07] <RItalMan> ok cool stupidkid that is far easier :)
[09:08] <stupidkid> wow
[09:08] <stupidkid> :D
[09:08] <RItalMan> have you got your lan/wifi separated ?
[09:09] <stupidkid> i dont have wifi
[09:12] <stupidkid> RItalMan, http://rafb.net/paste/results/o6dnA745.html
[09:12] <stupidkid> that what i had so far
[09:15] <RItalMan> ok so the interface advertising IPv6 should be vlan0 instead of eth0
[09:15] <stupidkid> oh
[09:15] <RItalMan> same thing for the ipv6 address assignation to eth0
[09:16] <RItalMan> then, there is a mistake in you line :
[09:16] <RItalMan> replace line 18 by :
[09:16] <RItalMan> ip -6 addr add ${IP6NET}::/64 dev eth0
[09:16] <RItalMan> ip -6 addr add ${IP6NET}::1/64 dev eth0
[09:16] <RItalMan> this is a "known" bug
[09:17] <RItalMan> finally add the following route
[09:17] <stupidkid> fix only 2 lines?
[09:17] <RItalMan> just another one
[09:17] <RItalMan> again and it should work
[09:18] <RItalMan> ip route add ::/0 dev sit0
[09:20] <stupidkid> http://rafb.net/paste/results/iOl70L27.html?
[09:20] <stupidkid> is that all?
[09:20] <stupidkid> Starting ipv6 (2002:18b1:347c)Error: either "local" is duplicate, or "via" is a garbage.
[09:21] <RItalMan> ok there is an error fetching your IPv6 prefix
[09:23] <RItalMan> printf is not available on the wrt
[09:23] <stupidkid> oh
[09:26] <stupidkid> RItalMan, how can i fix that
[10:03] <acce|> hey anyone experienced with kismet on a wrt54g?
[10:05] <stupidkid> RItalMan is back! :)
[10:07] <RItalMan> yeah :)
[10:36] <Soopaman> nbd, if you're still there, Ovislink WMU-9000VPN router
[11:15] <acce|> anyone experience a problem when they try to run 'wl disassoc' on their wrt54g and it gives and error for ifconfig eth1: invalid arguement..
[11:19] <mac|gyver> should the boot_wait setting be "on" or "yes"?
[11:24] <wbx> mac|gyver: on.
[11:25] <J4k3> boot_wait="mmhmm"
[11:25] <mac|gyver> hmm
[11:25] <mac|gyver> it doesn't seem to be working though :(
[11:33] <mac|gyver> another question, when I upgrade to the experimental build, which settings can I expect to survive, and which don't?
[11:46] <Soopaman> it's an Ovislink WMU-9000VPN router
[11:48] <Soopaman> any ideas?
[11:48] <inh> well is it compatible with openwrt?
[11:49] <wbx> Soopaman: you could try to modify existing firmware images.
[11:50] <wbx> Soopaman: is there any source open ?
[11:50] <jopi> wbx: no it isn´t
[11:50] <jopi> they say it is
[11:50] <mac|gyver> does anyone know what gentoo tftp client works? :)
[11:50] <jopi> but is only an archive with vanilla kernel sources, zebra and iptables
[11:51] <jopi> mac|gyver: in debian, I use atftp
[11:51] <mac|gyver> that segfaults for some reason
[11:51] <Soopaman> wbx, that's what i am hoping
[11:51] <geoman> mac|gyver: use tftp-hpa
[11:51] <mac|gyver> geoman: ty
[11:51] <geoman> mac|gyver: works just fine
[11:52] <geoman> mac|gyver: although none of the gentoo tftp clients should segfault like that...did you rice out your CFLAGS or something?
[11:52] <mac|gyver> no, run amd64
[11:52] <Soopaman> wbx, they have some open source, but it's no good
[11:52] <mac|gyver> but than that shouldn't happen either
[11:52] <mac|gyver> anyhow, I might be gone for a while :)
[11:53] <mac|gyver> oh one more thing, squashfs or jjfs?
[11:53] <Soopaman> squash isn't persistant, jffs is
[11:54] <mac|gyver> the non-experimental used jjfs right?
[11:54] <Soopaman> i'd assume it used squash for the root, and jffs for the config
[11:55] <mac|gyver> hmm ic
[11:55] <mac|gyver> but what's the best package to upload?
[11:56] <mac|gyver> ie, whats the difference between openwrt-*-squashfs.bin and openwrt-*-jjfs2.bin
[11:57] <Soopaman> wbx, any idea?
[12:02] <PolarWolf> mac|gyver: Uhm, hmm, lessee...maybe, uhm, one image uses the jffs2 filesystem and the other uses squashfs? I dunno, it's just a wild guess.
[12:02] <mac|gyver> yeah thats what I'd guess
[12:03] <PolarWolf> Try squashfs, it's what seems to be the future. Don't forget to run firstboot after flashing.
[12:03] <mac|gyver> uhm, but that's not persistant?
[12:03] <CptObvious> So um.. How's that website doing?
[12:03] <mac|gyver> so where would I store my firewall settings for example?
[12:03] <PolarWolf> mac|gyver: It's not?
[12:04] <mac|gyver> squashfs is read-only
[12:04] <CptObvious> Anyone know what's the story with the openwrt.org website? It seems to be down.
[12:05] <mac|gyver> CptObvious: it is
[12:05] <PolarWolf> mac|gyver: Oh, it looks like jffs2 is still used for the writeable parts, squashfs for /rom
[12:05] <PolarWolf> CptObvious: Again?
[12:05] <CptObvious> I guess... I didn't know it was before. Not responding at all.
[12:05] <mac|gyver> PolarWolf: so squashfs is the mixed thing, and jjfs2 is the old way around?
[12:05] <PolarWolf> mac|gyver: Looks like it
[12:05] <z3ro> openwrt.org is working for me.
[12:05] <mac|gyver> I'll try squashfs then
[12:06] <PolarWolf> z3ro: Make sure it's not a cached copy
[12:06] <baffled> not here it isn't.
[12:06] <PolarWolf> It seems dead as a brick
[12:06] <CptObvious> Somebody bricked the website?? :)
[12:06] <baffled> they broke it.
[12:06] <z3ro> PolarWolf: it's not cached.
[12:06] <PolarWolf> Maybe it runs off an experimental CVS build of openwrt
[12:06] <J4k3> openwrt's website will go down constantly until its hosted somewhere that doesn't all-out suck
[12:06] <J4k3> but mbm says thats impossible, so...
[12:06] <CptObvious> I've had excellent luck with my experimental build...
[12:07] <CptObvious> What's the bandwidth needs for the site??
[12:07] <PolarWolf> J4k3: Oh, he needs hosting?
[12:07] <J4k3> PolarWolf: its already been offered.
[12:07] <PolarWolf> Takes like 10 minutes to arrange
[12:07] <J4k3> he doesn't want to move it, and apparently it'd just be *impossible* to mirror (excuses excuses)
[12:07] <J4k3> so here we are
[12:07] <J4k3> with (effectively) no website.
[12:07] <PolarWolf> cp /etc/apache/vhosts/template /etc/apache/vhosts/openwrt.org
[12:08] <PolarWolf> He probably wants root access or somewhat
[12:08] <baffled> Could someone tell me how to change the lan ip range to be 10.10.10.xx from 192.168.1.xx?
[12:09] <PolarWolf> baffled: fiddle with the lan_ nvram variables
[12:09] <CptObvious> Alright then.. I would have offered, depending on bandwidth needs... But I'm a reseller as it is, so I can't quite offer root.
[12:09] <J4k3> if you don't own your box, you're not in the business.
[12:09] <wbx> no, i even suggested mbm a free root server..
[12:10] <J4k3> you're just the internet's equivilent of the order taker at McDonalds.
[12:10] <baffled> I was looking at them but didn't see any base address range that I recall.
[12:10] <CptObvious> j43k: donated space is donated space...
[12:10] <PolarWolf> I rent a colo box in an MCI datacenter in norway
[12:10] Action: J4k3 shrugs
[12:10] <teemu_> is there any good network statistic program
[12:11] <J4k3> as far as mbm's reaction - if we want a better/stable website, we get to make it
[12:11] <PolarWolf> teemu_: Depends on the amount of detail you want
[12:11] <PolarWolf> J4k3: Pff
[12:11] <CptObvious> Is it the website's problem, or a hosting issue?
[12:11] <J4k3> as mbm's site apparently will be stuck on this 90% uptime webhosting....
[12:11] <teemu_> PolarWolf: how much traffic per ip
[12:11] <teemu_> up and down
[12:11] <teemu_> and then total how much moved over internet
[12:11] <PolarWolf> teemu_: Custom log rules with iptables
[12:11] <CptObvious> teemu_: Can IP Chain's counters do what you need?
[12:11] <J4k3> the problem is mbm isn't interested in moving the site. the offer has been made in the past.
[12:12] <CptObvious> er, iptables
[12:12] <teemu_> mm
[12:12] <PolarWolf> teemu_: performance hit in action though
[12:12] <PolarWolf> J4k3: I talked to him about it before, it indeed seems a bit hard
[12:12] <CptObvious> It's just that Sunday, my day to work on fun projects like WRT gets bogged down with outages.... Not the best way to go..
[12:13] <PolarWolf> J4k3: I have a feeling there's more to it than just reluctance
[12:13] <teemu_> err
[12:13] <bone_idol> baffled: you mean the dhcp client range ?
[12:13] <CptObvious> OK.. Thanks for the info all.
[12:13] <bone_idol> baffled: look at /etc/dnsmasq.conf
[12:13] <J4k3> PolarWolf: *Shrug* end result is the crap is down for a few hours a day
[12:13] <PolarWolf> J4k3: Aye
[12:13] <teemu_> iptables, can I made it somehow automatic, I mean if someof mu friend comes and uses my wlan, it would automatically log he's traffic
[12:13] <J4k3> PolarWolf: hence my suggestion of a second website
[12:13] <J4k3> plus... some real docs would be great
[12:13] <J4k3> I really hate wiki's
[12:13] <J4k3> wiki = your complete source of incorrect and incomplete information
[12:14] <PolarWolf> J4k3: I suggested mirroring it too. Even the forum with some smart database tricks.
[12:14] <J4k3> yeah, it wouldn't be hard
[12:15] <PolarWolf> Oh well.
[12:15] <baffled> thanks bone_idol I'll check it out.
[12:16] <PolarWolf> Nothing keeps anyone from keeping a set of openwrt documentation. The wiki may suck at various levels but it's the best we have until someone feels like writing new stuff.
[12:16] <ralf> why if i set jiffies to something my kernel dies?
[12:16] <J4k3> IMHO the wiki's existance reduces that chance of anyone bothering to make real documentation
[12:18] <PolarWolf> J4k3: Feel creative? :-)
[12:18] <baffled> Okay, can anyone tell me how to switch from managed mode to ad-hoc mode on the wireless interface?
[12:18] <PolarWolf> Start typing
[12:18] <inh> hmmmmm
[12:19] <inh> well if i knew anyhting about using openwrt then id ponder writing some dos
[12:19] <inh> *dos
[12:19] <inh> docs
[12:19] <inh> stupid c key
[12:20] <inh> ah much better. had a cookie crumb under there
[12:20] <wbx> what would be a good format for docs? tex handbook?
[12:20] <inh> just normal text
[12:20] <PolarWolf> wbx: docbook-xml, I'd say
[12:20] <PolarWolf> You can get from there to anything else
[12:21] <inh> docbook-xml?
[12:21] <PolarWolf> And there's pretty editors which support it
[12:21] <wbx> hmm.. i hate sgml stuff :}
[12:21] <PolarWolf> Yeah, the XML version of docbook
[12:21] <inh> never even heard of that... *googles*
[12:21] <inh> wbx, are you gonna start writing docs?
[12:21] <PolarWolf> wbx: No need to touch it. just use a decent editor which is able to think in "section" and "paragraph" and stuff
[12:21] <wbx> dunno. i do not like the existing wiki and structure
[12:22] <wbx> i will not change my editor :}
[12:22] <wbx> i like vim.
[12:22] <inh> i know
[12:22] <inh> i hate the wiki too
[12:22] <inh> i get chewed out daily for asking questions whos answeres are on the wiki
[12:23] <inh> is docbook windows only?
[12:23] <PolarWolf> inh: Hell no
[12:23] <PolarWolf> Besides, stuff on the wiki doesn't apply anymore
[12:24] <PolarWolf> like "No matter how you uploaded the firmware, the router reboots automatically and runs a script called "firstboot" to do some initialization."
[12:24] <wbx> we need better docs.
[12:24] <PolarWolf> No it doesn't, it needs to be run by hand, as in the old days...for squashfs anyways
[12:25] <PolarWolf> That's a bit of information I had to glean from IRC logs of all places
[12:25] <z3ro> wbx: if your looking for a doc format, then checkout the format used for the gentoo docs.
[12:25] <wbx> z3ro: what they use?
[12:25] <z3ro> it's pretty simple, xml based, but nice and simple.
[12:25] <PolarWolf> Typically Gentoo, they probably reinvented the wheel for that too
[12:25] <wbx> i like tex, because it generates pdf or txt
[12:26] <PolarWolf> docbook is the defacto standard for technical documentation, developed over the course of several years. But alas, there are projects which severely suffer from the "not invented here" syndrom.
[12:27] <inh> hrm
[12:27] <inh> well im gonna look into docbook
[12:27] <wbx> you ever wrote a techincal documentation with docbook?
[12:27] <PolarWolf> wbx: Sure
[12:27] <inh> at the very least, i can write a quick primer on linux for newbs
[12:27] <wbx> how many pages?
[12:28] <PolarWolf> wbx: http://www.linuxops.net/ipsec/articles.php
[12:28] <wbx> i hate docbook. the tools to generate output sucks.
[12:28] <PolarWolf> wbx: Those are all derived from docbook sources
[12:30] <wbx> PolarWolf: do you have the source for this article? which tool i need to generate the html output?
[12:30] <PolarWolf> wbx: docbook2html :-)
[12:31] <inh> hehe
[12:31] <PolarWolf> I had to modify the resulting html a bit to make it unsuck with the CMS, it produces standalone html pages by default
[12:31] <inh> well im goin to subway
[12:31] <PolarWolf> Need to modify the xslt
[12:31] <inh> then i'll ponder an linux primer
[12:32] <wbx> hmm. i do not want to change anything to get a good result :p
[12:32] <inh> and probably ask an assload of annyoing questions, but then it will be the only time i need to ask them
[12:32] <PolarWolf> wbx: Then you only get the bog standard templates. If that suits you, fine :P
[12:33] <PolarWolf> The good thing about docbook-xml is that every xslt engine is able to transform it into anything you want, really
[12:33] <PolarWolf> Even binary formats if you got the FO's for it
[12:33] <wbx> that is one of the reason i dislike docbook
[12:33] <wbx> but last time i used it, is 4 years ago :}
[12:33] <PolarWolf> wbx: It changed :P
[12:34] <wbx> emacs, sgml mode *g*
[12:34] <PolarWolf> Anyway, I like docbook. Never was able to deal with latex, really
[12:34] <inh> i love latex
[12:34] <inh> especially on women
[12:34] <PolarWolf> I'm sure it has its charmes
[12:35] <inh> PolarWolf, where can i get docbook from? for linux
[12:36] <PolarWolf> inh: it's a format specification, it's not really something you install
[12:36] <PolarWolf> You install templates, transformers, editors, etc
[12:36] <PolarWolf> you *write* docbook
[12:36] <inh> uh huh.... hrm
[12:36] <wbx> inh: it is complicated.
[12:37] <PolarWolf> A good editor will help you
[12:37] <PolarWolf> I like XMLMind for it
[12:37] <_alejandro> I prefer latex than docbook. :)
[12:37] <PolarWolf> Though I now use Vex since it's OSS :-)
[12:37] <_alejandro> anyway both are not hard to learn.
[12:37] <inh> ah i see
[12:38] <PolarWolf> I need to benchmark the performance of my router again, hmm
[12:40] <inh> hmmm
[12:41] <inh> docbook article, or docbook part...?
[12:41] <inh> im thinking part.. so it can all be thrown together into one big doc later on...
[12:43] <caldari> can someone plz tell me what excactly boot_wait does ? what will happen if i turn it on ?
[12:43] <PolarWolf> caldari: It will make your router wait for a few seconds for tftp uploads
[12:43] <PolarWolf> caldari: enable it
[12:43] <wbx> we should start with plain text. anyone will convert it later. send me content :p
[12:43] <inh> wbx, start grabbing from the wiki
[12:44] <inh> im goin docbook format
[12:44] <Soopaman> wbx, any ideas on opening/reading firmwares?
[12:44] <inh> it sounds like a sane idea
[12:44] <caldari> PolarWolf if there is no tftp upload, will timeout and boot normaly ?
[12:44] <PolarWolf> caldari: yeah
[12:44] <caldari> ty :)
[12:45] <PolarWolf> caldari: You want it in case something b0rks and you need to recover...or even upload a different firmware as an upgrade
[12:45] <inh> yup
[12:45] <Death_INC> otherwise, you need to make a jtag interface or short pins (which is really nasty)
[12:46] <inh> take it from Death_INC he knows ;)
[12:46] <caldari> i want to move from hyperwrt to openwrt (and the experimental one cause i have the wrt54g v3)
[12:46] <Dabian> Death_INC: Short pins means to solder a lice on the board?
[12:48] Action: inh writes a linux primer
[12:49] <Dabian> Death_INC: I'm not english native tongue.
[12:52] <z3ro> Dabian: short pins means to "connect the pins together" so they are electrically connected.
[12:52] <Dabian> z3ro: Ahh .. thats what I thought .. isn't that called a lice also?
[12:53] <Dabian> Or is that a danish speciality?
[12:53] <z3ro> you are better off using jtag though, as Death_INC said: it's a nasty solution.
[12:53] <z3ro> Dabian: I think that might be a danish specific word.
[12:53] <Dabian> ok
[12:54] <Dabian> z3ro: When I first read about it, I thought "Why cut the legs shorter, to insert the chip halfway and then later push it all the way?"
[12:55] <frop> re
[12:56] <frop> ...as i've to buy a PCI eth card...have you got suggestion?
[12:56] <wbx> Soopaman: binary firmware files? sure.
[12:56] <inh> PolarWolf, since you have docbook exp. how would you suggest doing the openwrt docs? as individual articles, or as 'parts' so they can all be made into one big doc?
[12:57] <Dabian> z3ro: s/legs/pins/
[12:57] <Soopaman> wbx, what plan of attack would you suggest?
[13:00] <Dabian> ok .. I try this question before I go to bed:
[13:00] <Dabian> WL-500gd: I have connected my wan-port to the DMZ hub, the Lan3 port to my local switch. I can telnet to the wl-500gd from the local net. How can I make the wan interface work, so I can ping IP's on the wan side?
[13:02] <mac|gyver> as a matter of fact, yes :)
[13:03] <mac|gyver> I'm trying to get wds back up again
[13:03] <mac|gyver> anyone done that before with the experimental build?
[13:05] <caldari> anyone knows what version of iptables is there in the experimental ?
[13:05] <mac|gyver> 1.3.1
[13:06] <inh> wbx, what are you going to make docs for?
[13:07] <caldari> ok is above 1.2.7 so i can do SNAT :) ty ty
[13:08] <wbx> Soopaman: find out which rootfs is used.
[13:09] <wbx> Soopaman: hexdump | grep MAGIC .
[13:09] <wbx> inh: dunno. first i will finish my kernel stuff
[13:10] <inh> okie
[13:10] <Soopaman> good
[13:11] <t0mt0m> just a little question, hum ... is the experimental build really unstable ?
[13:11] <inh> quiet wrt
[13:11] <J4k3> "not really"
[13:11] Action: J4k3 can't complain... my vzw service kicks ass overall.
[13:11] <coder> Two friends, /exit and /quit sitting in the garden, /exit goes away,who is still there??
[13:11] <mac|gyver> /quit ofcourse
[13:11] <J4k3> I've been in some absolutely ass-end-of-the-earth locations and had to make calls... I might have had to climb a tree (its happened) but I've gotten my calls out
[13:12] <wbx> shit. route to my devel system is away. shit fuck
[13:12] <J4k3> coder: mm, new alt-f4
[13:13] <inh> lmfao
[13:13] <mac|gyver> hmm when I do wl wds xx:xx:xx:xx:xx:xx, I get "eth1: Invalid argument"
[13:14] <mac|gyver> any idea where I might look?
[13:15] <geoman> mac|gyver: why not just set the wl0_wds nvram variable to the MAC address(es) of your other access point(s)
[13:15] <geoman> ?
[13:15] <geoman> it will set up wds automagically every boot that way
[13:17] <mac|gyver> geoman: that's set
[13:17] <mac|gyver> but doesn't do a think
[13:17] <mac|gyver> *thing
[13:17] <mac|gyver> well the experimental thingy doesn't :)
[13:18] <wbx> wds works fine with experimental. which routers you use?
[13:18] <geoman> mac|gyver: all your ap's have to be set to the same channel and ssid
[13:18] <mac|gyver> 2 wrt54gs's
[13:18] <mac|gyver> they are
[13:18] <geoman> mac|gyver: and wl0_mode=ap
[13:18] <mac|gyver> checked that too
[13:18] <wbx> mac|gyver: then you need to deactivate afterburn
[13:19] <geoman> ahh yes, that too
[13:19] <wbx> geoman: show me your boardflags
[13:19] <wbx> eh, mac|gyver
[13:19] <mac|gyver> how do I get them?
[13:19] <geoman> nvram get boardflags
[13:19] <wbx> nvram show|grep board
[13:19] <mac|gyver> heh ok
[13:19] <geoman> or that
[13:20] <mac|gyver> 0x0388
[13:20] <Dabian> WL-500gd: I have an ip on Lan3 port. I telnet to the wl-500gd from the local net. How can I make the wan interface work, so I can ping IP's on the wan side? I am not talking about nat or anything, just to give the wan port an ip, and ping stuff.
[13:20] <Kaloz> ifconfig it
[13:20] <geoman> wbx: btw, I still got a couple of segfaults with cvs HEAD on my wl-500g
[13:20] <geoman> that and ipkg is putting stuff in /lib/ipkg instead of /usr/lib/ipkg for some reason
[13:20] <Dabian> Kaloz: But .. isn't both wan and lan eth0 on the wl-500gd ?
[13:20] <wbx> geoman: hmm. that is strange.
[13:21] <geoman> Dabian: no
[13:21] <geoman> well, I don't know about deluxe I guess
[13:21] <wbx> mac|gyver: change it with nvram set to 0x0118 on both and reboot
[13:21] <mac|gyver> on both?
[13:21] <Dabian> geoman: Thats what I have.
[13:21] <wbx> geoman: you know cvs, and your source is not tagged? cat CVS/Tag
[13:22] <Dabian> geoman: I think eth1 is the radio, which I don't use.
[13:22] <mac|gyver> wbx: the other is still running the stable version, and that's been working fine the way it is
[13:22] <geoman> Dabian: on my wl-500g, eth2 is radio, eth1 is wan, eth0 is lan
[13:22] <Dabian> eth2?
[13:22] <Dabian> Lemme check if I have taht.
[13:22] <mac|gyver> wbx: hmm that seems to do the trick
[13:23] <geoman> wbx: nope, not tagged
[13:23] <wbx> mac|gyver: just believe me or spent another 5 days to debug :p
[13:23] <Dabian> root@wl-500ge:/# ifconfig eth2
[13:23] <Dabian> ifconfig: eth2: error fetching interface information: Device not found
[13:23] <mac|gyver> wbx: does that need to be done on the stable version one as well?
[13:23] <wbx> i think so.
[13:24] <Dabian> geoman: eth0 is configured with a wan ip.
[13:24] <Dabian> geoman: The local IP is on "br0"
[13:24] <geoman> Dabian: yes, that's the bridge
[13:24] <wbx> geoman: only segfaults or bus error and illegal instructions?
[13:24] <geoman> wbx: only segfaults
[13:25] <geoman> wbx: they didn't kill my router this time, but I've still run into a couple
[13:25] <wbx> with other apps then ipkg?
[13:25] <geoman> wbx: yeah, ps triggered it
[13:25] <Kaloz> Dabian: vlan1 is wan, br0 is lan
[13:25] <wbx> geoman: are you sure the kernel is build with -fno-delayed=
[13:25] <J4k3> I think I'll make a 900 ISM vertical omni today
[13:26] Action: J4k3 makes any excuse to avoid direct sunlight
[13:26] <Dabian> Kaloz: oh ok
[13:26] <geoman> wbx: well, I took your word for it that it is in cvs...let me check ;)
[13:27] <wbx> geoman: it is... package/linux/linux.mk
[13:27] <Dabian> Kaloz: Hmm .. no such device :/
[13:27] <Dabian> Kaloz: Maybe its vlan0 ?
[13:27] <geoman> wbx: yeah, it is in there
[13:27] <geoman> actually
[13:27] <geoman> CFLAGS_KERNEL="-fno-delayed-branch
[13:27] <Dabian> how do I remove the IP from eth0 again?
[13:28] <wbx> hmm. strange. do you use jffs2 or squashfs images?
[13:28] <geoman> squashfs
[13:28] <Kaloz> Dabian: depends :)
[13:28] <wbx> no idea at the moment, and my devel system is not reachable to finish driver update. shitfuck
[13:28] <Kaloz> Dabian: by default, vlan1 is wan port, and lan is br0 (vlan0+eth1)
[13:29] <Dabian> ok
[13:29] <Dabian> Here there is no vlan1, apparently
[13:29] <geoman> wbx: well, I'm not too concerned with it at this point...I can't get cups to work anyway, which is what I really want to use on that thing
[13:29] <geoman> I'll probably have to go back to the asus firmware for now
[13:29] <wbx> geoman: hmm. cups is not working?
[13:29] <wbx> geoman: debug it :p
[13:30] <geoman> wbx: nope...all I get is "client-error-not-found"
[13:30] <geoman> which is quite possibly the least useful error I've ever seen ;)
[13:30] <geoman> I've never seen cups to fail printing to a local lpr printer like that, heh
[13:30] <wbx> seems more a configuration error :p
[13:31] <geoman> well, the default config comes with a parallel and usb printer entry, both of which look valid to me
[13:31] <geoman> from my experience with cups before
[13:31] <[mbm]> .
[13:31] <geoman> I've tried to create new entries manually, and they fail in the same way
[13:31] <wbx> geoman: usb or parallel port printer?
[13:31] <geoman> I also tried running cups-lpd via inetd, still no luck
[13:32] <geoman> wbx: parallel
[13:32] <Dabian> Kaloz: I got the WL-500gd ... its cool, except I am still not able to install packages to it.
[13:32] <wbx> geoman: parallel port module is loaded=
[13:32] <geoman> wbx: yep
[13:32] <Dabian> Kaloz: I cannot get the wan interface up.
[13:33] <geoman> parport, parport_splink, and lp modules are all loaded
[13:33] <wbx> [mbm]: hi. what was the reason for the downtime?
[13:33] <mac|gyve1> wbx: that didn't really seem to help :( to connection from my laptop to the wrt connected to the internet was lost
[13:33] <[mbm]> wbx: huh?
[13:33] <geoman> wbx: I've confirmed the port works...I can cat or echo text to /dev/printers/0 and the printer spits those out
[13:33] <kentpaul> Hi, my openwrt seems to be setup as NAT/router, i just need it to route packets, not NAT them, is there a 'good' way to do this ?
[13:34] <wbx> [mbm]: openwrt.org was down? or only a router between?
[13:34] <kentpaul> i mean by changing nvram variables, or do i have to create my custom initscript ?
[13:34] <[mbm]> wbx: my ssh session to it is still active, must have been a routing issue
[13:34] <Kaloz> Dabian: by default, it uses dhcp
[13:34] <wbx> mac|gyve1: you corrected both routers?
[13:34] <mac|gyve1> yup
[13:34] <Dabian> Kaloz: Right
[13:34] <wbx> mac|gyve1: and rebootet both?
[13:34] <mac|gyve1> yeah
[13:34] <Dabian> Kaloz: Should I set up a dhcp server for it?
[13:34] <Kaloz> Dabian: http://openwrt.org/OpenWrtNVRAM
[13:35] <Kaloz> Dabian: you can make it static
[13:35] <wbx> mac|gyve1: then it should work.
[13:35] <Dabian> Kaloz: I tried nvram set wan_proto=0 or something.
[13:35] <mac|gyve1> wbx: I do have a wds0.2 device on both of them now
[13:35] <mac|gyve1> but I can't connect any client to the wireless link
[13:35] <Dabian> wan_proto=static
[13:35] <Dabian> wan_ipaddr=theExtIP
[13:36] <wbx> mac|gyve1: same channel and same essid on both? nvram committet all changes?
[13:36] <mac|gyve1> yup
[13:36] <wbx> mac|gyve1: check the values.
[13:36] <mac|gyve1> I did
[13:36] <mac|gyve1> I checked them before I got back here :)
[13:36] <Dabian> hmmm .. I have this:
[13:37] <Dabian> wan_proto_t=Automatic IP
[13:38] <geoman> hmm, so anyway, as far as I can tell, the openwrt cups package is missing something it needs to communicate with the parallel port
[13:38] <Dabian> wan_ifname=eth0
[13:38] <Kaloz> Dabian: wan_proto static
[13:39] <Dabian> wan_proto=static
[13:39] <inh> weeee
[13:39] <Dabian> I have
[13:39] <inh> new ver of aircrack is gonna be gol
[13:39] <inh> cool
[13:39] <mac|gyve1> wbx: is there some kind of reference for those board flags?
[13:40] <wbx> mac|gyve1: forum.
[13:40] <Dabian> Kaloz: Its most likely a very stupid thing.
[13:41] <Kaloz> Dabian: you cna debug it. export DEBUG=echo && /etc/init.d/S40network start
[13:41] <Kaloz> Dabian: for static, you have to set the ip and the netmask, too
[13:41] <Dabian> Kaloz: I did that, and the hostmask, and the gateway
[13:41] <legodude> any major changes with v2.2 of the 54g?
[13:41] <Dabian> wan_hostmask
[13:41] <Dabian> wan_gateway
[13:41] <Dabian> wan_dns
[13:42] <Dabian> wan_netmask
[13:42] <mac|gyve1> wbx: I think I'm reverting for now
[13:42] <mac|gyve1> found a similar bug on the forums with 2.4.30
[13:42] <mac|gyve1> looks very familiar
[13:42] <mac|gyve1> could someone mention my original flags? :)
[13:43] <mac|gyve1> uhm whoops
[13:43] <Dabian> Kaloz: You running out of ideas as well?
[13:43] <mac|gyve1> wbx: I might be onto something
[13:43] <Kaloz> Dabian: seems so.. can you simply 'ifup wan'?
[13:44] <mac|gyve1> I think I want both my original and the suggested new boardflags
[13:44] <mac|gyve1> but my client quit, so if someone could look up a bit?
[13:44] <wbx> If it was 0x0318 then change it to 0x0118 (wrt54gs v1.1, v2.0)
[13:44] <Dabian> Kaloz: yes .. I can ping the interface own ip, but not others .. lemme add some firewall rules.
[13:46] <mac|gyve1> I found the post
[13:46] <stupidkid> hey if i forgot my route password can i get it back?
[13:46] <stupidkid> just in case
[13:46] <geoman> stupidkid: you could start your router up in failsafe mode and telnet in, and then fix it
[13:46] <Dabian> Kaloz: I get interesting stuff on a wan sniffer though:
[13:46] <Dabian> 23:48:11.511600 802.1Q vlan#0 P0 802.1d config 8000.00:11:d8:9f:98:95.8001 root
[13:46] <Dabian> 8000.00:11:d8:9f:98:95 pathcost 0 age 0 max 20 hello 2 fdelay 0
[13:47] <stupidkid> geoman: you mean hold the reset button?
[13:47] <geoman> stupidkid: yeah...where you hold the reset button for 2 seconds when the dmz light starts up
[13:47] <stupidkid> cool
[13:47] <stupidkid> thanks Ge0rG
[13:48] <stupidkid> geoman
[13:48] <stupidkid> :)
[13:48] <Dabian> oh well
[13:48] <Dabian> I will sleep
[13:48] <Dabian> then maybe set it up to nat later, like anyone else, and then go from there.
[13:49] <Dabian> Kaloz: Thanks for your ideas.
[13:49] <Kaloz> np
[13:50] <geoman> hmm, interesting
[13:50] <geoman> wbx: heh, I tried to strace cupsd, and got a segfault
[13:50] <geoman> then I tried to strace ls just for grins, and it locked the router up
[13:50] <geoman> although I can still ping it
[13:51] <wbx> that sucks. we have some problem with asus wl500g. maybe no-delayed-branch is not enough..
[13:51] <wbx> to fix this buggy board
[13:51] <nbd> .
[13:52] <mac|gyver> wbx: works :)
[13:52] <wbx> mac|gyver: your mistake? :p
[13:52] <mac|gyver> thnx alot man
[13:52] <mac|gyver> wbx: ofcourse :)
[13:52] <stupidkid> my vim is slow on openwrt
[13:53] <mac|gyver> nah both of us I think
[13:53] <stupidkid> is there a fast editor tool?
[13:53] <mac|gyver> but it doesn't really matter
[13:54] <mac|gyver> the problem is that when they start failing, so does my internet connection :)
[13:54] <nbd> wbx: we probably need a serial console on the wl500g to fix this problem
[13:55] <nbd> btw. was anybody here able to reproduce the 'missing telnet server' problem?
[13:55] <wbx> nbd: but there is no uart on wl500g ...
[13:55] <nbd> i don't have a router for testing at the moment
[13:55] <geoman> I opened my wl-500g when I got it...it has what looks like a serial port interface on the inside
[13:55] <geoman> but I'm not for certain
[13:55] <nbd> wbx: you can add an uart, can't you?
[13:56] <wbx> i have no idea, i thought serial console on wl500g is not possible
[13:56] <nbd> adding an uart should be possible
[13:57] <wbx> i will take it to my friend on tuesday
[14:02] <wbx> nbd: hmm. mixing up the different source balls=
[14:02] <nbd> yeah. why not?
[14:02] <Kaloz> wbx: *cough* mail
[14:03] <wbx> i see. b44 has a bad performance. and we still need more tests and sth for adm switch
[14:04] <nbd> *cough* mail
[14:04] <Kaloz> :D
[14:06] <Death_INC> stupidkid: vi is as fast as you're going to find, if it's slow you may have something else wrong...
[14:11] <Death_INC> anybody looked at the WRT54GX?
[14:12] <[mbm]> yep.
[14:12] <Death_INC> it a different hardware platform?
[14:12] <[mbm]> nope
[14:13] <[mbm]> new wireless card, apart from that openwrt runs perfectly as-is
[14:13] <Death_INC> cool
[14:13] <Death_INC> hmm
[14:13] <Death_INC> so we just need to get the drivers for the new wireless working?
[14:13] <[mbm]> wireless driver is a mess and hasn't worked properly yet
[14:13] <Death_INC> ick
[14:14] <[mbm]> instead of just one module there's a few modules and even some userspace applications that wireless depends on
[14:14] <legodude> is it some faster card?
[14:14] <Death_INC> legodude: it's their beginnings of a 802.11n router
[14:14] <teemu_> err
[14:14] <teemu_> miah: you there?
[14:14] <Death_INC> so yea, double speed and better range supposedly
[14:15] <legodude> ah
[14:15] <J4k3> I believe 11n also uses narrower channels
[14:15] <J4k3> not the 20mhz of crap 11b/g spews
[14:16] <teemu_> miah: are you now home?, If you are would you put your dnsmasq.conf somewhere where I can look that nameserverr thing :I
[14:16] <Death_INC> I'm going to get another router to try to get my WPA working right without bringing down my network, was thinking of getting a GX heh
[14:16] <legodude> backwards compat with g or is 11n the really new proto that belkin has stuff for?
[14:16] <Death_INC> backwards compatible on this one supposedly
[14:17] <Death_INC> but it's NOT 802.11n
[14:17] <Death_INC> it's just using alot of the technology in .11n -- the specs for n isn't final yet
[14:17] <legodude> aaah
[14:21] <Death_INC> it uses mini-pci for the radio board tho, so should be easy to switch out if people were so inclined
[14:21] Action: Death_INC looking on tomshardware now
[14:21] <[mbm]> only managed to find one serial header
[14:22] <legodude> any differences in the v2.2 version of the wrt54g?
[14:22] <Death_INC> jtag? I couldnt see anything on the pic on tomshardware
[14:22] <[mbm]> haven't looked for a jtag yet
[14:22] <[mbm]> whole thing is enclosed in a nice tin can
[14:23] <Death_INC> yah heh
[14:23] <Death_INC> and soldered ya
[14:23] <z3ro> [mbm]: how would you find jtag anyway? do you have a oscilloscope?
[14:23] <legodude> damn is that thing ugly
[14:23] Action: z3ro wants to find jtag on his wag54g.
[14:23] <legodude> jtag is usually a defined header
[14:23] <legodude> look for groups of what, 4pins?
[14:24] <legodude> sometimes you can then trace the leads to the chip
[14:24] <z3ro> not on the wag54g, they just go off for about 10mm, then go to a via.
[14:24] <legodude> ah
[14:24] <z3ro> jtag has a length limit right?
[14:24] <z3ro> about 12cm?
[14:25] <legodude> don't think so
[14:25] <legodude> I've seen lots of jtag cables longer than that
[14:25] <alxhh> works with more
[14:25] <Death_INC> length limit is because the instructions are for a passive cable
[14:25] <Death_INC> but of course everything has a length limit of something
[14:25] <z3ro> yes, I know - but would it make sense to have the jtag the closest header to the cpu?
[14:26] <legodude> pretty close probably
[14:26] <legodude> always is close on boards I have seen
[14:26] Action: J4k3 has half a 900 omni built
[14:26] <Death_INC> I cant find anything that tells me how much flash it has and how fast the cpu is bleh
[14:26] <z3ro> on the wag54g, there is one header almost right next to the cpu, and the others are on the other side of the board - away from the cpu.
[14:26] <legodude> how many pins on header right near cpu?
[14:26] <z3ro> 10
[14:26] <legodude> that toms hardware pic is terrible!
[14:26] <legodude> that might be it
[14:27] <z3ro> yeah, the problem is identifying which pin is which.
[14:27] <legodude> usually pretty standard, no?
[14:28] <z3ro> legodude: I don't know, is there a standard "10pin jtag connector"
[14:29] <legodude> doesn't the wrt54g have jtag?
[14:29] <Death_INC> legodude: it does
[14:30] <legodude> how many pins does it have?
[14:30] <Death_INC> I have a cable I used to unscrew my wrt heh
[14:30] <Death_INC> 12
[14:30] <Death_INC> but it only uses 4+ground
[14:30] <legodude> might be similar
[14:30] <legodude> yea
[14:30] <legodude> one side of teh 10pin might be all ground
[14:30] <legodude> that would probably be good indication that it is jtag
[14:31] <z3ro> hmm
[14:32] <teemu_> err, is there way to use dnsmasq allmost as like bind
[14:33] <z3ro> there are two 14pin headers far away from the cpu...
[14:34] <Death_INC> that could be it
[14:34] <Death_INC> JTAG is supposed to be 14 pins I think
[14:34] <Death_INC> course I'm just going by what I read :b
[14:35] <z3ro> on both connectors one side is connected to ground (from what I can tell). on the first connector the other side goes directly off to pcb traces, on the second connector it goes off to pcb traces via some small smd components (resistors/capacitors?)
[14:36] <z3ro> jtag would not have resistors, right?
[14:36] <legodude> certainly might
[14:36] <legodude> look up the schematics for some standard jtag ports
[14:37] <Death_INC> you have a wrt54g/gs to look at?
[14:37] <z3ro> http://www.ffii.org/~zoobab/bh.udev.org/filez/projects/uClinux-samsung4510/pasteleurs/jtag-samsung4510-ver0.2.png
[14:37] <z3ro> that has the pins for a 14pin jtag...
[14:38] <z3ro> so if I check the location of gnd and vcc - which is about all I can do with a multimeter...
[14:40] <Death_INC> [mbm] said he found a serial connection...
[14:40] <Death_INC> oh nm
[14:40] <Death_INC> wag54g not wrt54gx heh
[15:35] <teemu_> err..
[15:35] <teemu_> how I can set that dnsmasq to give specific ip per hostname,
[15:35] <nbd> add it to /etc/ethers
[15:35] <teemu_> I got it working with windows.. so when computer name is diablo he get ip 192.168.1.100
[15:36] <teemu_> nbd: I don't want that
[15:37] <teemu_> how I can get that to get hostnames from linux computers, and then give ip by that hostname
[15:39] <nbd> don't know
[15:41] <coob> do it by mac address?
[15:42] <teemu_> coob: well, nah
[15:42] <treysis> got a pptpd related question
[15:43] <treysis> anybody there to help me out?
[15:46] <treysis> hm?
[15:47] <nbd> sorry, don't know anything about pptp
[15:48] <treysis> hm. can't imagine nobody configured it.
[15:48] <treysis> the thing is, i can connect but i need to know how to use the router as a gateway
[15:49] <treysis> that is laptop -> noname-router -> inet~vpn-connection~inet -> WRT54G1.1 -> inet...
[15:50] <coob> man route
[15:50] <treysis> laptop is winxp
[15:51] <treysis> when i was using sveasoft's firmware and connected from within the lan, the wrt54g provided information like ip-adress, gateway and dns-server
[15:51] <treysis> now with my basic configuration file for pptp on openwrt causes that i even can
[15:52] <treysis> cannot ping the unit
[15:52] <treysis> i can connect, get a new interface under winxp with the correct ip assigned but i am not able to ping the router or anything else on the net
[15:55] <bone_idol> exit
[15:56] <bone_idol> oops
[15:57] <teemu_> err
[16:02] <treysis> hm
[16:02] <treysis> no clue yet?
[16:03] Action: legodude is excited as his second wrt54g comes on tuesday
[16:30] <HardCorePawn> howdy, are there plans to include support for WAG54G v2?
[16:49] <patrik> I don't understand how the network interfaces on my wrt54g v1.1 is supposed to be configured. Could someone please help me with that?
[17:40] <Eagle_Fire> #wrt54g is lonely today
[17:41] <elemental> alguien me puede ayudar con mi wrt54g le puse el firmware freemanbasic y los leds parpadean mucho
[17:41] <Eagle_Fire> this is an international channel, please speak english
[17:42] <elemental> someone can help me with my wrt54g
[17:42] <Eagle_Fire> that's what we're here for
[17:43] <elemental> the power led turn on and turn off
[17:43] <Eagle_Fire> that happens sometimes; it doesn't mean anything
[17:43] <elemental> and the dmz led turn on for 4 seconds and turn off for 4 seconds
[17:43] <elemental> i reflash the wrt54g with freemanbasic
[17:44] <elemental> and it say upgrade succesful
[17:44] <Eagle_Fire> and the router does not function now?
[17:44] <elemental> no function
[17:45] <Eagle_Fire> did freemanbasic tell you to turn on boot_wait
[17:45] <elemental> yes, i turn on the boot_wait
[17:45] <Eagle_Fire> okay
[17:46] <Eagle_Fire> it looks like this firmware you tried is not compatible with your router
[17:46] <Eagle_Fire> you need to send a working firmware by TFTP
[17:46] <elemental> ok
[17:47] <elemental> how i can send the firmware
[17:47] <elemental> ?
[17:47] <Eagle_Fire> instructions here: http://openwrt.org/OpenWrtDocs/Installing#head-f56e06c42cb97a7aace9a5b503d0d288697d98d9
[18:23] Action: DarkDream gnite
[19:17] Action: inh grumbles at his sd card mod
[20:38] <Death_INC> dammit
[20:38] <Death_INC> nvram set wl0_auth_mode=psk
[20:38] <Death_INC> nvram set wl0_wpa_psk=insecure
[20:38] <Death_INC> nvram set wl0_wep=tkip
[20:38] <Death_INC> nvram set wl0_crypto=tkip
[20:38] <Death_INC> ack sorry
[20:39] <Death_INC> root@wrt54gs-main:~# /usr/sbin/nas4not lan wds0.2 add
[20:39] <Death_INC> Unable to build command line. Quitting...
[20:39] <Death_INC> but it works otherwise grr
[20:48] <wt> anyone here?
[20:49] <wt> I would like to know if there is an experimental shorewall package for openwrt
[20:49] <wt> or another firewall package
[20:55] <wt> ~firewall
[20:58] <Death_INC> wt: look on the package tracker at openwrt.org
[21:00] <wt> Death_INC: nothing looks like it's for experiemental
[21:00] <wt> only stable stuff
[21:01] <wt> I just don't know if it is compatible
[21:01] <Death_INC> should be
[21:01] <wt> oh
[21:01] <wt> ok
[21:01] <Death_INC> not kernel modules is it?
[21:01] <wt> so...ser, opensimpad, or yani?
[21:01] <wt> Which one is best?
[21:02] <Death_INC> I dont use a tool to configure my iptables heh
[21:02] <Death_INC> so I donno
[21:02] <wt> no...I mean the source
[21:02] <wt> those are sources for shorewall
[21:02] <wt> it's too bad that the lead dev decided to step down on shorewall
[21:02] <wt> it's really good
[21:06] <Death_INC> aah
[21:06] <Death_INC> I need the damned command line for nas4not -- it can't build command line with new version of nas
[21:06] <Death_INC> heh
[21:06] <Death_INC> I could use old version as nas4not
[21:06] <Death_INC> maybe that will work
[21:08] <wbx> wt: we have S45firewall- why we need shorewall?
[21:08] <Death_INC> yay, that worked... at least it RAN... now I just gotta get it on other AP
[21:08] <wt> wbx because shorewall makes more sense, generally
[21:08] Action: Death_INC nods at wbx
[21:09] <wt> and is very easy to configure
[21:09] <wt> unlike writing rules for iptables
[21:10] <wt> on another note, does ez-ipupdate have to have a cache file?
[21:10] <wt> I don't want it writing to flash if not needed
[21:13] <wt> or do you have any recommendations for ez-ipupdate, if you run it?
[21:15] <inh> weeeeeeeee
[21:15] <wt> inh: what?
[21:15] <inh> nothing
[21:15] <wt> oh
[21:15] <inh> just enjoying hating every day :D
[21:15] <wt> do you use openwrt?
[21:15] <wt> word
[21:15] <wt> :-P~
[21:16] <wt> the sveasoft people are kinda mean if you don't buy it
[21:16] <inh> haha of course
[21:16] <inh> openwrt is really cool
[21:17] <wt> doesn't make me wanna buy it
[21:17] <inh> only issues most people have, like myself, are networking, as the wrt's internal layout is kinda odd
[21:17] <wt> inh: do you use ez-ipupdate?
[21:17] <inh> no
[21:17] <wt> inh: dynamic ip?
[21:17] <inh> no i usually set the ip statically
[21:18] <wt> I don't wanna pay extra for a static if it's not needed
[21:18] <inh> well heres the problem
[21:18] <inh> if you set the ip dynamicaly, everytime it changes, you wont know its ip, so how will you connect to it
[21:19] <wt> inh: that's where ez-ipupdate comes in
[21:20] <wt> it monitors for the changes and then contacts dyndns with the updates
[21:20] <wt> then I just access it with something like fl-house.dyndns.org
[21:20] <inh> ah
[21:20] <inh> well then
[21:20] <inh> go for it
[21:20] <wt> I have used it before
[21:21] <wt> I am just wondering if I can make it not write a cache file
[21:21] <wt> I don't want any unneccessary writes to the flash
[21:21] <wt> it just slows things down
[21:21] <inh> dont worry about it
[21:21] <wt> why not worry about it?
[21:21] <inh> with openwrt, i dont think it will write to flash
[21:21] <inh> it woudl write to ram, and then the fs should save the changes to flash. i dunnno
[21:22] <inh> youd have to talk to Eagle_Fire or [mbm]
[21:22] <wt> I am running the jffs2 version
[21:22] <wt> if that makes a difference
[21:22] <inh> hmm
[21:22] <inh> then i think it wirtes...
[21:22] <J4k3> wt: its probably ln'd to /tmp
[21:22] <J4k3> any temporary conf files reside in /tmp
[21:22] <inh> i would look into the source..
[21:22] <J4k3> openwrt is cool like that
[21:23] <inh> does it NEED the cache file?
[21:23] <wt> J4k3: and /tmp is a ramfs
[21:23] <wt> I think that settles it
[21:23] <wt> hehe
[21:23] <wbx> when it writes to filesystem?
[21:23] <wbx> why it should do that?
[21:23] <inh> if it writes to /tmp
[21:23] <inh> then your ok as that resides in ram
[21:24] <wbx> why should it write to tmp?
[21:24] <wt> wbx: are you asking about ez-ipupdate?
[21:24] <wbx> yes. i am using ez-update.
[21:24] <wt> wbx: it says that it writes a cache file
[21:24] <wt> wbx: is that default behavior?
[21:25] <wt> or can it be turned off?
[21:25] <wbx> when it says it?
[21:25] <wt> ez-ipupdate --help
[21:26] <wbx> it is an option.
[21:26] <wbx> but it is not used by default
[21:26] <wt> gotcha
[21:26] <wt> that is good
[21:26] <wbx> /usr/sbin/ez-ipupdate -c /etc/dyndns.conf --daemon
[21:26] <inh> i should use that
[21:26] <wt> put that in a startup script?
[21:26] <inh> i just dont like having to go across the internet to get to my router
[21:27] <wbx> cat /etc/init.d/S60dyndns
[21:27] <wbx> #!/bin/sh
[21:27] <wbx> /usr/sbin/ez-ipupdate -c /etc/dyndns.conf --daemon
[21:27] <wt> well...yeah
[21:27] <wt> cool
[21:27] <wt> thanks
[21:27] <wt> you have a dyndns.conf that you could share?
[21:27] <wbx> no.
[21:27] <wt> minux the password?
[21:28] <wbx> user=blah:xxx
[21:28] <wbx> service-type=dyndns
[21:28] <wbx> interface=ppp0
[21:28] <wbx> host=blah.dyndns.org
[21:29] <wt> so...
[21:29] <wt> user=wt:xxx
[21:29] <wt> service-type=dyndns
[21:30] <wt> interface=vlan1
[21:30] <wt> host=blah.dyndns.org
[21:30] <wt> something like that?
[21:30] <inh> xxx is the password
[21:31] <wt> right
[21:32] <wt> I was mainly making sure that the vlan1 was right
[21:32] <wbx> depends on your uplink
[21:33] <inh> vlan1 is for wan port right?
[21:33] <inh> and in order for that to work you gotta take down your firewall, or allow port 22 (for ssh)
[21:33] <wt> that's the default on wrt54g, right?
[21:33] <inh> i think..
[21:33] <inh> i saw a nice diagram of hwo the wrt's ports are..
[21:33] <wt> I am confused...what do I have to take down the firewall for?
[21:34] <inh> by default, openwrt blocks all ports coming in to the wan port
[21:36] <wt> are you sure
[21:36] <wt> the INPUT chain has a line:
[21:36] <wt> ACCEPT all -- anywhere anywhere
[21:37] <wt> that's the third rule
[21:37] <wt> or do you read a chain starting at the bottom?
[21:38] <inh> i dunno
[21:40] <wt> I guess I will install shorewall now
[21:40] <wt> cuz it flippin' rocks
[21:40] <wt> wbx: thanks for the ez-ip* help
[21:52] <cplx> can someone advise me on what cable/connectors are needed to go from a 24dbi Parabolic (http://www.freenet-antennas.com/~freenet-/oscommerce-2.2ms2/catalog/product_info.php?cPath=22_24_26&products_id=123) to a WRT54GS
[21:52] <wt> I sure can't
[21:53] <wt> they have a pic on the site
[21:54] <wt> at pic of the wrt54g, that is
[21:54] <wt> maybe they have the hardware to do it
[21:54] <wt> They want too much for a wrt54g though
[21:54] <wt> $125
[21:54] <wt> c'mon
[21:55] <wt> $155 for a GS?!?!
[21:55] <cplx> australian dollars..
[21:55] <cplx> thats about 80-100 USD
[21:56] <wt> oh
[21:56] <wt> nevermind
[21:56] <wt> hehe
[21:59] <inh> cpatrick,
[21:59] <inh> what connector type is on the parabolic?
[22:05] <inh> *cplx
[22:06] <inh> cplx, what connector on the dish?
[22:06] <cplx> N-F > CNT400 > N-F > N-M > CNT200 > TNC > AP
[22:11] <SeRi> hey guys I got a quick question... A ssh key generated in putty gen can it be use in Debian?
[22:13] <SeRi> when I open the key with putty it accepts my pasphrase but when I use SecPanel with Debian it wont accept my passphrase
[22:13] <SeRi> Any ideas?
[23:20] <inh> grrrr
[23:21] <inh> stupid squash
[23:24] <coder> -.-
[23:30] <inh> o know squash is read only
[23:30] <inh> * i know
[23:30] <inh> but
[23:30] <inh> ipkg cant create /usr/lib/ipkg/lists
[23:30] <inh> wtf
[23:31] <webmind> read online fs?
[23:31] <webmind> no directory ipkg in /usr/lib ?
[23:32] <inh> no its there..
[23:32] <inh> i need to install dropbear
[23:32] <inh> so i can put my jffs image on there
[23:32] <inh> and flash it
[23:33] <inh> ERROR: File not found: /usr/lib/ipkg/lists/experimental
[23:33] <inh> You probably want to run `ipkg update'
[23:33] <inh> but update gives me the previous error
[23:34] <Death_INC> inh: firstboot
[23:34] <Death_INC> makes symlinks and switches
[23:34] <Death_INC> or you booted up in failsafe mode
[23:35] <Death_INC> jffs2 bad :b
[23:35] <inh> i hate the symlink crap tho
[23:35] <Death_INC> yea, it's annoying
[23:35] <Death_INC> need a little unsymlink script
[23:36] <inh> i already ran firstboot
[23:36] <inh> i think this is bad:
[23:36] <Death_INC> I'm still in a battle with nas :\
[23:36] <inh> root@OpenWrt:/usr/lib# firstboot
[23:36] <inh> Creating jffs2 partition... Could not open mtd device: OpenWrt
[23:36] <inh> mount: Mounting /dev/mtdblock/4 on /jffs failed: No such file or directory
[23:36] <inh> done
[23:36] <inh> creating directories... done
[23:36] <inh> setting up symlinks... done
[23:38] <frink> mwaahhh
[23:38] <inh> ?
[23:40] <Death_INC> lol
[23:40] <Death_INC> not if your jffs2 is already mounted
[23:41] <Death_INC> frink: you kissing him? heh
[23:41] <inh> bah i want squash to go bye bye
[23:47] <frink> Has anybody made any Java work on the WRTs or is it just too BIG?
[23:48] <frink> not that I really want to do it mind you..
[23:52] <nettie> wbx: ping
[23:57] <wbx> nettie: pong
[23:58] <nbd> .
[00:00] --- Mon May 23 2005