**** BEGIN LOGGING AT Sun Feb 06 02:59:57 2011
Feb 06 03:34:42 <dmb> tinker-f595: you have one?
Feb 06 03:36:22 <dmb> anyone have the original rootfs of the guruplug server plus?
Feb 06 03:36:29 <dmb> i downloaded what I thought was it
Feb 06 03:36:41 <dmb> but it does not seem so
Feb 06 03:51:35 <dmb> for some reason my guruplug doesn't like to autoboot unless serial is connected
Feb 06 04:07:57 <mdm2k> dmb: I've noticed that the guruplug won't boot if you have the jtag board connected to it, but not connected to usb
Feb 06 04:08:58 <mdm2k> maybe it pulls too much power out of the guruplug when you do that or something; if you connect the jtag board to a powered usb hub it boots fine
Feb 06 04:23:17 <dmb> lol
Feb 06 04:25:34 <dmb> thats stupid
Feb 06 04:26:01 <dmb> mdm2k: any reason why it might not start wifi while jtaging also?
Feb 06 04:26:43 <mdm2k> I have also noticed that if you are running openocd on jtag while the kernel is running it's kind of unstable
Feb 06 04:27:09 <mdm2k> but just having the jtag board connected without running openocd doesn't seem to affect stability
Feb 06 04:28:13 <mdm2k> so I don't have an explanation for why it might not start wifi while the jtag board is connected unless you're running openocd, in which case, don't do that
Feb 06 04:28:54 <dmb> hmm
Feb 06 05:40:17 <dmb> man, this thing is buggy
Feb 06 05:40:38 <dmb> after debugging it for around an hour, one reboot it wifi just starts working, for no reason
Feb 06 05:46:13 <mdm2k> the wifi client mode is apparently not particularly robust
Feb 06 05:47:29 <mdm2k> and the default system image is kind of hacky and weird anyway
Feb 06 05:47:40 <mdm2k> best to just install something of your own if you ask me
Feb 06 05:48:32 <mdm2k> I compiled a new uboot and set it up to boot right off of esata, leaving the internal nand system basically untouched
Feb 06 05:48:50 <mdm2k> very reliable that way
Feb 06 06:04:58 <dmb> oh
Feb 06 07:16:20 <UnaClocker> Yeah, I set mine to boot off the SD card the day I got mine, my NAND image is factory fresh.
Feb 06 07:20:22 <tinker-f595> Tootoot222: sheevaplug, guruplug and openrd all use the Marvell Kirkwood SOC
Feb 06 16:05:26 <Barlow> hey anyone running debian squeeze on their plug?
Feb 06 16:07:07 <Barlow> atm i'm running lenny and wondering whether i still need tbm's repository for squeeze
Feb 06 16:30:10 <dmb> mdm2k: is there a chance the rootfs that is in downloads and the rootfs that was shipped was different ?
Feb 06 16:30:35 <dmb> reason why I ask is the "admin page" when I reflashed the rootfs is not there, its just a lighthttpd it works page
Feb 06 17:00:49 <tbm> Barlow: you don't need it
Feb 06 17:01:36 <Barlow> thanks tbm :)
Feb 06 18:39:21 <kerio> tbm's repository?
Feb 06 18:50:43 <Barlow> kerio: yeah with a kernel (and some libs as well i think) for lenny
Feb 06 18:50:53 <kerio> meh
Feb 06 18:50:55 <kerio> squeeze <3
Feb 06 18:51:38 <Barlow> i like stable. so i got squeeze today :)
Feb 06 18:51:57 <kerio> hehe
Feb 06 18:52:01 <kerio> is it officially stable now?
Feb 06 18:52:26 <kerio> damn, i have to move from squeeze to testing now
Feb 06 18:52:49 <kerio> who the hell is wheezy
Feb 06 19:04:29 <Barlow> kerio: google image search suggests a penguin
Feb 06 19:08:15 <dmb> kerio: testing is pretty much identicle to stable
Feb 06 19:08:18 <dmb> wonder if they unfroze it
Feb 06 19:08:30 <dmb> i don't like stable
Feb 06 19:08:30 <dmb> :P
Feb 06 19:10:38 <dmb> have any of you put openwrt on your device?
Feb 06 19:10:59 <UnaClocker> Meh, openwrt is for devices with jack for ram and jack for flash. I put full on Debian on mine.
Feb 06 19:11:06 <dmb> that is true
Feb 06 19:11:25 <dmb> UnaClocker: was looking for a nice router-configuration screen, because I do not have time to do it manually
Feb 06 19:11:32 <dmb> you know one for debian ?
Feb 06 19:12:04 <UnaClocker> ShoreWall, that's what I use. I don't recall it having an actual config screen that you can web into, but I do recall it being butt simple to setup.
Feb 06 19:14:07 <dmb> UnaClocker: what a really want is device to act like a wireless client, and every device that gets connected throught he port gets an ip from the built in dhcp server, and is routable
Feb 06 19:14:14 <dmb> i can handle the dhcp server part
Feb 06 19:14:18 <dmb> and probably wifi client
Feb 06 19:14:24 <dmb> not sure how to handle routing
Feb 06 19:19:55 <kerio> google for "linux nat howto"
Feb 06 19:19:56 <kerio> :)
Feb 06 19:20:05 <UnaClocker> Shorewall handled all the routing for me..
Feb 06 19:20:16 <UnaClocker> That's why I installed it, I couldn't wrap my head around the routing as well.
Feb 06 19:20:36 <kerio> just configure iptables and enable the forwarding
Feb 06 19:28:48 <Tootoot222> routing is literally 4 lines in iptables
Feb 06 19:28:53 <Tootoot222> +1 for every port forward you want to do
Feb 06 19:29:27 <Tootoot222> where eth0 is the internet facing device, and eth1 is the lan facing device:
Feb 06 19:29:56 <Tootoot222> iptables -A INPUT -i lo -j ACCEPT
Feb 06 19:29:57 <Tootoot222> iptables -A INPUT -i eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT
Feb 06 19:30:03 <Tootoot222> iptables -A INPUT -i eth1 -j ACCEPT
Feb 06 19:30:20 <Tootoot222> iptables -A POSTROUTING -o eth0 -j MASQUERADE
Feb 06 19:30:41 <Tootoot222> viola, you are now using NAT to masquerade all packets from eth1 to eth0
Feb 06 19:30:53 <kerio> he wants nat tho
Feb 06 19:31:00 <Tootoot222> that is NAT
Feb 06 19:31:06 <kerio> shouldn't you add something more to the last rule
Feb 06 19:31:16 <kerio> there *was* something iirc
Feb 06 19:31:30 <Tootoot222> oh i missed 3 other rules
Feb 06 19:31:34 <Tootoot222> -A FORWARD -d 192.168.0.0/16 -i eth1 -j DROP
Feb 06 19:31:34 <Tootoot222> -A FORWARD -s 192.168.0.0/16 -i eth1 -j ACCEPT
Feb 06 19:31:34 <Tootoot222> -A FORWARD -d 192.168.0.0/16 -i eth0 -j ACCEPT
Feb 06 19:31:41 <Tootoot222> so 7 lines
Feb 06 19:32:15 <Tootoot222> you'll probably want to set iptables -P INPUT DROP
Feb 06 19:32:16 <Tootoot222> too
Feb 06 19:32:29 <kerio> now that feels like too much :<
Feb 06 19:32:40 <kerio> i really never understood anything but -A INPUT, so...
Feb 06 19:32:49 <Tootoot222> drop all from the internet? that's the only sane thing to do
Feb 06 19:33:01 <Tootoot222> if you don't drop all you'll have all the services running on your plug exposed to the internet
Feb 06 19:33:04 <kerio> no, i mean, the whole thing
Feb 06 19:33:12 <kerio> also i have no firewall at the moment on my sheevaplug
Feb 06 19:33:15 <Tootoot222> well what would you  rather have lol
Feb 06 19:33:21 <Tootoot222> iptables *is* a firewall
Feb 06 19:33:33 <Tootoot222> that drop all rule, is the most basic firewall
Feb 06 19:33:45 <Tootoot222> you can use
Feb 06 19:33:46 <Tootoot222> -A INPUT -i eth0 -p tcp -m tcp --dport 22 -j ACCEPT
Feb 06 19:33:48 <kerio> i meant the 3 forwarding rules to drop everything
Feb 06 19:34:02 <kerio> i know, i *did* configure iptables multiple times on various desktops
Feb 07 00:16:48 <mdm2k> dmb: I guess it's possible that the factory rootfs differs from the one you can download, if one was updated without updating the other or something
Feb 07 00:16:57 <mdm2k> I haven't tried rewriting the rootfs though
**** ENDING LOGGING AT Mon Feb 07 02:59:56 2011